Domain vs Stand alone workgroup server

We just received a Dell preloaded sbs 2003 premium. Before we integrated into
the network, we needed to set it up with sql running a property management
system and 4 computers for training purposes. We did not want to setup the
server with users, computers and licenses yet, so we just downgraded the
server to a stand alone workgroup server.
I didn't realize that we would lose management services. How do we get it
back?
Eventually this will be an application server only. There is another server
running sbs that will be the domain controller. Should I leave the
application server as is? or change it back to domain?
Any help most appreciated

 

In

You cannot run SBS as anything other than a DC; it will not work. And you
can't have two SBS servers in the domain.....it sounds like you bought the
wrong product. If you needed a SQL server only, you should have bought
Windows & SQL. I'd see if you can return the server to Dell & exchange it.

 

Thank you for the quick reply. As it stands now the server is functioning,
but what you are telling me is that it is basically functioning as a client
not a server and I am paying $1500.00 for sql. Is that right? Can you please
explain to me why I can't have 2 SBS on the same network?

 

What do you want explained? Its a basic limitation built-in to SBS. You
should do more research about the products you're buying before actually
buying.

 

You can have 2 SBS on the same network, just not the same domain. This is an
SBS limitation. You can also not set up any domain trust between an SBS
domain and any other domain.

 

OK. So I have a server running sbs premium that is using only sql, is that
right? When I bring in another server running SBS as the Domain Controller
everything should be OK, except we just paid $1500.00 for an OS that we are
not using, right? As a stand alone, I can join the SQL Server to the Domain
of the New Server running SBS, no?

 

In

Sounds like it - and it won't work. You can't use it if you want it to be
part of your existing domain at all.

Nope.... sorry.

Unless you want two totally separate SBS servers with two different active
directory domains (and two sets of user accounts, and CALs for each user or
device on each domain), you need to try to return your SBS and get regular
W2003 and SQL.

You can't set up two SBS boxes in the same domain, you can't use an SBS box
as a member server (or standalone server), and you can't set up trusts with
SBS. You've got the wrong product.

 

OK I am starting to get the picture but this is the scoop. The current sbs
server was sent by the software company to host their PMS software. I can't
change that now. We thought we could use the same server for files & exchange
but they won't let us, so we need another server. What do we do?

 

Another question, no problem for two domains with users, cals etc. That is
not a problem, however now I have to get the sql server back to a domain
server. Can I do that without reinstalling the OS? The PMS company has
already loaded their software and set it up to the client computers.

 

In

You could look into the transition pack, maybe. I think this would unlock
the current SBS config so you can use it and its components without SBS. Or,
buy W2003 and SQL, regular products, and CALs for same, and flatten &
reinstall the box.

I don't know what software company would be sending you a server, but this
should've been looked at carefully before you guys ordered it, it seems!
Sorry to be the bearer of bad news, but there's no easy way around this.

 

In

Are you sure? I would never want that - you really want to maintain two sets
of accounts/passwords for each user? That is a bad plan. I suspect you will
also run into DNS problems.

I have no idea, sorry. I have never tried to do what you're doing.

 

OK for the two domains, two AD's Cals etc. However, how do I get the server
from stand alone to domain without reinstalling the OS? The PMS Company has
loaded their software on the server already and to the clients.

 

This PMS software company needs to take some responsbility here
If they sent you a server with SBS 2003 as the operating system and then
failed to add the other components, make it the (using old terminology) the
Primary Domain Controller, etc. then they have violated the End User License
Agreement for SBS and need to resolve that.

They have pretty much put you between the rock and a hard place.

If you complete the domain setup on "their" server, its likely to "break"
their software.

 

In

Agreed. I would not use this server (or SBS on this server) as is. I think
the OP should tell the PMS software people to take the server back and
replace it with the right box. There is no way that this is going to be an
easy config even if they can dcpromo the box - I'd never allow it myself.

 

You have no choice. Reinstall the OS. But seriously, this is the wrong way
to do things entirely, and I would first and foremost have a discussion with
your PMS software company. They should NEVER use SBS as the underlying OS if
they tell you that you can't run Exchange or File and Print on it. That's
just _stupid_ and won't work in just about anyone's network.