Fix for ‘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

There have been reports of a problem when running Refresh, Replace, Sysprep and Capture, and Custom task sequences with MDT 2010.  When running those scenarios an error message is displayed after completing the wizard that states “A connection to the distribution share could not be made”.  When looking at the log files the error states: ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.”

This problem seems to occur most often when logged onto the client machine as one user and entering different credentials into the deployment wizard or customsettings.ini.

We have developed a fix for this problem.  To fix the problem you should edit the ztiutility.vbs file in the deployment share under the scripts folder.  Open the file in notepad and replace the following code in the MapNetworkDriveEX function:

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

We thank you very much for your feedback and assistance in helping us fix this problem.  We are currently working on a KB article that decribes these steps and will update once that KB article is available