Software Deployment

I use SMS 2.0 and had the same issue the first time I tried to launch using a batch file. The solution for me at the time was to grab a freeware tool that compiled the batch file into a COM file and I think I remember that working fine. Since then, I've done most anything that I would have done in at Batch file in the SMS Installer and compiled it into an EXE. It's probably something simple, but I worked for a few days wondering why my app didn't launch on the remote computer.

Hmmm. Using Wise Script I've compiled an .exe with the same run command, however I get the same result, although this time SMS reports the advertisment as being successful, however the SQL setup doesn't start. I've confirmed this by removing the -s (install silent switch). When I run the exe manually on the client the install works fine.

There must be a setting I haven't got right on the package in SMS.
Dan.

Are u running the package with Admin priv in SMS?
Also try install with the CLient SW Installation account.

The batch files must be run with disk drive letter (any) not with UNC path. Hope it helps.

I have run into similar issues with trying to run batch files that call executables through SMS and would love to know of any other workarounds. I am currently working for a client who does not want to use the SMS Software Updates piece so were are stringing KB hotfix installs into one .BAT file. This actually does work, but whenever there is a problem with one of the hotfixes for a particular user, because the install is part of a batch file, the batch file just continues running and as long as the last line of the batch file is successful, SMS reports the whole install(s) as successful.

Here is an example of our script:

rem **Security Update KB896358 06-2005**
KB896358.exe /quiet /norestart
set exit=%errorlevel%
set failloc=2-KB896358
If NOT %exit% == 0 goto Fail
echo %failloc% installed successfully. >>C:\WINDOWS\system32\CCM\logs\Sec_Updates.log

So we are keeping a log file on the user's hard drive to track the success and failures (which works). The installs themselves do work a large majority of the time.

But at the end of our BAT file we have...

:Fail
echo %failloc% failed with error code %exit%. >>C:\WINDOWS\system32\CCM\logs\Sec_Updates.log
Rem Run qchain in case some updates have run
qchain.exe
exit /b %exit%

It's our understanding that the exit /b switch will force quit a BAT file and make it appear to SMS that the batch file has failed (which we want). We are also trying to pass SMS the errorlevel (our %exit% variable). But, we think, because the exit command actually succeeds, SMS thinks the whole batch file succeeded and returns a "Successful" install to the user.

How can we use BAT files to install multiple programs and error trap or pass errors to SMS? Others have told us Exit /B was the correct way to do this but it hasn't worked for us yet. Any help would be appreciated. Obviously we could create separate programs for each KB fix (or future combinations) but would like to avoid it if necessary.

Thanks,

Bill