Exchange migration from users in workgroup
I've got sketchy info right now guys, but here is the bottom line.
i've got a company with about 5 workgroups (for sake of discussion, call them W1, W2, W3...)
They have an Exchange server setup (2003 on SBS), so obviously they have an AD domain (call it company.local)
From what I'm being told, these users in the various workgroups all are using Exchange. I've never seen a setup where workgroup users are using exchange, so I guess that is my first question, is that even possible? Never seen it done that way.
Here is the plan. We are going to install a few more servers to implement an AD structure, with a new Exchange server (SBS is old and needs to be replaced). So from a migrating policy, I should be able to just add those new servers to the company.local domain, install exchange via MS documentation, move mailboxes to new exchange box, decommission SBS with exchange, right?
Just wanted to get more input on this. I understand that I will need to copy users profiles when I join them to the domain. Thanks in advance for any replies.
i've got a company with about 5 workgroups (for sake of discussion, call them W1, W2, W3...)
They have an Exchange server setup (2003 on SBS), so obviously they have an AD domain (call it company.local)
From what I'm being told, these users in the various workgroups all are using Exchange. I've never seen a setup where workgroup users are using exchange, so I guess that is my first question, is that even possible? Never seen it done that way.
Here is the plan. We are going to install a few more servers to implement an AD structure, with a new Exchange server (SBS is old and needs to be replaced). So from a migrating policy, I should be able to just add those new servers to the company.local domain, install exchange via MS documentation, move mailboxes to new exchange box, decommission SBS with exchange, right?
Just wanted to get more input on this. I understand that I will need to copy users profiles when I join them to the domain. Thanks in advance for any replies.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The only reason that I mentioned hanging on to the SBS server is so that you can use the network connection wizard. It does all the work for you when moving from a workgroup to a domain, including all the permission changes. You can set the machines off and leave it to get on with it.
The network connection wizard is available through the web site on the server... http://servername/ if I recall correctly it is on the home page.
Once you have all the machines connected to the domain then you can start to undo things. In fact, there would be nothing to stop you from starting to introduce the additional servers at any point, just use the SBS machine to manage the migration of the user profiles from the workgroup to the domain.
Simon.
The network connection wizard is available through the web site on the server... http://servername/ if I recall correctly it is on the home page.
Once you have all the machines connected to the domain then you can start to undo things. In fact, there would be nothing to stop you from starting to introduce the additional servers at any point, just use the SBS machine to manage the migration of the user profiles from the workgroup to the domain.
Simon.
ASKER
Nice. Appreciate it.
ASKER
We eventually want to move away from SBS server (as mentioned, on a dreadfully unreliable box). Do you think it is still wise to use the Network Connection wizard that would convert workgroup profile to a domain profile, and then just implement the new AD servers and phase out the SBS?
Also, anyone have a link to anything on the Network Connection wizard, having a bit of a problem tracking down a link or something helpful.
Thanks for the help, Simon. Much appreciated.