Upgrading from a Windows 2003 SBS Domain to a Windows 2003 Standard Domain.
I need to plan Upgrading from a Windows 2003 SBS Domain to a Windows 2003 Standard Domain. All the documention I can find on Technet and other Forums use the Transition Pack. I don't want to use the Transition Pack. I already setup a Windows 2003 Standard Domain Server and a Global Catalog of the Windows 2003 Small Business Server Active Directory. Can I just migrate the exchange mail users to a new Exchange 2003 or 2007 Server and migrate user home directories, also sharepoint which is another matter, then FDISK the SBS server and make it a Windows 2003 Standard Member Server for data storage.Any real experience and documentation is very needed ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When you have an SBS in a domain, the SBS must hold all the FSMO roles and there are various other restrictions, such as the 75 user limit. As I mentioned above, there are many different aspects of an SBS network which aren't standard in a 2003 Standard network. The transition pack allows you to get rid of these restrictions and migrate out to a normal network, although as I've already said I would be reinstalling the entire system and migrating information across to keep things clean, tidy and virtual error free.
-tigermatt
-tigermatt
ASKER
I have an open mind. Why can't I just use FSMO roles on the Windows 2003 Server that's a Global Catalog of the SBS Server?
Because your SBS licensing won't allow it. I've never actually tried to transfer the FSMO roles, but my guess is that it simply wouldn't let you do so. If it did, lots of other things in SBS, including Exchange, would stop working. I'm going to go with tigermatt on this one. I didn't understand from your OP that your Windows 2003 server was on the same domain as the SBS server. I thought you were saying that you had created a completely new domain when you installed your Windows 2003 server, separate from the SBS domain.
I've never trialled this method, so I can't advise as to what the results will be. SBS deliberately makes changes to Active Directory to make it an SBS setup. I'm sure if the SBS is immediately removed from the domain, then you won't have any issues with it not holding the FSMO roles, but that certainly isn't a recommended, and probably not supported, method of approaching this issue. The correct MS procedure would be to get the transition pack.
As I've already said, I expect there are ways around this which I am not aware of. I certainly wouldn't use it on my own systems and therefore won't advise such methods if I were to come across them.
I suggest you get the transition pack. Any issues you have will be supported in the SBS topic area here on EE. However, if you start playing around with the FSMO roles and moving things around that way and run into an issue, I doubt there will be many experts here on EE that will advise different from "Use the transition pack". Also, if you do run into an issue then realise you do need the transition pack but you have moved FSMO roles and other server roles around, the transition pack may not work correctly and you will have an awful set up to deal with.
If you wish to continue without the transition pack, do so at your own risk. It certainly isn't a recommended approach and other experts will advise similarly.
-tigermatt
As I've already said, I expect there are ways around this which I am not aware of. I certainly wouldn't use it on my own systems and therefore won't advise such methods if I were to come across them.
I suggest you get the transition pack. Any issues you have will be supported in the SBS topic area here on EE. However, if you start playing around with the FSMO roles and moving things around that way and run into an issue, I doubt there will be many experts here on EE that will advise different from "Use the transition pack". Also, if you do run into an issue then realise you do need the transition pack but you have moved FSMO roles and other server roles around, the transition pack may not work correctly and you will have an awful set up to deal with.
If you wish to continue without the transition pack, do so at your own risk. It certainly isn't a recommended approach and other experts will advise similarly.
-tigermatt
In fact, reading hypercat's post http:#20300496, I'm not sure where SBS licensing information is stored. If that's in Active Directory then you will have little to no chances of success without using the transition pack.
-tigermatt
-tigermatt
ASKER
I don't understand why it seems so dangerous, someone has to have tried what I'm want to do without the transistion pack, I'm not insane for trying to find away to not use the transistion pack. Is there anybody that has done this out there?
>>> I'm not insane for trying to find away to not use the transistion pack
Please don't take any of my or any other user's comments as if we are trying to say this. We are just advising what the best course of action would be based upon Microsoft's recommended guidelines. I don't blame you for wanting to try to do this without the transition pack, particularly since the transition pack can be quite costly. However, you seriously need to think about our advice and consider the consequences of using a non-Microsoft approved/recommended approach to this matter; think about the potential downtime if something goes wrong.
Whatever you do, make sure you have a good backup of your SBS before messing with anything.
-tigermatt
Please don't take any of my or any other user's comments as if we are trying to say this. We are just advising what the best course of action would be based upon Microsoft's recommended guidelines. I don't blame you for wanting to try to do this without the transition pack, particularly since the transition pack can be quite costly. However, you seriously need to think about our advice and consider the consequences of using a non-Microsoft approved/recommended approach to this matter; think about the potential downtime if something goes wrong.
Whatever you do, make sure you have a good backup of your SBS before messing with anything.
-tigermatt
Again, I support tigermatt's response. I don't really understand your reluctance to use the transition pack unless there are cost considerations. However, keep in mind that you have to purchase the necessary non-SBS server licenses and CALs anyway, so I'm not sure the cost is really that much more, if at all.
My experience with migrations is that the more automated tools you can find the better off you are. You asked for advice from experts and that's what you're getting - expert advice. But in the end the decision is up to you. However, if you want to transition from your current domain to one without SBS, without using the transition pack, my advice is to migrate to a completely new AD domain. This is what I was addressing in my first post. Depending on the number of users you have, it might work fine even doing it manually. You probably would be able to use some of the normal migration tools, like the ADMT (Active Directory Migration Tool) to migrate your users from the old SBS domain to the new standard domain without having to re-add users manually, as well as Exmerge as I mentioned above.
My experience with migrations is that the more automated tools you can find the better off you are. You asked for advice from experts and that's what you're getting - expert advice. But in the end the decision is up to you. However, if you want to transition from your current domain to one without SBS, without using the transition pack, my advice is to migrate to a completely new AD domain. This is what I was addressing in my first post. Depending on the number of users you have, it might work fine even doing it manually. You probably would be able to use some of the normal migration tools, like the ADMT (Active Directory Migration Tool) to migrate your users from the old SBS domain to the new standard domain without having to re-add users manually, as well as Exmerge as I mentioned above.
ASKER
I setup a new Windows 2003 server as a seconadry DC next to the Windows 2003 SBS Server on the network, then made the Windows 2003 Standard Server a Global catalog of the Windows 2003 SBS Server's AD. So thats why I ask who needs a tranistion pack ?
Cap