In this multi-part blog post I am going to show you have I have fully automated the deployment of the GoToMeeting Client each time there is an update.
In Part 1 we are going to go build three Orchestrator runbooks
- the first runbook will monitor when the process should run
- the second runbook will be the main control runbook
- the third runbook will Unzip the zip file if there was an update downloaded with the runbook we will build in Part 2
I recently needed to move the WSUS server that was synced with Config Manager. The first time I attempted to move WSUS to the new server I didn’t factor in that SCUP was also synced with WSUS/ConfigMgr and this resulted in some configuration errors in attempting to setup the new WSUS server when installing the software update point.
The SMS_WSUS_Configuration_Manager Component status giving me a 6603 error
In this blog post I am going to show you how to import the default Endpoint protection policies via the ConfMgr console or skip to the end for the powershell script to import them all at once.
Open assets and Compliance –> Endpoint protection –> antimalware Policies –> click Import
select the default policy you would like to importContinue reading
Microsoft has added System Center 2012 R2 to the volume licensing site.
During the setup of Application Approval Workflow that can be downloaded here, you are asked to provided a user to connect to ConfigMgr and Service Manager. These accounts are stored in Orchestrator to run different runbooks. There is a few things that the documentation doesn’t cover or assumes that you already know from using Orchestrator.
If you selected to use an AD group during install for your Orchestrator user Group you will need to create a local group called OrchestratorUsersGroup on your Orchestrator Server.
This is just a quick post to use as a reference for when writing powershell scripts for orchestrator. I will update this post in the future with other useful Import-Module powershell snippets as I write them or run across them in my runbooks.
The snippets that don’t say Remote connection next to them you need to have the powershell Cmdlets installed locally on your Orchestrator Server.
I recently had to rebuild my machine, after getting Windows 8 reinstalled I started installing my System Center Consoles since I was in a hurry to work on a powershell script for a runbook in Orchestrator that connected to ConfigMgr my first two consoles I installed were ConfigMgr and Orchestrator then went on to deploy the Integration packs for Orchestrator. Most of the IPs installed without any issues but the System Center 2012 ConfigMgr and OpsMgr IPs failed to install. The error message in the Deployment Manger was not very helpful. “Fatal error during installation.”
Since I wasn’t sure where the log files were on the remote computer or what was the root cause of the issue fired up Process Monitor this quickly lead me to the log directory that can be found at