Hi, I've been trying to deploy a .exe file but found out that when I manually installed this .exe it is a wrapped exe. So far, these are the steps I've tried to use a batch file to copy locally the .exe and execute it but for some reason it is not pushing thru. Tried to manually execute the batch file and it is working.

Any idea on this?

Regards,

Jeff

That is not a lot of information to work with.

You'll need to provide some more details ... what exe ... what parameters ... how does the batch file look like.

Anything in the client logs when you run this (execmgr.log for example)?

Quite common scenario with rapped EXE's is that the first EXE is terminated and this finishing off the installation and fires up the detection method however a 2nd EXE is running and still installing the product so the detection methods failes. In THAT case, I use a wrapper script (vb och posh) to what for the 2nd exe to terminate. Best is if the original exe can wait for the 2nd process so that we can get that process's exit code. Otherwise its time to start processing those log files :)

Could you please provide some more info e.g. your batch script, CM12 Software Package configurations and deployment options?

Here's a vbscript example what you could use in the case the application (.exe) is starting another process and therefore the SCCM engine fails to detect the app.

Set oShell = WScript.CreateObject("WScript.Shell")
objShell.Run("setup.exe /SILENT"), 1, True
WScript.Sleep 30000

Place the .vbs to same folder as your setup.exe and configure your application's install command as: cscript.exe install.vbs (or whatever filename you prefer to use). For the detection method, use registry, files/folders or combinations of these two.

• Proposed as answer by narcoticoo 19 hours 15 minutes ago

This is a bad solution since the installation very well could take longer or short time than the WScript.Sleep function. If the installation would take longer SCCM might detect it as a failed installation due to the fact that no detection methods evaluated to true. Also, it is a good idea to return the exit-code from the objShell for troubleshooting.

Like said, just an example. Wait time can easily be increased (30seconds in my example) and the logging part can be added, that was just something you can start up working with.

Here's a vbscript example what you could use in the case the application (.exe) is starting another process and therefore the SCCM engine fails to detect the app.

Set oShell = WScript.CreateObject("WScript.Shell")
objShell.Run("setup.exe /SILENT"), 1, True
WScript.Sleep 30000

Place the .vbs to same folder as your setup.exe and configure your application's install command as: cscript.exe install.vbs (or whatever filename you prefer to use). For the detection method, use registry, files/folders or combinations of these two.

• Proposed as answer by narcoticoo Sunday, January 26, 2014 5:06 PM
• Marked as answer by jeco 6 hours 33 minutes ago

Here's a vbscript example what you could use in the case the application (.exe) is starting another process and therefore the SCCM engine fails to detect the app.

Set oShell = WScript.CreateObject("WScript.Shell")
objShell.Run("setup.exe /SILENT"), 1, True
WScript.Sleep 30000

Place the .vbs to same folder as your setup.exe and configure your application's install command as: cscript.exe install.vbs (or whatever filename you prefer to use). For the detection method, use registry, files/folders or combinations of these two.

• Proposed as answer by narcoticoo Sunday, January 26, 2014 5:06 PM
• Marked as answer by jeco Tuesday, January 28, 2014 5:50 AM

xcopy /y /e "\\servername\software distribution\LN\FP4.exe*" "c:\"

There's your error. When deploying this with ConfigMgr, it's using SYSTEM account of the targeted computer and that account doesn't have access to your \\servername\software distribution\ -share.

What you should do is to place that FP4.exe inside the package source files you're deploying the batch file with, then change the batch file to be something like this:

@echo off
xcopy /y /e ".\*.*" %systemdrive%\
%systemdrive%\fp4.exe

Why don't you deploy that exe using application model instead?  Also have tried to extract the .exe -file so that you could get those individual executables (Notes, WebEx, Your internal app) and deploy them separately?

• Proposed as answer by narcoticoo Tuesday, January 28, 2014 3:29 AM

I strongly suggest that you dump the packages for installing programs and switch to the new application model, it's a lot better than the traditional packages.

http://allthingsconfigmgr.wordpress.com/2012/06/12/package-vs-application/

http://www.windowsmanagementexperts.com/sccm-2012-applications-vs-packages/sccm-2012-applications-vs-packages.htm

ok, here's additional info:

The .exe file that I have comprises of an update for Lotus Notes client for ver 8.5.2, an update for Cisco WebEx, and an update for our internal application. As for the parameters, I havent include any parameters because when I used the .exe file, the installation failed which led me to executing this .exe inside a batch file that copies the file and locally run this, below is the code of the batch I've been using:

@echo off

:: if not exist "C:\FP4.exe" goto Action1

:: goto Action2

:: Action1

xcopy /y /e "\\servername\software distribution\LN\FP4.exe*" "c:\"

c:\FP4.exe

Exit

I tried to comment out the 2nd, 3rd, and 4th line to simplify the batch. When I used this patch, it successfully copies the file to local disk C: and execute it, but it only shows installing for the status. Checked execmgr.log and this is the log below:

Regards,

xcopy /y /e "\\servername\software distribution\LN\FP4.exe*" "c:\"

There's your error. When deploying this with ConfigMgr, it's using SYSTEM account of the targeted computer and that account doesn't have access to your \\servername\software distribution\ -share.

What you should do is to place that FP4.exe inside the package source files you're deploying the batch file with, then change the batch file to be something like this:

@echo off
xcopy /y /e ".\*.*" %systemdrive%\
%systemdrive%\fp4.exe

Why don't you deploy that exe using application model instead?  Also have tried to extract the .exe -file so that you could get those individual executables (Notes, WebEx, Your internal app) and deploy them separately?

• Proposed as answer by narcoticoo 8 hours 54 minutes ago

Actually that is my next step is to request from our global partner to break down the wrapped exe and I would rather create an application for each installers.

FYI, the shared folder where the FP4.exe is located has access to everyone, I shared this folder to everyone just for t/s purposes thinking there might be some access issues.

I tried this before using application but it failed, possibly no detection method especially for updates only, not the whole application, updates has no detection methods.

Ill try your proposed batch and see if it'll work

Thanks

Jeff

BTW, in your batch script, on the second line

xcopy /y /e ".\*.*" %systemdrive%\

".\*.*" wont this copy the whole shared folder?

Jeff

Yes, you can change it to:

xcopy /y /e ".\FP4.exe" "%systemdrive%\"

By the way.. if you're deploying this as a package why don't you just:

1. Place FP4.exe in the package
2. Add program to your package that is simple FP4.exe

?

ok, thanks, let me try this first.

Yes I did this as a package, under the Programs tab inside command line, I did put in "FP4.exe /q" failed, tried "msiexec FP4.exe" failed as well.

Jeff

Try running "FP4.exe /?" from the commandline and see if it gives you anything. Also, you can check the properties of the FP4.exe and check if there's any indicators of the packaging software used to create the exe (vendor name) and start Googling with it to check if parameters are found for their installers.

msiexec is only for MSI packages, not executables.

Issue resolved! Thanks for all replies, narcoticoo's suggestion for vbscript worked!

Here's what I did, instead of package which I normally do with .exe files, I switch over to application which was also advised by narcoticoo. For the installation program I put in "FP4.exe" and for the deployment type is script, detection method I used the vbscript that was suggested by narcoticoo and it worked.

Thanks and have a great day ahead guys! !

Jeff