Setting SMSCacheSize in SCCM 2012 task sequence does not work

Issue:
There are a lot of threads discussing the SMSCACHESIZE and how to configure this. The issue is that configuring the SMSCACHESIZE in the task sequence doesn’t work. The issue we had is that no matter what size is configured using the parameter in the task sequence it always set the client’s cache size to the default, which is 5120 MB.
SMSCacheSize

Reason:
After checking the product documentation about the SMSCACHESIZE property we found:
“This setting is ignored when you upgrade an existing client and when the client downloads software updates.”
Because we included the SCCM 2012 client in the image (build & capture), Microsoft calls this an upgrade of the client.

Solution:
Change the task sequence by adding a VBS script to change the SMSCacheSize after the installation as described below:
– Save the script below in a .VBS file and place it on a reachable location (for instances on shared folder on the distribution points)

Dim ClientResource
Set objShell = WScript.CreateObject ("WScript.shell")
Set ClientResource = CreateObject("UIResource.UIResourceMgr")
Set CacheInfo = ClientResource.GetCacheInfo
CacheInfo.TotalSize = 7680 ' Your new cache size in MB.

– Go to Software Library, Packages and choose Create Package
Give the package a name like Set SCCM Cache Size, choose a source folder like \\SCCM-NLD-DP\sources$\Software\Packages\SCCM_2012\SCCMCacheSize
Choose Next and choose the option Do not create a program, Next and finish
– Open the Task sequence, After the SCCM setup add a Run Command Line
Task Sequence SMSCacheSize
– Add the following line to the Command Line: cscript.exe //nologo \\SCCM-NLD-DP\sources$\Software\Packages\SCCM_2012\SCCMCacheSize\setcache.vbs

Problem fixed !

 

 

 

Build, Capture and deploy Windows 7 and Windows 8 in SCCM 2012 SP1

Operating System Deployment is one of the most utilized features of Microsoft System Center Configuration Manager 2012(SCCM). Many companies are now planning to upgrade their machines from Windows XP to Windows 7 or Windows 8 and will be using SCCM to do so. In the SP1 version of SCCM 2012 there are some minor issues which cause the OSD to fail.

This blog will describe the right steps to deploy Windows 7 and also Windows 8. This because there are no differences between deploying them
In the steps taken below we presume this is a clean install and you don’t have an Windows 7 image file.

First install hotfix http://support.microsoft.com/kb/2801987 on the Site Servers. This is required to do a successful PXE boot.

1. Enable the Network Access Account

The “Network Access Account” is needed during deployment in WinPE. The account is uses to access the content on the network. Often forgotten so we start with it..

  1. In the Configuration Manager console, navigate to Administration, choose  Site Configuration, right-click on the Primary site, and select Configure Components, Software Distribution.
  2. In the Network Access Account tab, click the Specifiy the account that access network locations, choose Set and Add the network access account and provide it with a password choose OK to finish the config

 

1. Enable PXE support and boot

  1. In the Configuration Manager console, navigate to Administration, choose  Site Configuration, and choose Servers and Site System Roles, and select the server which hosts you’re distribution point.
  2. In the results pane, double click the Distribution Point role and select the PXE tab, place a checkmark on Enable PXE support for Clients, answer Yes for the firewall port question.
  3. Check the Allow this distribution point to respond to incoming PXE requests and Enable unknown computer support also I’ve removed the password option but this is not required.
    PXE Update
  4. Click OK and the SCCM machine will distribute the settings.
  5. Next step is to distribute the Boot Images to the distribution points
  6. In the Configuration Manager console, navigate to Software Library, Operating Systems, Boot Images. Right click the X64 boot image and choose Distributed Content, Click Next and click Add, Distribution Point choose you’re distribution point.
  7. Continue through the wizard to complete the distribution
  8. DON’T Forget to repeat this step for the X86 image

 

2. Enable the PXE boot image

  1. In the Configuration Manager console, navigate to Software Library, Operating Systems, Boot Images. Right click the X64 boot image and choose Properties
  2. In the results pane, click Data Source, and enable the  Deploy this boot image from the PXE service point.
    Distribution Point Settings
  3. Select OK and the distribution point will be updated
  4. DON’T Forget to repeat this step for the X86 image.

 

