SCCM 2012 SP1 Upgrade Checklist

This information was taken from Microsoft and could come in handy:

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

Use the information in the following check list to help you identify and plan for pre-upgrade configurations and additional actions that are related to upgrading your sites and hierarchy to Configuration Manager SP1.

Step More Information
Ensure that your computing environment meets the supported configurations that are required for upgrading to System Center 2012 Configuration Manager SP1. Before you upgrade to Configuration Manager SP1, install the required prerequisites on each computer that hosts a site system role. Several site system roles require new or upgraded prerequisites.

For example, to deploy an operating system, Configuration Manager SP1 uses the Windows Assessment and Deployment Kit (Windows ADK) instead of Windows Automated Installation Kit (Windows AIK). Before you run Setup, you must download and install Windows ADK on the site server and on each computer that runs an instance of the SMS Provider.

For general information about supported platforms and perquisite configurations, see Supported Configurations for Configuration Manager.

For information about how to use the Windows ADK with Configuration Manager, see the Prerequisites For Deploying Operating Systems in Configuration Manager topic in the Deploying Software and Operating Systems in System Center 2012 Configuration Manager guide.

Review the site and hierarchy status and verify that there are no unresolved issues. Before you upgrade a site, resolve all operational issues for the site server, the site database server, and site system roles installed on remote computers. A site upgrade can fail due to existing operational problems.

For information about the status of sites and site system roles, see Monitor Configuration Manager Sites and Hierarchy.

Install all applicable critical updates for operating systems on computers that host the site, the site database server, and remote site system roles. Before you upgrade a site, install any critical updates for each applicable site system. If it is required by an update that you install, reboot the applicable computers before you start the service pack update.

For more information, see Windows Update.

Disable database replicas for management points at primary sites. Configuration Manager cannot successful upgrade a primary site that has a database replica for management points enabled. Disable database replication before you create the backup of the site database to test the database upgrade, and before you upgrade the production site to Configuration Manager SP1.

For more information, see Configure Database Replicas for Management Points.

Reconfigure software update points that use NLBs. Configuration Manager cannot upgrade a site that uses a NLB cluster to host software update points. For more information, see the Upgrading from Configuration Manager with No Service Pack to Configuration Manager SP1 section in the Planning for Software Updates in Configuration Manager topic.
Back up the site database at the central administration site and primary sites. Before you upgrade a site, back up the site database to ensure that you have a successful back to use for disaster recovery.

For more information, see Backup and Recovery in Configuration Manager.

Disable the site maintenance task Delete Aged Client Operations on primary sites. Before you upgrade any sites to Configuration Manager SP1, disable this site maintenance task on each primary site in the hierarchy. When this task remains active at a primary site that runs Configuration Manager with no service pack, this task deletes information about active client operations for clients that run Configuration Manager SP1. After all primary sites are upgraded to Configuration Manager SP1; you can enable this task for standard site maintenance at each primary site.

For more information about site maintenance tasks, see the Planning for Maintenance Tasks for Configuration Manager section in the Planning for Site Operations in Configuration Manager topic.

Create a copy of each built-in collection you have modified. When you upgrade to Configuration Manager SP1, the built-in collections are overwritten in the site database. If you have customized a built-in collection, create a copy of that collection before you upgrade.

In Configuration Manager SP1, the built-in collections are read-only and cannot be modified.

Run the Setup Prerequisite Checker. Configuration Manager SP1 introduces new prerequisite checks. Before you upgrade a site, you can run the prerequisite checker independently from Setup to validate that your site meets the prerequisites. When you upgrade the site, the prerequisite checker runs again.

For more information, see the Prerequisite Checker section in the Install Sites and Create a Hierarchy for Configuration Manager topic.

For information about prerequisite checks, see Technical Reference for the Prerequisite Checker in Configuration Manager.

Download prerequisite files and redistributable files for Configuration Manager SP1. Use the Setup Downloader from the Configuration Manager SP1 source media to download prerequisite redistributable files, Configuration Manager SP1 language packs, and the latest product updates for the service pack upgrade.

