Failed to sync update fc5e8c16-7b3b-409f-8e42-5ffb3c1cf09d WSUS Synchronization failed with SCCM.

Today I faced a problem with WSUS Synchronization the update on SCCM.

This problem was annoying me. I can sync my WSUS db from Microsoft ok. But for some reason I am getting this error in SCCM.

Failed to sync update fc5e8c16-7b3b-409f-8e42-5ffb3c1cf09d. Error: The Microsoft Software License Terms have not been completely downloaded and cannot be accepted

It prevents my scheduled sync from passing and then it attempts to re-sync every 60 mins.

That above issue is known for MS and it’s often.

To resolve that issue you should have to run the following command on the WSUS server.

At the command line %drive%\Program Files\Update Services\Tools>, type:

Wsusut reset

Once you run the above command after that start the synchronization once again and you will see the synchronization.

Configuration Manager Content Library

The content library is a new concept that was introduced in System Center 2012 Configuration Manager.  In a nut-shell, the content library stores all the Configuration Manager content efficiently on the disk.  If the same file is part of two different packages, it stores only one copy in the content library.  However, references are kept indicating that the file is part of both the packages.

The focus of this blog is to provide more insights on what happens behind the scenes and help Configuration Manager users and administrators to understand the concept better.

Note: The content library is also known as the “single-instance store”, referring to the single instance of any particular file.

Rationale for the Content Library

The rationale for content library is to optimize disk storage and to avoid distributing a file that already exists on the distribution points.

If two different packages each contain a particular file that is identical (even if the file names are different), only one copy of this file will be stored by the content library.  This minimizes the disk space consumption.

When distributing a package, we first analyze all the files in that package. If a file to be distributed is already present on the distribution point as part of another package or part of a previous version of the same package, that file is not copied to the distribution point.  Instead, we add a mapping reference between that file and the new package that we are distributing. This helps reduce the network traffic by not copying files that already exist.  Additionally, it allows for more rapid provisioning of packages on the distribution point.

Location of the Content Library

A copy of the content library (containing all packages) is housed on the site server (as the source for distribution points).  Moreover, each distribution point will have a copy (as the source for clients), containing the packages distributed to the distribution point.  The content library is designed to optimize both network and disk usage in the distribution process.  This helps to keep our customers’ costs lower and efficiency higher.

The content library is typically stored on the root of a drive in a folder called “SCCMContentLib”.  This folder is shared and has restricted permissions to prevent accidental damage.  Within this are the Package Library (“PkgLib” folder), the Data Library (“DataLib” folder), and the File Library (“FileLib” folder).  The Package Library contains information about what packages are present on the distribution point.  The Data Library contains information about the original structure of the packages.  The File Library contains the original files in the package; this is typically where the bulk of the storage is used.

For instance, in the screenshot below, the content library is located on the root of the C: drive, in C:\SCCMContentLib.  It is shared as “SCCMContentLib$”.  Regardless of which drive the content library is located on, the primary share location will always be “SCCMContentLib$”.

Screenshot

 

Diagram

 

Package Library

The starting point for exploring the content library is the Package Library folder, “PkgLib”.  Within this folder will be several files, one for each package distributed to the distribution point.  The name will be the package ID, e.g. ABC00001.INI.  In this file is a list of contents IDs (under the “[Packages]” section) that are part of the package, as well as other information, such as the version.  Using these content IDs, we can continue exploring the contents of the content library.  Let us assume that ABC00001 is a legacy-style package, at version 1.  Thus, the content ID in this file will be ABC00001.1.

Data Library

Once we have found the content IDs we are interested in, we can continue exploring the content library.  In the Data Library folder, “DataLib”, there will be one file and one folder for each of the contents in each package.  This file and folder will be named, for example, ABC00001.1.INI and ABC00001.1, respectively.  The file contains information for validation.  Inside the folder, the folder structure from the original package is recreated. 

