Hello DoctorOwl,
Forget to mention DNS is important for AD to run correct. So if you post
the DNS problem/error we can see to fix it.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> Hey,
>
> Typical small business scenario, I don't know anything about domain
> administration, I just need to get a job done.
>
> We have two development machines running Windows XP that log onto an
> NT 4 server. I want to turn off the NT 4 server because it's 10+ years
> old and not used for anything (and actually sits sideways in a rack
> with 2x 8G disks inside and 2x 8G disks literally hanging out over the
> side where they've been for the past 5 years with a bit of cardboard
> stuck between them so their electronics don't touch).
>
> As far as I can tell it just stores their profiles, it used to store
> email but we don't need that.
>
> We have a separate PDC for all our newer workstations, which I won't
> be touching. We have a spare server running Windows Server 2003 that
> was in its own workgroup which we used for other stuff. Yesterday I
> made it a primary domain controller with a new domain name using a
> wizard, it complained a little about the DNS not being right but I
> continued anyway.
>
> Now I want to point the 2 workstations at that. I'm not sure how to go
> about it.
>
> Can I just log onto the machines, go into the System settings, and
> make it join the new domain? Will that copy all the profile
> information over so they can continue to log in? Do I need to give the
> new server the same domain name as the old one and do some trusting to
> transfer the profiles over? Do I need to run some migration tool?
>
> Whatever is easiest without breaking the old machines, so I can get on
> with my real job.
>
> Thanks,
>
> http://forums.techarena.in
>