Discussion on:

Why group policy and legacy login scripts may not matter anymore

How do you compare Novell 2.14 with a current release of Windows OS? Why not compare Novell 6.x with Windows 1.0? Login scripts are not typically setup in user and group objects and no CNE would do it that way. I started w/ Novell 3.x and even then user and group login scripts were discouraged except for special conditions because of the high maintenance. Then w/ Novell 4.x and NDS you can easily limit scripts to the container except for special situations. We have had the same basic loginscript for 8 years with only minor changes when we upgrade servers or volumes. No need to look at it for even user adds and deletes. Novell Directory Services (NDS) is a very stable and mature product and Active Directory emulates it.

Good article, as a follow-up and to give more merit to your assertion that Login scripts are obsolete a comparison of login scripts vs mandatory profiles and group policies would be helpful.

I use logon scripts in a Server2000/ClientXPPro environment to map network drives that change from time to time. In your article you mentioned setting up mapped drives in a profile. Is this done in AD? How is this accomplished?
Thanks, Phil

I work with mix environments where the Security processes and Data storage are handled by Netware and applications are on a Microsoft platform. A system login script that handles the complete environment is a significant part of making a smoth operation. A single point of change for a group policy, or a users access is easy to manage.

Thanks
Wendell