However, the files in the Data Library are replaced by INI files that have the name of the original file in the package, e.g. MyFile.exe.INI.  These files contain information about the original file, such as the size, time modified, and the hash.  The first four characters of the hash will help us find where the original file is in the File Library.  Suppose the hash in MyFile.exe.INI is “DEF98765”.  Thus, the first four characters are “DEF9”.

File Library

The last step in exploration is locating the file in the File Library, “FileLib”.  If the content library is spanned across multiple drives, the files could be in the File Library on any of these drives.

Using the first four characters from the hash found in the Data Library, we can locate the file.  Inside the File Library folder(s) will be many folders, each with a four-character name.  Find the folder that matches the first four characters from the hash.  Remember that the folder may be in the File Library on a different drive.

Once this folder is found, it will contain one or more sets of three files.  These three will share the same name, but one will have the extension INI, one will have the extension SIG, and one will not have any extension.  The file with no extension whose name is equal to the hash found above is the original file.

Using the example above, we would look for folder “DEF9”, containing “DEF98765.INI”, “DEF98765.SIG”, and “DEF98765”.  Here, “DEF98765” is MyFile.exe.  Additionally, in the INI file, there will be a list of “users”; these are content IDs that share the file.  The file will never be removed unless all of these contents are also removed.

Difference Between Distribute, Update, and Redistribute Actions

The first major action pertaining to content distribution is the Distribute action.  This refers to the initial distribution of a package to a distribution point.  This is triggered with Distribute Content in the Configuration Manager console.  This will transfer all files in a package to the target distribution points, excluding those which are already present as part of another package—these will become shared.

The second major action is the Update action.  This is typically used when a package has been changed and all distribution points to which it is distributed need the updated content.  This is triggered with Update Distribution Points in the console.  This will transfer the changed files to all distribution points.  Unchanged files will not be transferred.  If a file is removed from the package in the updated version, it will be deleted from the package on the distribution point (as long as no other packages are sharing it).

The third major action is the Redistribute action, triggered with Redistribute in the Configuration Manager console.  This will transfer the entire content to a specific distribution point.  Files will still be transferred and overwritten even if they are already present on the distribution point.  The chief purpose of the Redistribute action is to correct any inconsistencies that may exist in the content library.

Content Library Explorer

There is a new tool available in the System Center 2012 R2 Configuration Manager toolkit called “Content Library Explorer”.  This tool facilitates user-friendly exploration of the contents of the content library.  This tool cannot be used to modify the contents, but can provide insight into what is present, as well as allowing validation and redistribution.  Please refer to the toolkit documentation for more information. This documentation is installed with the toolkit.  There is typically a shortcut for it in the start menu called "System Center 2012 R2 Configuration Manager Toolkit Help".

Drive Spanning

The content library can be spanned across multiple drives.  These drives can be manually chosen by the administrator at the time the distribution point is created.  Alternatively, they can be chosen automatically by Configuration Manager (this is the default setting).

If they are chosen by the administrator, a primary and secondary drive can be chosen.  On the primary drive, all metadata will be stored.  Only the File Library will be spanned across to the secondary drive.  On secondary drives, the folder’s share name includes the drive letter.  For instance, if D: and E: are secondary drives for the content library, the share names would be “SCCMContentLibD$” and “SCCMContentLibE$”, respectively.

If “Automatic” is chosen, Configuration Manager selects the drive with the most available free space as its primary drive.  All of the metadata will be stored on this drive.  Only the File Library will be spanned across to secondary drives.  The administrator selects a reserve space amount; Configuration Manager attempts to use a secondary disk once the best available disk has only this reserve space amount left free.  Each time a new drive is selected for use, the drive with the most available free space is selected.

Currently it is not possible to specify that a distribution point should use all drives except for a specific set from the console.  It can be prevented by creating an empty file on the root of the drive, called exactly “NO_SMS_ON_DRIVE.SMS”.  This file must be present before the drive is selected for use by Configuration Manager.  If Configuration Manager detects this file on the root of the drive, it will not use the drive for the content library.  Additionally, there is a command-line tool in the toolkit for permanently moving the content library to a different drive, called “ContentLibraryTransfer.exe”.

