eglescout
asked on
SBS 2011 upgrade from SBS 2003
I have tried migrating our data from a SBS 2003 machine to a new server (SBS2011 Standard) several times without success. I have been using Microsoft's built-in migration tool.
SBS2003 machine has some issues. Sharepoint is not behaving well, and the companyweb site doesn't work. Even so, the Microsoft BP Analyzer thought the server was working well.
Some more stats:
I do want SharePoint functioning on the new server. That's part of the reason for the upgrade.
What would be the best way to get the data, AD, Exchange, etc. over on the new server?
Thanks!
BTW, if you want to see the migration logs, they're below. It's a DCpromo issue.
SBSSetup.log
dcpromoui.log
SBS2003 machine has some issues. Sharepoint is not behaving well, and the companyweb site doesn't work. Even so, the Microsoft BP Analyzer thought the server was working well.
Some more stats:
6-7 human users
Exchange is being used
Home directories (My Documents of users) are being stored on the server
I do want SharePoint functioning on the new server. That's part of the reason for the upgrade.
What would be the best way to get the data, AD, Exchange, etc. over on the new server?
Thanks!
BTW, if you want to see the migration logs, they're below. It's a DCpromo issue.
SBSSetup.log
dcpromoui.log
ASKER
I'm glad it worked for you. My main concern is Exchange. The rest is pretty easy to duplicate. We have some users that use Outlook on multiple machines.
Does Exchange pick up folders when you restore a .pst back into Outlook? Then I'd jump on this.
Does Exchange pick up folders when you restore a .pst back into Outlook? Then I'd jump on this.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
From the logs, my first guess is that you have. DNS issue. This is something the BPA cannot always test for or pick up. It is important to ensure the 2011 server is using the ok'd SBS server and ONLY the old SBS server for DNS during install.
-Cliff
-Cliff
ASKER
I ended up doing a clean install importing the Outlook data from PST files. I also had grabbed user files from each account before the switch. It worked alright. I did change the local domain because I was worried that some unknown settings would linger in the client computers if I stuck with the same domain. That caused some extra headaches.
The big question from this experience is this: will client computers behave well if the new server / domain controller (SBS 2011) uses the same local domain as the old server / domain controller (SBS 2003)? (The old server would be shut down before the new one would be brought online.)
The big question from this experience is this: will client computers behave well if the new server / domain controller (SBS 2011) uses the same local domain as the old server / domain controller (SBS 2003)? (The old server would be shut down before the new one would be brought online.)
Client computers will still see the new server as belonging to a new domain. You will need to disjoin the client PCs from the old domain and join them to the new one.
With both machines having the same domain name, DNS issues are likely to abound if you don't properly ensure all roles (DHCP/DNS) are *only* on the new server.
-Cliff
With both machines having the same domain name, DNS issues are likely to abound if you don't properly ensure all roles (DHCP/DNS) are *only* on the new server.
-Cliff
ASKER
Thanks Cliff. I feel better about just creating a new domain. It was a bit of work, but the dust has mostly settled.
You could consider using the Swing Migration technique. I have successfully migrated from SBS2003 to SBS2008 and from SBS2003 to SBS2011 offline with a great deal less pain than the direct Microsoft method which I tried first. You can obtain excellent additional support if you need it.
try here http://www.sbsmigration.com/
try here http://www.sbsmigration.com/
Good luck!