Hi All,
Just wanted to post this here as although I found odd bits of advice online, I couldn't find a complete solution. Hopefully this helps someone!
Deploying Sibelius using the packaged .exe and passing the command line parameters recommended by Avid does not work with SCCM under the local system account. It also fails if you specify an account which has local admin priviledges on the machine in question.
This is what you need to do - these instructions focus on SCCM but the principles should work for any deployment system.
1. Firstly, clear out your %temp% folder so you can see the wood for the trees...
2. Run the installer on a temporary machine, allow it to extract in the background. The main MSI extracts before the installer starts asking questions, but the prerequisites don't extract until you've started the install off.
3. In %temp%, you will find a folder named with a GUID, inside this will be a Sibelius.msi file. Copy this entire folder to somewhere safe.
4. As this installer progresses, another folder named with a GUID appears in %temp%, containing 6 x VCRedist files. Copy this entire folder to somewhere safe. You have to be quick with this, as the installer mops them up once installed. There is also an AVID desktop link folder inside this, which isn't required.
5. Once Sibelius has installed, go into your c:windowsinstaller folder, and search for msi files with todays date. The msi files in this folder are named randomly. You can right click and check the details to make sure you have the right one - you are looking for Sibelius OpenType Fonts. Copy this file and put it somewhere safe, rename it to Sibelius Fonts.msi or whatever.
So you should now have a Sibelius.msi, Sibelius Fonts.msi, and 6 x VCRedist.exe files.
6. Put the various VCRedist exe files into a single folder, and inside this create a file and call it something like VCRedist.cmd, inside it paste the following...
7. Then build a package in SCCM for this and deploy/apply via task sequence
8. For Sibelius and fonts, these can be created as applications in SCCM and deployed / applied via task sequences in the usual way. Sibelius.msi needs additional command line paramaters to specify the license server and the log path, e.g.