Migrate SBS2003 to Server 2008 R2 or just cut over

[guest]

We are installing a replacement server (changing from Dell SC1420 to Dell T410). At the same time, we are converting from SBS 2003 to Server 2008 R2. We do not use Exchange or other advanced features that come with SBS. We really just use the server as a file server, with limited security implemented only through shares and not ACLs. We have only a dozen workstations, five fixed IP addresses for printers etc (workstations are dynamically assigned by DHCP). My question is: do I really need to use some migration strategy or can I just recreate accounts, DHCP settings, security groups, etc., on the new server then just pull the plug and put the new one in? What, specifically, will go wrong if I do that, and is it easier to fix those problems after the fact than go through a migration (which I have never done before). I can imagine that ownership of files might be a problem but since we don't care who does what to which file, will that really matter? All of our shares but one allow everyone full control. One share restricts one directory tree to access by one security group. Will any problems be created on the workstations, or will they just be on the server? I'm thinking of just trying this with one workstation in the next day or so and see what goes wrong. What should I look for? Thanks!

[guest]

I think in this situation, the bigger question may be your workstation PCs. If you create a new Forest\Domain with new users, you will have to join the workstations to the new domain and perform a user state migration from the old profile to the new. If you have complicated workstation configurations, that may end up being the bigger headache.

So, if you want to save the extra work on the workstation end, then you should migrate your domain to the new server.

You'll have to migrate data and recreate ACLs & shares no matter if you move to a new server in the same domain or a another.

You will have to ensure that you do a graceful removal of the SBS system. Otherwise you may have issues if you decided to impliment Exchange 2010 in the future, or you'll receive AD replication errors.

[guest]

According to your description, I realize that you only have twelve clients, five printers, one Windows Server 2008 R2 domain controller and one Small Business Server 2003. It is real a small business.



It depends on you. If there are not too many settings in SBS 2003 need to be retained, you may consider to perform a Clean Install and recreate everything, then everything is new. But much more time is required.



If you want to retain the settings and save time, you may just add Windows Server 2008 R2 DC in this SBS 2003 domain, move FSMO roles to the new DC and install DNS Server on it. You will have 21 days to remove the SBS Server.

[guest]

If you don't use exchange or any other SBS utillities, doing a migration would not be that hard and big plus would be you keep the Domain structure and all user and client pc settings are kept you do not have to remove all clients from the existing domain and connect to the new domain. Also User profiles are kept the same so no manual user creation and profile migration.

If you follow this guide: http://demazter.wordpress.com/2010/04/2 ... s-2008-r2/ you will got all steps you need to do together. Because it is a step based guide, just skip the steps that are not applicable for your situation.


--------------------------------------------------------------------------------