Adding 2003 Server to domain - first steps

[Guest JPCLYONS]

I have a domain where I need to do the following. I am proceeding cautiously

since I ma not an MCSE - just an MCP.

 

The server is on the network, but not yet added to the domain. Eventually,

it will replace an old server, but not for now. It will be a DC, as well as

File Server and DNS.

 

The first step is needed so that I can use tape backup to restore files to

the new server in preparation for it to replace the old server.

 

I am concerned that just adding the server to the domain will cause some

issues, like the new server acting as the DC, or as DHCP, etc. Unless I run

the role wizard and specify what roles the server will have, no services are

on by default, correct?

 

In other words, just adding it to the domain will not cause login issues,

DHCP or DNS issues. correct?

 

Then, once it is added, I will run DCPROMO on the new server and on the old

server. Then I can add DNS to the new server and the migration will be

complete.

 

Sorry if these questions seem basic or have been answered elsewhere, but I

wanted to verify this before add the new server.

 

Thanks!

 

Jim Lyons

 

please contact here or at below address.

 

J PC LYONS at GEE male DOTT com

[Guest Mathieu CHATEAU]

Re: Adding 2003 Server to domain - first steps

 

Hello,

 

I would start by making it a DC.

Then DNS

then Global catalog (if needed)

then DHCP.

 

Take care of FSMO role placement and the infrastructure master that mustn't

be a Global catalog DC except if all DC are Global catalog.

 

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"JPCLYONS" <JPCLYONS@discussions.microsoft.com> wrote in message

news:AC140C5E-5BB6-4BC3-AD66-7AE94D31F8FA@microsoft.com...

>I have a domain where I need to do the following. I am proceeding

>cautiously

> since I ma not an MCSE - just an MCP.

>

> The server is on the network, but not yet added to the domain.

> Eventually,

> it will replace an old server, but not for now. It will be a DC, as well

> as

> File Server and DNS.

>

> The first step is needed so that I can use tape backup to restore files to

> the new server in preparation for it to replace the old server.

>

> I am concerned that just adding the server to the domain will cause some

> issues, like the new server acting as the DC, or as DHCP, etc. Unless I

> run

> the role wizard and specify what roles the server will have, no services

> are

> on by default, correct?

>

> In other words, just adding it to the domain will not cause login issues,

> DHCP or DNS issues. correct?

>

> Then, once it is added, I will run DCPROMO on the new server and on the

> old

> server. Then I can add DNS to the new server and the migration will be

> complete.

>

> Sorry if these questions seem basic or have been answered elsewhere, but I

> wanted to verify this before add the new server.

>

> Thanks!

>

> Jim Lyons

>

> please contact here or at below address.

>

> J PC LYONS at GEE male DOTT com

>

>

[Guest JPCLYONS]

Re: Adding 2003 Server to domain - first steps

 

DHCP is provided by other systems on the network. I don't need it to be a

DHCP server. I also cannot make it the DC until all files/shares are

replicated from the current DC.

 

I just wanted to know if it is added to the domain as a member server that

no issues will occur.

 

Anyway, thanks for your reply.

 

"Mathieu CHATEAU" wrote:

> Hello,

>

> I would start by making it a DC.

> Then DNS

> then Global catalog (if needed)

> then DHCP.

>

> Take care of FSMO role placement and the infrastructure master that mustn't

> be a Global catalog DC except if all DC are Global catalog.

>

>

> --

> Cordialement,

> Mathieu CHATEAU

> English blog: http://lordoftheping.blogspot.com

> French blog: http://www.lotp.fr

>

>

> "JPCLYONS" <JPCLYONS@discussions.microsoft.com> wrote in message

> news:AC140C5E-5BB6-4BC3-AD66-7AE94D31F8FA@microsoft.com...

> >I have a domain where I need to do the following. I am proceeding

> >cautiously

> > since I ma not an MCSE - just an MCP.

> >

> > The server is on the network, but not yet added to the domain.

> > Eventually,

> > it will replace an old server, but not for now. It will be a DC, as well

> > as

> > File Server and DNS.

> >

> > The first step is needed so that I can use tape backup to restore files to

> > the new server in preparation for it to replace the old server.

> >

> > I am concerned that just adding the server to the domain will cause some

> > issues, like the new server acting as the DC, or as DHCP, etc. Unless I

> > run

> > the role wizard and specify what roles the server will have, no services

> > are

> > on by default, correct?

> >

> > In other words, just adding it to the domain will not cause login issues,

> > DHCP or DNS issues. correct?

> >

> > Then, once it is added, I will run DCPROMO on the new server and on the

> > old

> > server. Then I can add DNS to the new server and the migration will be

> > complete.

> >

> > Sorry if these questions seem basic or have been answered elsewhere, but I

> > wanted to verify this before add the new server.

> >

> > Thanks!

> >

> > Jim Lyons

> >

> > please contact here or at below address.

> >

> > J PC LYONS at GEE male DOTT com

> >

> >

>

>

[Guest Mathieu CHATEAU]

Re: Adding 2003 Server to domain - first steps

 

You can make a server domain member without issue (going the normal way)

 

--

Cordialement,

Mathieu CHATEAU

English blog: http://lordoftheping.blogspot.com

French blog: http://www.lotp.fr

 

 

"JPCLYONS" <JPCLYONS@discussions.microsoft.com> wrote in message

news:FA355335-1EBC-4D53-AB93-B1059F0BBB8C@microsoft.com...

> DHCP is provided by other systems on the network. I don't need it to be a

> DHCP server. I also cannot make it the DC until all files/shares are

