New 2003 server to be DC in small NT 4.0 network
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
New 2003 server to be DC in small NT 4.0 network

 
Post new topic   Reply to topic    Windows Server Forum Index -> Migration
Author Message
gunit
Guest





Posted: Sat Jan 08, 2005 3:50 pm    Post subject: New 2003 server to be DC in small NT 4.0 network Reply with quote

Ok.. I have a very small NT 4.0 network with 5 users. Very simple
setup. We have a new 2003 server that we want to install and be the
new domain computer.

Why can't I install 2003 on the new computer with the same domain
(while it is not on the existing network), then create all of the user
accounts and restore the data files, then shut down the NT 4.0 server
and attach the new 2003 server to the network. Why couldn't the XP
clients not attach to the new server?

OR do the same thing above except make the new 2003 server as a new
domain name and why it is put on the network have the XP clients join
the new domain name?

I am not certain the first option could be done, but it seems like the
second option should definitely work. And if so I would guess that
maybe the users would have a new profile created... but couldn't you
then copy the old profile into the new directory and be good to go?

Anyway... looking to see if there is anyway to not have to go through
upgrades or migration. I can't upgrade the existing unit because of
disk space, and I would prefer not to install an NT 4.0 BDC, promote,
and then upgrade... seems like a lot of work.

Thanks in advance.
Back to top
Herb Martin
Guest





Posted: Sat Jan 08, 2005 10:28 pm    Post subject: Re: New 2003 server to be DC in small NT 4.0 network Reply with quote

"gunit" <gregs@branchgroup.com> wrote in message
news:1105177818.761636.289930@f14g2000cwb.googlegroups.com...
Quote:
Ok.. I have a very small NT 4.0 network with 5 users. Very simple
setup. We have a new 2003 server that we want to install and be the
new domain computer.

Why can't I install 2003 on the new computer with the same domain
(while it is not on the existing network), then create all of the user
accounts and restore the data files, then shut down the NT 4.0 server
and attach the new 2003 server to the network. Why couldn't the XP
clients not attach to the new server?

They can, but along with the new user accounts you will
need new computer accounts; you will have problems with
any permissions you use (new accounts even with the same
name are not the same person); and you may lose your user
profiles unless you know precisely what you are doing.

It's easy to migrate the user profiles but it is also easy to
lose them.

Quote:
OR do the same thing above except make the new 2003 server as a new
domain name and why it is put on the network have the XP clients join
the new domain name?

Yes -- same issues.

Quote:
I am not certain the first option could be done, but it seems like the
second option should definitely work. And if so I would guess that
maybe the users would have a new profile created... but couldn't you
then copy the old profile into the new directory and be good to go?

Yes. and Yes.

But Backup the profiles now just in case (even XCopy /s to a different
directory tree on each machine so you can always get back to them.

Quote:
Anyway... looking to see if there is anyway to not have to go through
upgrades or migration. I can't upgrade the existing unit because of
disk space, and I would prefer not to install an NT 4.0 BDC, promote,
and then upgrade... seems like a lot of work.

It's not that much, one quick install of NT 4, and
the upgrade plus a couple of reboots and nothing
really will change.

You can even keep the NT as a print server or
some such this way.

But with 5 users, I will not make my usual argument
for upgrading.

You seem to understand the options -- so as long as
you make an informed decision it is the right one for
you.

--
Herb Martin


Quote:
Thanks in advance.
Back to top
gunit
Guest





Posted: Sat Jan 08, 2005 11:41 pm    Post subject: Re: New 2003 server to be DC in small NT 4.0 network Reply with quote

Quote:
They can, but along with the new user accounts you will
need new computer accounts; you will have problems with
any permissions you use (new accounts even with the same
name are not the same person); and you may lose your user
profiles unless you know precisely what you are doing.

It's easy to migrate the user profiles but it is also easy to
lose them.

To confirm...
1) I can create a new 2003 Standard Server with the same domain name
and same server name as my NT 4.0 server (not while attached to the
existing network)
2) Create the user accounts
3) Restore the user data
4) Setup the user rights to the data. This is very basic... pretty
much all users have the exact same rights to several application data
directories which has almost all of the data stored on the server.
Then of course their home directory.
5) Make sure DNS and DHCP are setup also on 2003 server.
5) Shutdown and remove the NT4 server.
6) Put 2003 server in place of NT4.

