Microsoft Deployment Toolkit Team Blog

Official blog for the MDT engineering team

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

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

  • Comments 9
  • Likes

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

Comments
  • I encountered this issue and I found that it was caused by the local workstation credential trying to authenticate against the the network sharepoint with the same password.

    For example, if I have

    \\VS1\Deployment$ as a MDT 2010 sharepoint

    and VS1 (Win2008)'s local administrator's password is set to P@ssw0rd.

    When I installed W7 workstation by using MDT and login as W7's administrator with the password as P@ssw0rd (the same as VS1), Sysprep and Capture script can be initially accessed and launched from \\VS1\Deployment$ as W7\administrator (not VS1\administrator) then the ztiutility.vbs try to properly authenticate with VS1 by using VS1\administrator.

    Workarounds:

    1. Simply, change your W7\Administrator's password to something else like 1111, reboot and try again.

    2. or, provide your current user's credential (Domain should be W7 instead of VS1)

    Please update the script to avoid this issue...

    Thanks,

  • Still does not work

  • I found that if I gave full control of the share to the Users group, I was able to make things work.  I used //IP/share method to access the vbs script and the server name for the second part.

  • Just use full domain name or full computer name.

    Example: \\VS1.domain.org\Deployment$ OR \\VS1.computername\Deployment$

  • Thanks a lot newman, that worked for me

  • Thanks Newman. Using the full path worked.

  • I know there has been some time passed but I ran into this as well. after trying all the suggestions, I found that I will get the errors if I DON'T use DHCP addressing?????? once I set the box to DHCP, all runs fine....

    The info is good..

  • editing script didnt help me and am using MDT 2012(in testing phase.

    my problem was that i had local admin named "administrator" and that was also name of admin on my test domain and they had same passwords. After changing local password, i had no more issues.

  • I executed as YPAE said which is

    "I encountered this issue and I found that it was caused by the local workstation credential trying to authenticate against the the network sharepoint with the same password.

    For example, if I have

    \\VS1\Deployment$ as a MDT 2010 sharepoint

    and VS1 (Win2008)'s local administrator's password is set to P@ssw0rd.

    When I installed W7 workstation by using MDT and login as W7's administrator with the password as P@ssw0rd (the same as VS1), Sysprep and Capture script can be initially accessed and launched from \\VS1\Deployment$ as W7\administrator (not VS1\administrator) then the ztiutility.vbs try to properly authenticate with VS1 by using VS1\administrator.

    Workarounds:

    1. Simply, change your W7\Administrator's password to something else like 1111, reboot and try again.

    2. or, provide your current user's credential (Domain should be W7 instead of VS1)

    Please update the script to avoid this issue...

    Thanks,

    "

    I just changed the name from the remote computer that have MDT2010 to the local computer that I want to capture, and till now everything is fine.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment