Along with Update Rollup 2 for System Center 2012 R2 (KB2932881), also Update 2 (KB2932946) for Windows Azure Pack was released. Update 2 fixes 10 known issues, amongst others a fix for the problem created with the Usage Collector in Update 1. Because WAP does not currently support rolling upgrades, it is necessary to schedule downtime for the WAP machines. Please be careful running this update in your production environment and expose them to a test environment first. There are so many components which depend on each other so take any precautions in the form of checkpoints (formerly called Hyper-V snapshots) and make sure you have recent full backups of your environment.
Although it is stated nowhere, you would be advised to first start with the System Center 2012 R2 Update Rollup 2 and run the documented SQL Scripts for VMM and SCOM first (important!) before you approve the Windows Azure Pack Update 2 installation. The SQL Script for VMM can be found in http://support.microsoft.com/kb/2932926. A reference to the path of the SQL Scripts for the SCOM OperationsManager and OperationsManagerDW databases can be found in http://support.microsoft.com/kb/2929891.
Windows Azure Pack Update 2 solves the following issues:
The PowerShell cmdlets “Get-MgmtSvcSubscription”, “Get-MgmtSvcPlan”, “Get-MgmtSvcAddOn” cannot retrieve a Subscription, a Plan, or AddOn through a specific Subscription, Plan, or AddOn ID respectively.
Symptom: When using these PowerShell cmdlets to retrieve the corresponding objects, the objects are retrieved by name rather than by Id.
Resolution: Now the parameter with corresponding Id can be used to retrieve the corresponding object.
Usage Collector Service loses its current web.config settings after applying Windows Azure Pack Update 1 if instructions in the corresponding KB Article are not followed.
Symptom: When you deploy Update 1 over an existing deployment with the Usage Collector Service configured and fully functional, you will notice that the Usage Service stops working.
Resolution: This issues does not occur with Update 2, the Usage Service configuration is preserved and no manual steps are required. Notice that if you already applied Update 1 and did not fix this issue with the manual steps provided in the corresponding KB article, Update 2 will not fix it automatically; you still need to solve it manually.
Plan Creation Events exposed by the Usage API have a NULL value for the display name.
Symptom: Any Service receiving notifications or querying usage data will find the Plan Display Name to be NULL.
Resolution: With Update 2 the Display name value is passed instead of NULL. Notice that any already stored data prior to Update 2 will still show NULL for the Display Name.
The Web Application Gallery Service generates a large amount of temp files in its Temp folder.
Symptom: Every time the WebAppGallery service restarts it creates a new temp folder– the temp folder stores the cached feeds containing the Metadata of the available gallery applications and their dependencies and the actual application packages. The service is scheduled to restart every 1740 minutes which explains the growing number of temp files over time.
Resolution: The old WebAppGallery temp files are removed.
Resizing dynamic memory VMs through machine profiles results in an error when the new Startup Memory value wasn’t in the range between original Minimum memory and Maximum memory. Also changing between static to dynamic on vice versa in the machine profile results in error.
Symptom: When a tenant user sets the Start value of the dynamic memory VM to a value higher than the original maximum value or less then original minimum value an error is generated and the operation fails. Changing from Static to Dynamic did not change the kind of memory, only new memory value was set as Startup value in the profile.
Resolution: This is now possible with Update 2 and no errors are generated.
Active Directory was not enabled for Windows Azure Pack WebSites Resource Provider.
Symptom: Administrators had no way of configuring WebSites Clouds to use Active Directory. Tenants have no way of enabling Active Directory Account Management and Authentication for their Web Sites.
Resolution: In Update 2 this is available for Administrators to configure and for Tenants to use. The Admin has the option of always requiring Windows Authentication, in which case, tenants no longer have an option.
It is difficult to discover how to create Co-Administrators for an existing subscription.
Symptom: Tenant users tend to go to “My Account” and “Subscription” drawer and pane, but do not see an option there to create Co-Administrator.
Resolution: In this Update we have added a link to the “My Account” drawer set of options. This link will be enabled once the user has a valid subscription.
Error messages in Admin Site that refer to un-configured services in a Plan are not explicit as to what are the problems.
Symptom: when trying to update a Plan, for example when making it public, an error is generated if any of the Resource Providers it contains are not configured, this message does not mention what is the problem or which Resource Providers are affected.
Resolution: In Update 2 the messages are more informative and the user can take corresponding actions.
Obscured error is returned when a Tenant creates a database using a security token whose corresponding password does not meet the SQL Server domain policies.
Symptom: The user receives an unrelated SQL error regarding a select statement containing an invalid column (or an Internal Server Error message, depending on whether the created database belong to an Always On availability group).
Resolution: With Update 2 the tenant now sees the correct error and can take action to resolve it by changing the credential password.
Windows Azure Pack Management Databases were not created as partially contained when SQL Always-On was desired.
Symptom: When using SQL Always-On the user was forced to manually replicate the associated database logins.
Resolution: With Update 2 the administrator does not need to manually replicate the database logins.
These installation instructions are for the following Windows Azure Pack components:
- Tenant site
- Tenant API
- Tenant Public API
- Administration site
- Administration API
- Windows Authentication
- Microsoft SQL
- Web Application Gallery
- Configuration site
- Best Practices Analyzer
- PowerShell API
To install the update .msi files for each Windows Azure Pack (WAP) component, follow these steps:
- If the system is currently operational (handling customer traffic), schedule downtime for the WAP machines. WAP does not currently support rolling upgrades.
- Stop or redirect customer traffic to sites you consider adequate.
Create backups of the computers.
- This update does not include database changes, backing up and restoring databases is not necessary. In general, it is recommended to keep current database backups.
- If you are using Virtual Machines, take snapshots of their current state. Otherwise, go to the next step.
- If you are not using VM’s, take a backup of each MgmtSvc-* folder inside inetpub directory on each machine having a WAP component installed.
- Also collect information and files related to your certificates, host headers, or any port changes.
Important: Make sure to create a backup of the Windows Azure Pack Usage Extension Site and Application Pool settings before doing the update. You can do so by following this step:
In the computer containing the Usage Collector create a backup of the Usage Collector Site and Application Pool settings by running the following 2 appcmd commands:
%systemroot%\system32\inetsrv\appcmd.exe set site MgmtSvc-UsageCollector /name:MgmtSvc-UsageCollector.backup
%systemroot%\system32\inetsrv\appcmd.exe set config /section:applicationPools /[name=’MgmtSvc-UsageCollector’].name:MgmtSvc-UsageCollector.backup
- The Update .msi process will use these backups to restore the settings for this site. This manual step is required because the corresponding site .msi for the RTM and Update 1 releases did not include this step. With this Update (Update 2) the msi does include it, so that the next update will not require this manual step.
- Perform Update using Microsoft Update either directly on each node or through the Windows Server Update Services (WSUS) Server.
For each node under Load Balancing, run the updates for components in the following order:
- Update Resource Providers (RP’s) services (SQL Server, My SQL, SPF/VMM, Web Sites) as needed, make sure the RP sites are running.
- Update the Tenant API Site, Public Tenant API, and Admin API nodes.
- Update the Admin and Tenant Sites.
- If everything is updated and functioning as expected, you can proceed to open the traffic to your updated nodes. Otherwise see Rollback steps.
Update Rollback Instructions
In case an issue occurs and you determine that a rollback is necessary, follow these steps:
- If a snapshot is available from step 3.a then apply snapshots, if there are no snapshots continue with the next steps
- Uninstall the update from Microsoft Update or Uninstall programs
- Reinstall RTM bits from Web PI and DO NOT run the Config wizard. And reinstall the Update 1 bits from Windows Update if you have them to start with.
Replace following items from backup folders to RTM bits
- Content folder
- Manifest folder
- Web.Config file
- Apply any changes associated to your certificates, host headers, and/or port changes
- Do not leave the system in partially updated state. Perform rollback operations on all machines having WAP installed even if update failed on one node.
- Recommended: Run the Windows Azure Pack Best Practice Analyzer on each WAP node to ensure configuration items are correct
You can now proceed to open the traffic to your updated nodes.
|File that changed||Size (KB)||Version|