SC2012 : The WinRM settings are not configured correctly
When installing System Center 2012, if you get into the following error:
The WinRM settings are not configured correctly :
To Fix :
1. Make sure you installed all pre-requisites:
- One of the following versions of Windows operating systems:
- 64-bit edition of Windows 7 Service Pack 1 (SP1)
- 64-bit edition of Windows Server 2008 R2 with (SP1)
- Internet Information Services (IIS)
- Microsoft .NET Framework 3.51
- Windows PowerShell 2.0
Plus, depending on which component you want to install, verify that :
Prerequisite | Download | Component | ||
---|---|---|---|---|
.NET Framework 4 | Microsoft .NET Framework 4 (Standalone Installer) |
|
||
Windows Automated Installation Kit 2.0** | The Windows Automated Installation Kit (AIK) for Windows 7 |
|
||
Report Viewer 2008 SP1 Redistributable | Report Viewer Redistributable 2008 Service Pack 1 GDIPLUS.DLL Security Update |
|
||
Trial Version of Microsoft® SQL Server® 2008 R2 | Trial version of Microsoft® SQL Server® 2008 R2 |
|
||
SP1 for Microsoft® SQL Server® 2008 R2**Cumulative Update Package 4 for Microsoft SQL Server 2008 R2 SP1** | SP1 for Microsoft SQL Server 2008 R2CU4 for Microsoft SQL Server 2008 R2 SP1 |
|
||
SQL Server 2008 R2 Native Client | Three different setup files are available for installing Microsoft SQL Server 2008 R2 Native Client based on the microprocessor architecture that you are using, as indicated in the following list: |
|
||
Microsoft SQL Server 2008 R2 Command Line Utilities | Three different setup files are available for installing Microsoft SQL Server Command Line Utilities, based on the microprocessor architecture that you are using, as indicated in the following list:
|
|
||
Microsoft Analysis Management Objects | Three different setup files are available for installing Microsoft AMOs, based on the microprocessor architecture that you are using, as indicated in the following list: |
|
* App Controller depends on the installation of VMM.
** SP1 for Microsoft® SQL Server® 2008 R2, the Cumulative Update Package 4 for Microsoft SQL Server 2008 R2 SP1, and the Windows Automated Installation Kit 2.0 will need to be extracted (uncompressed). The other files ending in .exe are executable files.
The Windows Automated Installation Kit can be extracted using any ISO extraction utility. CU4 and SP1 for SQL Server should be uncompressed using the command <filename>.exe /x
—————-
2. Edit the following local computer policy settings:
- Computer Configuration / Administrative Templates / System / Credential Delegation / Allow Delegating Fresh Credentials
- Computer Configuration / Administrative Templates / System / Credential Delegation / Allow Delegating Fresh Credentials with NTLM-only Server Authentication
There are two methods that you can use to make the following policy changes. You can edit the local group policy, or you can open a command prompt and run a series of WinRM commands. If you edit the local group policy, it can take some time for the changes to take effect. If you run the WinRM commands, the changes take effect immediately.
- Computer Configuration / Administrative Templates / Windows Components / Windows Remote Management (WRM) / WinRm Client / Allow CredSSP authentication
- Computer Configuration / Administrative Templates / Windows Components / Windows Remote Management (WRM) / WinRm Client / Trusted Hosts
WinRM commands ( open the command prompt – Run as Administrator ):
winrm qc -q
winrm set winrm/config/service/auth @{CredSSP=”True”}
winrm set winrm/config/winrs @{AllowRemoteShellAccess=”True”}
winrm set winrm/config/winrs @{MaxMemoryPerShellMB=”2048″}
——————
3. If installing on a target computer, configure the target computer Windows firewall for the Unified Installer
- Click Start, click Administrative Tools, and then click Windows Firewall with Advanced Security.
- In the Windows Firewall with Advanced Security on Local Computer pane, click Inbound Rules.
- In the Actions pane, under Inbound Rules, click New Rule.
- In the New Inbound Rule Wizard, do the following:
- In Rule Type, click Port, and then click Next.
- In Protocol and Ports, click TCP, click Specific local ports, and then type 81, and then click Next.
- In Action, click Next.
- In Profile, click Next.
- In Name, type Installer Web TCP 81, and then click Finish.
- In the Actions pane, under Inbound Rules, click New Rule.
- In the New Inbound Rule Wizard, do the following:
- In Rule Type, click Port, and then click Next.
- In Protocol and Ports, click TCP, click Specific local ports, type 1433, and then click Next.
- In Action, click Next.
- In Profile, click Next.
- In Name, type Installer SQL TCP 1433, and then click Finish.
- In the Actions pane, under Inbound Rules, click New Rule.
- In the New Inbound Rule Wizard, do the following:
- In Rule Type, click Port, and then click Next.
- In Protocol and Ports, click UDP, click Specific local ports, type 1434, and then click Next.
- In Action, click Next.
- In Profile, click Next.
- In Name, type Installer SQL UDP 1434, and then click Finish.
- Close Windows Firewall with Advanced Security
Note: When you run the System Center 2012 – Unified Installer, you will be prompted for account credentials to use for installing a System Center 2012 component on a target computer. The account that you specify must be a member of the Administrators group on both the target computer and the installer computer
This worked for me and I am very grateful.
I got following message when entering WinRM commands,
WSManFault
Message = Access is denied.
Error number: -2147024891 0x80070005
And here is the System Center log
DEBUG – Creating session at server: localhost, user specified: False, username:
ERROR – WinRM is not configured on machine localhost. Exeption: System.UnauthorizedAccessException: Access is denied.
at WSManAutomation.IWSManSession.Get(Object resourceUri, Int32 flags)
at Microsoft.SystemCenter.UnifiedInstaller.Commons.EnvironmentChecks.WinRMHelper.GetConfig(Boolean useCurrentContext)
[22/05/2012 2:40:19 p.m.] WARN – The WinRM settings are not configured correctly
The WinRM setting cannot be verified on local machine.
Any suggestioins?
Hi Wayne
Are you running as Administrator?
Runas -> Administrator