Well, you reference the login script in AD with a Group Policy. That is
tied to the loopback processing for the machine(s). I have my login script
on a readable share on the server for the lab, since if the file server is
not available, the users will not get far on the machines. The staff login
script does not have to get things from the server, so that script
actually lives in AD. I am not roaming profiles - just setting network
drives and configuring network printer queues.
The best thing about using a script is that you can do some on-the-fly
configuration if, for example, a printer is unavailable. I use it to put
up Message of the Day notices (once per update), weekly code of conduct
notice, disk quota usage, and current printer usage. Separate scripts have
the advantage that they are easy to switch around without needing to edit
GPOs.
I can point you to the relevant GPOs in AD and my scripts if you like. I
have no shame 8-)
Graham
-- Graham Patterson Windows System Administrator Dept of Economics, UC Berkeley. 510-643-5397 ------------------------------------------------------------------------ The following was automatically added to this message by the list server: For information about Micronet, including subscribing to or unsubscribing from its mailing list and finding out about upcoming meetings, please visit the Micronet Web site: <http://micronet.berkeley.edu/>.Received on Mon Dec 11 2006 - 21:31:20 PST
This archive was generated by hypermail 2.2.0 : Mon Dec 11 2006 - 21:31:20 PST