Moving logon scripts out of the domain controller netlogon share
We have a Win2k Active Directory domain that will be migrating to another Active Directory domain. In our existing domain, user logon scripts are in the netlogon share on the domain controllers and are pointed to in each user's profile. Because so may other domains are migrating, the new domain admins have decided that logon scripts will not be placed in the netlogon share of the domain controllers.
We have tried using the user profile and pointing to a logon script maintained on our server using an UNC, but it has not worked. We have also been looking at using group policies, but it appears we would have to break users into smaller units. For example the Users OU would have a Division OU under it, under that a Branch, OU and under that a Section OU. The users would be placed in the OU level under which they reside within the organization and the logon script would be defined as a group policy at each OU level. Isn't there an easier, more generic way to do this? We use XP, W2K and Win98 workstations.
I'm not a scripting guy by any means, but I'm pretty darned sure you can do the equivalent of an old command entitled "ifmember". That is, using VBS you can say: "If the user is a member of <group X> then, <do something>" That way, if you're leery in having such a deep OU structure, you can just have a logon script as I've described which does the work. However, it should be noted that Win98 workstations cannot apply Group Policy, and, hence, cannot benefit from newer-style Group Policy logon scripts (which support VBS.) In that case, see if you can find an old copy of the command "ifmember". It's in the LanManager resource kit. (Wow, I guess I'm showing my number of years in this business.) There are doubtless other ways to perform this feat, likely including KIXTART scripts, which, I also believe have an "if member" type of functionality.
Additional Expert Help:
Be sure to check our Answer FAQ for more expert advice.
For faster answers, visit ITKnowledge Exchange.
This was first published in November 2004