Seit gestern steht das Update 2 für das Windows Azure Pack zur Verfügung. Damit werden die folgenden 10 Probleme behoben:
Issue 1
The PowerShell cmdlets Get-MgmtSvcSubscription, Get-MgmtSvcPlan and Get-MgmtSvcAddOn cannot retrieve a Subscription, a Plan, or AddOn through a specific Subscription, Plan, or AddOn ID, respectively.
Symptoms When you use these PowerShell cmdlets to retrieve any of these three objects, you notice that the command allows only the retrieval operation through the specific name of the objects, that you cannot retrieve base on a specific ID.
Resolution Now the parameter with a corresponding ID can be used to retrieve the corresponding object.Issue 2
Usage Collector Service loses its configuration after Windows Azure Pack Update 1 is applied.
Symptoms When you deploy Update 1 over an existing deployment by having the Usage Collector Service configured and fully functional, you notice that the Usage Service stops working.
Resolution This issue does not occur in Update 2. The Usage Service configuration is preserved and no manual steps are required.Issue 3
The Plan Creation Event provides NULL for the Plan Display Name to Services registered to receive this notification.
Symptoms For any Service that is registered to receive notifications, the Plan Display Name is passed as NULL when a Plan Creation event is generated.
Resolution In Update 2, the Display name value is passed instead of NULL.
Issue 4The Web Application Gallery Service generates a large amount of temp files in its Temp folder.
Symptoms Every time that the WebAppGallery service restarts, it creates a new temp folder. The temp folder stores the cached feeds that contains the Metadata of the available gallery applications and their dependencies and the actual application packages. The service is scheduled to restart every 1,740 minutes. This causes the growing number of temp files over time.
Resolution In Update 2, the Display name value is passed instead of NULL.
Issue 5Resizing dynamic memory virtual machines through machine profiles causes an error when the new maximum memory exceeds the original maximum memory. Also, changing between static to dynamic or vice versa in the machine profile results in an error.
Symptoms When a tenant user sets the value of the dynamic memory virtual machine to a value that is greater than the original maximum value, an error is generated and the operation fails.
Resolution This process is now possible in Update 2 and no errors are generated.
Issue 6Active Directory was not enabled for Windows Azure Pack WebSites Resource Provider.
Symptoms Administrators had no way to configure WebSites Clouds to use Active Directory. Tenants have no way of enabling Active Directory Account Management and Authentication for their websites.
Resolution In Update 2, this functionality is available for Administrators to configure and for Tenants to use.
Issue 7It is difficult to discover how to create Co-Administrators for an existing subscription.
Symptoms Tenant users typically go to “My Account” and “Subscription” drawer and pane, but do not see an option there to create Co-Administrator.
Resolution In this Update, a new link is added to the “My Account” drawer set of options.
Issue 8Error messages in Administration Site that refer to un-configured services in a Plan do not specify the problems.
Symptoms When you try to update a Plan, such as when you make it public, an error is generated if any of the Resource Providers it contains are not configured. This message does not specify the problem or which Resource Providers are affected.
Resolution In Update 2, the messages are more informative, and the user can take corresponding actions.
Issue 9Subscription Update Events are provided in the Pending Approval state instead of the Acknowledge state.
Symptoms Billing System receives the Subscription Update Event in the Pending Approval state.
Resolution In Update 2, the Billing System receives the Subscription Update Event in the correct state.
Issue 10An obscured error is returned when a Tenant creates a database by using a security token whose corresponding password does not meet the SQL Server domain policies.
Symptoms The user receives an unrelated SQL error about a SELECT statement that contains an invalid column.
Resolution In Update 2, the tenant sees the correct error and can resolve it by changing the credential password.