Installing App-v 5.0 sp1 client in a task sequence

When installing the App-v 5.0 SP1 client during a task sequence using the /q switch for silent installation it will give you a exit code 0x68e.

For silent installation you'll need to use both /q and /Accepteula

The correct syntax will be: APPV_CLIENT_SETUP.EXE /Q /ACCEPTEULA

SCCM 2012 R2 - SQL Requirements

Configuration Manager 2012 R2 requires the following SQL versions

SQL Server 2008 SP2 with Cumulative Update 9 or higher
SQL Server 2008 SP3 with Cumulative Update 4 or higher
SQL Server 2008 R2 SP1 with Cumulative Update 6 or higher
SQL Server 2008 R2 SP2 with no Cumulative Update
SQL Server 2012 with Cumulative Update 2 or higher
SQL Server 2012 SP1 with no Cumulative Update

Free ebook:Troubleshooting Configuration Manager

Free ebook: Microsoft System Center: Troubleshooting Configuration Manager
Download from link below:

http://blogs.msdn.com/b/microsoft_press/archive/2013/11/12/free-ebook-microsoft-system-center-troubleshooting-configuration-manager.aspx

Great tool from Sysinternals!

Sysinternals provides a great tool for creating VHD versions of physical disks for use in Microsoft Virtual PC or Microsoft Hyper-V virtual Machines.

More information about Disk2vhd and download can be found here:
http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx

Clients do not update with the latest antimalware definition files after you install the Endpoint Protection point site system role.

Today I ran into this problem:

Clients do not update with the latest antimalware definition files after you install the Endpoint Protection point site system role in System Center 2012 Configuration Manager.

Solution was found in the article below.
http://support.microsoft.com/kb/2688242

OSD Task Sequence Fails with Error 0x80091007

Hash could not be matched for the downloded content
The hash value is not correct. (Error: 80091007; Source: Windows)

This error just occured on one machine and was due to bad memory on the machine.

Default location of Cmtrace.exe in WinPE 4.0

Cmtrace.exe is included in WinPE 4.0 and can be found in X:\SMS\BIN\I386\cmtrace.exe or in X:\SMS\BIN\x64\cmtrace.exe depending on architecture.

Pre-provision BitLocker

When you have upgraded to SCCM 2012 SP1 (and WinPE 4.0) the new task sequence step "Pre-provision BitLocker" will be available to you. This means that encryption will start from WinPE, right after the "Format and Partition" steps and "Set OSDDiskPart" and the result is a much faster encryption process. This applicable to Windows 7 and later operating systems.

Command to load .inf files to a booted WinPE image

To add .inf files to a booted WinPE image run this command:

drvload.exe filename.inf

SMS_DISTRIBUTION_MANAGER Error Message ID: 2302

Recently I started to recieve lots of errors with Message ID: 2302 for the SMS_DISTRIBUTION_MANAGER component after validating a package. The only way to stop this error was to delete the package from the ditribution point and then redistribute it agin.
If I after that tried to validate the package once again, the error came back..
This happens to all my packages if I select "validate package".

After some help from Microsoft, the resolution to this problem was to move a FILE named "Program" (without any file extension) that was located in the root of my E:\ drive to another destination.

Task Sequence problem after SCCM 2007 to SCCM 2012 SP1 migration

Ran into some problem after I had migrated a SCCM 2007 site to SCCM 2012 SP1

When running the Task Sequence I got the following errors in SMSTS.LOG

Empty location for package: _SMSTSP01000F1 ApplyOperatingSystem

Installation of image 1 in package P01000F1 failed to complete..
The system cannot find the file specified. (Error: 80070002; Source: Windows) ApplyOperatingSystem

The resolution was to change the deployment properties on the Task Sequence from "Access content directly from a distribution Point" to "Download content locally".

I Believe that changing the operating system package properties under Data Access to "Copy the content in this package to a package share on distribution Points" would have been the other solution to this problem.

How to change SQL collation

Problem installing SCCM due to wrong SQL collation?

If your SQL installation media path is E:
The command line syntax would be:
(Always test in non-production environment before using them in production Environment)

E:\setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=DOMAIN\administrator /SAPWD=YourPassword /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS

KB2506143 Known Issue: Configuration Manager Management Points collocated with clients fail after installing Windows Management Framework 3.0 and running Client Health Evaluation

See this article for more information:

http://blogs.technet.com/b/configmgrteam/archive/2012/12/18/known-issue-configuration-manager-management-points-collocated-with-clients-fail.aspx

And here for resolution:
http://support.microsoft.com/kb/2796086