Was this page helpful?
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Release Notes for App Controller in System Center 2012 R2


Before you install and use App Controller in System Center 2012 R2, read these release notes.

Description: Self-service users attempting to change ownership of a virtual machine that is running at a hosting service provider will fail. The App Controller UI prevents self-service users from changing ownership of such virtual machines.

Workaround: Use a member of the Tenant Administrator role to change the ownership of virtual machines that are running at a service provider.

Description: The option to convert from the Evaluation version to the Licensed version appears on the Setup page only if Microsoft .Net Framework version 3.5 is installed on the App Controller server.

Workaround: Complete the following procedure to resolve this issue:

  1. Open Server Manager, and then start the Add Roles and Features Wizard.

  2. On the Features page, expand .Net Framework 3.5 Features.

  3. Select the .Net Framework 3.5 check box (includes .Net 2.0 and 3.0).

  4. Click Next, then click Install and Close.

  5. Run App Controller Setup, and then click Upgrade from evaluation license.

  6. Follow the steps in the wizard. On the last page of the wizard you’ll get the error message that starts with "The default cmdlet processor must be assigned a non-null value before this call can be made."

  7. Open IIS Manager, and restart the IIS website.

Description: When the last virtual machine in a deployment is stopped, Windows Azure automatically stops the deployment container. Virtual machines in a stopped deployment cannot be started until the deployment is started.

Workaround: From the diagram view of the virtual machine, right-click on Deployment and then click Start. Once the deployment is started the virtual machine can be started.

Description: App Controller Setup does not add all members of the local Administrators group, but it does add the person installing the product as an App Controller Administrator.

Workaround: Manually add the members of the local Administrators group to the Administrator user role in App Controller.

Description: App Controller Setup will not allow the user to continue if IIS is not present. This occurs both on Windows Server 2012 and on Windows Server 2008 R2.

Workaround: Install the IIS role on the computer before trying Setup again.

Description: Uninstall does not remove the App Controller database.

Cause: SQL Server is using the Availability Group feature.

Workaround: After uninstalling App Controller, remove the database manually.

Description: Setup crashes when loading prerequisites.

Workaround: Run Setup again without restarting the computer. The problem might return the first time you run Setup after restarting the computer.

Description: When you upgrade a prelease version of App Controller to System Center 2012 R2, if you cancel the upgrade before it is complete, App Controller cannot be uninstalled; you will see upgrade screens instead of the uninstall screens. Similarly, silent uninstall will also not uninstall the component.

Cause: The files in the App Controller setup folder are replaced by the upgrade files.

Workaround: Successfully complete the upgrade, and then uninstall App Controller.

Description: Upgrading from a Beta release of App Controller in System Center 2012 SP1 to System Center 2012 R2 might fail. You will see a red X symbol during the App Controller management server upgrade and a pointer to the Setup logs. The final portion of the Windows Installer log will show a failure to install.

Cause: Unknown.

Workaround: Run Setup again for the upgrade without restarting the computer. Setup should finish successfully, displaying a warning for the management server upgrade warnings. However, despite the warnings, App Controller should be successfully upgraded at this point.

Description: Uploading a file to a Windows Azure container never starts a job, but you are notified that the upload failed.

Cause: There are characters in the file name that are not valid, from among the following: ^%$&)(+!@#}{.

Workaround: Change the file name to eliminate valid characters, and try again.

Description: The header pane and navigation pane in App Controller might disappear after selecting a few nodes.

Workaround: Enable "Enhanced Security Configuration" settings under Local Computer.

Description: After an SSU copies a virtual machine or virtual machine template from VMM to Windows Azure, the VMM resource may remain locked, which prevents changes to it. This means a stored virtual machine cannot be moved back to a host.

Workaround: Use the VMM console to cancel the resource Export job that was started by App Controller.

Description: When a data disk is being added to a virtual machine in Windows Azure and the virtual machine already has an existing Windows Azure data disk with the same name, the conflict will not be detected in this release of App Controller.

Workaround: None.

Description: You cannot reimage a virtual machine in Windows Azure either before or after deployment using App Controller.

Workaround: None.

Description: The Upgrade command is not available for a deployed service in Windows Azure using App Controller.

Workaround: None.

Description: In this release of App Controller in System Center 2012 Service Pack 1 (SP1), Windows Azure virtual machine properties cannot be opened. The Properties command in the taskbar does not work and the Properties command on the right-click menu does not work.

Workaround: The virtual machine properties that are available on the Virtual Machines page can be viewed.

Description: If the self-signed certificate used for evaluating App Controller is not stored in the Trusted Root Certification Authorities store on the App Controller management server and on any computer that is accessing App Controller in a browser or running Windows PowerShell commands for App Controller, some features will not work.

  • When you copy a virtual machine from VMM to Windows Azure, the export job that copies the VHD will not be allowed to close the export. This will lock up the VHD resource in VMM until someone deletes the job in VMM or the export times out.

  • Windows PowerShell commands will not run.

  • Firefox cannot be used to access App Controller 


These conditions can also be caused by an expired certificate.

Workaround: Manually set up an HTTP binding for evaluation instead of using a self-signed certificate, or ensure that you store the self-signed certificate used for evaluating App Controller in the Trusted Root Certification Authorities store on the computers listed in the description for this release note. Also, ensure that the certificate is not expired.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft