With the Unified Installer it's possible to install all System Center products as once, without the need to install a single product multiple times. That way products can be installed quicker and less screens are needed to install them. Just download Microsoft Private Cloud Evaluation Software first.
Then the installation begins..
- Microsoft Software License Terms
- Component Selection (Orchestrator, Virtual Machine Manager, App Controller, Operations Manager, Configuration Manager, Service Manager & Data Protection Manager)
- Keep the following in mind:
- Orchestrator is a required Product Component (Unified Installer requires Orchestrator)
- App Controller depends on Virtual Machine Manager
- I've selected Orchestrator, Operations Manager & Configuration Manager here
- Component Media Location (for all products selected)
- Configuration Manager License Terms
- Prerequisite License Terms
- Prerequisite Media Location (e.g. SQL Server 2008 R2 + SP1 + CU4)
- Installation Destination Location (for all products selected)
- Servers (for all products selected)
- Service Accounts (Installer Account)
- Component Specific Questions (e.g. OpsMgr Management Group, ConfigMgr Site Code & Site Name)
- Communications and Updates
- Installation Validation
- Deployment Progress
- Deployment Summary Report
That's all you need to do to install the Microsoft Private Cloud Evaluation software. The hardest part here is to have enough available servers, download the Microsoft Private Cloud Evaluation software and all prerequisites needed for all products. Then the rest is fairly easy.
Update 30-1: Unfortunately it doesn't work in my demo environment. Even when I follow all needed preparation from Microsoft Technet, it's still failing on the first server, which is System Center Orchestrator. The error message displayed is: ERROR - Could not execute System Center Orchestrator Failed WinRM configuration checkWinRM configuration not confirmed. I like to hear feedback from other people on this specific installation. Maybe it's a known issue for you?
Update 6-2: Today I started the installation again because of new feedback (see comments). Thanks to ThomasH it's working now. Probably using WinRM is not enough when domain policies are also into place. Using Local Policies will start the installation and pass the WinRM configuration, which was failing before. Thanks for all feedback guys!
More information about the Unified Installer can be found on Microsoft TechNet: Unified Installer Release Candidate
I cannot find thed CU4 that Unifed installer wants. Any ideas or a link to where I can get it? I have all other media done, just not CU 4.
ReplyDeleteThe Cumulative update package 4 for SQL Server 2008 R2 Service Pack 1 can be found here: http://support.microsoft.com/kb/2633146
ReplyDeleteChoose View and request hotfix downloads for that. A link to the hotfix will be e-mailed to you.
Hi Henk.
ReplyDeleteNice to see you are busy with the unified installer too.
At the servers page the next button stays greyed out. Do you have any idea? My installer PC is Windows 7 and target machines are 2008 R2 SP1 servers. All with the right requirements.
Mark
Just select different servers for all products you want to install, then the Next button become available.
ReplyDeleteI had the same error. Turns out my DC was overwriting the local policy. After resetting domain policy, I was able to edit local policy.
ReplyDeleteTry this:
Computer Config \ Administrative Templates \ System \ Credentials Delegation \ Allow Delegating Fresh Credentials
State = Enabled
Server = WSMAN/*
Computer Config \ Administrative Templates \ System \ Credentials Delegation \ Allow Delegating Fresh Credentials with NTLM only server Authentication
State = Enabled
Server = WSMAN/*
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Client \ Allow CredSSP authentication
State = Enabled
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Client \ Trusted Hosts
State = Enabled
TrustedHostList = *
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Service \ Allow Automatic Configuration of listeners
State = Enabled
IPv4 filter = *
IPv6 filter = *
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Service \ Allow CredSSP authentication
State = Enabled
In a command prompt, run:
gpupdate
Winrm quickconfig
Hi, I can confirm the solution of ThomasH. You should use the GPEdit method and not the WinRM as mentioned in the Unified Installer User Guide (http://technet.microsoft.com/en-us/library/hh751273.aspx). This also goes for the Target Computer preparation! We installed Orchestrator, SCOM and SCSM without problems! The only issue is the installation of SCCM, but we're working on that.
ReplyDeleteI can confirm the solution of ThomasH as well. thanks a lot Thomas
ReplyDeleteThanks for all replies, and most ThomasH. I will start Unified Installer again today and post back results.
ReplyDeleteI tried ThomasH's settings and still not having any luck. Are these changes made at the DC and the server I'm installing to? I keep getting a WSManFault access denied error.
ReplyDeleteJust enable above settings on the Target and Installer systems and try again. Let me know the results after that for good overview.
ReplyDeleteHi Henk
ReplyDeleteInstaled the Orchestrator fine but when I tried two other components (ConfigMan, and VMM), each give me the same error: "All selected components have failed"
[3/5/2012 2:28:57 PM] INFO - Virtual Machine Manager: SQLSCVMM failed
[3/5/2012 2:29:00 PM] DEBUG - [Timer Details] 0/0 are over time limit
Name: Virtual Machine Manager
Status: Failed to complete
IsInstalled: false
ProgressMessageStatus: failed
IsEnded: True
OriginalStatus: SQLSCVMM failed
TimeSinceLastChanged: 00:00:03.0212472
[3/5/2012 2:29:00 PM] INFO - All selected Components have failed.
Anyone run into this, please help. Thanks
We get an error that the SQL SP1 and SQL CU4 folders do not contain the media. However, we have the SP1 file in that folder and the decompressed CU4 files in that folder.
ReplyDeleteWe tried renaming the .exe files to setup.exe (per procmon analysis) and it then says that the wrong files are present (version 10.51.x.x instead of 10.50.x.x). The rename seems like the right thing to do, but we somehow have the wrong versions?
Anyone get this to actually install? I am stuck on the prerequisite media location as well. Excited to test it out, but it just needs to simplify the install process and it shouldn't ask you to get everything separately. Unified should be completely unified!
ReplyDeleteI have uncompressed the SP1 and the media now shows as OK. However for the CU 4 I got 4 hotfixed, which I have also uncopressed to .msi files, but none of them seem to work.
ReplyDeleteJust keep in mind that you need the SQL Server 2008 R2 SP1 CU4, not some older version. It can be found here: http://support.microsoft.com/kb/2633146
ReplyDeletedoes anyone know this error:
ReplyDeleteERROR - Bootstrap failed on hostname
Failed to configure remote WinRS
Local WinRS: C:\Windows\system32\winrs.exe
Working Directory: C:\Windows\system32
Command: ServerManagerCmd.exe
Arguments: -query "C:\Users\administrator.CLOUDTEST\AppData\Local\Microsoft System Center 2012\Unified Installer\rolefeatures.xml"
Exit Code: -2144108125
[23-4-2012 16:04:46] ERROR - Could not execute Runbook:
Bootstrap failed on hostname
Failed to configure remote WinRS
Local WinRS: C:\Windows\system32\winrs.exe
Working Directory: C:\Windows\system32
Command: ServerManagerCmd.exe
Arguments: -query "C:\Users\administrator.CLOUDTEST\AppData\Local\Microsoft System Center 2012\Unified Installer\rolefeatures.xml"
Exit Code: -2144108125
+1 for that i am getting the same error for SCOM.
DeleteI have done both the WinRM and GPEdit methods.
I can do a WinRM -id -r:othercomputer and it works fine, so I know that works.
I have tried the source local and remote, orchestrator installs on the local computer OK.
solved : http://social.technet.microsoft.com/Forums/en-US/scodeployment/threads
DeleteHi,
ReplyDeletedoes anyone have an idea regarding the SP1 and CU4 not being discovered by the Unified Installer?
it sounds odd but you extract the extracted files, there are four or five you download. One is much larger than the rest. Extract it, and then extract it again.
ReplyDeleteI had a simliar issue where I had uncompressed the SP1 and CU4 files into seperate sub folders yet the installer still gave me the wrong path errors. I changed the path to the folder above where I expected them and it worked. Might be simliar issue for you.
ReplyDelete