3 replies
by anas.mroueh Accepted solution
by Former member Accepted solution
SBS'03 doesn't play well with others. It wants to be the only DC and for this reason it is difficult to add it to an existing domain. What you can do is "upgrade" or "replace" the existing DC utilizing the available tools.
SBS allows other DC's to be added to the domain. However, SBS cannot be added to an existing domain.
- SBS cannot have trusts. You can use ADMT, but you need to run it from the commandline. Not for the faint of heart!
ADMT works because when running it from the command line you use the RUNAS command to authenticate to the other domain. Similarly, you must syncronize passwords between the two domain administrator users.
But here is the real answer to your question. If you get what you want to work it is not legal according to Microsoft's acceptible use policy. SBS must be the only DC and all products must be installed onto it. You can only add other separately licensed products to the domain.
A typical SBS network for a larger amount of users would look like this:
SBS 2003 server: AD, Exchange, ISA, SQL
Windows 2003 Storage Server: File and Print
Windows 2003 Terminal Server: Remote users and single application publishing
This can be a great setup, however, keep your SBS server healthy because rebuilding it can be a difficult. I never recommend installing any third party applications onto the SBS server to clients. Why? Because Microsoft's SBS service packs often contain more than fixes and this can break 3rd party software. It is best to move them to small individual servers or virtual machines.
http://www.petri.co.il/forums/archive/index.php/t-2761.html
Please post back if you have any more problems or questions.
by bart777 Accepted solution
SBS is like an only child. It can only exist in it's own domain and has it's own licensing structure.
If you really need to do it this way you would need to build a new domain on the SBS server and then migrate the old domain to the new server. This is doable but definatley NOT the way to go. It would be easier to just create a normal server and join it to the domain. It might be possible to do a modified swing migration to get the data over without having to use the ADMT but this too adds potential risk.
My primary concern with either the ADMT or the Swing migration to a new domain is what it may do to your financial application. If it's tied to your current AD tree and uses LDAP for authentication you may break that application and have to start over there. If it uses SQL you would ONLY want to do a Swing migration as this will maintain all of the current domain security.
Don't get me wrong. You could do this but it's not my first choice. If you are doing this for $$$ reasons due to the price point of SBS and the exchange piece then I fully understand.
Take a step back first and see how your financial app works. Determine if it will blow up if you alter AD of the domain. Also look at just building a new server and adding it to your current domain. This is the simplest way to get the job done. If you are trying to get the added benefit of Exchange and cannot afford to buy a full copy of that server software then you will want to do the swing migration.
Just take you time and don't rush this one or you'll be working some very long hours and cursing all over the computer room.
Best of luck.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending