SBS 2003 Log workstation onto domain but keep local user profile?

Question

Hello all,

I just installed a new server in our office with SBS 2003. I thought I would just use it as a file or standalone server since we only have 7 active workstations in the office and I thought Active Directory might be overkill.Then I found out that SBS won't let you do that, it only likes to be a domain controller (unless someone knows a hack to demote it) the problem/question is:

Everyone (as well as me) wants to keep their present desktops/user profiles including their fav email client, programs, desktop icons..ect. Is there a way to log onto the domain but not change ANYTHING on the workstations?

This would be so awesome if I could figure this out..

Thanks for the help!! :-)

Answer 1

Why not just copy the user profiles (the folders) to the server?

Answer 2

Evidence the previous users have never used SBS.

When you properly setup SBS it is VERY stable.  Further, when you PROPERLY connect computers to the SBS domain, using the http://YourSBSserverName/ConnectComputer link, the wizard will allow you to migrate your local profiles to the new user account domain profiles.

If you just right click my computer and add it to the domain, then you're not setting things up properly and are ASKING for trouble.  SBS works GREAT - if you use the wizards and set it up properly.  (This is why it's always a good idea to install it a few times to LEARN the processes it uses AND to hire a consultant if you don't care to learn it so that it gets done RIGHT.

Answer 3

This is a profiles issue. Windows allows you to have two basic kind of profiles, roaming and local. The profiles are stored on the PC (local) or on the server (roaming).

Roaming profiles allow a user to see the same desktop and program configuration on any machine on the domain. There can be issues with roamers: profiles can get very large, and even though only changes usually get propagated back to the server, if the user comes to a new machine, that first login could take a while.

In your case, I would use locals, especially if your users don't change machines at all or rarely.

Since you're running a domain (and having a domain and Active Directory is a good thing, trust me), your users have to authenticate off the server anyway. If they do log into a different machine (say, to show someone how to do a certain function or to help with administration), they'll just get a copy of the local default profile.

I would also suggest:

1. Link the user's My Documents folder to a folder on the server. They can then copy personal files into that directory, and they get saved on the server, which you should be backing up with extreme regularity. This way, if they lose an important file on thelr local machine, there's a copy on the server. You can do this with File Synchronization. Read up on it to see how it works. It's easy to set up and it's a nice feature.

2. Use the Distributed File System feature in Windows server to map common directories. You can give the directories long, easy names and map them all to one drive letter. I loved this when I used to manage Windows networks.

3. Backup. Backup. Backup. Backup. Backup. Backup.

4. Did I tell you to Backup?

Don't fear AD and domain controllers. Windows did it right when they introduced that into their servers with Windows 2000 server. I banged on NT boxes for years, and being able to remotely access nearly everything from my desk was a great improvement. make sure you install the full suite of Administrator Tools on your system so you can take advantage of all that stuff.