Vista - Roaming profile not copied to server on log-off

Hello,

I have joined a Windows 2003 (AD) domain successfully. I can log in to the
domain accounts on the local machine.

When I log in, I do NOT receive an error which says my "profile could not be
loaded properly", and on the server profiles share I DO see that a
"<username>.V2" directory is created by the Vista host with permissions that
make the share fully accessible to the user only. At this stage the
directory is empty.

After logging off, the directory remains empty - no profile data was saved.
Windows XP clients are working fine. I do not receive any error messages
during logout.

The client is Windows Vista Ultimate OEM.

The only error I receive is an information message referring to
"TrustedInstaller" not listening on an event hook. This message occurs
during login, and is not repeated during log out.

Log Name: Application
Source: Microsoft-Windows-Winlogon
Date: 18/02/2007 21:54:52
Event ID: 6003
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: arwen.internal.adixein.com
Description:
The winlogon notification subscriber <TrustedInstaller> was unavailable to
handle a critical notification event.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Winlogon"
Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Wlclntfy" />
<EventID Qualifiers="32768">6003</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2007-02-18T21:54:52.000Z" />
<EventRecordID>1683</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>arwen.internal.adixein.com</Computer>
<Security />
</System>
<EventData>
<Data>TrustedInstaller</Data>
<Binary>D9060000</Binary>
</EventData>
</Event>

If anyone has any suggestions, I'd be most grateful. I am out of ideas now.

Kind regards,
Elliot.

I have the exact same issue. Other Vista clients successfully copy
back roaming profiles. Anyone have any ideas?

I have a very similar issue except I only have one computer connected to the this domain, mostly because I wanted to test this whole Vista x64 working with Windows 2003 before I screwed up all my servers.

So basically. On the Vista Workstation I redirected my 'coyote' (coyote has been a Domain admin and Domain user, I have tried setting them to both but never at the same time) documents and other folders to a different drive. Say from C: to F: Basically getting my Data off the O/S drive. When I login in with this account no message pops up as long as I have a \\domain\users\coyote\profile.V2 . However nothing ever saves to this folder. And if the folder does not exist it says access is denied to roaming profile and thus its going with my local profile. Now I remember when I first added this computer to the domain I was running Server 2003 R2 without SP2, and the workstation said I could only have a local profile. After some gyrations, I got the Vista computer to change to roaming profile, but then I got the nice access is denied error. And after that I decided best to create profile.V2 manually and change it to hidden. It along with the coyote folder has full control for the user coyote. When I created the profile.V2 it never complained about getting the roaming profile again. And Vista believes that it succeeded in getting a roaming profile because it list me (coyote) as using roaming profile on the Vista Workstation. But the profile never saves remotely. Now that I think about it could all this be because I only have one computer on the domain besides the server itself? Although it should not take these types of shortcuts. I really don't have another Vista Capable computer without critical information that I could spare so if at all possible I would like to keep this one server one workstation setup. Once I get that working I will transfer the entire network over. But if something like the roaming profile has this many problems, I am sure you can see why I would be hesitant to make the switch.

After a long thread with Microsoft themselves, it looks like there was an
issue with an ATI driver not exiting cleanly, and thus not allowing the
profile to unload. Most annoying was that the only error message we obtained
was the output from a profile trace (published in obfuscated form and MS
needs to translate), but nonetheless the profile would not unload cleanly.

The workaround was to permanently disable the ATI External Event service -
and I have yet to see any ill-effects as a result.

I'm now following this up with ATI directly.

If it's not the ATI service that is causing your issue, run MSCONFIG and
disable all of the unnecessary services and applications that start at login
and try that.

M.

"CoyoteWAN" wrote:

>
> I have a very similar issue except I only have one computer connected to
> the this domain, mostly because I wanted to test this whole Vista x64
> working with Windows 2003 before I screwed up all my servers.
>
> So basically. On the Vista Workstation I redirected my 'coyote'
> (coyote has been a Domain admin and Domain user, I have tried setting
> them to both but never at the same time) documents and other folders to
> a different drive. Say from C: to F: Basically getting my Data off the
> O/S drive. When I login in with this account no message pops up as
> long as I have a \\domain\users\coyote\profile.V2 . However nothing
> ever saves to this folder. And if the folder does not exist it says
> access is denied to roaming profile and thus its going with my local
> profile. Now I remember when I first added this computer to the domain
> I was running Server 2003 R2 without SP2, and the workstation said I
> could only have a local profile. After some gyrations, I got the Vista
> computer to change to roaming profile, but then I got the nice access is
> denied error. And after that I decided best to create profile.V2
> manually and change it to hidden. It along with the coyote folder has
> full control for the user coyote. When I created the profile.V2 it
> never complained about getting the roaming profile again. And Vista
> believes that it succeeded in getting a roaming profile because it list
> me (coyote) as using roaming profile on the Vista Workstation. But the
> profile never saves remotely. Now that I think about it could all this
> be because I only have one computer on the domain besides the server
> itself? Although it should not take these types of shortcuts. I
> really don't have another Vista Capable computer without critical
> information that I could spare so if at all possible I would like to
> keep this one server one workstation setup. Once I get that working I
> will transfer the entire network over. But if something like the
> roaming profile has this many problems, I am sure you can see why I
> would be hesitant to make the switch.
>
>
> --
> CoyoteWAN
>

Well I would hope not as I have a nice Nvidia Card in my Workstation. But at anyrate, can I simply do tests by just logging in and logging out or do I need to reboot. It seems that in Vista logging in never tries to update my profile. I say this because when I had the access denied error, it would go and logout, and then when I logged back in it would go back to my local profile, but not generate an access denied error. Those only happened during first log in after a reboot or power on.

I will try the 'great' MSCONFIG suggestion, although is it built into Vista or do I have to go get it from XP? Also, is there a way I can kind of start from scratch easily like removing the computer and user from the AD, and turning my workstation back to workgroup and then make again part of the domain. Any suggestions there or do you guys think that won't help a bit. The main thing I am trying to prevent is obviously starting from scratch on either computer. While I love to format, because I seem to do it quite often, I like to know it will solve something before I get out Partition Magic or these days just Vista x64 CD!