Software Deployment

If NetOp is supplied as an MSI from the vendor, you need to make changes via a transform file. If you have captured the installation to you rown MSI, then where I say to do something to a transform, that 'something' can be added directly to your MSI. The reason is that it's a VERY bad idea to edit vendor-supplied MSIs.

You need to capture the registration process and add whatever changes it makes to a transform file which you will then apply to the MSI at installation time. I use a Ziff-Davis snapshot tool called In Control (Google for 'InCtrl5.ZIP').

- run the MSI
- do a 'Before' snapshot of the machine
- run the program, to trigger the registration screen
- complete the registration process
- do an 'After' snapshot of the machine
- add the *relevant* changes to a transform file (an MST)

To apply a transform to an MSI at installation time:
MSIExec /i [path_to_and_name_of_MSI] TRANSFORMS="[path_to_and_name_of_MST]" [other command-line arguments]

Note that the keyword TRANSFORMS must be plural and in upper-case. Note also that license numbers and such are often computed by reference to a workstation's computername or processor serial number (or some other property unique to a machine or user) and will therefore not be transferrable between machines!

bickyz,

Just a thought - I seem to remember that NetOp had it's own deployment tool, which handled everything for you.

I'm just not sure if that tool allows you to then 'port' over the deployment for group policy.

Failing that - VBScab has provided the information for you to progress.

Thanks,

Dunnpy