8 Replies Latest reply on Mar 3, 2009 7:52 AM by Trevor.Sullivan

    Error: Can NOT establish connection with target device - Provisioning attempt on SCCM 2007

    swood

       

      I recently discovered that our systems had some problems getting provisioned from SCCM because our machine names have underscores in them. We're working to change our naming scheme however we still are getting errors in our efforts to provision our Vpro systems. Here's a bit from our amtopmgr.log showing an attempt to provision

       

       

       

       

       

      Provision target is indicated with SMS resource id. (MachineId = 2734 10TH-85357.da.ocgov.com)

      Found valid basic machine property for machine id = 2734.

      Warning: Currently we don't support mutual auth. Change to TLS server auth mode.

      The provision mode for device 10TH-85357.da.ocgov.com is 1.

      Attempting to establish connection with target device using SOAP.

      Found matched certificate hash in current memory of provisioning certificate

      Create provisionHelper with (Hash: C2512FF7A3A558C88896C7EE51F152B15965C468)

      Set credential on provisionHelper...

      Try to use provisioning account to connect target machine 10TH-85357.da.ocgov.com...

      Fail to connect and get core version of machine 10TH-85357.da.ocgov.com using provisioning account #0.

      Fail to connect and get core version of machine 10TH-85357.da.ocgov.com using default factory account.

      Try to use provisioned account (random generated password) to connect target machine 10TH-85357.da.ocgov.com...

      Fail to connect and get core version of machine 10TH-85357.da.ocgov.com using provisioned account (random generated password).

      Error: Device internal error. Check Schannel, provision certificate, network configuration, device. (MachineId = 2734)

      Error: Can NOT establish connection with target device. (MachineId = 2734)

       

       

      I've done a full unprovision before  the attempt above and even hard-coded the provisioning account for good measure but still nothing.

       

       

       

       

       

      Has anyone run into this issue before?