5 Replies Latest reply on Jun 21, 2010 8:01 PM by jasonhe40

    Problem getting a connection to vPro system

      Hi,

       

      I'm running a vPro compatible system consisting of an Intel DQ57TM mainboard and an i5 660 cpu. At the moment there is no harddisc attached, but in my opinion this should be no problem.

      I tried to configure the system as described here: http://communities.intel.com/docs/DOC-4795

      When it comes to section 5 and I execute the kvm.hta on my laptop, I get the following message at step 2:

       

      http://img59.imageshack.us/img59/5345/wsmanfault.jpg

       

      I think this is the problem why I can not connect to the client using vnc viewer. By the way I am able to access the clients web interface with the following link: http://192.168.1.55:16992/index.htm, but logging in is also impossible.

       

      Do you have any hints how to solve the problem?

       

      Thanks a lot.

        • 1. Re: Problem getting a connection to vPro system
          jasonhe40

          I can't download the jpg file for view, but some tips:

          1. Make sure the WinRM is correct configured

          2. Please remember setting the RFB password correctly, especially for the password definition.

          3. If you still have problem, please contact you local Intel Customer Support to get help.

           

          Thanks

          Jason

          • 2. Re: Problem getting a connection to vPro system

            For the console PC, is there Windows XP Professional required or is XP Home also fine? Maybe this is my problem.

            • 3. Re: Problem getting a connection to vPro system
              jasonhe40

              Console system requirements:

              System Requirements

               

              • Supported Operating Systems: Windows Server 2003 Service Pack 2; Windows Server 2003 Service Pack 2 x64 Edition; Windows XP; Windows XP 64-bit

              Standard hardware configuration that runs Windows 2003 Server and Windows XP and the following:
              • Windows XP requires Windows XP Service Pack 2 installed, refer to KB322389
              • Windows Server 2003 requires Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed, refer to KB889100
              • Windows Remote Management requires hotfixes in KBs 898708 and 899900
              • Creating an entry in the certificate mapping table for a user account that is a

              member of the Administrators group require a hotfix obtaining by contacting Microsoft Customer Support Services.



              My console system is installed Windows Xp Professional SP3.

              • 4. Re: Problem getting a connection to vPro system

                I tried another PC with Windows Server 2003 and got the same error when executing the KVMon.bat file as described in the first post. I don't know why you can't view the picture, I just klick the link and it pops up. The error message is:

                 

                <f:WSManFault Code="5" Machine="laptop666" xml:lang="de-DE" xmlns:F="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault">

                <f:Message>Zugriff verweigert </f:Message>

                </f:WSManFault>

                 

                Fehlernummer: -2147024891 0x80070005

                Zugriff verweigert

                WSManFault

                Message = Zugriff verweigert

                 

                Fehlernummer: -2147024891 0x80070005

                Zugriff verweigert

                • 5. Re: Problem getting a connection to vPro system
                  jasonhe40

                  I can't get the image file may be due to network connection limitation.

                  Again, my suggestion are:

                  1. Reinstall you console system with Windows XP Pro SP3 and download the WinRM, or install a new Win 7 system.

                  2. Another workaround is try to download latest AMT DTK from Intel website and in that DTK, there is another way to enable remote KVM.

                  http://software.intel.com/en-us/articles/download-the-latest-version-of-manageability-developer-tool-kit/

                   

                  I also had an issue that can't connect to client in my first time and after installing DTK and trying the way in DTK to enable remote KVM, I found my issue was the KVM connection password was not set correctly, it did not follow the password definition. Pls. noted, this is not the ME password, it's the password connecting to remote client when using WinRM.