>we recently had to replace a defective PC and the new PC came with Vista[color=blue]
>preinstalled[/color]

you replaced a defective pc with a new one that has a defective OS, also
known as vista.


"Michael Arm" <muellcollectingbox********.com> wrote in message
news:#wgbfeGYJHA.556@TK2MSFTNGP06.phx.gbl...[color=blue]
> Hello,
>
> we recently had to replace a defective PC and the new PC came with Vista
> preinstalled. So we thought it would be a good idea to try it out.
>
> I joined the Vista PC to our 2003 Server Active Directory Domain
> (previously a 2000 AD, but the 2000 Server is now only a Fileserver for
> the roaming profiles).
>
> Now everytime I log in, I get a speech bubble in the lower right telling
> me, that my profile was not loaded correctly, and that I'm now signed in
> with a temporary profile.
>
> However, when I go to a Windows XP PC right next to the Vista PC, I can
> log in without problems, and my profile gets copied from the server.
>
> I found several websites about this problem, but all sites I found deal
> with stand alone PC's where Vista has to deal with a corrupted user
> profile, and the user should delete his User directory and delete a backup
> registry key of his unique identifier.
>
> However, this is of no help in my case, as Vista doesn't have my user
> directory in the "User" directory, and also not the *.bak entry in the
> registry.
>
> Even newly created domain users get a temporary profile in Vista, and if
> logged in via Windows XP, it neatly creates a roaming profile for the user
> and stores it on the server.
>
> How do I convince Vista to just get the roaming profile?
> I already forced Vista via Group Policy to wait for the network before
> logon, to no avail.
>
> With kind regards,
> Michael Arm
>
> P.S. The new PC had a Windows XP downgrade license, so it's currently
> working with XP, but that's not a "future proof" solution in the long
> run...
>[/color]