Config Mgr (SCCM) 2012 R2 Hotfix installation

Back to ConfigMgr main menu

The release of ConfigMgr 2012 R2 caused some issues with Operating System Deployment when a PXE enabled Distribution Point was co-located with Site Servers.

1. WDS crashing
2. Very slow download speeds for OSD files

The official descriptions are as follows:

Issue 1
After you enable the PXE Service Point role on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running.
Note: This problem affects only distribution points that are installed on site servers.


Issue 2
When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behavior when the target client is running Windows PE or a full Windows operating system.

These issues were resolved with Hotfix KB2905002. The Hotfix can be downloaded here

http://support.microsoft.com/kb/2905002/en-us?sd=rss&spid=1060

You can also find installation information on this page.

Download and extract the Hotfix files.

Launch the executable.

See the "Welcome Screen". It gives information on how KB2905002 should be applied. Click Next.

Accept the License Terms and click Next.

The prerequisite check begins. See the Warning.

A pending restart has been detected. Close and restart the server.

After the restart the prerequisite check passes.

Choose to install the update for the console.

Choose all the options.

Enter your preferred names and source for the Server package.

Enter your preferred names and source for the Console package.

Enter your preferred names and source for the client package.

Review the summary and click to install.

Update installation has completed successfully. Review the log file and click Next.

Click Finish to close the wizard.

Now deploy the server, console and client packages. Create x86 and x64 collections to deploy the correct client package.

Don't forget you HAVE to update all boot images on your Distribution Points.

Basic PowerShell Cmdlets for ConfigMgr 2012 (SCCM 2012)

Back to ConfigMgr main menu

Back to ConfigMgr & PowerShell menu

Native PowerShell support for ConfigMgr 2012 was introduced with SP1. Microsoft have published a Configuration Manager Cmdlet Reference in the Technet Library. You can find it here

http://technet.microsoft.com/en-us/library/jj821831(v=sc.10).aspx

I'd like to highlight some of the more commonly used cmdlets (ones that I find very useful and could use daily). Click on the cmdlet to link to the Technet library page explaining its use and syntax.

Hierarchy

Add-CMBoundaryToGroup                                                         

Assigns boundaries to a boundary group

Add-CmDistributionPoint                                                             

Creates a distribution point

New-CMBoundary                                                                          

Creates a new boundary

New-CMBoundaryGroup                                                             

Creates a new boundary group

New-CMSecondarySite                                                                 

Creates a secondary site in Configuration Manager

Assets

Add-CMDeviceCollectionDirectMembershipRule

Adds a direct membership rule to one or more Configuration Manager device collection

Approve-CMDevice                                                                        

Approves Configuration Manager device clients

Add-CMDeviceCollectionQueryMembershipRule             

Adds a query membership rule to one or more Configuration Manager device collections.

Install-CMClient                                                                                               

Installs a Configuration Manager client

New-CMDeviceCollection                                                            

Creates a collection for devices and adds the collection to the Configuration Manager hierarchy

Software Distribution

Add-CMDeploymentType                                                           

Adds a deployment type for an application

Approve-CMApprovalRequest                                                 

Approves a request to allow the installation of an application

Get-CMDeployment                                                                      

Gets a summary of Configuration Manager deployments

New-CMApplication                                                                       

Creates an application in Configuration Manager

Operating System Deployment

Add-CMDriverToDriverPackage                                                

Adds a device driver to a driver package

Clear-CMPxeDeployment                                                            

Clears the status of the most recent PXE deployment in Configuration Manager

New-CMDriverPackage                                                                 

Creates a driver package

New-CMOperatingSystemImage                                              

Creates an operating system image

New-CMTaskSequence                                                                

Creates a task sequence

Remove-CMDriverFromDriverPackage                                  

Removes a driver from a driver package

Set-CMDriverBootImage                                                              

Adds a driver to a boot image or removes a driver from a boot image

Software Updates

Add-CMSoftwareUpdateToGroup                                           

Adds a software update to a software update group in Configuration Manager

New-CMSoftwareUpdateGroup                                               

Creates a software update group

Connecting to ConfigMgr site via PowerShell

Back to ConfigMgr main menu

Back to ConfigMgr & PowerShell menu


There are two ways to connect to your Configuration Manager site via PowerShell.

Method 1: Using the Configuration Manager console

See the blue tab in the top left corner of the console. Click on the down arrow to reveal the menu. Select "Connect via Windows PowerShell".

