Worry about Transferring PDC from NT to Windows Server 2003
Hey everyone. Small company (50 employees) and we are running our PDC and DHCP on a very old HP PII running NT 4.0. We do have a Windows Server 2003 running on a Dell Pedge 2800 that is running as our fileserver. I would like to find out:
1) Opinion if it can handle the PDC duties as well. Considering the PII was handling it, I don't think it should be a problem. We are serving under 1TB of files.
2) Transferring the user logins. This is where I am worried. No clue how to do this. If i just rebuild them (hand type the user logins in), I am assuming that will destroy people's logins on their machines and they will lose their docs/settings, etc.
3) DHCP - Again, I think I'll have to hand exempt the IP addresses for the printers, etc.
I took over for the old head of IT, and I was left with this very ancient machine. I think he had been avoiding switching over for years and years because of the problems outlined above.
Thanks everyone.
1) Opinion if it can handle the PDC duties as well. Considering the PII was handling it, I don't think it should be a problem. We are serving under 1TB of files.
2) Transferring the user logins. This is where I am worried. No clue how to do this. If i just rebuild them (hand type the user logins in), I am assuming that will destroy people's logins on their machines and they will lose their docs/settings, etc.
3) DHCP - Again, I think I'll have to hand exempt the IP addresses for the printers, etc.
I took over for the old head of IT, and I was left with this very ancient machine. I think he had been avoiding switching over for years and years because of the problems outlined above.
Thanks everyone.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
forgot to mention, you will also have to configure FSMO roles on the new server. Mastering windows Server 2003 by Mark Minasi is a good resource book to help you get your domain configured prior to transferring the old NT stuff over.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks everyone for your input. It helps tremendously. Can anyone speak to whether or not the Pedge2800 will be fine as a PDC/DHCP while working as a fileserver at the same time?
My guess is yes since the PDC is currently on that almost 15 years old PII, but would like feedback.
Thanks!
-adam
My guess is yes since the PDC is currently on that almost 15 years old PII, but would like feedback.
Thanks!
-adam
For most the part, the activity associated with the PDC and DHCP in a single server environment only occurs when users are logging on or machines are rebooting. If you are only managing files (assuming documents like word, excel, etc and not interactive applications that are storing their data on the server), then these roles would not put a significant additional load on your hardware. IS your DNS handled by another machine? Depending on how it's configured DNS can sometimes cause resource spikes (especially when integrated with spam filters and such).
ASKER
Our DNS is being handled by a linux machine (Dell Optiplex) that runs FTP/Apache/DNS.
Then I wouldn't expect any problems unless you have some application that is constantly writing to the file server. My original 2003 server was a P3 IBM server with 512 mb of memory running PDC, DNS, DHCP, printer server, scanning software and all FSMO roles and we never had any resource issues other than some DNS timeouts.
the answer is simple I have 2650's doing the same stuff .. but the model doesn't give the specs....
but also I've had an optiplex do just that dc and dhcp and dns and print (it was temporary since the dell poweredge died.. )
dc role is only heavy when there
a. a lot of users
b. a big application load
c a lot of replication
d etc etc..
but mostly it's a mix of these factors that make a server slow of fast.
but also I've had an optiplex do just that dc and dhcp and dns and print (it was temporary since the dell poweredge died.. )
dc role is only heavy when there
a. a lot of users
b. a big application load
c a lot of replication
d etc etc..
but mostly it's a mix of these factors that make a server slow of fast.
ASKER
Hey everyone.
I am moving my PDC and DHCP this Friday after the users (55 users) have gone home at noon. I hired a consultant to come and help, but here is my next question. Which 2003 Server to put it on?
1) Pedge 2800 - Running Email (IPSwitch - 60 users), File Server, & Print Server roles. NOT under warranty any more. Ran out 1 month ago.
2) Pedge 2800 - File Server - about 1 TB. Running a few things in addition, including adobe version cue for very small creative group. Motherboard died last month and I renewed warranty and they replaced motherboard with new one.
3) Pedge R300 - Brand new. 1U. Using it only for finance group's software that they bought from proprietary company. Used by only a few people. My thinking is maybe this one??
Any and all input is appreciated!!
Thanks!
-adam
PS - Someone suggested above to make a new domain and migrate the users. How many agree that would be less tricky than using same domain name? Thoughts??
I am moving my PDC and DHCP this Friday after the users (55 users) have gone home at noon. I hired a consultant to come and help, but here is my next question. Which 2003 Server to put it on?
1) Pedge 2800 - Running Email (IPSwitch - 60 users), File Server, & Print Server roles. NOT under warranty any more. Ran out 1 month ago.
2) Pedge 2800 - File Server - about 1 TB. Running a few things in addition, including adobe version cue for very small creative group. Motherboard died last month and I renewed warranty and they replaced motherboard with new one.
3) Pedge R300 - Brand new. 1U. Using it only for finance group's software that they bought from proprietary company. Used by only a few people. My thinking is maybe this one??
Any and all input is appreciated!!
Thanks!
-adam
PS - Someone suggested above to make a new domain and migrate the users. How many agree that would be less tricky than using same domain name? Thoughts??
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.