Azure Distribution Points

Azure distribution points do not use single instancing.  This is because packages are encrypted before they are sent, and each package has a unique encrypted key.  So, even if two files were identical, the encrypted versions would not be.

Troubleshooting

Here are a few tips for troubleshooting issues with the content library:

• Check the logs on both the site server (distmgr.log and PkgXferMgr.log) as well as on the distribution point (smsdpprov.log) for any pointers to the failures.
• Use the Content Library Explorer tool to gain any additional insights.
• Check if there are any file locks by other processes (e.g. antivirus) or other software.  It is a good practice to exempt the content library on all drives from automatic antivirus scans, as well as the temporary staging directory, “SMS_DP$”, on each drive.
• If you still have issues you can try Validating the package from the Configuration Manager console and see if there are any hash mismatches.
• As a last option, you can redistribute the content which should resolve the issue.

Orphaned Contents

On occasion, it is possible for, files, contents, or packages to be orphaned on a distribution point—they are not distributed to the distribution point, but due to an error during deletion, they were not deleted.  Often this is due to external programs (such as antivirus) having file locks on the content when deletion is attempted by Configuration Manager.

This is a known issue.  The operability of Configuration Manager is not affected; the distribution point will still function as intended.  However, this orphaned content can waste disk space.  We are investigating ways to clean up the existing orphaned content in future releases of the toolkit, as well as fixing the product to ensure that no future content is orphaned.

http://blogs.technet.com/b/configmgrteam/archive/2013/10/29/understanding-the-configuration-manager-content-library.aspx

OS deployment fails (Failed to download policy )

Recently I have faced an issue with OS deployment. While OSD I got an error

While checking the smsts.log file I found the error in log file that was showing

BOM not found on policy reply

Failed to download policy {172A41CC-19A7-4BE3-91BC-0D979432CA10}/9 (Code 0x80004005).

 

 

 

I checked multiple things but nothing has worked.  Checked the package versions, scope IDs in application but everything was fine.

After that I searched the Policy in the SCCM database in table policyassignment and Policy

select * from policyassignment where policyid = '{172A41CC-19A7-4BE3-91BC-0D979432CA10}/9'

select * from policy where policyid = '{172A41CC-19A7-4BE3-91BC-0D979432CA10}/9'

 

after that I have deleted the policy which was showing as error in smsts.log file.

Delete from policyassignment where policyid = '{172A41CC-19A7-4BE3-91BC-0D979432CA10}/9'

Error while doing Prestage file on Sec Site/DP ExtractContent failed; 0x80040e09

I had an error while doing extract the prestage file on Sec Site

Above error was showing failed to execute the query to register content of package.

When I was checking everything was fine from DP site and as well as from Primary site.

Then again I checked the SQL permission on database, then found we have to grant the permission on service account in SQL server, which has been used for SQL server and Sec site/DP installation.

Then I provided the full permission on Service account then I was success

List of errors code during the client installation

2 – The system cannot find the file specified.

5 – Access denied.

52 – You were not connected because a duplicate name exists on the network. Make sure there is not a duplicate name in DNS and that 2 machines don’t have the same IP in DNS.

53 – Unable to locate, cannot connect to admin$ – Computer Browser not started 

58 – The specified server cannot perform The requested operation

64 – The specified network name is no longer available. Source: Windows

67 – network name cannot be found.

86 – network password is not correct? Machine Name <> resolved name.

112 – Not enough disk space

120– Mobile client on the target machine has the same version, and ‘forced’ flag is not turned on. Not processing this CCR ,target machine already have cm client and no force install selected(always install).

1003 – Cannot complete this function.

1053 – The service did not respond to the start or control request in a timely fashion.

1068 – The dependency service or group failed to start

