Kevin Remde's IT Pro Weblog
I thought I’d just take this opportunity to again share my three-part screencast series with you; this time all in one place.
The topic: System Center 2012 Unified Installer
The goal: Help you prepare for and use the Unified Installer to build your lab for testing and trying the System Center 2012 components out
The added benefit: You get to see my pretty metro-style (I like to call them “metrofied!”) PowerPoint slides.
Enjoy. And enjoy even more in full-screen, and 1280x768 if you can…
Here is Part 1:
Here is Part 2:
And here is Part 3:
I ran all pre-reqs but I have an issue after install orchestator. when unified installer tries to install all other products takes about 2 hours and receive the messaje:
progress.xml has not changed for more than 120 minutes check Runbook status and exit installer.
Could you give me some ideas about the issue?
I've heard that this can happen if there are other errors that aren't picked up, or if the installation is simply taking too long across a slow network or to an over-burdened machine. After 2 hours the installer throws its hands in the air and gives up.
I'm sorry I don't know an easy solution for you. I suggest that you bring up the issue on (or search in, since someone else may very likely have seen this and asked about it in) the TechNet Forums.
Best of luck!
Maybe this time my post will stick...
Kevin, Thank you for your walk-through, I'm trying to wrap my skull around System Center. Specifically, Configuration Manager.
I'm selecting Orchestrator and Config Manager only. And when I get to the point where is asks for the server names to install the components to, I get the error:
Could not determine WinRM configuration on server: ORC
The server ORC is where I'm trying to install it, and SCCM is the server for Config Manager. I do not get the error for SCCM.
I have set the WinRM settings in a GPO and via command line.
From the command line it shows the settings are each already configured "Source=GPO"
Have any suggestions?
Hmm.. Have you thought to look at GP Results to see if there are any overriding policies that are conflicting (and winning)? Beyond that I don't have any ideas for you, I'm sorry to say.
As I told Osvaldo, you should definitely post this question in the TechNet Forums. social.technet.microsoft.com/.../categories
Actually, now that I look there, I can't find a forum specifically for general System Center installation or the Unified Installer.. so perhaps that forum will come after the 2012 launch.
Has anyone else seen this issue and a potential cause that they were able to overcome?
Has anyone found a solution to the "Could not determine WinRM configuration on server:" problem? I'm getting the same error as LT.Son above and as far as I can tell, all of the settings (both installer and target) that the word doc indicated should be set have been set.
It's driving me crazy, because I've put so much energy into this and feel I am so close to getting SC2012 up and running.
Any help anyone can give would be greatly greatly appreciated.
Once again - I suggest you try the TechNet Forums. By now I know that other people have asked the question there. Unfortunately they haven't added any Unified Installer specific forums (yet), but there is a System Center Orchestrator forum there that will be your best bet.
For the "Could not determine WinRM configuration on server:" error, when I had this I went on to the servers reporting the problem and ran the 'winrm qc' command, which then prompted me to start the WinRM service. After that, it worked (or at least to the point of the progress.xml message that brought me here!)
Thanks for sharing that, Hindy. Yes, I've seen and heard about that error many times. It's a very picky tool, currently. Making sure that the Windows Remote Management (WINRM) service is alive and well, and able to respond through the firewall, is critical. Since the Unified Installer is just for deploying a test and trial environment, it's probably easiest to just disable the firewall on all of the System Center 2012 servers. In your real, production deployment, you'll do individual installations and use the recommended firewall and security best-practices.