3. Add the Windows 7 Operating System

Here’s where it get’s a bit tricky, SP1 doesn’t support the old Operating System Installers so a little change in SP1.

  1.  First of all I created the following structure to get a structured collection of Operating System Deployments.
    ScreenHunter_258 Feb. 18 15.52
  2.  Second I extracted the Windows 7 ISO and copied it to \\demo-sccm01\Sources\OSD\OSD Uploads\Windows7_x64_NLD folder.
  3. In the Configuration Manager console, navigate to Software Library, Operating Systems, Operating System Images, Right click and choose Add Operating System ImageAdd OS Image
  4. Browse to the to the Windows 7\Sources directory and select the install.wim like “\\demo-sccm01\Sources\OSD\OSD Uploads\Windows7_x64_NLD\Sources\install.wim
  5. Choose Next and finish the import of the WIM file
    Add the WIM File
  6. In the Configuration Manager console, navigate to Software Library, Operating Systems Images,  Right click the Image, choose Distribute Content,  Click Next and click Add, Distribution Point and choose you’re distribution point.

 

4. Next is build and capture the new image

Now we are going to build a new WIM file. This will be an template file which SCCM uses to rollout new Operating System Deployments

  1. In the Configuration Manager console, navigate to Administration, choose  Software library, Operating Systems, Task Sequences, Create a folder called Windows 7 x64, right click the folder and select Create Task Sequence
    1
  2. At the Create new task sequence choose Build and Capture a reference operating system image, Next
    2
  3. In the Task Sequence Information, give the task sequence a logical name like “Build and Capture – Windows 7 Pro x64 – NLD” , choose the “Boot Image (x64)…” and click Next
    3
  4. Choose the Operating System Image we imported (OSD Media – Windows 7 x64 Pro – NLD) in the previous step and choose Next
    4
  5. Choose the Image file, Optional license key and administrator password. I filled in the password to login in the reference machine after the build and capture. If the license key is also not necessary both settings can be set in the Deploy Sequence afterwards.
    6
  6. In the Configure Network choose the workgroup option. This because Sysprep will not work when you join the machine to a domain.
    7
  7. In the Install Configuration Manager Client section leave this default (installation properties can be blank, we will change this in the actual deployment.) Next.
    8
  8. At the Include Updates we checked Do not install any software updates, choose Next
    9
  9. Choose Next at the Install Applications
    10
  10. Choose Next at the System Preparation Section
    11
  11. Fill in the details on the Image Properties and choose Next
    12
  12. At the Save As dialog box, choose the created  \\demo-sccm01\Sources\OSD\OSD\Captures\ folder and give the image a proper name.
    13
  13. Choose Save, Next and Finish the task sequence
    15
  14. Right click the newly created task sequence and choose Edit
    16
  15. Click on the last partition task, choose Add, General, Set Task Sequence Variable
    This is to assign the C:\ as boot drive. Otherwise the sequence will install Windows on D:\.
    17
  16. Name tab type Assign C:\ to Boot drive, at the task Sequence Variable type OSDPreserveDriveLetter with the value false place the task behind the partition tasks
    18
  17. Choose OK to apply the task sequence changes.
  18. Now we are going to distribute the task sequence to the distribution point; right-click the newly build task sequence and choose deploy
    19
  19. I’ve chosen the collection All Unknown Computers, this results that the capture is available for everyone. In a test environment this is not issue but in production it’s not recommended, choose Next
    20
  20. In the Make available to the following choose Only Media and PXE, Next
    21
  21. Just next, next finish to the configuration; no additional changes are required.
    26
  22. OK now it’s get exiting; if everything went well you now can startup you’re client machine to boot with F12 and rollout a package!
  23. At the task Sequence Wizard, choose the Build and Capture – Windows 7 Pro x64 – NLD
    28
  24. The capture begins, the sequence finishes some steps to build the new WIM file
    29
    30 31 32
  25. In these steps you will see that the new WIM file is build in de Captures directory
    33

 

