So first things first….the title of this article is misleading; thus far Avid do not seem to have released a sounds pack specific for Sibelius 8 as you will see on the website when you login in (https://my.avid.com/account/orientation) the only option is for the 7.5 sounds pack. But…this works!
Now deploying Sibelius it’s self in a silent manner is (in my opinion) pretty well documented at this link – http://avid.force.com/pkb/articles/en_US/how_to/en396971.
When you get to the sounds the documentation (again in my opinion) (which can be found here – http://avid.force.com/pkb/articles/en_US/How_To/Installing-and-using-Sibelius-Sounds-across-a-network) is flaky at best not to mention the confusion around version 7/7.5/8.
For example the install path is listed as C:\Program Files (x86)\Avid\Sibelius Sounds\Sibelius 7 Sounds, well Sibelius 8 is x64 only so do we put it in the C:\Program Files folder instead? The registry entry is listed as HKEY_LOCAL_MACHINE\SOFTWARE\Avid\Sibelius Sounds\Sibelius 7 Sounds\ContentPath – well again do we update this to be ‘Sibelius 8 Sounds’?
Well as it transpires their guide is correct in all respects; however, as it states in the clear there is no silent install command for the sounds. Ultimately though its just a copy and paste operation with the addition of a registry key so lets use some PowerShell to get this software deployed! Continue reading
After a fair few months of work and with support from the team at PACKT my new book (Microsoft Application Virtualization Cookbook) is out on sale.
With over 60 recipes for the practical application of Microsoft Application Virtualization (Version 5) from every angle including…
- Setting up your first App-V infrastructure
- Deploying the software clients and prerequisites
- Sequencing applications into packages
- Publishing applications and connection groups to your clients
- Integrating with XenDesktop, Microsoft Remote Desktop Services and System Centre Configuration Manager
- and lots more!
Go into any school these days and it will be hard to avoid any shiny ‘iDevices’ and in support of that I have recently deployed AirServer by App Dynamic.
The installer is provided as an MSI although our retailer suggested a command line option to deploy and activate the software for all users of the PC; a very nice idea there is a much simpler method which involves a quick modification of the downloaded MSI using Orca. For the full guide take a look at the screenshot sequence below-
One point to note is that upon installation the installer will reach out to the AirServer website to perform product activation; as in most schools a web proxy will get in the way of this however if you allow unfiltered access to 126.96.36.199 the authentication will go through without any issues.
Another point to note – make sure you have all the prerequisites installed on any machine targeted for AirServer installation. The deployment of these is outside the scope of this document however the easiest way I have found so far is to download the full iTunes installer, unzip it (with 7zip) and deploy the MSIs inside it separately.
When trying to capture a Windows 8.1 (Enterprise 64bit for anyone that wants to keep track) using the System Centre Configuration Manager Capture Image ISO I kept getting the error message
Task Sequence: Image Capture Wizard has failed with the error code (0x00004005).
For more information, contact your system administrator or helpdesk operator.
The image was as normal as any other Windows 7 image that I had captured and included Office/some LOB applications. In addition I had used a powershell command to remove some of the built in Windows 8.1 apps.
As it turns out this error message was being generated by sysprep as I hadn’t removed the Windows 8 applications in the supported manner (as detailed here – http://support.microsoft.com/kb/2769827).
As a work around I decided to capture the image with the apps included and then remove them as part of the SCCM task sequence.
To see how I did this take a look at the screen shot sequence below.
A bit of a silly one this time round but when running a deploy/capture (with application installation half way through) SCCM 2012 task sequence just after installing the applications I got the error message.
Task sequence: <task sequence name> has failed with the error code (0x00000032). For more information, contact your system administrator or helpdesk operator.
As it turns out at the end of my application deployment phase of the task sequence I had a restart listed, however instead of being set to ‘The currently installed default operating system’ I had it set to ‘The boot image assigned to this task sequence’.
Setting this correctly to ‘The currently installed default operating system’ resolved the problem and I was back on my merry way to creating an updated OS deployment image.
Recently I came across a need to update the BIOS of a number of Dell PCs, given that the PCs were due to be re-imaged it made sense to perform the update as part of the System Centre Configuration Manager 2012 task sequence process.
To kick this process off you will need
- A need to update the BIOS – you should only update the BIOS on a PC if a later revision fixes a particular issue you are having (in my case it was a wake on LAN issue)
- The BIOS update files from the Dell Support site – on occasion you may need to perform a staged update process, for example on the Dell Optiplex 390 to go from Revision A01 to A10 you must first update to A02.
The first step of this process requires that you put the BIOS update in as a Package, follow the guide below to see how this is done.
Please note – this guide only applies to the ‘newer’ packaged style of Dell BIOS updates, the steps to identify if you have one of the newer style packages can be seen in the first three screen shots.
Next you need to include the package in the SCCM task sequence, during the process you will need this WMI query (contained within the download to make copy/paste easy)
BIOS WMI query (83 bytes, 3,760 hits)
A few points to note
- You do not want the BIOS update to trigger the restart – (I have never been able to get this to work without causing a error and stopping the task sequence)
- If you have one of the older BIOS versions you may find this list of legacy command line switches useful.
When it comes to SCCM 2012 you have a powerful bit of software to deploy software updates and applications however all of this is worthless without the SCCM 2012 client which must first be installed.
This client comes as part of any task sequence that you configure however what if you have PCs that have been previously imaged or have an older version of the client?
In this case I prefer to fall back to good old GPO/MSI deployment; Microsoft does have an article on it in Technet http://technet.microsoft.com/en-US/library/gg712298.aspx however its far from descriptive so for a full guide on deploying the System 2012 Config Manager Client see the screen shot sequence below.
For a long time we’ve been using the built in features of Windows Server to allow users to recover their own work through the ‘Previous Versions’ tab in Windows Explorer (which works on the Volume Snapshot service) however the long term plan has been to get our DPM 2012 server to do the heavy lifting instead.
When trying to extend the AD schema (as per this Technet Article) we were coming across this error message
Active Directory could not be configured because the Active Directory domain could not be found. Make sure that the domain name is properly constructed. The following example shows a properly constructed domain name: city.corp.company.com
The best fix I have found is to manually extend the schema by copying the EXE that DPM uses to extend the schema right onto your domain controller that runs the Schema Master role and running it there.
In my case that file can be found here C:\Program Files\Microsoft System Center 2012\DPM\DPM\End User Recovery
The screenshots below show how to do this in a little more detail
NB about DFS shares: If you intend on using end user recovery against shares that are using DFS you will need Hotfix KB2466048. Why this is a hotfix and not included with Windows 7 SP1 I do not know – I just hope it comes along in SP2.
On occasion it maybe necessary to forcefully remove a server from the DPM management console. Maybe you have taken the server out of use without first uninstalling the DPM client through the console or have some kind of weird issue with the server you are protecting.
Regardless if you want to force remove a server from the DPM management console it has to be done through good old PowerShell (there is no way in the UI to do this).
The instructions you need to do this are in the screenshot series below
So you’ve got your shiny new System Centre 2012 Virtual Machine Manager install up and running, Virtual Hosts are running, you’ve done P2V migrations of a few old machines all during the while you are watching the ‘Evaluation Version – xyz days remaining’ ticker counting down.
So where do I put this product key?
You may think its in settings, but that would be too obvious Microsoft instead have decided to hide it in File (blue button top left) and then in About, once in the About dialogue box you will see a nice big button that says Enter Product Key – from there on in you are on your own! (or just follow the screen shots below)