R
Rich
It seems like whenever we roll out a new version of 3rd party software, like
Acrobat Reader 9 or Firefox 3.5 as of late, the apps will not work with
non-admin users who have roaming profiles. My guess is because the
installers weren't run as them, so the roaming registry is messed up and
causes issues.
To solve it we delete the existing copy of their roaming profile, replace it
with a copy of a profile we made a couple years ago, our "default" profile
we'll call it, then after they log in they're good to go. Assuming the
necessary registry settings are done when they log in for the first time with
th enew profile, but I don't really know.
Is that how roaming profiles are supposed to work? This is a big headache
and time waster when you have lots of users.
Acrobat Reader 9 or Firefox 3.5 as of late, the apps will not work with
non-admin users who have roaming profiles. My guess is because the
installers weren't run as them, so the roaming registry is messed up and
causes issues.
To solve it we delete the existing copy of their roaming profile, replace it
with a copy of a profile we made a couple years ago, our "default" profile
we'll call it, then after they log in they're good to go. Assuming the
necessary registry settings are done when they log in for the first time with
th enew profile, but I don't really know.
Is that how roaming profiles are supposed to work? This is a big headache
and time waster when you have lots of users.