What is Update Rollup 1 for Windows Azure Pack? And do I need it?
As with any enterprise-class software, Windows Azure Pack is routinely patched and updated to address performance issues and security flaws and improve features or concerns. Many installations allow software to automatically update through the Windows Update feature. To find the latest update status, open the Windows Server Control Panel and select System and Security, Windows Update. If the Install automatic updates setting is selected, the server should already receive updates such as Update 1 (also known as Update Rollup 1, or UR1). If this is not selected, you'll probably need to manually download and install the update, if desired. UR1 is an optional update.
Always protect Windows Azure Pack servers with backups or snapshots before attempting any patching or upgrades. Given the level of sophistication and complex interdependencies involved with Windows Azure Pack, there may be some situations when the patch or update installation fails and requires a rollback to the previous "known good" working state.
If your organization needs a rollback after applying Update Rollup 1, it's possible for an IT professional to recover the prior state by simply applying the last known good snapshot of each server or virtual machine (even if the update only fails on one component server). Doing this will prevent discontinuity and further errors that might occur from a partial update. If there is no snapshot, administrators will need to uninstall the update, reinstall Windows Azure Pack, and replace the Content, Manifest and Web.Config folder contents from backups.
Issues like rollback or recovery are a good reminder to test updates and patches in a lab setting before rolling updates out to the production environment. This offers an opportunity to test the update process and find workarounds to potential problems in advance.
Dig Deeper on Microsoft Windows Azure and cloud computing
Related Q&A from Stephen J. Bigelow
Not all hypervisors and OSes can play nice with others. The best method for avoiding complications down the road is to thoroughly test your nested ...continue reading
Theoretically, there is no limit on how 'deep' a nested VM can go. The best way to avoid any confusion is to appropriately label hypervisor nesting ...continue reading
Interested in giving nested virtualization a try in your data center? There are a few software and hardware requirements you'll have to meet first.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.