Hello,
The pain of NT4 is growing, as I try to install NT4 server on a Dell PowerEdge with a Sata raid. Gave up on that, tried an Promise IDE raid card, and it's slow going.
I spent a few hours reading the forum, looks like one way to move is small steps...member servers while keeping the NT domain. Right now higher ups want a server at a remote location, only five to ten users. If I installed Server 2003 as a member server, from what I have read, I could later upgrade a NT PDC (formerly a BDC), then promote the Server 2003, wipe the PDC(BDC) and reinstall Server 2003, going forward on the rest of our servers (total of five.)
I have been nervous about the idea of integrating Server 2003 with NT, but feel like the member server for now should be relativly painless, and my gut says shouldn't cause problems for the NT domain. Is this correct, in your experience?
I could forsee migrating the remaining NT Workstations to XP, which would leave only two Win2000 workstations. I bet a domain with XP and one W2000 would be a bit easier than mixed with NT Workstations, comments?
Domain has total of 60 or so users (I know, five DC's seem like a lot, but three remote sites (eaiser with DC and not peer2peer.))
If we install the first member server, I can see a total of ten users max.. What about the second member server, there would be some overlap, can a member server talk to another member server and coordintate CAL's? Higher ups probably would support a 2003 server, even though we could use a workstation for ten connections--they would say it's on the job testing/training (they are good that way.)
I would really appreciate any comments about a member server 2003 in a NT domain, and CAL's. And of course, any links to good reading material is appreciated.
Thanks, thanks, thanks,
Jeff
The pain of NT4 is growing, as I try to install NT4 server on a Dell PowerEdge with a Sata raid. Gave up on that, tried an Promise IDE raid card, and it's slow going.
I spent a few hours reading the forum, looks like one way to move is small steps...member servers while keeping the NT domain. Right now higher ups want a server at a remote location, only five to ten users. If I installed Server 2003 as a member server, from what I have read, I could later upgrade a NT PDC (formerly a BDC), then promote the Server 2003, wipe the PDC(BDC) and reinstall Server 2003, going forward on the rest of our servers (total of five.)
I have been nervous about the idea of integrating Server 2003 with NT, but feel like the member server for now should be relativly painless, and my gut says shouldn't cause problems for the NT domain. Is this correct, in your experience?
I could forsee migrating the remaining NT Workstations to XP, which would leave only two Win2000 workstations. I bet a domain with XP and one W2000 would be a bit easier than mixed with NT Workstations, comments?
Domain has total of 60 or so users (I know, five DC's seem like a lot, but three remote sites (eaiser with DC and not peer2peer.))
If we install the first member server, I can see a total of ten users max.. What about the second member server, there would be some overlap, can a member server talk to another member server and coordintate CAL's? Higher ups probably would support a 2003 server, even though we could use a workstation for ten connections--they would say it's on the job testing/training (they are good that way.)
I would really appreciate any comments about a member server 2003 in a NT domain, and CAL's. And of course, any links to good reading material is appreciated.
Thanks, thanks, thanks,
Jeff