/build/static/layout/Breadcrumb_cap_w.png

Uninstalling Office 2007

Hello Everyone,

We currently have Office 2007 Enterprise in our department. I have a .bat file that calls the exe and an mst to install silently. The problem is this: How do I uninstall or reinstall? Also, how do I remove the Privacy screen that pops up at first launch?

Thanks

0 Comments   [ + ] Show comments

Answers (4)

Posted by: trey_999 17 years ago
Senior Yellow Belt
0
try going to HKLM\Software\Microsoft\Windows\CurrentVersion\Unintsall and look for the software and the uninstall string.

put it in a batch file :

msiexec.exe /x {uninstallstring}
Posted by: spartacus 17 years ago
Black Belt
0
The Office 2007 article in the Package KnowledgeBase here on appdeploy details registry settings that will suppress the Privacy screen.

They are HKCU registry settings so incorporate them into your transform making sure you set a suitable keypath and then self-heal at first launch should take care of it for you.

Regards,

Spartacus
Posted by: jdolan 17 years ago
Senior Yellow Belt
0
Hello Spartacus,

Will you please elaborate on "making sure you set a suitable keypath and then self-heal at first launch". I am fairly new to this and am unsure how to do this.
Posted by: spartacus 17 years ago
Black Belt
0
Hello again,

You'll need to add a new component to the transform you have already created.
The new component could be assigned to any of one of the Office 2007 features that you know will always be installed. You could use OfficeUserData, for example but you'll need to check this particular feature exists in Office 2007, I only have Office 2003 to refer to - perhaps others with access to Office 2007 might want to suggest an alternate/better feature you could use ??
In the new component, you need to add the following registry settings (as per the Package KnowledgeBase article I referred to earlier).

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\User Settings\Product code]

"Count"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\General]
"Authorized"=dword:00009904
"ShownOptIn"=dword:00000001

Once you have done this, you then mark any one of the above values as the keypath for the component.

At the risk of over simplifying the process, what happens then is when an Office Application is launched for the first time by a user through any of the regular entry points (e.g. shortcut, double clicking a file with a registered extension &c), Windows Installer will check the keypath of the newly created component and notice it is missing for this particular user. It then instigates a "repair" of the component by creating the HKCU settings shown above for the user.

Hope this helps out,

Spartacus
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