Description of Update 1 for Windows Azure Pack

This article describes the following issues that are fixed in Update 1 for Windows Azure Pack.

Issues that are fixed in Update 1

Issue 1

After Windows Azure Pack Express is installed and configured on a computer that is running Windows 8.1, you receive an error message when you browse to the Administration site. This problem occurs even if the configuration step reported success.

Symptoms: On a Windows 8.1 client computer, you are routed to the following webpage:

Note In this URL, <sitename> is a placeholder for the actual website name.

Additionally, you receive the corresponding error message:

Issue 2

In the Administration site, the name that is used for the publishing certificates is "Microsoft Azure Services for Windows Server." The name for the certificates should be "Windows Azure Pack for Windows Server Tools."

Symptoms: When publishing certificates are generated, you see the certificate name as "Microsoft Azure Services for Windows Server."

Issue 3

By default, the PowerShell command Get-MgmtSvcResourceProviderConfiguration returns a decrypted password string.

Symptoms: When you run the Get-MgmtSvcResourceProviderConfiguration cmdlet in the PowerShell command prompt, you see the decrypted account password displayed in plain text.

Issue 4

Sometimes, a security token is created by using an invalid value for the key effective start time. This occurs because of the assignation of an invalid value to the KeyEffectiveTime property of the token.

Symptoms: An exception about an argument that is out of range is logged in the Tenant Site Windows event log.

Issue 5

The Dropbox source control information is not completely displayed. This occurs because you do not have access to the Consumer Settings Client ID.

Symptoms: In the websites interface, when you access the page that has the Dropbox source control settings, some information is missing.

Issue 6

In the Virtual Machine (VM) role management interface of the Tenant site, you can set maximum and minimum values for the instance counts. You can use these values when you increase or decrease the number of instances for the VM role. The minimum value is not reflected in the Tenant interface for scaling control for the VM role. This enables you to set a value lower than the minimum allowed.

Symptoms: When you set the scaling slider control for the VM role to a value that is lower than the minimum allowed, an error message is generated.

Issue 7

When you use the Tenant portal to attach a VNet to a VM or a Disk to a VM, the site waits longer than it is necessary.

Symptoms: When you use the VM interface extension in the Tenant portal to attach a VNet to a VM, there is a one-minute wait.

Issue 8

Subscription update events are not exposed through the Usage Approval API. This makes it impossible for the billing systems to stop a subscription update transaction.

Symptoms: When a subscription update transaction is requested for a user or plan that breaks any Billing System policies, the transaction is performed. This occurs because the Billing System is not notified of the event and cannot prevent the event from running.

Issue 9

Subscription Update Events are issued for transactions other than migration scenarios.

Symptoms: Billing Systems receive Subscription Update Events out of the context of migration scenarios.

Issue 10

Subscription Update Events are exposed in the "Pending Approval" state instead of the "Acknowledge" state.

Symptoms: Billing Systems receive the Subscription Update Event in the "Pending Approval" state.