Switching from workgroup to server 2003 domain

[Guest]

Hi, I apologize if this is the wrong news group to be posting this, but I'm
getting a little frustrated and thought maybe someone could point me in the
right direction. I think I want to switch users on our network over to a
domain from the workgroup they are currently using. I haven't created the
domain yet, the machine its going to be on is running Windows Server 2003. Is
creating and adding users to a domain very difficult? Is there a tutorial
that someone might know of? Do I just have to change the server to tell it
that its now a domain controller, and then have all the other machines join
the domain?

 

[Guest]

Unless 2003 was installed as a domain controller initially, you will have to
rebuild it to create the domain. The use of domain accounts will make
administration easier. What NOS are the users running on their workstations?

 

[Guest]

They're running either XP, and a couple are running win98, there's only like
8 workstations so theres not that much work involved....I hope

 

[Guest]

Couldn't I just add the "domain controller" as a "role" on the server as
opposed to rebuilding the whole thing? The workstations are either XP or
win98, theres only about 7 or 8 of them so there shouldn't be to much work
involved....I'm hoping

 

[Ron Lowe]

Unless 2003 was installed as a domain controller initially, you will have
to
rebuild it to create the domain. The use of domain accounts will make
administration easier. What NOS are the users running on their
workstations?

No, that's not correct.

You can start with a regular server then run 'dcpromo' to promote the
machine to become a Domain Controller.

Perhaps you are thinking of NT4 server?

To the OP:
You are embarking on a non-trivial exercise.
There will be a steepish learning curve initially.
I'd STRONGLY recommend:

1) Buy a book about this.
I used 'Mastering Windows 2000 Server by Mark Minassi'.
This applies to server 2003 too.

2) Build a test lab with a test domain controller and clients,
and get real comfortable with all the core network services
particularly DNS.

Do this before dcpromo-ing a live server so there are no surprises
along the way, no 'what the heck does that mean' moments.

 

[Guest]

Does that book also have a detailed section on Active Directory?

 

[Guest]

Thanks Ron.

No, that's not correct.

You can start with a regular server then run 'dcpromo' to promote the
machine to become a Domain Controller.

Perhaps you are thinking of NT4 server?

To the OP:
You are embarking on a non-trivial exercise.
There will be a steepish learning curve initially.
I'd STRONGLY recommend:

1) Buy a book about this.
I used 'Mastering Windows 2000 Server by Mark Minassi'.
This applies to server 2003 too.

2) Build a test lab with a test domain controller and clients,
and get real comfortable with all the core network services
particularly DNS.

Do this before dcpromo-ing a live server so there are no surprises
along the way, no 'what the heck does that mean' moments.

 

[Ron Lowe]

I used 'Mastering Windows 2000 Server by Mark Minassi'.

Does that book also have a detailed section on Active Directory?

Yes, and a bunch about DNS which is critical to the correct operation of AD.

The best thing I did was to build a test lab of old PCs and actually go
through it.
It was worth it.

 

[CZ]

Unless 2003 was installed as a domain controller initially, you will haverebuild it to create the domain.

Crash Override:

That is incorrect.
After you install the Win2k3 server op system, you can use any of the
following to promote that computer to a DC:

Configure My Server utility
or Start: Run: dcpromo
or Manage your Server utility

 

[CZ]

Hi, I apologize if this is the wrong news group to be posting this, butgetting a little frustrated and thought maybe someone could point me in the
right direction. I think I want to switch users on our network over to a
domain from the workgroup they are currently using. I haven't created the
domain yet, the machine its going to be on is running Windows Server 2003.
Is
creating and adding users to a domain very difficult? Is there a tutorial
that someone might know of? Do I just have to change the server to tell it
that its now a domain controller, and then have all the other machines join
the domain?

Cooler:

I use Win2k3 server as a DC and as a standalone server in a workgp.
Why are you interested in having a domain?

 

[Guest]

The developer here says he needs a domain to do certain things, and the added
security of AD is always nice. I ordered that book that Ron Lowe was talking
about today, so I think I won't have to many problems once I get that. I
remember going over most of this stuff at school (Dc's and AD) but its hard
to remember things until you apply then in a real world environement.

 

[NobodyMan]

getting a little frustrated and thought maybe someone could point me in the
right direction. I think I want to switch users on our network over to a
domain from the workgroup they are currently using. I haven't created the
domain yet, the machine its going to be on is running Windows Server 2003.
Is
creating and adding users to a domain very difficult? Is there a tutorial
that someone might know of? Do I just have to change the server to tell it
that its now a domain controller, and then have all the other machines join
the domain?

Cooler:

I use Win2k3 server as a DC and as a standalone server in a workgp.
Why are you interested in having a domain?

I'm a little confused. Are you using your Server as a Domain
Controller or as a Stand Alone server for a workgroup? You can't have
both!

Or are you referring to two separate servers? You message isn't real
clear here, and it makes a huge difference on how to take your advice!

 

[NobodyMan]

That book is a great resource. Pay special attention to the
information regarding DNS. Active Directory is very interdependent on
DNS, so if you screw that part up you will have big problems!

 

[CZ]

I use Win2k3 server as a DC and as a standalone server in a workgp.

NoBodyMan wrote:
I'm a little confused. Are you using your Server as a Domain
Controller or as a Stand Alone server for a workgroup?
Or are you referring to two separate servers?

NoBodyMan:

Separate servers.

 

[CZ]

I ordered that book that Ron Lowe was talking
about today, so I think I won't have to many problems once I get that.

Cooler:

Notice Ron's other comment: "The best thing I did was to build a test lab of
old PCs and actually go through it."

Some thoughts:
Win2k3 server is a fantastic server op system.
Learning about domains (AD, FSMOs, GC, GPO, disaster recovery, etc.) is not
a small project.
If you value your job, learn via a test setup, not a production setup.

 

[Guest]

So can you have a workgroup and a domain running on a Windows 2003 server?
Because it would be nice to be able to create the domain, and then add one
workstation to it and check everything like that while the workgroup remains
undisturbed until I'm fully ready to put everyone on the domain. Is that
possible?

 

[CZ]

So can you have a workgroup and a domain running on a Windows 2003Because it would be nice to be able to create the domain, and then add one
workstation to it and check everything like that while the workgroup remains
undisturbed until I'm fully ready to put everyone on the domain. Is that
possible?

Cooler:

Not on the same server computer. A Win2k3 server computer is either a DC
(domain controller) or it is not a DC.

You can promote a Win2k3 server to a DC, and then demote it to non-DC status
(aka a standalone server).
However, I would not recommend this on a production server.

A cheap way to learn about a domain is to get a MS demo of Win2k3 server and
install it on a test computer. The demo is good for 6 months.

Also, a domain is much more complex than a workgp, so plan to spend some
time learning about it.