This post we discuss how to update your Windows 8.1 image with Update 1 in SCCM 2012 R2.
In most environments this update isn't downloaded automatically with any ADR(due to the update classifications set in it). You need to manually download the update.
Also, make sure that at least the KB2919442 update has been installed (servicing stack update) in your image.
First, open the SCCM 2012 console. Navigate to Software Library > Software Updates > All Software updates. Search for KB2919355 and hit enter (this is the Update 1 update). Rightclick it, and select download.
Then, choose the deployment package you want to use.
In the example, we chose Windows 8.1 monthly updates.
Click Next
Click Next
If needed, select extra languages. Then click next when done.
Check the overview to see what actions are going to be done. Click Next.
You can monitor the progress bar (this can take some time because the update is about 700 MB)
Once done, you should receive a screen looking like the one below.
Now rightclick the update, and select 'Edit Membership'. Choose the ADR rule you want, and select OK.
Now you can add the update to an image using Offline Servicing. Go to Software Library > Operating Systems > Operating System Images. Rightclick the image you want to update, and select Schedule Updates.
Select the update and click Next
Set the scheduling settings as you desire, and click Next
Confirm the settings, click Next
Monitor the progress.
Once done, click Close
Check the update status in the OfflineServiceMgr.log
Once that's finished, you succesfully integrated/slipstreamed the Update 1 rollup in your Windows 8.1 image :)
In this post we are going to discuss how to create a clean software packaging environment, or package street/package factory.
1). It is highly recommended to use a virtual machine and a good tool is VMware Workstation for PC or VMware Fusion for Mac. If you use Windows 8(or higher), then you could use Hyper-V, which is free (see my other post HERE on how to enable this)
2). Choose an Operating System. Preferably Windows 7 32-bit or 64-bit (depends on what environment is most used in your company, possibly both are needed).
3). Create a 30 GB virtual hard disk and a 10GB virtual hard disk (used for page file) and attached to your virtual machine. If you have a SSD in your host system, it is recommended to point it to that disk (to achieve best performance)
4). Install Windows to the freshly created virtual hard disk(the 30 GB one)
5). Turn Off Automatic Updates then Run Windows Updates but only Security Updates, Service Packs, and other Critical Updates. Avoid Language Packs, Windows Defender, Internet Explorer Updates, and Driver Updates. You are best off not installing any dependencies like Visual C++ or .NET Framework. In this case, if your software complains then you'll know what .NET Framework your software package needs. You can then add it as a dependency (for instance when creating the package using Adminstudio).
6). Turn Off System Restore
7). Disable Extra Features from Programs / Add or Remove Windows Features you will not need. It is necessary to create a reference computer that is as clean as possible.
8). Create your page file. You may need to format your 6GB Hard Drive.
Right Click Computer -> Properties -> Advanced System Settings -> Advanced Tab -> Performance Settings -> Adjust for Best Perfomance -> Advanced Tab -> Change... -> Uncheck Automatically manage paging File size for all drives -> Check Custom size -> Click your Second 6GB Drive -> Take the amount of Physical Memory in your PC and double it for both Initial size and Maximum Size EX 2048 Physical is 4096 -> Click Set -> OK -> OK -> OK -> Restart
9). Turn off Services you don't need. Services.msc Double click a service, Choose Disabled, Click Stop, Click Apply.
Services I disabled were:
- Disable BITS
- Disable MpsSvc (Windows Firewall)
- Disable wuauserv (Windows Update)
- Disable WSearch (Windows Search)
- Disable WinDefend (Windows Defender)
- Disable Themes
- Disable wscsvc (Security Center)
10). Install VMware Tools, Parallels Tools, VirtualBox tools, Hyper-V Integration Services etcetera. Whichever hypervisor you are using. Reboot when done
11). Install your MSI Packaging Tool, (for instance, Admin Studio, InstallShield, AppDeploy, EMCO, Orca) I'm using AdminStudio
12). Add anything else you think you may need. Now you can configure your Machine how you want it.
13). Shutdown the machine and create a snapshot/checkpoint. Now you can use your MSI creating tool, and create snapshots when done. You can also use this machine to create captures.
Cumulative update 1 (CU1)(KB2938441) for SCCM 2012 R2 has been released!
See this link for the Microsoft documentation.
In this blog we'll describe how to install this CU.
First, make sure you pick an appropriate time to install this update (preferably after Office working hours). Second, make sure you create a backup / snapshot / checkpoint before proceeding with installing this CU.
Download the CU update by requesting the hotfix (see the Microsoft link at the top of this post)
Extract the update by doubleclicking the executable, or by rightclicking it, and extracting it manually.
Click next on the Welcome Screen.
Click 'I accept', and click Next.
If all the prerequisites have passed, click Next.
Check the box to update the console, and click Next.
Click the 'Yes, update the site database' radio button, and click Next.
Leave all the checkmarks, and click Next.
Change the Package name if desired.
Change the Package name if desired.
Change the Package names if desired.
Review the Setup summary. If everything is OK, click Install.
Monitor the progress of the installation.
Click 'View log', to monitor all the components using CMTrace.
When finished, click Finish.
Reboot the server.
Check the version by opening the SCCM Console, and click About. The version should be 5.0.7958.1203.
Next, select all the CU1 packages, and click Distribute Content.
Click Next.
Add distribution point(s) and click Next.
Review the summary, and click Next.
Once done, click close. You can then deploy the packages to the appropriate device collections if desired.
Optionally you can check the Site status and Component status in the Monitoring pane.
How to determine the installation status of this cumulative update
This cumulative update changes the following Configuration Manager version numbers and installation properties.
Site systems
The CULevel value is located under the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup
Note: The CULevel value is set to 1 for Cumulative Update 1.
Administrator Console
The version that is displayed in the About System Center Configuration Manager dialog is 5.0.7958.1203 (as stated above, including the screenshot)
Client
The version that is displayed on the General tab of the Configuration Manager Control Panel item or the Client Version field of device properties in the Administrator Console is 5.00.7958.1203.
Endpoint Protection Client
This update brings the anti-malware client version to 4.5.0216.0. You can find the version information by clicking About on the Help menu of the Endpoint Protection client UI.
You now succesfully have installed the CU1 update! :)
In this post we'll discuss how to slipstream SP1 into your Office 2013 installation.
The great benefit of this is that after installing Office 2013, it's at SP1 level, so that you don't need to install so many updates after your base installation.
First off, download the SP1 installer package:
Office 2013 SP1 32-bit version
Office 2013 SP1 64-bit version
Once downloaded, put them in a seperate folder on your hard drive:
Then, create the following folder structure:
Copy the content of your Office 2013 DVD to the appropriate DVD folder.
Use the following commandline to extract the contents of the Service Pack to the extract folder.
Accept the license information (note: despite the fact that I'm running an English version of my OS, and I've opened the en-us version of the Service Pack installer, it still somehow comes with the EULA prompt in Dutch...... VERY strange).
The files are being extracted....
After it's completed, it should look something like this:
Now, copy all the files within extract_x86 or extract_x64 to your DVD\Updates folder
After it's done, you can test it by running setup.exe. In my case, I've used a custom msp file, which makes the installation silent. Note that if you have made a custom msp file, it still works, so no further customization is neccessary.
Once installed, you can open up Word 2013 for example, to check what version is installed.
The version 15.0.4569.1506 is the minimum version SP1 is at. Any higher or equal number indicates that you have installed SP1 (this is the same for the 64-bit version).
If you use SCCM, don't forget to update your distribution points!
Welcome back! Today we'll discuss how to create a driver package in SCCM 2012 R2, and add it to a Task Sequence. We will discuss how to use a WMI query in the Task Sequence, to distinguish the model to get the correct driver package. This way, we prevent that the wrong drivers will be installed on a certain device!
So lets start off by opening the SCCM console, and browsing to 'Software Library'.
Then rightclick 'Driver Packages' and click on 'Create Driver Package'
Give the driver package an appropriate name, in this case we are making a package for the DELL XPS 17.
Point it to the correct UNC path, and click on OK.
Next, we'll import the driver to SCCM. Rightclick 'Drivers', and click on 'Import Driver'.
A Wizard appears. Choose the location of where the driver resides.
Next, the wizard will show the recognized drivers.
Optionally, you can create or select a categorie. In this case, it's a Storage driver.
Next, choose the driver package where you want to add the driver(s) to. Optionally, you can check the checkbox 'Update distribution points when finished'.
You can optionally also add the driver to a boot image, and update the distibution point when the wizard finishes.
Check the details to see if everything is correct.
The drivers are being imported.
Everything went OK!
Next, you can update the driver package on the distribution point.
Accept the warning message.
Now, you can update the boot image(if needed) on the distribution point.
Follow the short wizard.
Now, you can edit the appropriate task sequence to include the driver package. First off, it's wise to retrieve the WMI information for the specific model.
1. Open a command prompt on the model (in this case a Dell XPS 17).
2. Type: WMIC Computersystem GET Model and hit enter
3. The output should be something like this:
Model
Dell System XPS L702X
Copy and paste this information to a Notepad, so that you can use it in your task sequence in a moment.
Next, rightclick the task sequence, and click Edit
Add an 'Apply Driver Package' step, in the appropriate place in the task sequence.
Give it the correct name, and choose the correct driver package.
On the Options tab, using 'Add Condition', you can add a Query WMI rule.
Paste in the following code:
SELECT * FROM Win32_ComputerSystem WHERE Model LIKE ""
Put the model you got from the WMI query you ran, between the quotation marks.
Click on Test Query. If it says that it contains valix syntax, the query should work.
Save the task sequence. Now you are ready to roll out a machine with the correct drivers!
