ZLucas
asked on
Computers create multiple profiles when there is no local caching of roaming profiles in AD
So on our network here I have some users in AD that require a roaming profile. I dissabled caching of these on the local machines, but now when they sign in, it makes for errors. Like outlook doesn't know where to find their .ost or .pst files. And it will create a new profile folder for that user. Our naming convention for profiles is as such: first.last when it makes the new folder it will call it something like: first.last.000 or first.last.PDX (PDX is the name of my domain). Any ideas on how to resolve this?
ASKER
The policy I'm using is "Delete cached copies of roaming profiles". Where can I find the other policy you're talking about? Or is it the same one?
That's the one.
Where are you linking this (or what existing policy are you using)?
Where are you linking this (or what existing policy are you using)?
ASKER
At the top of our domain under All Users_Software Installation > computer configuration > System > User Profiles.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You should be using "delete local copies of roaming profiles" as opposed to disabling it. You always require a local copy during the logon session - this is how it is supposed to work.