Problem / Solution: Provisioning Error "Could Not Map or unmap drive. Error code: 2250" in maptopreferredhanlder.log

Error message:

Could not map or unmap drive. Error code: 2250

Problem:

In X:\Ldprosivion or C:\Ldprovision folder, you open the file MaptoPreferredHandler.log and read the following;;

2015-09-01 23:28:46(520-1624) maptopreferredhandler.exe:******Mapping to: \\core95sp3.sebdomain.local\PRC_Landesk_Files\Images\LatestWin7\LatestWin7.TBI

2015-09-01 23:28:46(520-1624) maptopreferredhandler.exe:Drive letter = e

2015-09-01 23:28:46(520-1624) maptopreferredhandler.exe:Mode - Attempt preferred server.

2015-09-01 23:28:47(520-1624) maptopreferredhandler.exe:Could not get credentials for preferred server.

2015-09-01 23:28:47(520-1624) maptopreferredhandler.exe:End of Map Drive.  Path used: - \\core95sp3.sebdomain.local\PRC_Landesk_Files\Images\LatestWin7\LatestWin7.TBI.

2015-09-01 23:28:47(1448-1452) maptopreferredhandler.exe:******UnMapping Drive

2015-09-01 23:28:47(1448-1452) maptopreferredhandler.exe:Drive letter = e

2015-09-01 23:28:47(1448-1452) maptopreferredhandler.exe:Could not map or unmap drive. Error code: 2250

2015-09-01 23:28:47(1448-1452) maptopreferredhandler.exe:End of UnMap Drive.

Cause:

There is a big chance that there is an authentication issue when trying to map to the server "Core95sp3.sebdomain.local"..

Solution / Workaround:

To solve it, you need to be sure that the preferred server exists with the same "Server name" than the one mentioned in your UNC path; In our example; core95sp3.sebdomain.local and if that's core95sp3, it may not work. To do it, follow these steps;

1. - On the LDMS Console,go in Menu Configure > Preferred Server > A window "Preferred Server Properties" opens
2. - On the "Configuration" tab,
   1. Enter the server name core95sp3.sebdomain.local
   2. Enter the User name having some READ rights on the share drive when you stored your file
   3. Enter the password twice
   4. Press on button "Test Credentials" > A "TestCrentials" window opens
      1. Leave the box UNC checked
      2. Click OK > A "Test Credentials" window opens
         1. If that's "UNC Authentication successful", then you are ready to go
         2. If that's "UNC Authentication failed", then it could be due to some different issues;
            1. Be sure that you defined well the UserName and Password
               
            2. Be sure, that you can access to the UNC path with this credentials defined via a CMD
            3. Close all the current LDMS consoles opened and restart the Console on the Core Server to do another TestCredentials test
            4. On the Core Server, do a test net use * /d /y because the server has a remembered connection to the target device under a specific set of credentials and will not allow multiple connections to be created with different credentials
            5. Close all the Window Explorer windows and try again
               
            6. Check if there isn't any mapped drive on the computer where you are doing the TestCredential test and try to disconnect the one corresponding the server name
            7. Create a specific account to have access to this share and do the TestCredential
   5. If still not working after a test, yyou may also have an issue with the boot.wim deployed on the PXE Server, and in that case;
      1. Follow the instructions given in article https://community.landesk.com/support/docs/DOC-26968
      2. Check as well in the boot.wim (BIOS) or boot_x64.wim (UEFI) when there are mounted (As explained in the article above), if the certificate (File with an .0 extension) is existing on the folder "c:\program files (x86)\LANDesk\Shared Files\cbaroot\certs" and if that's the correct one (You can check it by comparing the name of it with the one on the Core Server in \\<CORESERVERNAME>\ldlogon shared folder. If that's not the one, copy the .0 file from the ldlogon folder and paste it in the boot.wim mounted and proceed as followed in the article mentioned above to unmount the .wim then deploy again the PXE through the script.
         

Other interesting links:

Understanding UNC Authentication (Preferred Server)

How to troubleshoot Provisioning Template Action Handlers