Client Management Suite

Dear all,

I recently find some challenging about how to create a software package inlcuding below.

1) First step is to install the hotfix (msp) file.

2) Final step is to use regsvr32 command to register a specific dll file on the target machine.

In this case, how could I cater both different task in one same software delivery task?

Actually I intend to use VB script to handle two different tasks on the altiris server but looks failed.

The script is like this
=============================================

Option Explicit
On Error Resume Next
 
Dim objShell, strCmd
 
Set objShell = WScript.CreateObject("WScript.Shell")
strCmd = "msiexec.exe /p ""\\path\hotfix.msp"" /qb"
strCmd = "regsvr32 "C:\Program Files\Software\123.dll""
objShell.Run (strCmd,2,True)

=======================================================================

Any fault from above or any suggestions on this?  Please advise.

Many thanks!

You forgot to escape the double quotes in the second command line.

strCmd = "regsvr32 ""C:\Program Files\Software\123.dll"""

 

It probably would be easier to just execute an "install.cmd" as install command line having both commands inside.

A Software Release is more than just a package and command line - it's an identity for a piece of software defined by the detection rule. You should have two separate software releases, one for the msp and one for the regsvr32 command with two separate detection rules. Then put both Software Releases into one Managed Software Delivery Policy and have the policy compliance check daily. There will almost certainly always be machines that are shut down halfway through the process, good detection rules and separation of tasks will prevent them ending up with half a job done on them. And install scripts, whether vb or windows command, almost always lose error information unless you write error handling into the script. But then you are writing your own management tool instead of using Symantec's.

I don't think a msp should ever be a release ... it's an "update" ... maybe a "service pack" (msp could be both).

And as long the regsvr32 is needed to make it work, i would never seperate it from the msp software component.

Detection rule can check both and rerunning both commands would (in this case) never harm, if already installed/registered.

As it will be installed as a Quick Delivery Task (this is what I read) the detection rule will not matter anyway, as tasks will not do any compliance check.

That's one of the problems with using a Quick Delivery Task, no Compliance check so you never know if it's worked or not. Because if you have an estate of over 1,000 PCs chances are that not all will work first time for both elements. And if you have a wrapper script then the msp install can fail, the subsequent regsvr command succeed and the overall command reports as succeeded.

Don't forget to mention the timeouts you will have for sure when using a quick delivery task. ^^

Not all computers will be available.