1 Reply Latest reply on Jun 28, 2010 6:37 PM by Dan_O

    Provision issue on VMware client units

    CallMeBruce

      Provision failed on VMware client installed units, when sent a Discover Management Controllers from SCCM console, amtopmgr.log shows:

      CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 192.168.89.1:16992.
      CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 192.168.89.1:16993.
      CAMTDiscoveryWSMan::DoIcmpPingForAMTDevice - failed to recieve reply from 192.168.89.1
      Error: CSMSAMTDiscoveryTask::Execute, discovery to (192.168.89.1-C686375)failed

       

      Noticed this is the "VMware" ip address[3] from this unit SCCM properties.

      Also read, http://communities.intel.com/docs/DOC-1247#Virtual_adapters_may_cause_network_discovery_to_fail

      I tried stopping VMnet DHCP & VMware NAT service on computer, but no success.

      But when I rebuild the machine without VMware installed, no problem provisioning the units!!

       

      Question:

      Is removing the "VMware" ip address[] from SCCM will prevent provision the wrong ip?

      If so, how should i go about to do that?

      And how long does it take to update SCCM database?

       

      Thanks for your help!

      Dennis