Computers create multiple profiles when there is no local caching of roaming profiles in AD
Posted on 2007-10-10
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?