If I can do everything up to this point what do I need to do to get the
existing XP computers to become a part of the (same) domain name that
now exists on the 2003 server? I know if it was a different domain
name I would join that new domain, but if the domain name is the same
how do I get the existing XP units that were already a part of a domain
with the same name to be a part of the new domain of the same name?

Or should I make it a different domain so I can have the XP units join
the domain.

Then to confirm...

1) If I get the XP units to join the domain the profiles should be new
ones on the XP units.
2) I can then login as an administrator account on the XP units and
copy the old profile to the new profile and should be good to go.

right? or will this not work?

As I had mentioned before I don't have the disk space to do an in place
upgrade and I would rather avoid installing NT4 BDC, promote to PDC,
then to upgrade it to 2003. This may be what I have to do if none of
the above is feasible.

Thanks again and I welcome comments and thoughts from the other gurus
as well.
Back to top
Herb Martin
Guest





Posted: Sun Jan 09, 2005 2:05 am    Post subject: Re: New 2003 server to be DC in small NT 4.0 network Reply with quote

"gunit" <gregs@branchgroup.com> wrote in message
news:1105206092.983121.251600@c13g2000cwb.googlegroups.com...
Quote:
They can, but along with the new user accounts you will
need new computer accounts; you will have problems with
any permissions you use (new accounts even with the same
name are not the same person); and you may lose your user
profiles unless you know precisely what you are doing.

It's easy to migrate the user profiles but it is also easy to
lose them.

To confirm...
1) I can create a new 2003 Standard Server with the same domain name
and same server name as my NT 4.0 server (not while attached to the
existing network)
2) Create the user accounts
3) Restore the user data
4) Setup the user rights to the data. This is very basic... pretty
much all users have the exact same rights to several application data
directories which has almost all of the data stored on the server.
Then of course their home directory.
5) Make sure DNS and DHCP are setup also on 2003 server.
5) Shutdown and remove the NT4 server.
6) Put 2003 server in place of NT4.

If I can do everything up to this point what do I need to do to get the
existing XP computers to become a part of the (same) domain name that
now exists on the 2003 server? I know if it was a different domain
name I would join that new domain, but if the domain name is the same
how do I get the existing XP units that were already a part of a domain
with the same name to be a part of the new domain of the same name?

Or should I make it a different domain so I can have the XP units join
the domain.

It will work either way. At worst the XP boxes will
have to leave their current domain -- take down the
old PDC etc. -- then have them join the new domain.

They are also going to use DNS preferentially for
names resolution so you are going to have a DNS
type name, e.g., Domain.Com instead of just DOMAIN.
(There is still the issue of the NetBIOS so you will
have to remove the old PDC etc.)

Quote:
Then to confirm...

1) If I get the XP units to join the domain the profiles should be new
ones on the XP units.

By default.

Quote:
2) I can then login as an administrator account on the XP units and
copy the old profile to the new profile and should be good to go.
right? or will this not work?

I have done it: xcopy /s /c /h /r source destination 1>2 1>c:\log.txt

That complicated 1>2 1>log.txt is to get BOTH the standard
output AND the standard ERROR into the log file together so
you can read them as they should be read.

Quote:
As I had mentioned before I don't have the disk space to do an in place
upgrade and I would rather avoid installing NT4 BDC, promote to PDC,
then to upgrade it to 2003. This may be what I have to do if none of
the above is feasible.

I bet I could get the upgrade done (unless you have a REALLY) small
drive or an impossible BIOS --- generally you have to update
the BIOS on NT machines to get Win2003 or even Win2000 to work.

Quote:
Thanks again and I welcome comments and thoughts from the other gurus
as well.

I am just another hacker.

--
Herb Martin


>
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Migration All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB