Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Release Notes for App Controller in System Center 2012 SP1

Updated: November 1, 2013

Applies To: System Center 2012 R2 App Controller, System Center 2012 SP1 - App Controller

These release notes contain information that is required to successfully install App Controller in System Center 2012 Service Pack 1 (SP1). They contain information that is not available in the product documentation.

Before you install and use App Controller, read these release notes. These release notes apply to App Controller in System Center 2012 SP1.

The information in this topic applies only to System Center 2012 SP1. If you are looking for the Release Notes for the original release of System Center 2012 - App Controller, see Release Notes for System Center 2012 - App Controller.

Known Issues

App Controller Setup does not add all members of local Administrators group to the Administrator user role on Windows Server 2012

Description: The 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.

Setup blocks App Controller installation if the IIS prerequisite is not present.

Description: 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.

Uninstall will not remove the App Controller database if SQL Server is using the Availability Group feature

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.

App Controller Setup crashes when loading prerequisites

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.

If you cancel App Controller upgrade, you cannot uninstall

Description: When you upgrade from a different prerelease version of App Controller to this release, 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.

Unexpected failure possible for App Controller upgrade

Description: Upgrade from the Beta release of App Controller in System Center 2012 SP1 to this release 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.

Uploading a file with non-valid characters in the file name to a Windows Azure container will fail

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.

App Controller header pane containing System Center signout might disappear

Description: The header pane and navigation pane disappear after selecting a few nodes.

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

Virtual Machines or templates copied to Windows Azure might remain locked

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.

Conflict checks are not performed when you add a data disk with the same name to a virtual machine in Windows Azure using App Controller in System Center 2012 Service Pack 1 (SP1)

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.

A virtual machine in Windows Azure cannot be reimaged using App Controller in System Center 2012 Service Pack 1 (SP1)

Description: Using this release of App Controller, you cannot reimage a virtual machine in Windows Azure either before or after deployment.

Workaround: None.

A deployed service in Windows Azure cannot be upgraded by App Controller in System Center 2012 Service Pack 1 (SP1)

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

Workaround: None.

The Properties command for a virtual machine in Windows Azure does not work in CTP2

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.

An Expired or improperly stored certificate can cause an Export job to hang in VMM

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

noteNote
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.

See Also

Concepts

App Controller

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.