5. Deploy the captured image in a task sequence

Next we going to create the deploy sequence to rollout the WIM image to the clients.

  1. In the Configuration Manager console, navigate to Administration, choose  Software library, Operating Systems, Task Sequences, Create a folder called Windows 7 x64, right click the folder and select Create Task Sequence
    -1
  2. At the Create new task sequence choose Install an existing image package, Next
    -2
  3. In the Task Sequence Information, give the task sequence a logical name like “Deploy – Windows 7 Pro x64 – NLD“, choose the “Boot image (x64) 6….” boot image and click Next
    -3
  4. Choose the Operating System Image we created  (OSD Captued – Windows 7 x64 Pro – NLD nl-NL) in the previous step and choose Next
    -4
  5. Choose the Image file, Optional (if no KMS used) license key and set the administrator password to random and select the 2-2 image (the other one is the 100 MB partition).-5
  6. In the Configure Network choose the Join a Domain option. Fill in the domain, Domain OU and account (this is a test environment but please do not use administrator)-6
  7. In the Install Configuration Manager Client section and set the installation properties to SMSMP=Demo-SCCM01.demo.local
    Next.
    -7
  8. At the state migration we deselect all check boxes because we do not use this in the lab., choose Next
    -8
  9. At the Include Updates we checked Do not install any software updates, choose Next
    -9
  10. Choose Next at the Install Applications and finish the wizard.-10
  11. Right click the newly created task sequence and choose Edit-11
  12. Choose Add, General, Set task Sequence Variable.-12
  13. Name tab type Assign C:\ to Boot drive, at the task Sequence Variable type OSDPreserveDriveLetter with the value false place the task behind the partition task-13
  14. Choose OK to apply the task sequence changes.
  15. Now we are going to distribute the task sequence to the distribution point; right-click the newly build task sequence and choose deploy
    -14
  16. I’ve chosen the collection All Unknown Computers, this results that the deployment is available for everyone.
    -15
  17. In the Make available to the following choose Only Media and PXE, Next-16
  18. Just next, next finish to the configuration; no additional changes are required.
  19. OK now it’s get exiting; if everything went well you now can startup you’re client machine to boot with F12 and rollout a package!
    Boot with F12
  20. Choose the new created task sequence!
    Choose the Deploy image
  21. That’s it! The deployment will run successfully!!

Event ID 7000 : not a valid Win32 application during WSUS installation on SCCM 2012 SP1

Issue
Today after installing another fancy Windows 2012 SCCM Server I noticed that when I tried to configure WSUS and WDS the service crashed with the following error:
The WSUS Service failed to start due the following error: WSUS Service is not a valid Win32 application.
Event ID 7000.

Reason:
About a hour ago I also had an error on File Name Warning:
There is a file or folder on your computer called “C:\program” which could cause certain applications to not function correctly. Renaming it to “C:\program2” would solve this issue.
program error
I made a note of it but did not rename it because the message wasn’t wrong, there IS a file called program (no extension) on my Systemdrive. But why?
program
After a deep dive in my server configuration I discovered the distmgr.log of ConfigMgr is missing quotations while saving the log file. This could be an solution; after some more digging It looks like if the “” (quotation marks) were missing in the command line for the logfile path. Windows would then go and interpret the logfile as “C:Program”.

Program2
So this looks like a bug in the installation of the SCCM 2012 Distribution Manager installation.
To be sure I opened the program file with notepad and noticed that it’s indeed a text file.
program3

Resolution:
Rename or delete the c:\program file and the issue is solved.

WSUS sync issues after installation of SCCM 2012 SP1; Event ID 6703 SMS_WSUS_SYNC_MANAGER

Issue:

Today I bumped into a strange issue when upgrading SCCM 2012 to SP1. The installation went well and after checking the eventlog everything seemed to run smoothly.

