Started our network in Windows 2003 w/ Windows 2000 and XP, at the time, a simple .vbs login script worked great w/ setting it the profiles of the user in AD Users and Computers. Over the years, we added Server 2008, Windows 7 and now 8.1 into the environment and it seems that the newer system doesn't work well w/ the script. It will run at times, and sometime, staff will report that none of the network drives are mapped, and at times, even a complete rebooting the machine doesn't trigger the login script. My questions are:
1. Why isn't the script "firing" correctly for all users / computers? (most users have the same security access)
2. Is there a better option to map drives? I know using GP is an option, however, a lot of our users need specific mapped drives which makes it difficult to set an "universal" policy.
3. Is there a way to make the mapping process visible so I can see exactly what the script is doing when mapping the drives?
Thanks in advance.
Roget Luo