Workgroup to Domain - Worth The Trouble?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello all. Current setup - 9 PC's all running XP (some Home, some Pro)
connected to Netgear router (if that matters) and networked as a Workgroup. I
just bought a nice shiny new server running Windows Server 2003. I will
probably have to pay someone to fully utilize the benefits of the server but
I am doing my best to learn as much as possible first. It seems the main
benefits of going to a domain system is security and control. What are the
disadvantages? for example - I switched my PC from workgroup to domain and
when i logged in to the domain (not my local computer) my outlook was not
configured, my desktop background changed, etc. I assume there is a way to
migrate this stuff from my local XP user account to the domain account (or
whatever I am logging into) but does that mean if the server crashes, my
settings, etc goes with it? If I am not connected to the internet, what will
I logon to when I boot my computer? Am I opening up a can of worms? Any
advice/discussion of the workgroup vs domain is appreciated. Also, is there a
networking/server "bible" that I can buy (that will be updated for server
2003) or is this more like a go back to college type subject? Thanks. Ron
 
See below.

Shiny New Server Boy said:
Hello all. Current setup - 9 PC's all running XP (some Home, some Pro)
connected to Netgear router (if that matters) and networked as a Workgroup. I
just bought a nice shiny new server running Windows Server 2003. I will
probably have to pay someone to fully utilize the benefits of the server but
I am doing my best to learn as much as possible first. It seems the main
benefits of going to a domain system is security . . .
Click to expand...

No. A sever model provides no more and no less security than
a workgroup model.
... and control.
Click to expand...

Yes. A server gives you the facility to administer accounts, passwords,
scripts and policies centrally. It also supports more than 10 concurrent
connections to shared resources.
What are the
disadvantages? for example - I switched my PC from workgroup to domain and
when i logged in to the domain (not my local computer) my outlook was not
configured, my desktop background changed, etc. I assume there is a way to
migrate this stuff from my local XP user account to the domain account (or
whatever I am logging into) but does that mean if the server crashes, my
settings, etc goes with it?
Click to expand...

No. Your server credentials are cached and can be used even while
the server is off-line.
 
Shiny New Server Boy said:
Hello all. Current setup - 9 PC's all running XP (some Home, some Pro)
connected to Netgear router (if that matters) and networked as a Workgroup. I
just bought a nice shiny new server running Windows Server 2003. I will
probably have to pay someone to fully utilize the benefits of the server but
I am doing my best to learn as much as possible first. It seems the main
benefits of going to a domain system is security and control. What are the
disadvantages? for example - I switched my PC from workgroup to domain and
when i logged in to the domain (not my local computer) my outlook was not
configured, my desktop background changed, etc. I assume there is a way to
migrate this stuff from my local XP user account to the domain account (or
whatever I am logging into) but does that mean if the server crashes, my
settings, etc goes with it? If I am not connected to the internet, what will
I logon to when I boot my computer? Am I opening up a can of worms? Any
advice/discussion of the workgroup vs domain is appreciated. Also, is there a
networking/server "bible" that I can buy (that will be updated for server
2003) or is this more like a go back to college type subject? Thanks. Ron
Click to expand...

The benefits of a domain is *centralized* security and control. The
principle modification between a stand-alone server and a domain DC or
member server is the scope of security and the management requirements
involved.

In a domain, both a computer account and a user account is required to
participate (the client becomes part of the domain). In a workgroup, an
existing user account at the server is used to connect to the server (the
client station and the client user aren't part of the standalone security
model).

A domain user is managed and located in the domain, not on the client. Which
explains the user account configuration loss when connecting to a domain.
Note that isn't a problematic issue since the administrator can be
preconfigure a default user with his/her attributes to derive from (using
variables like %username%).

The knowledge required to setup and manage a domain are far-reaching. They
involve more than just domain setup (dns hierarchy, OU, replication,
security and specially recovery).

Since you haven't the need for a second DC (for AD redundancy), unless you
have a stringent security requirement and unless you plan to perform a
serious expansion, i'ld stick with the workgroup scenario. XP home, for
example can't participate in a domain. It can connect to a domain share but
its not integral to the domain.
 
Back
Top