For information about Setup Downloader, see the Setup Downloader section in the Install Sites and Create a Hierarchy for Configuration Manager topic.

Plan to manage server and client languages when you upgrade a site. Configuration Manager SP1 supports the same server and client languages as Configuration Manager with no service pack and it also supports additional languages that are introduced with Configuration Manager SP1. However, when you upgrade to Configuration Manager SP1, the site upgrade installs new versions of each language pack.

When you run Setup, Setup reviews the current language configuration of your site, and then identifies the language packs that are available in the folder where you store previously downloaded prerequisite files. You can then affirm the selection of the current server and client language packs, or change the selections to add or remove support for languages. Only those language packs that are available with the perquisite files you download are available.

Important
Server and Client language packs are service pack version-specific. You cannot use the language packs from Configuration Manager with no service pack to enable languages for a Configuration Manager SP1 site.

If you have previously installed a language pack for servers or clients at a site and a Configuration Manager SP1 version of that language pack is not available with the prerequisite files, that language cannot be selected and support for that language is removed from the site when it upgrades.

For more information about language packs, see the Planning for Client and Server Operating System Languages in Configuration Manager section in the Planning for Sites and Hierarchies in Configuration Manager topic.

For information about Setup Downloader, see the Setup Downloader section in the Install Sites and Create a Hierarchy for Configuration Manager topic.

Plan for new site system role prerequisites.

Important
The Prerequisite Checker for Configuration Manager does not verify the prerequisites for site system roles on the site server or on remote computers.
Several site system roles have new prerequisites for Configuration Manager SP1. Before you upgrade a site, verify that each computer that hosts a site system role meets any new prerequisites for Configuration Manager SP1.

During a site upgrade, Configuration Manager automatically upgrades site system roles at the site by reinstalling each site system role. When prerequisites are not met, the site system role might not reinstall or might reinstall but fail to operate correctly.

For information about prerequisites for site system roles, see the Site System Requirements section in the Supported Configurations for Configuration Manager topic.

Review the list of considerations for site upgrades. When you upgrade a site, some features and configurations reset to a default configuration. To help you plan for these and related changes in Configuration Manager SP1, review the information in the Considerations For Upgrading to Configuration Manager SP1 section in this topic.
Test the database upgrade process on a copy of the most recent site database backup. Before you upgrade a Configuration Manager central administration site or primary site to a new service pack, plan to test the site database upgrade process on a copy of the site database. This is because when you upgrade a site, the site database might be modified and although a test database upgrade is not required, it can identify problems for the upgrade before your production database is affected. A failed site database upgrade can render your site database inoperable and might require a site recovery to restore functionality.

Note
Configuration Manager does not support the backup of secondary sites, nor the test upgrade of a secondary site database.

Although the site database is shared between sites in a hierarchy, plan to test the database at each applicable site before upgrading that site. If you use database replicas for management points at a primary site, disable replication before you create the backup of the site database.

Important
It is not supported to run a test database upgrade on the production site database. Doing so will upgrade the site database and could render your site inoperable.

For more information, see the Test the Configuration Manager Site Database for the Upgrade section in the Upgrade Configuration Manager to a New Service Pack topic.

Restart the site server and each computer that hosts a site system role to ensure that there are no pending actions from recent installation of updates or prerequisites. Internal process that is company-specific.
Install the service pack. Starting at the top-level site in the hierarchy, run Setup.exe from the Configuration Manager SP1 source media. After the top-level site completes upgrade to Service Pack 1, you can begin upgrade of each child site. Complete the upgrade of each site before beginning upgrade of the next site.

Until all sites in your hierarchy upgrade to the same service pack version, you hierarchy operates in a mixed service pack version mode.

For information about how to run the service pack installation, see the Upgrade a Configuration Manager Site section in the Upgrade Configuration Manager to a New Service Pack topic.

For information about operating a Configuration Manager hierarchy in mixed mode, see the Interoperability between Sites with Different Service Pack Versions in System Center 2012 Configuration Manager section in the Interoperability between Different Versions of Configuration Manager topic.

