So, when I run the command manually: The launcher appears with the choice between Install and Custom.
When I choose Install, I get the configuration I entered in my MSP file (the license, the installation without access).
But I just realized my mistake: I put my MSP in the UPDATES folder, and now when I select the "install now" button, the installation starts. So, can I try a WAPT package again?
WAPT and MS Office
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
That explains your problem.
You can therefore try a WAPT package again.
You can therefore try a WAPT package again.
I just tried the manual command "setup.exe /adminfile "install_sans_access.msp" and it worked. However, the window (office) appears and disappears.
When I run my package on my machine, I get information that the task is complete but nothing is installed.
When I go into the Temp files, I get the following log:
When I run my package on my machine, I get information that the task is complete but nothing is installed.
When I go into the Temp files, I get the following log:
Code: Select all
PERF: TickCount=1506718 Name=OBootStrapper::Run Description=Begin function
Operating System version: 6.1.7601 Service Pack 1. Platform ID: 2
Running on a 64-bit operating system.
Command line: "setup.exe" /adminfile "install_sans_access.MSP"
Parsing command line.
Admin patch file/path specified: c:\windows\temp\wapthsykwx\install_sans_access.MSP
Verify file signature in "c:\windows\temp\wapthsykwx\SETUP.EXE"
Verify file signature in "c:\windows\temp\wapthsykwx\PROPLUS.WW\OSETUP.DLL"
Using setup controller dll at [c:\windows\temp\wapthsykwx\PROPLUS.WW\OSETUP.DLL].
PERF: TickCount=1509078 Name=OBootStrapper::Run Description=Calling RunSetup
Opening log file C:\Windows\TEMP\SetupExe(201603151634055FC).log.
=========================================================================
PERF: TickCount=1509093 Name=RunSetup Description=Begin function
Catalyst execution began: 03/15/2016 16:34:05.
Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode]
Searching for updated versions of resource files under the 'updates' folder [c:\windows\temp\wapthsykwx\updates].
Found [0] resource files under the update folder.
Searching for default versions of resource files under the folder [c:\windows\temp\wapthsykwx].
Resource File Manager : Found (CultureTag=fr-FR) resource file at [c:\windows\temp\wapthsykwx\OFFICE.FR-FR\OSETUPUI.DLL].
Found [1] resource files under the default folder.
Resource File Manager : Current user's LCID is [1036].
Resource File Manager : Selecting resource file (File=c:\windows\temp\wapthsykwx\OFFICE.FR-FR\OSETUPUI.DLL) for CultureTag [fr-FR].
Running in [InstallExecutionMode]. Run from TEMP folder at [C:\Windows\TEMP\Setup000005fc].
Loaded resource file [C:\Windows\TEMP\Setup000005fc\OSETUPUI.DLL] (CultureTag=fr-FR).
Loaded Dll : c:\windows\temp\wapthsykwx\PROPLUS.WW\OSETUP.DLL.
Catalyst version is : 12.0.4518.1014
JobExecutionMode is InstallExecutionMode.
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-0015-040C-0000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-0016-040C-0000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-0044-040C-0000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-006E-040C-0000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-002A-040C-1000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-001A-040C-0000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-0018-040C-0000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-002C-040C-0000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-0011-0000-0000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-0019-040C-0000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-0010-040C-0000-0000000FF1CE}"
LIS: start parsing setup xml
LIS: finished parsing LIS package "{90120000-001B-040C-0000-0000000FF1CE}"
Product: PROPLUS
AddOnGroup Culture: fr-fr
AddOnId: OFFICE.FR-FR
AddOnId: ACCESS.FR-FR
AddOnId: WORD.FR-FR
AddOnId: PUBLISHER.FR-FR
AddOnId: PROOFING.FR-FR
AddOnId: OFFICE64.FR-FR
AddOnId: INFOPATH.FR-FR
AddOnId: POWERPOINT.FR-FR
AddOnId: OUTLOOK.FR-FR
AddOnId: EXCEL.FR-FR
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
The logs don't tell me anything.
If the command `setup.exe /adminfile "install.msp"` succeeds when you test it manually (without any manual intervention on your part), but your WAPT package doesn't work, that's quite strange.
If the command `setup.exe /adminfile "install.msp"` succeeds when you test it manually (without any manual intervention on your part), but your WAPT package doesn't work, that's quite strange.
Here's my procedure:
1) I run the "setup /admin" command to create my MSP configuration file.
2) I create a package with the command "wapt-get make-template path\setup.exe".
3) I modify my Python files as described above.
4) I run the package build with "wapt-get build-upload path\aiz-office2007-wapt".
5) The package automatically uploads to my repositories.
6) I associate it with a machine.
7) I run a package update and installation on that machine.
I just succeeded!! I'm now going to try your uninstallation procedure.
1) I run the "setup /admin" command to create my MSP configuration file.
2) I create a package with the command "wapt-get make-template path\setup.exe".
3) I modify my Python files as described above.
4) I run the package build with "wapt-get build-upload path\aiz-office2007-wapt".
5) The package automatically uploads to my repositories.
6) I associate it with a machine.
7) I run a package update and installation on that machine.
I just succeeded!! I'm now going to try your uninstallation procedure.
I'm having some trouble uninstalling.
I understand that I need to insert an "uninstall.xml" file, but I don't understand how it works.
I added this to my Python script: "uninstallstring = 'MsiExec.exe /qn /X{90120000-0011-0000-0000-0000000FF1CE}'" without success.
Any ideas?
I understand that I need to insert an "uninstall.xml" file, but I don't understand how it works.
I added this to my Python script: "uninstallstring = 'MsiExec.exe /qn /X{90120000-0011-0000-0000-0000000FF1CE}'" without success.
Any ideas?
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Here is the content of the uninstall.xml file for Office Pro Plus:
Here is the uninstall string that I specify at the top of setup.py:
Note that for the uninstall to work, the file must be copied to %programfiles%\Common Files\
I copy it using this command during software installation:
Code: Select all
<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
</Configuration>
Code: Select all
uninstallstring =['"%s\Common Files\microsoft shared\OFFICE15\Office Setup Controller\Setup.exe" /uninstall ProPlus /config "%s\Common Files\uninstall.xml"' % (programfiles32,programfiles32) ]
Note that for the uninstall to work, the file must be copied to %programfiles%\Common Files\
I copy it using this command during software installation:
Code: Select all
filecopyto("uninstall.xml",os.path.join(programfiles32,"Common Files"))
I'm writing to let you know that I've successfully deployed and uninstalled my Office 2007 package.
Now I need to uninstall the existing Microsoft Office Professional installation and replace it with Office Standard 2007. Is this possible?
I tried creating a new Office Standard package, but it doesn't reinstall Office; it copies it alongside the existing installation. So I have two entries in Windows, and Access is still present.
Now I need to uninstall the existing Microsoft Office Professional installation and replace it with Office Standard 2007. Is this possible?
I tried creating a new Office Standard package, but it doesn't reinstall Office; it copies it alongside the existing installation. So I have two entries in Windows, and Access is still present.
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
When creating the MSP, it is normally possible to check "Uninstall previous versions of Microsoft Office".
Otherwise, you have to resort to scripting the uninstallations.
Otherwise, you have to resort to scripting the uninstallations.