1130 – Not enough server storage is available to process this command. Source: Windows

1203 – The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator.

1208 – An extended error has occurred. Source: Windows

1305 – The revision level is unknown.

1396 – Logon Failure: The target account name is incorrect. (NBTSTAT -a reverse lookup, duplicate IP address)

1450 – Insufficient system resources exist to complete the requested service. Source: Windows

1789 – The trust relationship between this workstation and the primary domain failed.

2147749889 – Generic WMI failure (Broken WMI)

2147749890 – not found – Source: Windows Management (WMI) – try repair WMI

2147749904 – Invalid class – Source: Windows Management (WMI)

2147749908 – Initialization failure – Source: Windows Management (WMI)

2147942405 – Access is Denied (Firewall rule? / MacAfee-HIPS?)

2147944122 – The RPC server is unavailable. 

2148007941 – Server Execution Failed

Improve SCCM console performance

We can improve SCCM 2012 Console performance by using of SQL server, we will have to configure a setting known as Maximum Degree of Parallelism or MAXDOP for short. When SQL Server runs on a computer with more than one CPU, it detects the best degree of parallelism, the number of processors employed to run a single statement, for each parallel plan execution. This means that multiple queries may be executed. Setting the MAXDOP setting to the optimal setting can help improve performance by setting the limit to the number of physical processors.

We will use SQL to configure this value by using SQL Management Studio using the following steps:

1) In the object explorer, right click a server and select Properties.

 2)      Click the Advanced node.

      3) In the Max Degree of Parallelism box, select the maximum number of processors to use in parallel plan execution.

The default value of 0 uses all available processors. Set max degree of parallelism to 1 to suppress parallel plan generation. Set the value to a number greater than 1 to restrict the maximum number of processors used by a single parallel query execution. If a value greater than the number of available processors is specified, the actual number of available processors is used. If the computer has only one processor, the max degree of parallelism value is ignored.

Improve the performance of PXE boot

To improve the PXE boot we have to enable/add a registry value in DP where PXE is enabled,

From the distribution point (where you enabled PXE) complete the following

1.        Open regedit and locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP

2.        Add a QWORD value and call it RamDiskTFTPBlockSize

3.        Give it a Hexadecimal value of “4000″

Installation Prerequisite Check for ConfigMgr 2012

One day I was installing SCCM 2012 secondary site, I had installed SQL express on local machine because from CM12 primary site it install on C drive,

Error when doing the Prerequisite installation checks Likewise “Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue.”

And “The logon account for the SQL Server service cannot be a local user account or LOCAL SERVICE. You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM;”

 

 

Both errors were normal but I was sure I have configured correct domain account for local service, and installation account was configured as the sysadmin server roles in SQL.

After that I did, went to services and again I have reconfigured the same domain account and did stop the service and start the service of SQL server,

And SQL Agent service was by default disabled, I made this enable and automatic.

Then again I did the Prerequisite installation checks and now this time all went pass.

Software Updates That Require Multiple Reboots may Cause Task Sequence Failure within Configuration Manager

Today Microsoft released a new KB targeting problems with the Install Software Updates hanging when you use the Install Software Updates step in a Task Sequence. This issue has been around since Configuration Manager 2007 and is still an issue in Configuration Manager 2012 with some updates.

“Software Updates That Require Multiple Reboots may Cause Task Sequence Failure within Configuration Manager“ 

The KB article is applicable both to Configuration Manager 2007 and 2012. Keep an eye on the KB above as it will be updated with more updates as they are reported, that will save a lot of troubleshooting time!

Symptoms:

“If a Configuration Manager Task Sequence that leverages the Install Software Updates step installs a software update that triggers multiple reboots, the task sequence can fail to complete successfully.”

Cause:

The first reboot initiated by the software update is properly controlled by the Task Sequence. However the second reboot request is initiated by a Windows component (typically Component-Based Servicing) and therefore not controlled by the Task Sequence.

Resolution:

“To resolve this issue, it is recommended that any updates that require dual reboots be applied using the normal Software Updates feature of Configuration Manager instead of Task Sequences. The following software updates have been reported as requiring multiple reboots. This KB will be updated as more updates are reported.”

For more information http://support.microsoft.com/kb/2894518/

CU3 for Configuration Manager 2012 SP1 (KB2882125)

Cumulative Update 3 for Configuration Manager 2012 SP1 has been released. Besides several fixes in all areas of the product, this cumulative update also adds support for Windows 8.1.

Supported Platforms
This update adds support for Windows 8.1-based client computers in Microsoft System Center 2012 Configuration Manager Service Pack 1. Windows 8.1 is added to the supported platform list for the following features:

1-Software distribution
2-Software update management
3-Compliance Settings


Have a look here for the complete list of issues that have been fixed and download the cumulative update
Here

SCCM report for Domain controller

Recently I have queried for a SCCM report for Server Configuration for domain controller ,
User wants to find the all details in one report like, Server Name, Bios Name, Serial Number, Model, Manufacturer, Ram Size, and Drive later and How many drives server have,

here is SQL query to find out the complete report

SELECT
sys.Name0 AS 'System Name',
os.Caption0 AS 'Operating System',
os.CSDVersion0 AS 'Service Pack',
PM.TotalPhysicalMemory0 /1024 as 'RAM in MB',
OS.InstallDate0 AS 'Original OS Install Date',
os.LastBootUpTime0 AS 'Last Boot Time',
NAC.IPAddress0 AS 'IP Address',
NAC.IPSubnet0 AS 'Subnet Mask'
FROM
dbo.v_GS_NETWORK_ADAPTER_CONFIGUR NAC
INNER JOIN dbo.v_GS_OPERATING_SYSTEM OS ON NAC.ResourceID = OS.ResourceID
INNER JOIN dbo.v_GS_PC_BIOS BIOS ON NAC.ResourceID = BIOS.ResourceID
INNER JOIN dbo.v_GS_SYSTEM sys ON NAC.ResourceID = sys.ResourceID
INNER JOIN dbo.v_GS_COMPUTER_SYSTEM CS on NAC.ResourceID = CS.ResourceID
INNER JOIN dbo.v_GS_X86_PC_MEMORY PM on NAC.ResourceID = PM.ResourceID
Where
NAC.IPaddress0 is Not Null
and CS.Roles0 like '%Domain_Controller%'

SCCM Report for Server Configuration

Recently I have queried for a SCCM report for Server Configuration,
User wants to find the all details in one report like, Server Name, Bios Name, Serial Number, Model, Manufacturer, Ram Size, and Drive later and How many drives server have,

here is SQL query to find out the complete report,

Select distinct V_R_System.Name0 as 'Server Name', V_R_System.Operating_System_name_and0 as 'OS', V_GS_Computer_System.Model0 as 'Model',
V_GS_Computer_System.NumberOfProcessors0 as 'Processors', v_GS_COMPUTER_SYSTEM_PRODUCT.IdentifyingNumber0 as 'Serial-Number' , V_GS_X86_PC_Memory.TotalPhysicalMemory0 as 'RAM'
,V_GS_Logical_Disk.DeviceID0 as 'Disk_Drive', V_GS_Logical_Disk.FreeSpace0,
V_GS_Logical_Disk.Size0 as 'Total'

from V_r_System inner join


V_GS_Logical_Disk on V_r_System.ResourceID=V_GS_Logical_Disk.resourceId Inner Join
V_GS_Disk on V_r_System.ResourceID=V_GS_Disk.ResourceID Inner Join
V_GS_Computer_System on V_r_System.ResourceID=V_GS_Computer_System.ResourceID inner join
v_GS_COMPUTER_SYSTEM_PRODUCT on V_r_System.ResourceID=v_GS_COMPUTER_SYSTEM_PRODUCT.ResourceId inner join
V_GS_X86_PC_Memory on V_r_System.ResourceID=V_GS_X86_PC_Memory.ResourceID

where V_R_System.Operating_System_name_and0 like '%Microsoft%Server%' and DriveType0='3'

New HOTFIX available: The content status of a package is stuck at "In progress - Waiting for Content" in ConfigMgr 2012 SP1

Microsoft has released new Hotfix for the issue "The content status of a package is stuck at "In progress - Waiting for Content" in ConfigMgr 2012 SP1"
Configuration Manager 2012 Service Pack 1 to correct the following issue:

1-You configure a Microsoft System Center 2012 Configuration Manager Service Pack 1 (SP1) primary site and a System Center 2012 Configuration Manager SP1 secondary site.
2-You create a package on the primary site.
3-You distribute the package to the distribution point of the secondary site.
4-You validate the package on the distribution point of the secondary site after the content status reads Success.
5-You verify that the content status reads Success after the validation is completed.
6-You right-click the package and then select Update distribution point.


In this scenario, the content status is stuck in In progress - Waiting for Content status instead of Success status.
You can find the complete article as well as download information for the hotfix here:

KB2828900 - FIX: The content status of a package is stuck in "In progress - Waiting for Content" status in System Center 2012 Configuration Manager SP1 (http://support.microsoft.com/kb/2828900)

Deploy Windows 8 Enterprise x86 on a UEFI x86 device using SCCM 2012 SP1

New Toys For The Boys
Don’t we all love new toys, especially the ones that require an occasional recharge.

The latest thing I got my hands on is the Lenovo Tablet 2, a very nice 10” tablet thing, with a couple of nice add-ons, like a docking station, Bluetooth keyboard and a pen like stylus. But what I really like about it is that it runs a full version of Windows 8 x86, which means that I can deploy its OS over and over again

So I fired up my SCCM Console to do exactly that …

The Drivers
First off I needed a driver package and Lenovo has been kind enough to supply a ready-made kit for SCCM.

Which can be downloaded from this URL http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS033326

After unpacking the kit, I imported the driver package without any issues





Reading through the readme file for the Lenovo driver kit, I found out that a few extra steps would be required to completely support the Tablet 2 device. The Mobile WAN device need a software package to be installed, and KB2761094 must be installed to remove two “yellow marks” in the device manager. So I added a package for each of these issues.

Mobile WAN device Package
I downloaded the driver for the Ericsson WAN device and got a Lenovo installer and a setup.exe (the only thing actually needed)

I created a package co

full article on
http://blog.coretech.dk/rja/deploy-windows-8-enterprise-x86-on-a-uefi-x86-device-using-sccm-2012-sp1

System Center 2012 Configuration Manager RTM Upgrade to SP1: DMP Proxy is not responding to HTTP requests

Recently I tried to upgrade my System Center 2012 Configuration

Manager RTM hierarchy to SP1, and found that the Device Management Point was

down after the upgrade. In the site console monitoring->component status, the

SMS_MP_CONTROL_MANAGER turned to critical and showed the error message: “DMP

Proxy is not responding to HTTP requests.” And there are also error messages in

mpcontrol.log: ”Call to HttpSendRequestSync failed for port 443 with status

code 500, text: Internal Server Error.”, and reinstall the DMP would not fix

this issue.

Then I tried to run the “\Windows\Microsoft.Net\Framework64\v4.0.30319\aspnet_regiis.exe–i” 

to refresh the ASP.net and IIS configuration, 

now the issue was resolved

When not to use IP Address Ranges as Boundaries in Configuration Manager

It is often surprising to me how what may seem like innocuous decisions on how to configure settings in Configuration Manager can lead to very different performance results. A case that has come up recently is the difference between using IP subnet based...(read more)

• Read the complete post at http://blogs.technet.com/b/configmgrteam/archive/2013/03/01/when-not-to-use-ip-address-ranges-as-boundaries-in-configuration-manager.aspx