Soldato
- Joined
- 15 Mar 2010
- Posts
- 11,523
- Location
- Bucks
My home server (Win12R2) is set to send a login script to users that connect via a domain allocated username through other network based machines. Its pretty standard stuff.
The script flushes the network drives on that users machine, then reinstates them followed by running a small test file which is then deleted on each of the drives to ensure they have spoiled up correctly.
The script works fine, and does exactly what it is meant to do. It is in place to avoid the annoying 'windows can not connect to network drives' error message on boot.
However when a domain user logs in I sometimes have occurrences where the script is not run at all.
Does anyone know why this would happen and are there any good ways of checking to see if the server is even attempting to issue the script on the occasions it doesn't work?
ie. would this likely be a server or client side issue?
The script flushes the network drives on that users machine, then reinstates them followed by running a small test file which is then deleted on each of the drives to ensure they have spoiled up correctly.
The script works fine, and does exactly what it is meant to do. It is in place to avoid the annoying 'windows can not connect to network drives' error message on boot.
However when a domain user logs in I sometimes have occurrences where the script is not run at all.
Does anyone know why this would happen and are there any good ways of checking to see if the server is even attempting to issue the script on the occasions it doesn't work?
ie. would this likely be a server or client side issue?
Last edited: