So first lets determine what kind of scripted logon process you want to use..

As far as best practices there are only two types I would try to implement, dos batch files or VBScripts. The later being my preference.

• Decide the scope of your needs.
  1. You need to map static drives and that's it.
  2. You need to map drives based on group membership.
  3. You need "choice 2" and to collect info on your networked PC's.
• Understand your environment
  • What operating systems do you have to support ?(I am only focusing on windows environments here)
  • What OS versions?
  • How will remote users connect and run the logon script?
• Choose your method
  • If you chose "#1" then you can get by with a dos batch file in the "netlogon" share.

  NOTE: if you need to only map one drive then use ADUC (Active Directory Users and Computers). For this method go the "Single Drive Mapping Method".

If you chose "#2"

• You can get buy with a dos batch file and the MS program "Ifmember.exe" (a resource kit utility) placed in the Netlogon share of a domain controller.
• Although this method works it is slower and clumsier than a VBScript deployed by GPO.

NOTE: if you need to support older systems like NT 4.0, Windows 95, etc, then the batch file method is your best choice. You can find an excellent article on implementing this at the Microsoft TechNet site. The link is here.

If you chose "#3"

• Then definitely you will want to use the VBScript and GPO method. I outline this in detail here.
• This option is best if you don't need to support older legacy systems. It gives you great flexibility in what you can accomplish.

Donations

I spend a lot of late nights building this site up and if it helps you or makes your job a little easier please think about making a donation to support it. Remember any donation small or large, 50 cents to 50 dollars is greatly appreciated.