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
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.
Update 1/30/2013: I don’t recommend this as a primary way to install the SCCM agent on computers now that there is a supported solution from Microsoft, this was just a temporary workaround until SCCM SP1 was released.
In this blog post I’m going to document the high level steps to get the SCCM agent (Pre beta 1) on Server 2012, Windows 8 and this can be used also as a secondary method to catch any machines that didn’t get the agent installed by client push or WSUS depending on your main deployment method for the client.