Tranquil IT Forum

Hello everyone,

I'm writing to you because I'm a bit lost. I'm currently creating a package for installing Office 2016, in which I want to handle the removal of previous versions of Office, such as 2003, 2007, and 2010, beforehand.

To perform this removal, I downloaded the Microsoft Fixit tools for each Office version. When each Fixit tool is run, a temporary VBScript file is created which is sufficient to remove the various versions of Office 2003 and others.

These files are called Offscrub03.vbs (for 2003), Offscrub07.vbs (for 2007), etc.

To completely uninstall the products, simply enter the following command:

This command works perfectly when entered directly at the DOS prompt.

However, in the WAPT package code: It's not working. I'm getting the following error: We are therefore talking about rights that would be insufficient to access the register.

My question is this:
Why do we have two different results where in one case rights don't seem to be a problem at all and in the other they are? Is there another way to do this?

Thank you very much, my Waptian friends!

Hello Patrice,

Your post deserves a reply because we know each other well and we're very proud that WAPT is of interest to your large and prestigious organization (whose identity I cannot reveal out of respect for confidentiality).

I'm not the WAPT super expert, but I would suggest creating a new Office 2016 package that conflicts with your previous Office packages. So, search for "conflict" in the WAPT documentation for more information on this function.

Your previous Office packages, if they exist, will have had an uninstallation key. Therefore, running the WAPT package for your Office 2016 would uninstall the previous versions because they would conflict with the version of Office you want to install. This way, you wouldn't need to rely on a specific Microsoft VBS—magic!

This method has the added benefit of being more robust and easier to manage over time.

When everyone returns from vacation, we'll be discussing with Mr. S. and Mr. F. from Toulouse, and Mr. A. and Mr. D. from Paris, to upgrade you to the Enterprise version, which is better suited to your needs.

In the meantime, have a great summer.

Sincerely,

Vincent

It seems that the problem is "known":
https://social.technet.microsoft.com/Fo...roprevious

I had the same issue when running the script with SCCM 2012 in system context on Win7. For some reason the function CheckRegPermissions returns false. When I ran the script manually with admin rights it worked. It even worked when I tried with psexec -s \\machine cmd which launches a command prompt in system context.

I decided to delete the code in CheckRegPermissions. The script works fine now and does what it should.

Function CheckRegPermissions
CheckRegPermissions = True
End Function 'CheckRegPermissions