-
Titel
How to troubleshoot drive mappings -
Beschreibung
How to troubleshoot drive mappings.
-
Lösung
Drive mappings are performed by Kace Desktop Authority (KDA) utilizing the KiXtart USE command which uses the same Windows API as the Microsoft NET USE command. The drive mappings performed by the script are executed in the security context of the logged-on user. If the drive cannot be successfully mapped manually by the user, then the script is not going to be able to successfully automate the mapping. Likewise, if the drive can be successfully manually mapped by the user, then the script should be able to automate it. All return codes listed in the SLTrace.htm file, including those returned for drive mapping elements, are standard Microsoft return codes. For instance, a return code of 0 always means that the command is completed successfully and a return code of 5 always means that access is denied.
The most common reason why a drive mapping may fail is that the user does not have the necessary permissions to access the target share being mapped to. The shared folder that is being specified as the target must be shared properly at both the share level permissions and security (NTFS) permissions to allow the user to access it. The user must have at least read access to the share level permissions and the security permissions of the share to access it and map a drive letter to it.
Since drive mappings are performed in the security context of the logged-on user, the easiest method to determine why a drive will not map is to copy the UNC out of the trace file and click on Start | Run and paste the UNC (\\Server\Share) on the run line and then press enter. If that action is successful, and the user can access the destination folder, then permissions are clearly not the problem.
The actual drive letter being specified to map to could also be the source of the problem. If the test above is completed successfully, then perhaps the drive letter being used is the problem. Therefore, the next test is to drop to a command prompt and see if the drive letter is being used by typing NET USE and then pressing the enter key. If the drive letter is not being used, then attempt to map the drive utilizing the NET USE command. The syntax is NET USE X: \\Server\Share.