Upgrade stand-alone Configuration Manager consoles. By default, when you upgrade a central administration site or primary site, the installation also upgrades a Configuration Manager console that is installed on the site server. However, you must manually upgrade each Configuration Manager console that is installed on a computer other than the site server

Tip
When you use a Configuration Manager console that is of a lower service pack version than the site you connect to, the console cannot display or create some objects and information that are available in the new service pack version. When you use a Configuration Manager console that is of a higher service pack version than the site you connect to, the connection is blocked.

When you upgrade a Configuration Manager console, the installation process uninstalls the existing Configuration Manager console, and then installs the new version of the software. Therefore, to upgrade a Configuration Manager console on computers other than site servers, you can use any method that Configuration Manager supports to install the Configuration Manager console. This can include a manual installation, or a deployment that installs the console.

For more information about how to install the Configuration Manager console, see the Install a Configuration Manager Console section in the Install Sites and Create a Hierarchy for Configuration Manager topic.

Reconfigure database replicas for management points at primary sites. If you use database replicas for management points at primary sites, you must uninstall the database replicas before you upgrade the site. After you upgrade a primary site, reconfigure the database replica for management points.

For more information, see the Configurations for Using a Database Replica section in Configure Database Replicas for Management Points topic.

Upgrade clients. After you upgrade a primary site, plan to upgrade clients that are assigned to that site. Although a Configuration Manager primary site or secondary site can support communication from clients that have a lower service pack version, this should be a temporary configuration. Clients that run a previous service pack version of Configuration Manager cannot use the new functionality that is available with the new service pack version of Configuration Manager.

When you upgrade a client, the current client software uninstalls and the new client software version installs. To upgrade clients, you can use any method that Configuration Manager supports.

Tip
When you upgrade the top-level site of a hierarchy to a new service pack, the client installation package on each distribution point in the hierarchy updates as well. When you upgrade a primary site, the client upgrade package that is available from that primary site updates.

For information about how to upgrade existing clients and how to install new clients, see How to Install Clients on Windows-Based Computers in Configuration Manager.

SCCM 2012 SP1 Site Backup and Afterbackup.bat

It’s always better and a preventive thought to Back-up your Daily SCCM 2012 Backup, (keeping a daily copy on the server and copying the backups to an alternate location). Because if your SCCM server falls down you still have a back-up!

In the process of SCCM’s daily backup (visible in smsbkup.log), there’s an ‘AfterBackup.bat‘ file used to perform post-backup actions automatically after the Backup Site Server maintenance task runs successfully. By default, the AfterBackup.bat batch file does not exist. You have to create and place it manually.


As we all know there was a bug in the SCCM 2012 RTM Backup Site procedure. There was a workaround by creating a sub-folder underneath the Backup folder when using UNC paths.

This is described by Microsoft in: http://blogs.technet.com/b/configurationmgr/archive/2012/08/01/support-tip-a-backup-site-server-maintenance-task-may-fail-to-run-in-configmgr-2012.aspx

 

Microsoft stated this would be addressed in SP1 of SCCM 2012, well let’s take a look and check-out the use of the ‘AfterBackup.bat’ procedure!

Activating site backup

ConfigMgr console > Administration tab > Site settings > Site maintainance > Backup site server


Edit and fill out the needed values.


You can set a local or remote UNC backup path and the scheduling options. Whatever you decide you can use the AfterBackup.bat to move or archive it afterwards.

The computer account of the ConfigMgr server has to have been granted full control permissions on the remote backup location.

Creating the AfterBackup.bat file

Here is a simple script for ‘AfterBackup.bat’ written by ‘Garth Jones’, which saves 7 days backup to a folder named after the first 3 letters of the day of the week, and also deletes/overwrites the older ones.

***********************************************************************************

REM @echo off

setlocal enabledelayedexpansion

set target=\\Destination_Server\E$\AfterBackup\%date:~0,3%

If not exist %target% goto datacopy

RD %target% /s /q

