I wasn't aware of the Export Manifest option in the sequencer. I'll be diving in to that shortly. And thanks for reminding me about ProcMon.
Much obliged to you for taking the time to answer my questions.
Package scripts are added either to those external DeploymentConfig.xml files or better done in the internal AppXManifest file.
To access the internal file, in the sequence editor go to the advanced tab and export the manifest. Then use the free tool AppXManifestEditor downloaded from the resources section of this site. Make the edits, save, then import from the same advanced tab and save off the package. The alternative to this is avoid reopening the package and to use TMEdit tool (also on this site but not free) against your already saved package.
Depending on how published, you want to edit either the MachineConfig/PublishGlobal script or UserConfig/PublishUser script. The path is a system EXE without command line arguments, like "cmd.exe" or "powershell.exe", or "regedit.exe" and EVERYTHING else goes in the arguments field. You can import reg settings or copy a file from network share/homedrive inside the package or whatever you need.
You'll probably want to procmon against adding the license on a native install to see what's going on when the license is applied.
Thanks for the reply. It doesn’t use Flexnet. The license key is required to be entered during the install. I’ll have a look through the registry and the install folder to see if I can spot anything. Can you expand on your final sentence. I’m not up to speed on PublishPackage scripts. Thanks again.
It depends on the specifics of how the application controls its licenses.
If the app uses Flexnet licensing, you just do as you normally would with your flex server.
Otherwise, if you can script adding a license to an unlicensed installed copy, then you can use that technique with App-V. Depending on the app, this might mean populating the registry, copying a file, or running a command. Typically this would be in the form of a PublishPackage script to inject the license when the package is delivered to the client.
My first post to the forum and best wishes to everyone.
Here is my problem.
I look after 9 Secondary schools and they all use the same software, but have purchased individual site (school) licenses.
My question is this. How can I use App-V 5 to create just one virtualised application, but also manage the license for each school?
I'd prefer not to create 9 different applications that are all essentially the same apart from the licensing, which is applied during the sequencing.
The schools are part of a single domain in Active Directory, so have access to Group Policy and network shares, etc.