Licensing Error Messages Windows 2003 Server Part 2
Being that we cannot add the Windows SBS 2003 Standard Edition Server to our Windows 2000 Domain, we are under the assuption that we have to make the SBS 2003 Server the new Domain Controller.
Here's the question we have:
We run our Exchange Service off of our Domain Controller because we are small office, and have a low budget. If we DCPROMO the SBS 2003 Server, what happens to the original domain, email accounts, network connections for users, Active Directory Accounts, and the rest of the network?
Does everything just magically flow over to the AD of SBS 2003 Server?
We have only 5 CALs for SBS 2003 Server, and we will only have 2 or 3 people ever accessing the server, but do we now need to buy a CAL for each user on the network?
Thanks!
Tim
Here's the question we have:
We run our Exchange Service off of our Domain Controller because we are small office, and have a low budget. If we DCPROMO the SBS 2003 Server, what happens to the original domain, email accounts, network connections for users, Active Directory Accounts, and the rest of the network?
Does everything just magically flow over to the AD of SBS 2003 Server?
We have only 5 CALs for SBS 2003 Server, and we will only have 2 or 3 people ever accessing the server, but do we now need to buy a CAL for each user on the network?
Thanks!
Tim
Forgot to mention - every user will need an SBS CAL - more money than a Server 2003 CAL. In your existing case, every user needs a Server CAL and Exchange CAL.
ASKER
So what if we upgraded the current domain controller that runs the domain to SBS Windows 2003 Server? We would only have to buy CALs for the clients or everyone in the network, but not for Exchange. Exchange 2000 runs on the same machine, but we don't need to do anything to that right? Exchange 2000 will continue to work once the server is upgraded to SBS Windows 2003 Server right?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This bites. I guess we'll get the Windows 2003 Standard version, and are you sure that we can do what we want without a ground-up build/install with this standard version?
Yes. You run adprep /forestprep then adprep /domainprep on the Windows 2000 Server, then join the 2003 server to it as an additional domain controller in an existing domain. Now both servers are in the same domain and are peers.
What are you going to be doing with the second server? - I'm not sure you mentioned it.
What are you going to be doing with the second server? - I'm not sure you mentioned it.
I have a similar situation. I have a 2000 SBS domain, and it definitely looks like I can't add 2003 SBS as a member server. I need SQL server on the new server. Do I need to purchase 2003 Server and stand alone SQL Server to accomplish this? Or would you advise purchasing 2000? Thanks!
Can you not use the SQL install in SBS2000? or does it have to be on another machine?
If it needs to be on another machine then you will need a Windows 2000 Standard server with SQL as you are suggesting.
If it needs to be on another machine then you will need a Windows 2000 Standard server with SQL as you are suggesting.
We have SQL server on the 2000 SBS machine. The issue that we are having is that a remote office is accessing info from the database (via Remote Desktop), and their performance is horrible. I am not sure why the group chose to use remote desktop instead of installing the software locally on the workstations and accessing the database only (I am new at the company, and the previous IT guy walked out of the company). We wanted to add a server to the remote location and make SQL Server resident at the remote location to help improve performance.
Thanks for your help!!!
I would do as you already want to and install the apps locally and have them access the data from SQL remotely.
This should help the bandwidth problem somewhat.
This should help the bandwidth problem somewhat.
You'll have to create all the users and rejoin the computers to the new domain, then copy the data over and create new shares. Exchange is a totally different ballgame. Is the Exchange server on SBS now? It's going to be messy. But basically, you'll be starting over. You might be able to backup and restore the mail stores but the naming context will change in the domain.
My advice - sell SBS to someone legally. Buy a copy of 2003 Server Standard and add it to the domain. If you do not already have Exchange (standalone) you'll need that too. If it's installed already on the 2000 domain - you're laughing.
Why are you running the SBS server? What are you trying to do with this server?