Release Notes for System Center 2012 - App Controller


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

These release notes contain information that is required to successfully install System Center 2012 - App Controller. 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 System Center 2012 - App Controller.

If you are looking for the Release Notes for App Controller in System Center 2012 Service Pack 1 (SP1), see Release Notes for App Controller in System Center 2012 Service Pack 1.

Known Issues

App Controller cannot share SQL Server instance

Description: You receive the following error when specifying a SQL Server instance that previously contained an App Controller database: App Controller SQL Agent jobs installed. App Controller cannot share SQL Server instance.

Cause: Previous builds of App Controller did not correctly remove the SQL Server Agent Jobs when removing the database.

Workaround: Manually remove the two SQL Server Agent jobs that begin with CloudManager, and then attempt App Controller Setup again.

App Controller appears to stop responding when checking for updates

Description: Setup appears to “hang” or stop responding when checking for updates after clicking Install on the first screen of setup.

Cause: App Controller is unable to check for updates on Microsoft Update and takes around 7-10 minutes before returning to setup.

Workaround: Ensure there is connectivity to the Internet when checking for updates. For additional troubleshooting information, see Microsoft Knowledge Base article 836941 (

Error when running Setup after an uninstall

Description: If you run Setup after uninstalling App Controller on the same computer, you might see Setup return an error.

Cause: After uninstalling App Controller, a race condition can occur with configuring the IIS website.

Workaround: After uninstalling App Controller, restart the computer before you run Setup again.

Cannot connect to App Controller after running Setup

Description: Cannot navigate to App Controller after installing.

Cause: The SSL certificate that was specified during Setup was not valid.

Workaround: Use the IIS Management Console to change the SSL certificate used by App Controller.

Certain characters cannot be used in VMM user role names

Description: An error is reported when using certain characters in a VMM user role name with App Controller.

Cause: App Controller does not support VMM user role names that end with '.' or contain '+'.

Workaround: App Controller can be configured to support '+' in user role names. For more information, see the article at Microsoft Support.

Overlapping tooltips and error messages

Description: Tooltips and error messages can overlap text fields when using a high DPI setting, or a browser zoom other than 100%.

Cause: Incorrect calculation of the location to display the tooltip or error message.

Workaround: Change the browser zoom or DPI setting.

No keyboard input during console connection

Description: Console session for virtual machine does not accept keyboard input.

Cause: Virtual machine has lost keyboard focus.

Workaround: Click the Reconnect button to regain keyboard focus for virtual machine.

Keyboard navigation issues

Description: Difficulty using only the keyboard to navigate.

Cause: Keyboard focus is not always clearly shown.

Workaround: Use a mouse or other pointing device.

Changing ownership of virtual machine

Description: A member of a self-service user role is unable to change the ownership of a virtual machine to another user.

Workaround: Have an App Controller Administrator change ownership of the virtual machine.

Windows Azure .cscfg files created in App Controller might not work as expected

Description: Any .cscfg files created by a prerelease version of App Controller might not work correctly when used in a region other than the one for which it was created, because the expiration date might be misinterpreted (for example, the month and day transposed) or might not be readable at all.

Cause: App Controller did not store the expiration date in ISO 8601 format (for example, “2008-04-10T06:30:00.0000000-07:00”), but instead stored it in the short date format for the local region (for example, “10/25/2012”).

Workaround: Edit the .cscfg file in a text file editor such as Notepad, and change the Expiration Date to ISO 8601 format or upgrade to the release version of App Controller.

App Controller site might not connect when published

Description: When you publish the App Controller site such that the publishing rule maps the external IP address of the server to the internal site that is part of an isolated domain for App Controller, you might see a security exception.

Cause: When the App Controller site is being downloaded from one site, but Silverlight is trying to send requests to a different site, Silverlight cross-site protection triggers the security exception.

Workaround: Configure a clientaccesspolicy.xml file as described in Making a Service Available Across Domain Boundaries. Place the file in %programfiles%\System Center 2012\App Controller\wwwroot and reload the Silverlight client.

Import of VMM library certificates might not succeed

Description: When you access App Controller from a browser that is running on the App Controller server, you might not be able to successfully import VMM library certificates.

Workaround: Import the library certificates from a remote browser session.

Administrators can sign in to App Controller but cannot see settings

Description: Running the Repair option on App Controller from the Programs and Features control panel removes database configuration information for App Controller. Without this configuration information, App Controller services are not able to connect to the database. Administrators can sign in to App Controller but cannot see App Controller settings.

Fix: Download and install App Controller Update Rollup 1 (UR1) from Microsoft Update (available April 10, 2012).

Workaround: If App Controller UR1 is not or cannot be installed, the following changes can be made to restore the database configuration. In the Microsoft.SystemCenter.CloudManager.Providers.System.exe.config file, set the connection strings from following:

                <add name="CloudSystemsContainer" connectionString="" providerName="System.Data.EntityClient"/>  
                <add name="AuthorizationEntities" connectionString="" providerName="System.Data.EntityClient"/>  
                <add name="JobsDataContext" connectionString="" providerName="System.Data.EntityClient"/>  

To the following (where [DATASOURCE] is the SQL Server data source used for the App Controller database (such as localhost\instance1) and [DATABASENAME] is the App Controller database name):

                <add name="CloudSystemsContainer" connectionString="metadata=res://Microsoft.SystemCenter.CloudManager.Providers.System/CloudSystems.csdl|res://Microsoft.SystemCenter.CloudManager.Providers.System/CloudSystems.ssdl|res://Microsoft.SystemCenter.CloudManager.Providers.System/CloudSystems.msl;provider=System.Data.SqlClient;provider connection string="Data Source=[DATASOURCE];Initial Catalog==[DATABASENAME];Integrated Security=True;MultipleActiveResultSets=True;Connect Timeout=30"" providerName="System.Data.EntityClient"/>  
                <add name="AuthorizationEntities" connectionString="metadata=res://Microsoft.SystemCenter.CloudManager.Providers.System.Common/Authorization.csdl|res://Microsoft.SystemCenter.CloudManager.Providers.System.Common/Authorization.ssdl|res://Microsoft.SystemCenter.CloudManager.Providers.System.Common/Authorization.msl;provider=System.Data.SqlClient;provider connection string="Data Source=[DATASOURCE];Initial Catalog==[DATABASENAME];Integrated Security=True;MultipleActiveResultSets=True;Connect Timeout=30"" providerName="System.Data.EntityClient"/>  
                <add name="JobsDataContext" connectionString="metadata=res://Microsoft.SystemCenter.CloudManager.Providers.JobHandler/JobsEntityModel.csdl|res://Microsoft.SystemCenter.CloudManager.Providers.JobHandler/JobsEntityModel.ssdl|res://Microsoft.SystemCenter.CloudManager.Providers.JobHandler/JobsEntityModel.msl;provider=System.Data.SqlClient;provider connection string="Data Source=[DATASOURCE];Initial Catalog==[DATABASENAME];Integrated Security=True;MultipleActiveResultSets=True;Connect Timeout=30"" providerName="System.Data.EntityClient"/>  

Using ENTER to accept characters in the Input Method Editor (IME) clicks the OK button in dialog boxes

Description: When you press the ENTER key to accept characters in the IME, the keypress event is treated as an OK command in App Controller dialog boxes.

Workaround: Use the mouse or the numeric keypad to select IME characters.

See Also

App Controller