It takes a few moments but PowerShell loads. See your Site Code in the command prompt.

Type the cmdlet get-cmsite for information about your site.


Method 2: Manually through PowerShell console

All Windows PowerShell cmdlets are coded and stored in a module.  The modules for Windows are available by default in your Windows PowerShell window and you can add more modules.  You add modules to your Windows PowerShell session by importing them using the Import-Module cmdlet.

This is the ConfigMgr module and can be found C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin

Open PowerShell as Administrator (Note that we need the x86 version - the ConfigMgr Admin Console is a 32-bit application) and navigate to that path.

Enter the cmdlet import-module .\ConfigurationManager.psd1 and press enter

Now all the ConfigMgr cmdlets are available

Connect to your site by typing the command

CD P01: (where P01 is your Site Code)

Try get-cmsite again

PowerShell Basics

Back to ConfigMgr main menu

Back to ConfigMgr & PowerShell menu

Windows PowerShell is Microsoft's task automation and configuration management framework, consisting of a command line shell and associated scripting language built on .NET Framework. It is a valuable administration tool as it combines the speed of a command line with the flexibility of a scripting language.

PowerShell commands are referred to as Cmdlets. All cmdlets are made up of two parts: a verb and a noun.  They are separated by a hyphen ‘-‘ character.

Some cmdlets are integrated with Windows, and others are installed with programs like ConfigMgr.

Launch PowerShell by clicking on this icon on the taskbar. (Open PowerShell as Administrator by right clicking - you should do this as most of the cmdlets you will be using will require this)

You can also search by typing PowerShell.

(Note that we need the x86 version - the ConfigMgr Admin Console is a 32-bit application)

Note the PS telling you that you are running PowerShell

Some useful commands

get-command gives you a list of all available PowerShell commands

See the verbs that can be used in cmdlets. Each verb can be used with in conjunction with various nouns to create powerful cmdlets

Add 
Block
Clear
Close
Connect
Copy
Disable 
Disconnect
Dismount
Enable
End
Export
Format
Get
Grant
Initialize
Import
Install
Invoke
Join
Limit
Measure
Merge
Mount
Move
New
Open
Optimize
Publish
Register
Remove
Rename
Repair
Reset
Resize
Resolve
Restore
Restart
Resume
Revoke
Save
Select
Send
Set
Show
Start
Stop
Suspend
Sync
Test
Unblock
Undo
Uninstall
Unregister
Update
Use
Wait
Write

get-command -verb Get

This will list all the Get cmdlets

Example

Get-service

Try this (use a service that you are allowed to stop - requires PowerShell to be run as administrator)

Get-Service -name WsusService
Stop-Service -name WsusService
Get-Service -name WsusService 

Start the service again

Start-Service -name WsusService

Verify that it is started

Get-Service -name WsusService

ConfigMgr 2012 & PowerShell

Back to main menu

Windows PowerShell is a very powerful way to automate your administrative tasks and native support was introduced with System Center 2012 Configuration Manager SP1.


ConfigMgr requires the 32-bit version of Windows PowerShell 3.0. It can be downloaded here: 

http://www.microsoft.com/en-us/download/details.aspx?id=34595

Powershell is already included as part of Windows Server 2012 Operating System so no further installation or configuration is necessary.

Note: Microsoft have published a "Windows PowerShell User's Guide". It is available on TechNet

http://technet.microsoft.com/en-us/library/cc196356.aspx

Please browse the following sections to learn about ConfigMgr and Powershell.

PowerShell Basics

Connecting to ConfigMgr site via PowerShell

Basic PowerShell Cmdlets for ConfigMgr 2012

Advanced PowerShell for ConfigMgr 2012

ConfigMgr 2012 / SCCM 2012 Anti-Virus exclusions

Back to Endpoint Protection menu

Back to main menu

When you install any Anti-Virus product on one of your ConfigMgr servers you must apply AV exclusions to avoid performance and functionality issues.

Also, if you are using SCEP you need to apply exclusions to your SCEP clients.  
These two blogs contain all the information you need.


Clifton Hughes

http://blogs.technet.com/b/systemcenterpfe/archive/2013/01/11/updated-system-center-2012-configuration-manager-antivirus-exclusions-with-more-details.aspx


Peter Daalmans 

http://www.systemcenterblog.nl/2012/05/09/anti-virus-scan-exclusions-for-configuration-manager-2012/