This update resolves the following issues.
Issue 1
An Advisor gateway cannot create a self-signed certificate because a key container already exists.
Issue 2
Code quality is improved by moving the add urlacl and add firewall rule operations from the SaveToRegistry assembly to the PowerShell assembly.
Issue 3
Setup in the configuration tool cannot support a computer that uses a NetBIOS name which is 15 characters or more.
Issue 4
A standard user account can register or unregister an Advisor gateway by running Windows PowerShell cmdlets.
Issue 5
The Apply button in the Advisor setup wizard is confusing because there is nothing to be applied.
Issue 6
Symptoms
The GetMonitorState cmdlet fails in System Center Advisor.
Cause
This issue occurs because the workflow list that is used by the ProcessWorkflowReport function is out of sync.
Issue 7
Symptom
The configuration information and the warning data of customers are not processed in System Center Advisor.
Cause
This issue occurs because the Model.xml data package that is published to the cloud server contains orphaned entities.
Issue 8
Symptom
The Advisor agent does not run the MPUpdate cmdlet after initial setup.
Cause
This issue occurs because the SpecifiedCreateOwner property's value is set to NULL.
Issue 9
After you perform a repair or an uninstallation of an Advisor agent by using Add Or Remove Programs, the prompt that instructs users to start the configuration tool may not appear.
Issue 10
The Advisor configuration tool that is used for setup may incorrectly reset the customized gateway port for the Advisor agent in certain conditions.
Issue 11
The Advisor configuration tool may appear incorrectly when some agents are removed from the tool.