The D-Spot (The Deployment Spot)

Suddenly my deployment environment had issues connecting to the deployment share while performing a MDT 2010 LTI Refresh scenario.

Log files BDD.log and LiteTouch.log says this: Unable to connect to DeploymentShare Connection OK Possible cause: invalid credentials A connection to the deployment share DeploymentShare could not be made The deployment will not proceed.

Error:

I found some solutions on the web, but only the last one did the trick for me.

Possible solution: Change ZTIUtility.vbs

Microsoft posted a solution for the ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed” problem with MDT 2010. By changing the script ZTIUtility.vbs.

Replace this code:

Case Else
' Case &h800704C3 ' Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.
' Case &h8007052E ' Logon failure: unknown user name or bad password.
' There was a some kind of fatal error.
If ErrDesc <> "" then
             MapNetworkDriveEx = ErrDesc
Else
             MapNetworkDriveEx = "Unable to map UNC Path " & sShare & " :" & "( 0x" & hex(HasError) & " ) "
End if
oLogging.CreateEntry MapNetworkDriveEx & "", iLogType
Exit function
End select

With this code:

Case Else
Err.Clear
On Error Resume Next
oNetwork.MapNetworkDrive  chr(sDrive)&":", sShare, False
HasError = err.number
ErrDesc = err.Description
On Error Goto 0
If Err.Number <> 0 Then
' There was a some kind of fatal error.
             If ErrDesc <> "" then
                                        MapNetworkDriveEx = ErrDesc
             Else
                                        MapNetworkDriveEx = "Unable to map UNC Path " & sShare & " :" & "( 0x" & hex(HasError) & " ) "
             End if
             oLogging.CreateEntry MapNetworkDriveEx & "", iLogType
                           Exit function
Else
      Exit Function
End If
End select

However, this didn’t solved my issue at all.  I tried some other possible fixes found on the wild wild web; like using the pushd-command, using the IP address and FQDN name, and disconnecting all network connections (with net use * /d) before the actual installation begins. But none of this actually solved my issue.

The solution was map a network drive to the deployment share, with the same credentials as these used in bootstrap.ini and launching Litetouch.vbs from there. I found the solution on the Minasi forum (post by Johan Arwidmark).