Originally Posted By: Allen
Is this script defined in a GPO or as part of the user via the Logon Script?


Login script on AD records. Mapped via kix32 kixtart.kix /f

If we run the script from the file server via Batch file it does this:

 Originally Posted By: Batch File
C:
cd c:\temp
net use g: "[network drive\location\remote\]"
xcopy g:\kix32.exe c:\temp /Y
xcopy g:\kixtart.dll c:\temp /Y
xcopy g:\kixtart.kix c:\temp /Y
xcopy g:\mapdrives.kix c:\temp /Y
net use g: /delete
kix32.exe mapdrives.kix /f
timeout 5





 Originally Posted By: ShaneEP
There may also be a system check in the script that skips drive mappings if a server is detected. Would you mind copying an anonymized version of the script if it's not too large?


Its quite a large script in a couple of parts. Lot of company info in there so not easy to anonymize. Broken into Kixtart.kix which then calls mapdrives.kix



Looking at it based on these replies though I am wondering if it may be due to the script having two parts to it Kixtart.kix and mapdrives.kix - the batch drive explicitly calls mapdrives.kix.


The only part in kixtart.kix that references OS is this one which on looking is functionally useless:

 Originally Posted By: Kixtart.kix

;************************************************************************************
;* If the Operating System is not the current standard desktop, "Windows XP" *
;* do not run any login script commands. *
;************************************************************************************

if (INSTR(@ProductType, "Windows XP") = 0) AND (INSTR(@ProductType, "Windows 7")= 0)
Exit
ENDIF


There is also a reference to what image the devices are using that references W7 and XP - these are long deprecated and we don't use these.

 Originally Posted By: Kixtart.kix

$HKLMImageNo = ReadValue("HKEY_LOCAL_MACHINE\Software\[company]","ImageVersionNo")
IF (@ERROR = 0)
$HKLMImageNo = Left($HKLMImageNo,1)
ELSE
$HKLMImageNo = "0" ; PC is not a standard image or registry has been corrupt.
ENDIF

;************************************************************************************
;* Run common logon scripts for all machines, then run specific scripts for images *
;************************************************************************************

Call MapDrives.kix ; Maps drives for this user



But again, this is currently working fine for our users on desktop clients.

The Mapdrives file itself just maps drives based on AD membership and it is absolutely huge.

My initial thoughts were based on server OS and OU related issues - perhaps the way it process login scripts or SMB in server 2016.