:datacopy

xcopy “\\Source_Server\*” “%target%\” /E /-Y

***********************************************************************************

where, “Source_Server” is the Primary Server from which the backup has to be copied,

and “Destination_Server” is the Remote Server where you want to copy the Site Backup.

 

Source_Server (This is the UNC path specified in ConfigMgr)

\\SCCM2012\sccm$\_Backup

Destination_Server (This is where we store the backup)

\\FILE01\SCCM$\SCCM_Backup

 

Although the intended use of AfterBackup.bat is to archive SCCM backup snapshots, you can use that file for other tasks that you need to perform at the end of every back up operation, such as:

 

  • Run a SQL Server DBCC test to verify that there are no integrity problems with the SCCM Site database.
  • Run a site health tool, or other health tools.

 

Putting the AfterBackup.bat to work

ConfigMgr has the ability to run an after backup batch file which you can use to perform archiving and other administrative functions.

Start by creating the AfterBackup.bat and copy it to the location below.

{ConfigMgrInstallPath}\inboxes\smsbkup.box\AfterBackup.bat

Once it’s in place ConfigMgr will automatically execute its contents at the end of a sms_site_backup task. It runs as the computer system account.

ConfigMgr overwrites each backup when it runs the site backup task. You must use the AfterBackup.bat or manual copy to archive more than one backup.

Starting a backup outside of the schedule

You can start a backup at any time by going into the service manager which can be launched through the console.

Monitoring tab > System Status > Component State > Ribbon > Start > Configuration Manager Service Manager

Once in service manager, locate the SMS_SITE_BACKUP service and right click start. A backup will now start.


Another option is to go to Windows Services.msc and start the SMS_SITE_BACKUP service.


 

After a successful backup you will see this in your logs:

And the backup is copied over to your alternate backup location!

SCCM 2012 SP1 binaries released for re-download

There were some flaws in the initial download files for Config Manager 2012 SP1. Microsoft has released the new binaries according to Steve TH – MSFT.

The binaries for System Center Configuration Manager 2012 and System Center Endpoint Protection 2012 have been updated to correct some minor issues. The binaries have been updated at the Download Center, and also on the Technet and MSDN download sites. For Configuration Manager 2012 SP1, the updated download release of SP1 includes the following hotfix:

Installation error 0x800b0101: System Center 2012 Configuration Manager Service Pack 1 client

http://support.microsoft.com/kb/2801987

For Endpoint Protection, the new binaries include fixed files (Linux/iOS) that were corrupt in the initial release.

MSDN Download Link:

https://msdn.microsoft.com/en-us/subscriptions/securedownloads/hh442898#FileId=52479

Technet Download Link:

https://technet.microsoft.com/en-us/subscriptions/securedownloads/hh442904#FileId=52479

Microsoft System Center 2012 Service Pack 1 Configuration Manager – Clients for Additional Operating Systems

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

This means if you downloaded the binaries prior to today (1/25) – you will likely need to re-download them.

 

Full post at: http://blogs.technet.com/b/gladiatormsft/archive/2013/01/26/you-may-need-to-re-download-configuration-manager-2012-and-endpoint-protection-2012-sp1-binaries.aspx

SCCM 2012 SP1 Client push fails with Authenticode Signature error

There is a problem with Client Push installation in Microsoft System Center Configuration Manager 2012 SP1. One of the prerequisites, MicrosoftPolicyPlatformSetup.msi, which comes during the ccmsetup installation is digitally signed and the signature expired on 10-01-2012. Therefore Client Installation cannot be performed!

Following error will appear in the ccmsetup.log:

c:\windows\ccmsetup\logs\ccmsetup.log:

Couldn’t verify ‘C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi’ authenticode signature. Return code 0x800b0101

 

Now what?!

 

Microsoft has released an update for this issue. Problem is that when you have your current images depending on SCCM for updates this will be a catch-22 situation!

Client will not install and updates will not be pushed to the clients…

You can off-line service your image with the following update, or use DSIM!

 

 