After I changed the WSUS Sync setting of SCCM to every hour (because of Forefront Endpoint Protection) we noticed that the WSUS server didn’t function properly anymore. The Software Update Point gave the following error:
Log Name:      Application
Source:           SMS Server
Date:              14-1-2013 12:05:02
Event ID:         6703
Task Category: SMS_WSUS_SYNC_MANAGER
Level:              Error
Keywords:       Classic
User:               N/A
Computer:       SCCM01-SUP.internal.local
Description: On 14-1-2013 12:05:02, component SMS_WSUS_SYNC_MANAGER on computer SCCM01-SUP.internal.local reported:   WSUS Synchronization failed. Message: WSUS server not configured. Please refer to WCM.log for configuration error details.. Source: CWSyncMgr::DoSync. The operating system reported error 2147500037: Unspecified error

1 - Issue SCCM 2012 SP1 WSUS

Cause:
After some investigation we looked into the SUP properties via Administration, Site Configuration, Servers and Site System Roles.2 - SCCM 2012 SP1 WSUS ISSUE

In the Software Update Point settings we found that SP1 has changed the 8530 and 8531 ports back into 80 and 443 (default)
3 - SCCM 2012 SP1 WSUS ISSUE

Solution:
Well this looked like an easy one; we changed the ports back to where we configured WSUS (8530 and 8531) on and the issue was solved.
4 - SCCM 2012 SP1 WSUS ISSUE

 

Upgrading System Center Configuration Manager 2012 to Service Pack 1

After upgrading my test (Beta SP1) environment to SP1 went smoothly we rolled out SCCM 2012 SP1 to one of our customers (because of a running issue which should be solved in SP1).

It caused me some sweat but got it running eventually.
The scenario:
– Windows 2008 R2
– SQL 2008 R2
– SCCM 2012 CU2

Note: To install ConfigMgr 2012 SP1 with Windows Server 2012 and SQL 2012 SP1 see http://www.toolzz.com/?p=602

Here are the steps I took:
1. Install the WADK (Windows Assessment and Deployment Kit)
First of all there are some extra requirements to take for the upgrade. In SCCM 2012 SP1 you no longer use WAIK, we’re now on WADK.
– Go to http://go.microsoft.com/fwlink/?LinkID=252874and download the ADK Setup.
– Run the ADKSetup.exe as an administrator

– I left the path’s default and choose Next
– Choose if you want to join CEIP and choose Next
Accept the Licence Agreement and choose Accept
– Check Deployment Tools, Windows Preinstallation Environment (Windows PE) and User State Migration Tools (USMT)

– Choose Next and install the Software

2. Installing the SCCM 2012 SP1 software.
– I Downloaded the SP1 software from the Microsoft TechNet Site. It’s a little bit confusing but
System Center 2012 Configuration Manager and Endpoint Protection with sp1 x86 x64″
and “System Center 2012 Configuration Manager and Endpoint Protection x86 x64” with the date of 12 December are both valid.
– Start the Splash.hta on the disk
– Choose the Install option
SCCM SP1 Setup
– Choose “Upgrade this Configuration Manager site” and choose Next
SCCM SP1 Update 1
-Just note that there are more languages available then prior to SP1. Choose Next to continue
SCCM SP1 Update 2
– Check the prerequisite check. Because we implemented step 1 already we can continue by clicking Begin Install.
SCCM SP1 Update 3_1
In my case the installation took about one hour. The SQL database which was running on a different server was automatically updated.

3. The console issue
After starting up the console I bumped into an issue which was not very clear:

After upgrading to SP1 my console disappeared from my management server.
SCCM 2012 SP1 Console
After some troubleshooting I tried starting up the console from the directory; but it could not connect to the server.
Console issue SCCM 2012 SP1
This was strange, but after some investigating I discovered that the Console is not automatically updated with SP1 which causes this issue.
– Restarting the SP1 Splash.HTA and running Install Configuration Manager console solved the issue for me!
Update Console SCCM 2012 SP1
Checked the installation and we are indeed running on SP1 !!
SCCM SP1 Update 4
Henk Hoogendoorn posted a blog on what features are updated in the SP1 HERE.