I recently upgraded a domain controller by reinstalling Windows 2003 Server
on biggerbetterfaster hardware. In my ignorance I though that the client
workstations (about 20 of them all XP Pro) would maintain the same domain
user profiles on the clients as they had before the upgrade
(username.domain). I unjoined each machine from the domain, re-installed the
DC and rejoined the client stations to the domain. Instead of utilizing the
already existing domain profile, each machine created another new profiles
called "Username.DomainName.000". This caused me have to go to each client
and move user settings around to recreate the users' desktop environments. Is
there a way I could have done it without causing myself this trouble? Is
there a more automated way to replace a DC without having to visit each
client? TIA!
Did you add the new server to the domain BEFORE promoting it to a DC, or
do you built a new Domain with a new Domain controller and just the old name?
If this was your way, you didn't upgrade you built the domain completely
new and that's the reason for joining the clients to the new builded domain
and that the user profiles are not working.
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
> I recently upgraded a domain controller by reinstalling Windows 2003
> Server on biggerbetterfaster hardware. In my ignorance I though that
> the client workstations (about 20 of them all XP Pro) would maintain
> the same domain user profiles on the clients as they had before the
> upgrade (username.domain). I unjoined each machine from the domain,
> re-installed the DC and rejoined the client stations to the domain.
> Instead of utilizing the already existing domain profile, each machine
> created another new profiles called "Username.DomainName.000". This
> caused me have to go to each client and move user settings around to
> recreate the users' desktop environments. Is there a way I could have
> done it without causing myself this trouble? Is there a more automated
> way to replace a DC without having to visit each client? TIA!
>
Thanks Meinolf. Thats kind of what I expected to hear at this point. Luckily
I got to learn that lesson on a network of only a few clients.
"Meinolf Weber" wrote:
> Hello SeriousSam,
>
> Did you add the new server to the domain BEFORE promoting it to a DC, or
> do you built a new Domain with a new Domain controller and just the old name?
> If this was your way, you didn't upgrade you built the domain completely
> new and that's the reason for joining the clients to the new builded domain
> and that the user profiles are not working.
>
> 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
>
> > I recently upgraded a domain controller by reinstalling Windows 2003
> > Server on biggerbetterfaster hardware. In my ignorance I though that
> > the client workstations (about 20 of them all XP Pro) would maintain
> > the same domain user profiles on the clients as they had before the
> > upgrade (username.domain). I unjoined each machine from the domain,
> > re-installed the DC and rejoined the client stations to the domain.
> > Instead of utilizing the already existing domain profile, each machine
> > created another new profiles called "Username.DomainName.000". This
> > caused me have to go to each client and move user settings around to
> > recreate the users' desktop environments. Is there a way I could have
> > done it without causing myself this trouble? Is there a more automated
> > way to replace a DC without having to visit each client? TIA!
> >
>
>
>
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
> Thanks Meinolf. Thats kind of what I expected to hear at this point.
> Luckily I got to learn that lesson on a network of only a few clients.
>
> "Meinolf Weber" wrote:
>
>> Hello SeriousSam,
>>
>> Did you add the new server to the domain BEFORE promoting it to a DC,
>> or do you built a new Domain with a new Domain controller and just
>> the old name? If this was your way, you didn't upgrade you built the
>> domain completely new and that's the reason for joining the clients
>> to the new builded domain and that the user profiles are not working.
>>
>> 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
>>> I recently upgraded a domain controller by reinstalling Windows 2003
>>> Server on biggerbetterfaster hardware. In my ignorance I though that
>>> the client workstations (about 20 of them all XP Pro) would maintain
>>> the same domain user profiles on the clients as they had before the
>>> upgrade (username.domain). I unjoined each machine from the domain,
>>> re-installed the DC and rejoined the client stations to the domain.
>>> Instead of utilizing the already existing domain profile, each
>>> machine created another new profiles called
>>> "Username.DomainName.000". This caused me have to go to each client
>>> and move user settings around to recreate the users' desktop
>>> environments. Is there a way I could have done it without causing
>>> myself this trouble? Is there a more automated way to replace a DC
>>> without having to visit each client? TIA!
>>>
I've been trying to contact you regarding your great contributions to
Microsoft newsgroups and online community.
Would you mind sending me an email (malu.menezes [at] microsoft.com)?
Thanks
--Malu
--
Malu Menezes [MSFT]
------------------------------
Messages posted to this newsgroup are provided "AS IS" with no warranties,
and confer no rights.
Check the Storage Solutions Division Team blog at http://blogs.technet.com/filecab
"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb669c35f8ca88d86b2ed7e4@msnews.microsoft.com...
> Hello SeriousSam,
>
> You're welcome, also for other questions.
>
> 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
>
>> Thanks Meinolf. Thats kind of what I expected to hear at this point.
>> Luckily I got to learn that lesson on a network of only a few clients.
>>
>> "Meinolf Weber" wrote:
>>
>>> Hello SeriousSam,
>>>
>>> Did you add the new server to the domain BEFORE promoting it to a DC,
>>> or do you built a new Domain with a new Domain controller and just
>>> the old name? If this was your way, you didn't upgrade you built the
>>> domain completely new and that's the reason for joining the clients
>>> to the new builded domain and that the user profiles are not working.
>>>
>>> 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
>>>> I recently upgraded a domain controller by reinstalling Windows 2003
>>>> Server on biggerbetterfaster hardware. In my ignorance I though that
>>>> the client workstations (about 20 of them all XP Pro) would maintain
>>>> the same domain user profiles on the clients as they had before the
>>>> upgrade (username.domain). I unjoined each machine from the domain,
>>>> re-installed the DC and rejoined the client stations to the domain.
>>>> Instead of utilizing the already existing domain profile, each
>>>> machine created another new profiles called
>>>> "Username.DomainName.000". This caused me have to go to each client
>>>> and move user settings around to recreate the users' desktop
>>>> environments. Is there a way I could have done it without causing
>>>> myself this trouble? Is there a more automated way to replace a DC
>>>> without having to visit each client? TIA!
>>>>
>
>
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.