With this update installed you will be able to install your SCCM 2012 Clients again.

Let’s see if Microsoft will release an update for SCCM soon…

Well Microsoft was quick 😉

Hotfix available: http://support.microsoft.com/kb/2801987

Server 2012 DirectAccess: Useful NETSH Commands

During DirectAccess deployments, you can use several netsh commands as part of the initial deployment testing from a DirectAccess client. In the event of problems, this will often include the use of additional advanced netsh commands which are more troubleshooting focused.

The netsh tool is immensely powerful, and the following commands provide a good starting point to assess, understand and troubleshoot the DirectAccess client.

DirectAccess Client:

Settings and Status

Command: netsh dns show state

Description: This is probably the first and most useful command you will run, as it provides essential information on the current DirectAccess status and general configuration state.

netsh dns show state

netsh dns show state

Command: netsh namespace show policy

Description: This command is used to display the Name Resolution Policy Table (NRPT) that has been defined within Group Policy.

Command: netsh namespace show effectivepolicy

Description: This command is similar to the previous command but outputs the actual NRPT entries that are currently active on the DirectAccess client.

Common Transition Technology Interfaces

Command: netsh interface teredo show state

Description: This command shows the current status of the Teredo interface, if used at that time.

netsh interface teredo show state

netsh interface teredo show state

(Teredo not in use here)

Command: netsh interface httpstunnel show interfaces

Description: This command shows the current status of the IP-HTTPS interface, if used at that time.

netsh interface httpstunnel show interfaces

netsh interface httpstunnel show interfaces

Windows Firewall Settings and Status

Command: netsh advfirewall monitor show firewall

Description: This command is used to show the current status and configuration state of the local Windows Firewall.

 netsh advfirewall monitor show firewall      netsh advfirewall monitor show firewall

Command: netsh advfirewall show currentprofile

Description: This command is used to show the current Windows Firewall profile that is in use.

netsh advfirewall show currentprofile

netsh advfirewall show currentprofile

Command: netsh advfirewall monitor show mmsa

Description: This command is used to show the current status of the Windows Firewall main mode security associations that are present when the DirectAccess infrastructure and intranet IPsec tunnels are active.

Command: netsh advfirewall monitor show consec

Description: This command is used to show the current status of the Windows Firewall connection security rules which are used to define the DirectAccess infrastructure and intranet IPsec tunnels.

These commands can save you a lot of time during initial deployment!

Windows Server 2012 KMS Service Activation

So we have Windows Server 2012 and Windows 8 RTM and want to activate them with our KMS server. For this to be successful we need to update our KMS Service, with is currently servicing out Windows Server 2008 R2 servers and Windows 7 clients.

When we try to activate a Server 2012 server the following error will occur:

To resolve this issue:

Download and install the following update: KB2757817 (Update adds support for Windows 8 and Windows Server 2012 to Windows Server 2008, Windows 7, and Windows Server 2008 R2 KMS hosts).

How to obtain this update

The following files are available for download from the Microsoft Download Center:Collapse this tableExpand this table

Operating system Update
All supported x86-based versions of Windows Vista and of Windows Server 2008 Collapse this imageExpand this image

Download the update package now.

