1 Reply Latest reply on Mar 25, 2010 2:41 AM by LMichel

    provisioning issue w/ multiple adapters in SCCM

    markcedwards

      I have an issue where the VMWare adapaters that are installed by default (and enabled) are preventing SCCM from properly performing an OOB Discover Management Controllers sequence.  It appears that the process will only use the last registered IP Address for the System Resource, rather than progressing through each IP address registered in the SCCM database. anyone else seen this?  We're just beginning to deploy, so I haven't really rolled this out to many PCs.  I'm wondering if the same thing will happen to our laptops that register their wireless IP (and then disconnect from the wireless into a docking station).... SCCM 2007 SP2 R2 Provisioning is otherwise working IPAddresses[0] - x.x.x.x (our real network) IPAddresses[1] - 192.168.139.1 (vmware network adapter) IPAddresses[2] - 192.168.233.1 (vmware network adapter) CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 192.168.233.1:16992. SMS_AMT_OPERATION_MANAGER 3/2/2010 9:43:57 AM 32800 (0x8020) AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 3/2/2010 9:44:16 AM 41092 (0xA084) AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 3/2/2010 9:44:16 AM 41092 (0xA084) CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 192.168.233.1:16993. SMS_AMT_OPERATION_MANAGER 3/2/2010 9:44:18 AM 32800 (0x8020) CAMTDiscoveryWSMan::DoIcmpPingForAMTDevice - failed to recieve reply from 192.168.233.1 SMS_AMT_OPERATION_MANAGER 3/2/2010 9:44:18 AM 32800 (0x8020) Error: CSMSAMTDiscoveryTask::Execute, discovery to (192.168.233.1-ODT0045446)failed SMS_AMT_OPERATION_MANAGER 3/2/2010 9:44:18 AM 32800 (0x8020) Auto-worker Thread Pool: Error, Can not execute the task successfully after try it 3 times. Remove it from task list. SMS_AMT_OPERATION_MANAGER 3/2/2010 9:44:18 AM 32800 (0x8020)