Software Deployment

I'm trying to deploy an application from SCCM 2012 to Windows 7 x64 clients.

I need to run Setup.exe (with switches) and copy an XML configuration file to the installation directory.  So I wrote a VBS script called 'install.vbs':

---------------------------------------------------------------------------
Set objShell = CreateObject("Wscript.Shell")
strArgument = "Setup.exe /s /w /v" & chr(34) & "/qn /L*vx+ \" & chr(34) & "%temp%\AppNInstallation.log\" & chr(34) & " EULAACCEPTED=YES" & chr(34)
objShell.Run(strArgument), 0, TRUE
Set objShell = Nothing

Set filesys = CreateObject("Scripting.FileSystemObject")
If filesys.FileExists("BusinessSystemSettings.xml") Then
filesys.CopyFile "BusinessSystemSettings.xml", "C:\ProgramData\TheCompany\AppN\"
End If
---------------------------------------------------------------------------

When I run the script locally, things go perfectly.  When I run it as an application deployment from SCCM 2012 it errors out.  So, I took a look at what was happening.

When I double click the script (or run it from an elevated command prompt) Setup.exe runs as 'Setup.exe *32'.  When the script is run from SCCM 2012, Setup.exe runs as 'Setup.exe' (which I believe to be in a 64-bit context).  When I tried to deploy without using the /s switch on Setup.exe, I see the error message: "Windows Installer: The installation package could not be opened.  Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package."

I researched the question of how to create Wscript.Shell as 32-bit within the script, but I didn't come up with a method.

Then I tried checking the box "Run installation and uninstall program as 32-bit process on 64-bit clients".  When I tried to deploy the application that way, I got.....nothing.  Nothing happened. I see a process for 'wscript.exe *32' appear, but nothing gets executed.  I tried changing the script to:

----------------------------------------------------------------------------------------------
MsgBox("Working?")
----------------------------------------------------------------------------------------------

But still nothing.  No msgbox popped up.

I'm stumped, and suffering from a lack of understanding.

Can someone offer some guidance?

Thanks.



QUICK UPDATE:

I have found out that anytime this setup.exe is run under the system account (nt authority\system) that this error occurs.  I tried it using PsExec and I came across the same problem.  Another application by the same vendor has the same problem.  i tried getting to the msi directly, but there are multiple prerequisites that are also installed by the setup.exe, (and I can't make heads or tails out of it).  Any ideas?

Thanks.

NEWEST UPDATE 12/4/14

Following the information from EdT, I looked at the changes made to the user folder when I installed the application under the context of my own username.  I noticed that it stores the msi during installation in 'C:\Users\\AppData\Local\Downloaded Installations'.  Could it be that because the LocalSystem account doesn't have a user folder that it's erroring out when it tries to do that step?  Or is the installation using an environmental variable that gives it an equivalent path when installing under LocalSystem?  I'll investigate, but any additional information would be appreciated.

Thanks.

Asked 9 years ago 7045 views