(http://www.microsoft.com/downloads/details.aspx?FamilyId=cca1a7a5-10f5-4aea-b0c5-999f2dc9f07f)

All supported x64-based versions of Windows Vista and of Windows Server 2008 Collapse this imageExpand this image

Download the update package now.

(http://www.microsoft.com/downloads/details.aspx?FamilyId=85cdb6a5-9658-47b3-b344-0284954a7379)

All supported IA-64-based versions of Windows Vista and of Windows Server 2008 Collapse this imageExpand this image

Download the update package now.

(http://www.microsoft.com/downloads/details.aspx?FamilyId=799f0f06-cbca-483c-8130-9bb99d8dc87e)

All supported x86-based versions of Windows 7 Collapse this imageExpand this image

Download the update package now.

(http://www.microsoft.com/downloads/details.aspx?FamilyId=a1829040-975f-43ab-877d-5cf4a5382987)

All supported x64-based versions of Windows 7 Collapse this imageExpand this image

Download the update package now.

(http://www.microsoft.com/downloads/details.aspx?FamilyId=23fd50b9-baa5-466f-9dff-af06729f23a9)

All supported x64-based versions of Windows Server 2008 R2 Collapse this imageExpand this image

Download the update package now.

(http://www.microsoft.com/downloads/details.aspx?FamilyId=bd2cda64-6319-4beb-91e3-9439048bf19d)

All supported IA-64-based versions of Windows Server 2008 R2 Collapse this imageExpand this image

Download the update package now.

 

If you don’t install this Update then registering a Windows Server 2012 KMS will throw an Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid.

So install the update (Windows6.1-KB2757817-x64.msu) and restart the server!
Just restarting the KMS service (“net stop sppsvc” and “net start sppsvc“) is NOT enough.

Let’s see what is already running:

slmgr.vbs /dlv => The Windows 2008 R2 KMS key.

Uninstall the current KMS key using slmgr.vbs /upk
(We all know this has to be done from an elevated command prompt..)

Now it is time to install the new KMS key.

slmgr.vbs /ipk {YOUR_SERVER_2012_KMS_KEY}

slmgr.vbs /ato to activate the KMS Service

And now we can check our environment to see what we can activate:

slmgr.vbs /dlv => the Windows Server 2012 KMS key.

 

RoboCopy switches

So I was busy with the most fabulous copy tool ever – RoboCopy.
I always forget the exact switches, so for reference use here they are:

/S Copies subdirectories (excluding empty ones).
/E Copies all subdirectories (including empty ones).
/LEV:n Copies only the top n levels of the source directory tree.
/Z Copies files in restartable mode (that is, restarts the copy process from the point of failure).
/B Copies files in Backup mode (Backup copies are not restartable, but can copy some files that restartable mode cannot).
/ZB Tries to copy files in restartable mode, but if that fails with an “Access Denied” error, switches automatically to Backup mode.
/COPY:copyflags Copies the file information specified by copyflags, which can be any combination of the following :
D – file Data. S – file Security (NTFS ACLs).
A – file Attributes. O – file Ownership information.
T – file Timestamps. U – file aUditing infomation.
Source and destination volumes must both be NTFS to copy Security, Ownership or Auditing information.
/COPYALL Copies Everything. Equivalent to /COPY:DATSOU.
/NOCOPY Copies Nothing. Can be useful with /PURGE.
/SEC Copies NTFS security information. (Source and destination volumes must both be NTFS). Equivalent to /COPY:DATS.
/MOV Moves files (that is, deletes source files after copying).
/MOVE Moves files and directories (that is, deletes source files and directories after copying).
/PURGE Deletes destination files and directories that no longer exist in the source.
/MIR Mirrors a directory tree (equivalent to running both /E and /PURGE).
/A+:{RASHNT} Sets the specified attributes in copied files.
The following attributes can be set:
R – Read only S – System N – Not content indexed
A – Archive H – Hidden T – Temporary
/A-:{RASHNT} Turns off the specified attributes in copied files.
The following attributes can be turned off:
R – Read only S – System N – Not content indexed
A – Archive H – Hidden T – Temporary
/CREATE Creates a directory tree structure containing zero-length files only (that is, no file data is copied).
/FAT Creates destination files using only 8.3 FAT file names.
/FFT Assume FAT File Times (2-second granularity). Useful for copying to third-party systems that declare a volume to be NTFS but only implement file times with a 2-second granularity.
/MON:n Monitors the source directory for changes, and runs again when n changes have been detected, and the minimum time interval specified by /MOT has elapsed.
/MOT:n Monitors the source directory for changes, and runs again when a further n minutes have elapsed, and the minimum number of changes specified by /MON have been detected.
/RH:hhmm-hhmm Defines the time slot during which starting new copies is allowed. Useful for restricting copies to certain times of the day. Both values must be 24-hour times in the range 0000 to 2359.
/PF Makes more frequent checks to see if starting new copies is allowed (per file rather than per pass). Useful in stopping copy activity more promptly at the end of the run hours time slot.
/IPG:n Inserts a delay of n milliseconds after each 64k chunk of file data is copied. Useful for freeing up bandwidth on slow lines.
/IA:{RASHCNETO} Includes files with the specified attributes.
The following file attributes can be acted upon:
R – Read only A – Archive S – System
H – Hidden C – Compressed N – Not content indexed
E – Encrypted T – Temporary O – Offline
/XA:{RASHCNETO} Excludes files with the specified attributes.
The following file attributes can be acted upon:
R – Read only A – Archive S – System
H – Hidden C – Compressed N – Not content indexed
E – Encrypted T – Temporary O – Offline
/A Copies only files with the archive attribute set.
/M Copies only files with the archive attribute set and then resets (turns off) the archive attribute in the source files.
/XJ Excludes Junction points.
/XF file [file] Excludes files with the specified names, paths, or wildcard characters.
/XD dir [dir] Excludes directories with the specified names, paths, or wildcard characters.
/XC Excludes files tagged as “Changed”.
/XN Excludes files tagged as “Newer”.
/XO Excludes files tagged as “Older”..
/XX Excludes files and directories tagged as “Extra”.
/XL Excludes files and directories tagged as “Lonely”.
/IS Includes files tagged as “Same”.
/IT Includes files tagged as “Tweaked”.
/MAX:n Excludes files larger than n bytes.
/MIN:n Excludes files smaller than n bytes.
/MAXAGE:n Excludes files with a Last Modified Date older than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.
/MINAGE:n Excludes files with a Last Modified Date newer than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.
/MAXLAD:n Excludes files with a Last Access Date older than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.
/MINLAD:n Excludes files with a Last Access Date newer than n days or specified date. If n is less than 1900, then n is expressed in days. Otherwise, n is a date expressed as YYYYMMDD.
/R:n Specifies the number of retries on failed copies. (The default is 1 million.)
/W:n Specifies the wait time between retries. (The default is 30 seconds.)
/REG Saves /R:n and /W:n in the registry as default settings.
/TBD Waits for share names to be defined on a “Network Name Not Found” error.
/L Lists files without copying, deleting, or applying a time stamp to any files.
/X Reports all files tagged as “Extra”(including files not selected).
/V Produces verbose output (including skipped files).
/TS Displays source file timestamps in the output log.
/FP Displays full pathnames of files in the output log.
/NC Suppresses output of Robocopy file classes.
/NS Suppresses output of file and directory sizes.
/NDL Turns off logging of directory names. Full file pathnames (as opposed to simple file names) will be shown if /NDL is used.
/NFL Turns off logging of file names. File names are still shown, however, if file copy errors occur.
/NJH Turns of logging of the job header.
/NJS Turns off logging of the job summary.
/NP Turns off copy progress indicator (% copied).
/ETA Shows estimated time of completion for copied files.
/LOG:file Redirects output to the specified file, overwriting the file if it already exists.
/LOG+:file Redirects output to the specified file, appending it to the file if it already exists.
/TEE Displays output in the console window, in addition to directing it to the log file specified by /LOG or /LOG+.
/JOB:job Reads parameters from the named Job file.
/SAVE:job Writes the current parameter settings to the named Job file.
/QUIT Quits after processing the command line. No files will be copied. Use /QUIT with /JOB to view job file contents.
/NOSD Declares that no source directory is specified. Useful in template Jobs for which the source is provided at run time.
/NODD Declares that no destination directory is specified. Useful in template Jobs for which the destination is provided at run time.
/IF Includes files with the specified names, paths, or wildcard characters. Intended for use in Job files only.
/SD:path Explicity specifies the source directory for the copy. Intended for use in Job files only.
/DD:path Explicitly specifies the destination directory for the copy. Intended for use in Job files only.

Microsoft System Center 2012 Endpoint Protection Cookbook

Hi,

I have done a book review on the Microsoft System Center 2012 Endpoint Protection Cookbook which I wanted to share with you.

The auther, Andrew Plue, has done a great job on explaining the latest and greatest anti-virus and anti-malware product of Microsoft, Endpoint Protection.

The book was published by Packt Publishing and can be found here!

Microsoft Forefront EndPoint Protection 2010 Cookbook

Microsoft Forefront EndPoint Protection 2010 Cookbook

Have fun with it, I did!

Report Builder 2.0 is not installed as a click-once application on report server – SCCM 2012

When you click on Monitoring > Reporting and you want to create a new custom report, you could get a prompt with the message that Report Builder 2.0 is not installed as a click once application.

Error custom report - SCCM 2012

Error custom report – SCCM 2012

 

Do not type in the url in to Internet Explorer and start downloading and installing the Report Builder 2.0. Instead do this, because ConfigMgr 2012 has the Report Builder 3.0 application bundled:

  1. Open Regedit
  2. Browse to[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ConfigMgr10\AdminUI\Reporting]
  3. Double click on ReportBuilderApplicationManifestName
  4. Change the Value data from ReportBuilder_2_0_0_0.application to ReportBuilder_3_0_0_0.application
  5. Run the SCCM Console as Administrator
Regedit for Report Builder 3.0

Regedit for Report Builder 3.0

Data Deduplication in Windows Server 2012


With Windows Server 2012 Microsoft introduces a built-in software based data deduplication solution. Where some deduplication solutions provide their services file-based, the deduplication in Windows Server 2012 is block-based.

Deduplication in Windows Server 2012:

  • Only available in Windows Server 2012.
  • Deduplication is cluster aware.
  • Based on a filter driver per volume.
  • Not supported on boot- or system volumes, only intended for data storage volumes.
  • Does not work on compressed or NTFS encrypted files.
  • Deduplication requires an NTFS file system and is not supported for the new ReFS file system which is introduced in Windows Server 2012.
  • Does not work with Cluster Shared Volumes.
  • Does not work with encrypted files, files smaller than 32KB, re-parse points or files with extended attributes.
  • Not configurable through Group Policy.
  • It is a post-process deduplication process.
  • Windows caching is deduplication aware.

Data deduplication – Possible Savings
Microsoft has done some research in their deduplication technology and come up with some numbers on the storage savings deduplication provided:

Usage Possible Saving
General 50-60%
Documents 30-50%
Application Library 70-80%
VHD(X) Library 80-95%

Data deduplication – Performance

Data deduplication will cost you some performance, that is a fact.

Whether done on a storage level or in an OS…

Microsoft has offered some information about this.
Write actions have no direct performance hit since the deduplication process is done in the background when the system is idle.
Read actions do have a performance hit, around 3% when the file is not in cache.

My real life experience so far: the performance loss is totally neglectable and the you will love the amount of data you can put on that fast SSD!

Data deduplication and PowerShell
Deduplication can be configured, controlled and monitored via the new Server Manager GUI or by PowerShell.


To enable the deduplication feature by using PowerShell commands:
 

Add-WindowsFeature -name FS-Data-Deduplication

To configure deduplication on volume D on a device:

Enable-DedupVolume D:

To get the statistics of a volume (the amount of storage we actually saved) use:

Get-DedupStatus

By default, the deduplication process will only affect files that have not been changed for 30 days.

To change this value to for example: 0 (process the file a.s.a.p.) use:

Set-DedupVolume D: -MinimumFileAgeDays 0

The deduplication process is done through scheduled tasks.

My advice: do not use the scheduled tasks if you are running Virtual Machines on the volume.
If this is your scenario (like mine), shut down the VM’s and do a manual optimization after creating one or more VM’s!
To start this process manually use:

Start-DedupJob D: –Type Optimization

To view the status of a job, use:

Get-DedupJob

We can use PowerShell to enable deduplication, but we can also disable deduplication on a volume with PowerShell.

Use this:

Start-DedupJob -Volume D: -Type Unoptimization

For the PowerShell cmdlet’s for deduplication use:

Help Dedup