During automation boot, a computer will receive the error "Invalid drive specification. Cannot map drive."
This error can be caused by a number of issues:
NTLM authentication setting are found in the following Group Policy:
Domain Security Settings > Security Settings > Local Policies > Security Options >
Network security: LAN Manager authentication level.
The following two policies are disabled:
Windows Settings / Security Settings / Local Policies / Security Options
* Microsoft Network Server: Digitally sign communications (always)
* Microsoft Network Server: Digitally sign communications (if client agrees)\
6. The drive letter "F" is already in use by the device
DOS and Linux automation cannot be used when NTLM is disabled. WinPE is the only automation environment that will authenticate with this network restriction.
If the drive letter "F" is already in use (this is common when using WinPE automation), it will be necessary to change the drive letter that maps to the express share, to something higher. Also be aware that any other drive mappings done in automation (such as to image store locations) also need to be mapped to drives that will not have conflicts. i.e. "M", "N", "O", etc. [Note: Do not map drives to the letters "X", "Y" or "Z" since these can be used by the automation as RAM drives.]
Applies To
Deployment Solution all versions