Roaming profile quandry...

[Jerry Girard]

During every log on of a client machine, the entire roaming profile is
copied from the server into a folder called "user.domain". Normally, it
uses the local folder copy "user" and only copies changes. After log off,
the entire folder "user.domain" is removed by the system.

What would cause the romaing profile to all of a sudden stop using the local
copy and be generating this weird copy? How can I get it back on track to
work with the local copy and stop generating a new folder?

Thanks.

 

[David Adner]

If there's a local account named John and a Domain account named John,
the local account's profile will be "john" while the Domain account uses
"john.domainname". This scenario assumes the local account logged on
first. Why this would suddenly happen, I'm not sure about.

 

[Jerry Girard]

Okay, that makes sense.

I logged on as Administrator and deleted the local profile folders in
question. I went to Users and Passwords, deleted the username in question
and re-assigned it. I logged off administrator and back on as the user and
the local profile was re-created correctly.

Everything works now. Thanks.

 

[Jerry Girard]

I realized now that things aren't working.

The client machine is deleting the local profile at log off and at log on,
it has to re-load the entire profile from the server. What would cause
this?

 

[David Adner]

There's a setting to delete the locally cached profiles. I believe it's
accessible via a GPO; try looking through there.

 

[Jerry Girard]

Funny thing, the option to delete at log-off is not defined in the Group
Policy for either the server side nor the client side machines. I'll set it
to disable to see if it overrides whatever is causing it.