> replicated from the current DC.

>

> I just wanted to know if it is added to the domain as a member server that

> no issues will occur.

>

> Anyway, thanks for your reply.

>

> "Mathieu CHATEAU" wrote:

>

>> Hello,

>>

>> I would start by making it a DC.

>> Then DNS

>> then Global catalog (if needed)

>> then DHCP.

>>

>> Take care of FSMO role placement and the infrastructure master that

>> mustn't

>> be a Global catalog DC except if all DC are Global catalog.

>>

>>

>> --

>> Cordialement,

>> Mathieu CHATEAU

>> English blog: http://lordoftheping.blogspot.com

>> French blog: http://www.lotp.fr

>>

>>

>> "JPCLYONS" <JPCLYONS@discussions.microsoft.com> wrote in message

>> news:AC140C5E-5BB6-4BC3-AD66-7AE94D31F8FA@microsoft.com...

>> >I have a domain where I need to do the following. I am proceeding

>> >cautiously

>> > since I ma not an MCSE - just an MCP.

>> >

>> > The server is on the network, but not yet added to the domain.

>> > Eventually,

>> > it will replace an old server, but not for now. It will be a DC, as

>> > well

>> > as

>> > File Server and DNS.

>> >

>> > The first step is needed so that I can use tape backup to restore files

>> > to

>> > the new server in preparation for it to replace the old server.

>> >

>> > I am concerned that just adding the server to the domain will cause

>> > some

>> > issues, like the new server acting as the DC, or as DHCP, etc. Unless

>> > I

>> > run

>> > the role wizard and specify what roles the server will have, no

>> > services

>> > are

>> > on by default, correct?

>> >

>> > In other words, just adding it to the domain will not cause login

>> > issues,

>> > DHCP or DNS issues. correct?

>> >

>> > Then, once it is added, I will run DCPROMO on the new server and on the

>> > old

>> > server. Then I can add DNS to the new server and the migration will be

>> > complete.

>> >

>> > Sorry if these questions seem basic or have been answered elsewhere,

>> > but I

>> > wanted to verify this before add the new server.

>> >

>> > Thanks!

>> >

>> > Jim Lyons

>> >

>> > please contact here or at below address.

>> >

>> > J PC LYONS at GEE male DOTT com

>> >

>> >

>>

>>

[Guest JPCLYONS]

Re: Adding 2003 Server to domain - first steps

 

Wish me luck!

 

Merci, monsieur!

 

http://www.poconopcdoctor.com/2006/08/05/mon-dieu-is-it-true/

 

"Mathieu CHATEAU" wrote:

> You can make a server domain member without issue (going the normal way)

>

> --

> Cordialement,

> Mathieu CHATEAU

> English blog: http://lordoftheping.blogspot.com

> French blog: http://www.lotp.fr

>

>

> "JPCLYONS" <JPCLYONS@discussions.microsoft.com> wrote in message

> news:FA355335-1EBC-4D53-AB93-B1059F0BBB8C@microsoft.com...

> > DHCP is provided by other systems on the network. I don't need it to be a

> > DHCP server. I also cannot make it the DC until all files/shares are

> > replicated from the current DC.

> >

> > I just wanted to know if it is added to the domain as a member server that

> > no issues will occur.

> >

> > Anyway, thanks for your reply.

> >

> > "Mathieu CHATEAU" wrote:

> >

> >> Hello,

> >>

> >> I would start by making it a DC.

> >> Then DNS

> >> then Global catalog (if needed)

> >> then DHCP.

> >>

> >> Take care of FSMO role placement and the infrastructure master that

> >> mustn't

> >> be a Global catalog DC except if all DC are Global catalog.

> >>

> >>

> >> --

> >> Cordialement,

> >> Mathieu CHATEAU

> >> English blog: http://lordoftheping.blogspot.com

> >> French blog: http://www.lotp.fr

> >>

> >>

> >> "JPCLYONS" <JPCLYONS@discussions.microsoft.com> wrote in message

> >> news:AC140C5E-5BB6-4BC3-AD66-7AE94D31F8FA@microsoft.com...

> >> >I have a domain where I need to do the following. I am proceeding

> >> >cautiously

> >> > since I ma not an MCSE - just an MCP.

> >> >

> >> > The server is on the network, but not yet added to the domain.

> >> > Eventually,

> >> > it will replace an old server, but not for now. It will be a DC, as

> >> > well

> >> > as

> >> > File Server and DNS.

> >> >

> >> > The first step is needed so that I can use tape backup to restore files

> >> > to

> >> > the new server in preparation for it to replace the old server.

> >> >

> >> > I am concerned that just adding the server to the domain will cause

> >> > some

> >> > issues, like the new server acting as the DC, or as DHCP, etc. Unless

> >> > I

> >> > run

> >> > the role wizard and specify what roles the server will have, no

> >> > services

> >> > are

> >> > on by default, correct?

> >> >

> >> > In other words, just adding it to the domain will not cause login

> >> > issues,

> >> > DHCP or DNS issues. correct?

> >> >

> >> > Then, once it is added, I will run DCPROMO on the new server and on the

> >> > old

> >> > server. Then I can add DNS to the new server and the migration will be

> >> > complete.

> >> >

> >> > Sorry if these questions seem basic or have been answered elsewhere,

> >> > but I

> >> > wanted to verify this before add the new server.

> >> >

> >> > Thanks!

> >> >

> >> > Jim Lyons

> >> >

> >> > please contact here or at below address.

> >> >

> >> > J PC LYONS at GEE male DOTT com

> >> >

> >> >

> >>

> >>

>

>