1 reply
by fumitake
Not sure if I completely understand what it is you wish to do. But here comes the pitch. Roaming Profiles can be a tedious task to setup and maintain without something such as Systems Mangmt Server, which requires significant overhead.
Setting up local profiles on each individual machine is the alternate, obvious alternative. Setting up a local login script, generic for all users pointing to a common folder within the domain. Process all base configurations common to each user.
That script could then evaluate, comparing each user to the list of possible user groups and pass each client on to their more specific configuration and setup's respectively.
If it is the case that there will only be one user to one machine than the logonscripts can be stored locally. In the case that access is any user to any machine than each user will need to carry a, CD ROM, Zip Disk, flash RAM, containing user specific data, More technical than a roaming profile but does have various advantages.
Homogeneity from an administrative point generally minimizes errors and is quicker to untangle as the domain grows, optimizing time factors with regards to troubleshooting.
Regardless of the over all network plan, each user does need to have a home directory, if not on a central server than on respective desktop systems.
I think your solution can be found in a combination of logon scripts, profile manager, security manager, user groups, device management(NT4)
NT2K: uses "wmimgmt.msc" (Win Mngmt Infrastructure) as a central core combining linked hierarchy to the "MS Management Console" This is the tool that intertwines all the various systems, functions and devices within NT2K administration. In conjunction with the "ComponentServices Console" Manage, manipulate, or destroy anything within permitted virtual reach.
Caution: know what is happening before making too many changes in Component Services.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending