Removal of Office 2007 or 2010 triggers request for an old Lotus Notes msi

Topics: Archive - Deployment Scripts
Mar 5, 2015 at 10:55 PM
Good afternoon,

I am deploying MS O365 using toolkit version 3.6. Removal of Office 2013 non-CTR runs fine; however, any time the tool attempts to remove Office 2007 or 2010, Windows Installer requests a source location for Lotus Notes 8.5.3.msi

I searched OffScrub2007.vbs and OffScrub2010.vbs and of course did not notice anything that should trigger a request for a Notes msi. Has anyone else seen this or know what might cause it?

Thank you.
Mar 6, 2015 at 12:30 AM
Edited Mar 9, 2015 at 8:55 PM
The OffScrub scripts were at fault here. I resolved this by bypassing Component Detection in both OffScrub07.vbs and OffScrub10.vbs in line 92: (set bypass to True)

Dim fBypass_Stage1 : fBypass_Stage1 = True 'Component Detection

Verified resolved.
Marked as answer by jteuhs on 3/9/2015 at 1:55 PM
Apr 13, 2015 at 5:37 PM
Thanks for the find. I was running into this issue as well. Question, by bypassing the Component Detection, what else is it going to not discover?

Apr 13, 2015 at 7:44 PM
FYI: This is caused by the OffScrub scripts looking for a MSI Product Code GUID of an office product that just so happens to be also used by that old Lotus Notes msi Product Code GUID. A Product Code GUID Collision if you will.
Apr 19, 2015 at 5:39 PM
Parameters for Offscrub07/10/13.vbs with /BYPASS 1 will do the job (lines 171, 178, 186).

Execute-Process -Path 'cscript.exe' -Parameters ""$dirSupportFiles\OffScrub07.vbs" ClientAll /S /Q /NoCancel /BYPASS 1" -WindowStyle Hidden -IgnoreExitCodes '1,2,3'
Apr 20, 2015 at 3:29 PM
I have a problem with the OffScrub13.vbs script. It runs and I can track via event logs on the system that components are being uninstalled, Office 2013 is being uninstalled, etc. However, the process just runs and runs and runs. If I run the script standalone with the same exact commands that are in my Application it works without a problem.

Any suggestions? I have about 400 machines we are about to push the application to and half of those are Office 2013. I have been successful at killing the cscript.exe process on all the test machines and then the application continues without an issue.