Hi all,

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

Read http://communities.intel.com/docs/DOC-1247#Virtual_adapters_may_cause_network_discovery_to_fail
from Intel VPro forum, that it is a known issue with SCCM - When discovering vPro systems via a console that has a virtual adapter enabled with an IP address assigned, such as Microsoft SCCM, the discovery process may fail if the virtual adapter IP address is used for the discovery process.

I tried stopping VMnet DHCP & VMware NAT service on computer, no success.
But when I rebuild the machine without VMware installed, no problem provisioning the units!!

Questions:

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

So did you ever find a solution to the VMnetAdapter isseu?

Strange that SCCM does not do a dns lookup but uses the info in his database what if the IPnumber is changed?

We have the same isseu

VMnetAdapter nics on a pc with Ipenabeld.

Hello,

I've the same Issue.

Was this problem solved ?

Sincerely,

Yes, I know this is an old post, but Im trying to clean them up.

Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.