Author Archive

Happy New Year!!

2014 was a great year, with a lot of great blogposts, great products and knowledge from the community. I want to thank all the sponsors for the support on my blog!

Also from a stats perspective 2014 was a great year. I am hoping 2015 will be even better, and I want to wish all of you a Happy New Year!

happy-new-year-2015-1920-1080-3088

How to: Deploy packages using collection variable with ConfigMgr 2012 R2

During a OS deployment you don’t want to deploy all your packages and software to every workstation. You can deploy the software after a full OS deployment, but you can also deploy packages during the OSD using collection variables. Now it is possible to deploy packages only if a specific machine is a member of a collection. This collection can be query based, for example OU membership or Active Directory security group, or it can be static (direct membership).

In this example I’ve created a realy simple deployment, Adobe Reader 11.0. I’ve two virtual machines, SCWIN81-01 and SCWIN81-02. Both machines are members of the collection “Deploy – Windows 8.1 Enterprise x64”, where the task sequence is deployed on. Machine SCWIN81-01 is also member of the collection “Install – Adobe Reader 11.0”. This collection has a limited collection of “Deploy – Windows 8.1 Enterprise x64”. Both machines are deployed on the same time, the only difference is that machine SCWIN81-01 has Adobe Reader 11.0 installed and machine SCWIN81-02 not. Why……based on the collection variable during the OSD ūüôā

1.) First create the collections
2.) Make the specific machines members of the right collections (query based or direct membership)
3.) Open the properties of the collection “Install – Adobe Reader 11.0” and navigate to the “Collection Variables” tab
4.) Add one or more variables with some values. In this example the variable is “APP-AdobeReader” with the value “Yes”
5.) Open the task sequence and add a package installation step
6.) Add the package with the program and navigate to the “Options” tab
7.) Select “Add Condition” and select “Task Sequence Variable”
8.) Enter the collection variable you’ve created earlier with the same value. In my example:
Task Sequences Variable APP-AdobeReader equals “Yes”
9.) Select “Apply” and close the task sequence.
10.) Start the OSD on both machines and wait until the installation is done!
11.) Watch the differences between both machines, if everything is okay, one machine has Adobe Reader installed and the other not.

This is an extremely powerfull thing within ConfigMgr, and really helpfull is some scenario’s. For example VDI golden image deployments or hybrid environments with laptops/desktops or multiple organizations using one ConfigMgr environment. One main reason could be consolidation in task sequences. If you want, there should be only one task sequence for all you different deployments. This is why I’m loving collection varaibles! ūüôā

2014-12-22_15h45_33    2014-12-22_15h46_26    2014-12-22_15h46_48

2014-12-22_15h47_23    2014-12-22_15h49_46    2014-12-22_15h50_15

2014-12-22_15h50_37    2014-12-22_15h51_16    2014-12-22_15h51_58

How to: Apply Windows updates during OSD with ConfigMgr 2012 R2

During a OS deployment with ConfigMgr 2012 R2, you definitely want to apply the latest Windows updates and patches, for example with Windows Server Update Service (WSUS). You can also integrate WSUS within ConfigMgr 2012 R2, but in this example WSUS is not integrated!!

This example is also very usefull to create a fully patches golden image in ConfigMgr 2012 R2 (Build & Capture). After the task sequence you’ve a fully patches Windows 8.1 machine that you can use for example VDI environments.

1.) Fist open your task sequence
2.) Create a new computer group “Desktops” within the WSUS console (or choose another name, for exmaple: servers, laptops, etc.)
3.) Add a custom group within the task sequence
4.) Add the following steps in your task sequence
Run Command Line:
reg ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate” /v WUServer /t REG_SZ /d http://wsus01.cloud.local:8530 /f
Run Command Line:
reg ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate” /v WUStatusServer /t REG_SZ /d http://wsus01.cloud.local:8530 /f
Run Command Line:
reg ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate” /v TargetGroup /t REG_SZ /d “Desktops” /f
Run Command Line:
reg ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate” /v TargetGroupEnabled /t REG_DWORD /d 1 /f
Run Command Line:
reg ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU” /v UseWUServer /t REG_DWORD /d 1 /f
Run Command Line:
wuauclt.exe /resetauthorization /detectnow
5.) Don’t forget to set the name of your WSUS server and computer group¬†in the commands above!
6.) Create a new package in ConfigMgr 2012 R2 with the following two files in it, located in the MDT 2013 deployment share directory
ZTIUtility.vbs
ZTIWindowsUpdate.wsf
7.) Don’t create a program in this package, but you only have to distribute it to the distribution point(s)
8.) Add a new step “Run Command Line” to the task sequence with the following command:
cscript.exe ZTIWindowsUpdate.wsf
Select the package where the source files are located
9.) Deploy the task sequence to your client collection!

COAU_01    COAU_02    COAU_03

COAU_04    COAU_05    COAU_06

COAU_07    COAU_08    COAU_09

COAU_10    COAU_11    COAU_12

How to: Disable first sign-in animation in Windows 8.1 using ConfigMgr 2012 R2

When a user login the very first time on a Windows 8 of 8.1 machine, they will see a ‚Äúanimation‚ÄĚ with some helpful tips. During this stage the userprofile is being created and prepared. While the first sign-in animation may be helpful to new users to see, but it slows down the logintimes. So let‚Äôs turn this animation off using ConfigMgr 2012 R2.

1.) Open your task sequence
2.) Add a action “Run Command Line” after Setup Windows and ConfigMgr
3.) Copy and paste the following command line:
reg ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System” /v EnableFirstLogonAnimation /t REG_DWORD /d 0 /f
4.) Give it the value 0 to disable and 1 to enable
5.) Deploy your task sequence to a collection of devices

FRA_01    2014-12-22_10h44_09    2014-12-22_10h44_50

How to: Add computer to security group with ConfigMgr 2012 during OSD

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…)

2014-12-12_15h53_47    2014-12-12_15h58_35    2014-12-12_15h59_14

2014-12-12_15h59_50    2014-12-12_16h42_54    2014-12-12_16h43_11

2014-12-12_16h43_34    2014-12-12_16h43_48

Build your own FREE virtualization lab environment

2014-06-27_12h36_26

The most affordable toolkit to meet your goals!

There is no better way to start virtualizing than with a FREE Microsoft Hyper-V environment, free backup, free virtual storage and free management software!

With this free toolkit, you can create your own test lab, run a small business or even scale your production environment up to 1,000 VMs. It’s a FREE way to virtualize!

  1. Microsoft Hyper-V Server 2012 R2
    Free Hypervisor with all the functionality of it‚Äôs ‚Äėbig brother‚Äô, Windows Server 2012 R2 Hyper-V
  2. Veeam Backup & Replication
    Effective and easy-to-use tool for Hyper-V backup
  3. StarWind Virtual SAN
    Reliable shared storage with unlimited storage capacity for a single-node device
  4. 5nine Manager
    Simple and easy-to-use Graphical User Interface, local or remote, to manage Hyper-V virtual machines

Start today!!

And if you would like to just download Free Microsoft Hyper-V Server 2012 R2, please click here.

2014-06-27_12h36_43

How to: Create multiple boundaries in ConfigMgr 2012 within a few seconds

When you’re installing and configuring a new ConfigMgr 2012 environment, one of the steps is to configure the right boundaries for your environment. Sometimes there’re only a few boundaries you have to create, but what if there’re several boundaries to configure. Are you gonna click that much….Let’s create some Powershell command to do the job for us.

1.) First of all we are going to import the ConfigMgr 2012 Powershell module. Use the x86 Windows PowerShell, bacause x64 is not supported!!
Import-Module “C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\ConfigurationManager.psd1”
4.) Make a connection to your Primary Site server
Set-Connection P01
3.) Now we are going to create some new boundaries. In this example a whole IP subnet (172.16.10.0 and 172.16.11.0)
New-CMBoundary -Name “Client VLAN1” -Type IPsubnet -Value “172.16.10.0”
New-CMBoundary -Name “Client VLAN2” -Type IPsubnet -Value
“172.16.11.0”
5.) Create a new boundary group. In my example “Main Building”
New-CMBoundaryGroup -Name “Main Building”
6.) The next step is to add the boundaries to the right boundary group
Add-CMBoundaryToGroup -BoundaryName “Client VLAN1” -BoundaryGroupName “Main Building”
Add-CMBoundaryToGroup -BoundaryName “Client VLAN2” -BoundaryGroupName “Main
Building”

Now the job is done. How easy and fast was that…

CMB_01    CMB_02    CMB_03

CMB_04    CMB_05    CMB_06

CMB_07    CMB_08    CMB_09

CMB_10    CMB_11    CMB_12

ConfigMgr 2012 client installation on Windows 8 returns an error 0x800b101

Last week I have been working on a Windows 8 deployment with ConfigMgr 2012. After configuring a new task sequence, I was able to deploy the first Windows 8 image to one of many virtual desktops. The deployment went fine, until the ConfigMgr client installation. Okay, so what about now. Let’s have a look in the CCMSETUP.LOG on the client. I received the following error:
“Couldn’t verify C:\WINDOWS\ccmsetup\MicrosoftPolicyPlatformSetup.msi authenticode signature. Return code 0x800b101”.

After some search on Microsoft TechNet, I found the solution for this problemn. Microsoft has released a hotfix for this error (KB2801987) . You have to request this hotfix by e-mail.

After requesting and downloading the hotfix, you have to install this hotfix on your primary site server. It wil create a new update package named “KB 2801987 – server update – P01”. If you browse to your client installation files on your primary site server, you’ll also see that the timestamp has changed. So the ConfigMgr client installation files are also updated! Make sure you update the distribution point(s) with the new version of the ConfigMgr 2012 client installation package.

Now you’re able to succesfully deploy Windows 8 with the ConfigMgr 2012 client.

WIN8_01    WIN8_02    WIN8_03

WIN8_04    WIN8_05    WIN8_06

WIN8_07    WIN8_08    WIN8_09

WIN8_10    WIN8_11    WIN8_12

WIN8_13    WIN8_14    WIN8_15

WIN8_16    WIN8_17    WIN8_18