In some cases you’ve to add computer to a Active Directory security group. For example Direct Access laptops. In this example I’ve created a VBS script for adding a computer to an Active Directory security group during OSD in ConfigMgr 2012 R2.
1.) Create a new package within ConfigMgr 2012 R2 without a program
2.) Distribute the new package to you distribution point(s)
3.) Copy the script “ADgroup.vbs” to the source location of your new package
4.) Add a step “Run Command Line” to your task sequence
5.) Add the command line: cscript.exe adgroup.vbs [name of your AD group]
6.) Select the package “Scripts”
7.) Select a account with enough privileges to add (new) computer object to the Active Directory
8.) Deploy your task sequence to a collection
You can download the script here. (Right-click and save…)
Working with System Center products is one of my favorite things!! A great solution I’m using is the Powershell Deployment Toolkit (PDT). The PowerShell Deployment Toolkit (PDT) is a set of scripts and knowledge for automated deployment of System Center 2012 SP1/R2, including SQL all prerequisites, and all automatable post-setup integration. PDT is written by Rob Willis.
Download the Powershell Deployment Toolkit (PDT) here.
Because Powershell Deployment Toolkit contains some Powershell scripts and XML files, this is not a easy thing for everyone! To make this powershell scripts just more powerfull, the Powershell Deployment Toolkit GUI is created!! This is a graphical user interface for the Powershell Deployment Toolkit. The original PDT is created and maintained by Rob Willis from Microsoft Corporation. The PDT GUI is created and maintained by German Microsoft Partner ‘Elanity Network Partner GmbH’ and is not an official Microsoft Product. The PDT GUI helps to create fast PDT Configuration-Files (Variable.xml) for Zero Touch System Center Deployments. PDT GUI creates and validates the configuration files for PDT, it does not alter the existing PDT in any way. An installed PDT is neccessary for a succesful PDT Deployment.
Download the Powershell Deployment Toolkit GUI here.
Benedict Berger (Hyper-V MVP and Hybrid Cloud Geek) and Kamil Kosek (Powershell Geek and Automation IT Pro) teamed up end created this free tool. Special credits to this guys, great job!!
Microsoft System Center: Integrated Cloud Platform
David Ziembicki and Mitch Tulloch, Series Editor
This book is organized by cloud type and begins with a short overview of the Cloud OS strategy from Microsoft and a high-level hybrid cloud architecture. It also covers the design and deployment of private cloud solutions using Windows and System Center to deliver the software-defined datacenter where storage, network, compute, and management are all virtualized and delivered by the Microsoft platform.
Download the PDF
Download the EPUB file
Download the Mobi for Kindle file
When you’ve to install an operating system in you’re environment, it is easy and usefull to test your OS deployment first in a virtual environment. In my case, it is an Microsoft Hyper-V host server, where I can deploy some virtual machines using ConfigMgr 2012 R2.
One of the important things when deploying a virtual machine within Hyper-V, are the Integration Components (Integration Services). These components installs all the necesarry drivers for that VM. Maybe you want to perform this action during the OS deployment fase (OSD). What steps do you need to make?
1.) First install a new clean Windows 7 VM (in my case it is Windows 7 Service Pack 1)
2.) Insert the Integration Services Setup Disk
Action / Insert Integration Services Setup Disk
3.) Navigate to your Windows Explorer and open the mounted disk
4.) Navigate to the right folder of your architecture, x86 or x64. In my case it is x64.
5.) Copy all the files in this to your Configuration Manager Site Server. In my case E:\Sources\Applications\Level 0\Hyper-V Integration Services x64
6.) The silent installation is not that hard. Just execute setup.exe /? to see all the options.
7.) Create a new package within ConfigMgr 2012 R2 with a normal program
8.) The source location is the location to your folder created in step 5
9.) The command line to perform is setup.exe /quiet /norestart
10.) After succesfully created to new package, don’t forget to distribute it to your distribution point(s)
11.) Now open you task sequence and at the end create a new folder called “Install Applications”
12.) Add a new package to install and select the wright package and program
13.) All you need to do now is deploy a virtual machine
14.) After your virtual machine has succesfully deployed, look at your device manager. All the components are installed.
Today I had to install a new System Center Configuration Manager 2012 R2 environment. One of the features this customer is going to use is OS Deployment. In this environment we are using the Build & Capture task sequence voor deploying a Master Image of Windows 8.1. The Master Images will be deployed in Hyper-V. One of the important steps is to import the “Master VM” into the ConfigMgr database. Two things you’ve to know are….PC name and the MAC address. With this PowerShell command you can find all the MAC addresses very easy!
1.) Open Microsoft PowerShell on your Hyper-V server
2.) First list all the VM’s
3.) List the name of the VM, MAC address, Virtual Switch name and IP address
get-vm -Name SC2012R2-PC0002 | select -ExpandProperty networkadapters | select vmname, macaddress, switchname, ipaddresses
4.) Import the VM into ConfigMgr
If you want to save some time installing all the System Center 2012 R2 products within your production environment or demo lab environment, the HydrationKit is just the way to go!! System Center guru Johan Arwidmark has created a fully automated installation upon MDT 2013! Within just a few minutes, you’re ready to rock!!
Download the HydrationKit for System Center 2012 R2
Special thanks to Johan!! Please visit his blog at http://www.deploymentresearch.com and leave a message for him!!
Microsoft released Update Rollup 1 for System Center 2012 R2 with updates and fixes for Virtual Machine Manager, Data Protection Manager and Operations Manager.
Components that are fixed in this update rollup
• Data Protection Manager (KB 2904687)
• Operations Manager (KB 2904678)
• Virtual Machine Manager (KB 2904712)