profile bloat in W2k Pro

Although it means a little extra work, I use a local account. If I need to connect to a clients machine, then I give the required credentials via a net use command, or put the unc path into the run box and fill in the pop up box that appears. besides, to log into each clients domain would mean removing and adding your machine to each domain as needed, and thats gotta be a major pain. Remote control software (such as terminal services in admin mode, or VNC) requires that you put in the logon details when you open the session anyway.... Another point is that I don't want anyone nosing around in my machine, and if you are adding it to multiple domains - and not removing the domain admin group from the local admin group each time - then you are opening your machine up to anyone with a domain admin account !! Hope this gives you some food for thought...

It's easy enough if you install all your applications as the local administrator, then when you are happy copy this profile over the top of the default one. This will ensure that you keep all the custom settings you have etc.

It does take up moredisk space this way, but it doesn't matter where you login as you always get the same default profile, with all your applications configured. All you need to do is customise Printers etc for each profile dependent upon where you are working.

The only way to just have one profile is to always log in as a local user, everytime you want to connect to a system you will need to authenticate.

This question was closed by the author