hi guys
i have a problem with office 2007 with users, after a reboot when a user logins office 2007 always wants to run the windows installer to configure office. all users use man profiles, and i have done this in the man profile, i have open all the office programs then renamed the the ntuser to .man.
when the user logs off and logs in its fine but a reboot losses that config and windows installer starts up again.
what am i missing here? as i need to stop this from happening.
mark
Did you use an old profile that was configured for Office 2003?
ful56_uk (11th August 2009)
Nope brand new profiles. Could be a permission on the local workstation? What does and were does the installer access were in the workstations do windows installer access that they might need full control. Or a user.
Im not sure, i haven't seen this before. Someone on here had this problem when he deployed office as an MSI and also upgrading from older versions of office compared to a clean install.
ful56_uk (11th August 2009)
A full install using gpo install. In general thow is there a part of the system were users need access in order for the windows installer to config a program
Windows Installer will write to user portion of registry (HKEY_CURRENT_USER) and to files in AppData and Local App Data.
Depending on how the mandatory profiles were created, writing to the user portion of the registry can go wrong. Occasionally people try to copy a profile by dragging/dropping and then changing file permissions on the profile folder so that any user can use. This will not work properly. Profiles MUST be copied using the 'copy profile' function in the System dialog box or registry permissions will be incorrect.
Having said all that, I don't think that incorrect registry permissions would explain the problem you describe. If the Installer settings survive a logout but not a reboot, then something else must be going on. Perhaps a startup script deleting cached copies of roaming/mandatory profiles?
ful56_uk (11th August 2009)
I suspect it's a combination of problems. Are you 100% sure the roaming profile is definitely being picked up and not a new locally cached profile? As an experiment, try re-naming the roaming profile with a "1" on the end to make it unique, then change the path accordingly in AD.
If you've created a share called Profiles$ users should have Full Control to this share, otherwise it can create all kinds of weird and wonderful problems writing back to the profile.
ful56_uk (11th August 2009)
He's using mandatory profiles that aren't supposed to be written back to the server. Read/List is all that is required.Originally Posted by Michael
ful56_uk (11th August 2009)
Generally in my experience I setup one Profiles$ share for all whether it's for mandatory profiles or not. For example you wouldn't setup a domain administrator with a mandatory profile!He's using mandatory profiles that aren't supposed to be written back to the server.
ful56_uk (11th August 2009)
I wouldn't set one up with a roaming profile either BTW. I take your point however.
Your original post referred to 'writing back to the profile' which seemed to me not relevant in this case as mandatory profiles are in use and the permissions to these would surely be limited to list/read.
ful56_uk (11th August 2009)
all sorted, security permission on the profile folder, now working prefectly
cheers guys for the input
Normally administrator accounts I use on servers I use a local profile only, however for a secondary administrator account I use for workstations I do specify a roaming profile path.I wouldn't set one up with a roaming profile either BTW. I take your point however.
Can you tell us what you had to change them to?
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote