Install Software Packages in a OSD Task Sequence using variables

Issue:
When looking in SCCM implementations I regularly bump into the same issues. Lots of task sequences with a lot of different settings in them. Because of the exploding amount of task sequences there is a lot if differiation between them. This blog post describes how to use OSD variables to bring back the amount of sequences.

Let’s start,
This example is an school with student’s as well as teachers. They are divided into rooms by using the device collections. Depending on the (class) room they get the software they need.

First we start with creating a device collection for a room:
We are going to set the variables to the collections
– Go to Assets and Compliance, Device Collections, and choose Create Device Collection.
– Give the collection a name like “Classroom 141” and limit the collection to “All Collections
– Check Use incremental updates for this collection and turn off Schedule a full update on this collection.
– Choose Next, Yes and Finish the collection

Next we are going to set the collection variables
– Get the properties of the newly made collection, go to collection variables and fill in the following variables (depending on your structure)
Name                  Value
BSL                     Students Desktops
Domain                Students
OSDOUName       OU=R141,OU=Students Desktops,OU=Workstations,DC=students,DC=domain,DC=local

BSL1

 

1. Let’s install software based on a variable
Now we can add the variables to the software library

– Go to Software Library, Task Sequences and Edit an task sequence.
– We created a Install CSL Applications (Common Software Layer); this is for software that is scoped on all desktop (like Office, flash, Adobe Reader ETC)
– We also created an Install BSL Applications (Business Software Layer) for specific software per/pc/room
Add the software to the BSL and choose Options
Add Condition and choose Task Sequence Variable BSL equals “Students Desktops”

BSL 2

2. Let’s install sofware based on a variable

OK lets go a little bit further, we are now going to add the computer in the AD OU based in the computer variable of the collection.
– Go to the Network Settings, Apply Network settings and set Join a domain, fill in the domain name and in the OU part you choose LDAP://%OSDOUName% as stated in the variable.

Flexible Domain Name

Now we are going to set the options so the proper collection is selected.
– Go to Options, Add condition, Task Sequence Variable and choose Domain equals “Students”

Flexible Domain Name II

 

Little recap;
– Made device collections based on rooms
– Filled in the variables for that device collections
– Set options for installing software based on device collection variables
– Placed machines in the proper OU based on device collection variables

Simple as that!

Office 2013 deployment with SCCM 2012 SP1 (Beta)

Just another tutorial on how to deploy Office 2013 using Configuration Manager 2012 SP1.

Extracting the Office installation and customizing the installation
First I started to get the Office 2013 software from the MSDN site and extracted it into my demo lab share file.
1. In my case it was on \\demo-sccm01\Sources\Software\Office\Office 2013 Pro NL x64.


Second step is to customize the Office 2013 installation using the “Office Customization Tool”;
2. Go to a DOS prompt, go the Office 2013 folder and run setup.exe /admin
If the setup /admin runs well go to step 3, otherwise go to step 2.1
2.1 – Optional
If you run the setup.exe /admin you can receive the following error:

Files necessary to run the Office Customization Tool were not found. Run Setup from the installation point of a qualifying product.

To solve this issue, click HERE and extract the admin files in the root of the Office 2013 directory.

3. Choose Ok to create a new Setup Customization file

4. On Default File Types, I selected Office Open XML formats

5. On the Licensing and user interface check the I Accept terms and choose Display Level – none

6. Customize the further installation of Office 2013 to you’re needs.
7. Save it where the setup.exe is located. I used the name Office2013NLD_x64_Custom.msp

Next step is do deploy Office 2013 to the SCCM 2012 SP1 environment
1. Open the Configuration Manager 2012 console, Software Library, Application Management, right-click Applications
2. Create an folder named Office and a subfolder called Office 2013
3. Right Click Create application

4. Browse to proplusww.msi (location where you extract the Office, subfolder proplusrww) and click Next
5. On view imported information, click next
6. On the General information, make adjustments/notes and click next

7. Summary, click Next and choose Close
8. Select the Microsoft Professional Plus 2013 application, and select the Deployment Type tab, click Properties
9. In the Deployment Type properties, of the Microsoft Professional Plus 2013 application, go to content tab and change the Content location from “\\demo-sccm01\Sources\Software\Office\Office 2013 Pro NL x64\proplusr.ww” to “\\demo-sccm01\Sources\Software\Office\Office 2013 Pro NL x64”
10. Go to programs tab, Installation program, type setup.exe /adminfile Office2013NLD_x64_Custom.msp

11. If necessary you can go to the requirements section and add requirements like
– 1 gigahertz (Ghz) or faster
– 1 gigabyte (GB) RAM (32 bit);
– 2 gigabytes (GB) RAM (64 bit)

12. Select the Microsoft Office Professional Plus 2013 x64 – NLD, change to Home tab and click Properties

13. Select “Allow this application to be installed form the install application task sequence action without being deployed”; this is necessary if you want to use it during the Operating System Deployment.

14. Select the Microsoft Professional Plus 2013 application and click Distribute Content

15. On the General, Click Next
16. On Content, click Next
17. On Content Destination, add the Distribution Point and click Next
18. Summary, click Next and choose Close
19. Right click on the Office App and choose Deploy, select All systems as collection (because we use it as an OSD deployment.

20. Just click next until completion, if you want to make adjustments it’s possible.
21. On the client force the machine policy retrieval

22. Open the Software Center, select Microsoft Professional Plus 2013 x64 NLD and click Install and the installation will start. After a minute of ten the installation is completed.
23. To check the deployment on the server, open the ConfigMgr console, go to monitoring, Deployments.
24. Select Microsoft Professional Plus 2013 and confirm the completion statistics