Running “apply operating system” is failing with error code 0x80070241

Issue: - Running “apply operating system” is failing with error code 0x80070241

The SMSTS.log looked like below

<![LOG[Skipping C:\_SMSTaskSequence for wipe]LOG]!><time="10:43:35.088+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="1" thread="896" file="ccmfile.cpp:983">

<![LOG[Calculating expected free space.]LOG]!><time="10:43:35.103+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="0" thread="1336" file="installcommon.cpp:229">

<![LOG[Reporting deletion progress.]LOG]!><time="10:43:35.103+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="0" thread="1336" file="installcommon.cpp:247">

<![LOG[Successfully wiped C:\]LOG]!><time="10:43:35.119+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="1" thread="896" file="installcommon.cpp:860">

<![LOG[Applying image to C:\]LOG]!><time="10:43:35.119+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="1" thread="896" file="installimage.cpp:709">

<![LOG[Applying image 1 to volume C:]LOG]!><time="10:43:35.134+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="1" thread="896" file="wimfile.cpp:511">

<![LOG[WIM error:C:\Windows\winsxs\x86_microsoft-windows-d..ndwritingrecognizer_31bf3856ad364e35_6.1.7600.16385_none_2bca79fd9bfe072a\mshwjpnrIME.dll.

Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Error: 80070241; Source: Windows)]LOG]!><time="10:49:30.097+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="3" thread="1340" file="wimstate.cpp:193">

<![LOG[WIMApplyImage( hVolumeImage, const_cast<LPWSTR>(pathTargetVolume.c_str()), WIM_FLAG_VERIFY), HRESULT=80070241 (e:\nts_sccm_release\sms\framework\tscore\wimfile.cpp,557)]LOG]!><time="10:49:30.238+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="0" thread="896" file="wimfile.cpp:557">

<![LOG[Unable to apply (0x80070241)]LOG]!><time="10:49:30.238+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="3" thread="896" file="wimfile.cpp:557">

<![LOG[this->imageFile.ApplyVolumeImage(imageIndex, this->targetVolume), HRESULT=80070241 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,727)]LOG]!><time="10:49:30.300+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="0" thread="896" file="installimage.cpp:727">

<![LOG[ApplyImage(), HRESULT=80070241 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1431)]LOG]!><time="10:49:30.300+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="0" thread="896" file="installimage.cpp:1431">

<![LOG[Apply(), HRESULT=80070241 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1614)]LOG]!><time="10:49:30.316+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="0" thread="896" file="installimage.cpp:1614">

<![LOG[Installation of image 1 in package CAS0017B failed to complete.. Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Error: 80070241; Source: Windows)]LOG]!><time="10:49:30.316+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="3" thread="896" file="installimage.cpp:1636">

<![LOG[installer.install(), HRESULT=80070241 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1689)]LOG]!><time="10:49:30.316+00" date="03-06-2014" component="ApplyOperatingSystem" context="" type="0" thread="896" file="installimage.cpp:1689">

Screenshot from trace32:

Steps tried, but failed to fix it:

• Re-uploaded the entire WIM file
• Uploaded the WIM by splitting the WIM to smaller size and smaller parts
• At the failed phase tried to apply the WIM by using DISM/Imegex but the wim can be applied
• Able to Mount and unmount the same WIM by Using DISM
• Verified the WIM Hash file and matched exactly
• Finally no clue how to proceed further
• Tried to re-upload the WIM from FTP and created all new packages and tried
• Downloaded the failed WIM to other SCCM Test system and tried to deploy by creating a test system and found same error at same phase this confirmed the issue with WIM but not sure how to confirm.

Solution:-

We have recopied the Original WIM file by using ROBOCOPY and the issue was fixed. Thanks to ROBOCOPY

Add remove programs will not display and it is Blank

 

We have come across after system build Add remove programs not displaying the installed programs nor not able to add any new features

There is a Patch for this is more into Certificate file expiry

Windows6.1-KB2749655-x86.msu
http://support.microsoft.com/kb/2749655

KMDF Related Issues

I have seen a strange problem when we target the drivers as software package the installation was never triggered in the Task sequence, When we look for an alternative to make this package as PnP it will fail some time the package will install however we will get below error screen,

By looking at the error screen… we can think of it could be sysprep issue or unattended.xml issue but that is not the case. I have even suspected the issue with “Open File Security Warning” but interestingly this is not the case. I have also tested on SCCM 2007 and 2012 I got the same errors and When I have changed my program command lines execution method i.e., sometimes I used .Bat, .CMD, .PS1 and .Vbs atleast sometimes it works sometimes it is not working………. But the root cause is un-known…. When investigated further found below….

Issue was Experienced Models: X440, L440, T440p, M83, X240

When looked at the Smsts.log file found “Not enough storage is available to complete this operation. (Error: 8007000E; Source: Windows)”

Log file entries:-

pInstall->Install(sPackageID, sProgramName), HRESULT=8007000e (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,374) InstallSoftware 04/03/2014 10:23:42 2776 (0x0AD8)

Install Software failed, hr=0x8007000e InstallSoftware 04/03/2014 10:23:42 2776 (0x0AD8)

Process completed with exit code 2147942414 TSManager 04/03/2014 10:23:42 1408 (0x0580)

!--------------------------------------------------------------------------------------------! TSManager 04/03/2014 10:23:42 1408 (0x0580)

Failed to run the action: AMTSOLLMS.

Not enough storage is available to complete this operation. (Error: 8007000E; Source: Windows) TSManager 04/03/2014 10:23:42 1408 (0x0580)

Sending status message . . . TSManager 04/03/2014 10:23:42 1408 (0x0580)

When looked from Trace…

Solution:-

This kind of issues we have on almost on all the new release of 2013 laptop models regardless of Manufacture Dell/HP/Lenovo because these are meant for Windows 8 OS where windows 8 support the UEFI.

Before we install OS we need to apply KMDF patch on all OS, as a SOE engineer it’s better to include this in all your WIM images before you actually deploy to latest models (I personally suggest).

For the solution steps, keep a look at my simple Task sequence that I have … I will be explaining you in next section

For my Partition Disk I have defined variable as %OSDisk% .. see the below screenshot

After apply Operating system, I have added a command line as below, for DISM Temp Directory

cmd.exe /c mkdir %OSDisk%\Dummy

I have downloaded the patch from Microsoft and used 7zip tool and extracted it
Path for Download link

http://www.microsoft.com/en-in/download/details.aspx?id=38423

Based on the X86 (kmdf-1.11-Win-6.1-x86.msu) or X64 (kmdf-1.11-Win-6.1-x64.msu) Once you have extracted the
If extracted X86 you will be getting below

If Extracted X64 you will be getting as below

Create a SCCM Software package (program is not required) from the source that you have extracted above i.e., X86 or X64 the version is dependent on your WIM Architecture

In the SCCM task Sequence call a Step as Install KMDF and type of step should be a “Run Command Line”

And in the command line paste below and replace the package ID with your package ID i.e., LAB00080 with your package ID

cmd.exe /c X:\windows\system32\dism.exe /ScratchDir:%OSDisk%\Dummy /Image:%OSDisk%\ /Add-Package /PackagePath:%_SMSTSMDataPath%\Packages\LAB00080\Windows6.1-KB2685811-x86.cab

Note:- if you are deploying for Windows X64 Bit then you also need to change the from Windows6.1-KB2685811-x86.cab to Windows6.1-KB2685811-x64.cab in the above command line

Show the Package that we have created in SCCM sw distribution section.

Finally in the task Sequence will call a command line to clean up the Directory temp Directory that we used at the first step of task sequence

cmd.exe /c rmdir "%OSDisk%\Dummy" /q /s

That’s all….

Now it should start installing all the drivers packages that you pushed from PnP or as Bad package / Software Distribution based..

Packages are not distributed to Child Sites

This behavior can occur because the Sms\Inboxes\Schedule.box\Uid folder is empty or does not exist or incorrect files in the \SMS\inboxes\schedule.box\UID folder can stop or inhibit communications

To resolve this behavior, you must open the Sms\Inboxes\Schedule.box\Uid folder and create two empty text files called nnnnnnnn.job and nnnnnnnn.req, where nnnnnnnn is the number in the filename, which is greater than any of the files' names that were already found in the directory SMS\Inboxes\Schedule.box (Guess what could be the greater name???? it took for me some time but finally the file name should be… ZZZZZZZZ …..I have mentioned below the process for how to do it)

How to do it:-

Stop the SMS Executive Service.

Verify that the \SMS\inboxes\schedule.box\UID folder exists. Create it if it does not.

Place two files in this folder. Because the scheduler processes jobs in a sequential fashion, you will want to create files that are at the end of the processing cycle. Name the first one ZZZZZZZZ.JOB and the other ZZZZZZZZ.REQ. 

Start the SMS Executive Service.

In some cases communications will be in stopped state, but there are two files already in the UID directory, Just delete them and adding the "Z" files.

Note:- Make sure there are 8 "Z"'s in the file name

~~~~~~~~~~

Enjoy

How to grant the SCCM Console permissions to Support Executive

Scenario SCCM installed on cm07.test.com & I have a test system with windows XP/7.
I have a User called RBAC and RBAC wanted some permissions on SCCM console.

Steps:-

Install the SCCM console on windows Xp/7

add the RBAC user to SMS Admins Group.

Follow these steps for granting the DCOM rights.

1. From SCCM Server the Start menu, click Run and type Dcomcnfg.exe.

2. In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties.

3. In the My Computer Properties dialog box, on the COM Security tab, in the Launch and Activation Permissions section, click Edit Limits.

4. In the Launch Permissions dialog box, click Add.

5. In the Select User, Computers, or Groups dialog box, in the Enter the object names to select (examples): box, typeSMS Admins and click OK.

6. In the Permissions for SMS Admins section, select the check box to allow Remote Activation.

7. Click OK twice, and then close Computer Management.

To get ride of IIS Webdav issue

Most of the time some or other application extension would be blocked because of IIS Webdav Settings issue, to stop filtering in IIS Webdav we can change the

setting at the site level, i.e., open inetmgr/ IIS Console and chose the server name and in the right side we need to choose the “WebDav Authoring Rules” and in actions you will see “WebDAV  settings” click on the  button and you need to configure you Request filtering Behavior as below.

 

 

Okey, we may read in the blogs as we need to change in the applicationHost.config file.. if we do above settings it must be appear in the file… okey if you want to see the file how it looks like ……..

<requestFiltering>

                <fileExtensions allowUnlisted="true" applyToWebDAV="false">

                    <add fileExtension=".asa" allowed="true" />

                    <add fileExtension=".asax" allowed="true" />

                    <add fileExtension=".ascx" allowed="true" />

                    <add fileExtension=".master" allowed="true" />

                    <add fileExtension=".skin" allowed="true" />

                    <add fileExtension=".browser" allowed="true" />

                    <add fileExtension=".sitemap" allowed="true" />

                    <add fileExtension=".config" allowed="true" />

                    <add fileExtension=".cs" allowed="true" />

                    <add fileExtension=".csproj" allowed="true" />

                    <add fileExtension=".vb" allowed="true" />

                    <add fileExtension=".vbproj" allowed="true" />

                    <add fileExtension=".webinfo" allowed="true" />

                    <add fileExtension=".licx" allowed="true" />

                    <add fileExtension=".resx" allowed="true" />

                    <add fileExtension=".resources" allowed="true" />

                    <add fileExtension=".mdb" allowed="true" />

                    <add fileExtension=".vjsproj" allowed="true" />

                    <add fileExtension=".java" allowed="true" />

                    <add fileExtension=".jsl" allowed="true" />

                    <add fileExtension=".ldb" allowed="true" />

                    <add fileExtension=".dsdgm" allowed="true" />

                    <add fileExtension=".ssdgm" allowed="true" />

                    <add fileExtension=".lsad" allowed="true" />

                    <add fileExtension=".ssmap" allowed="true" />

                    <add fileExtension=".cd" allowed="true" />

                    <add fileExtension=".dsprototype" allowed="true" />

                    <add fileExtension=".lsaprototype" allowed="true" />

                    <add fileExtension=".sdm" allowed="true" />

                    <add fileExtension=".sdmDocument" allowed="true" />

                    <add fileExtension=".mdf" allowed="true" />

                    <add fileExtension=".ldf" allowed="true" />

                    <add fileExtension=".ad" allowed="true" />

                    <add fileExtension=".dd" allowed="true" />

                    <add fileExtension=".ldd" allowed="true" />

                    <add fileExtension=".sd" allowed="true" />

                    <add fileExtension=".adprototype" allowed="true" />

                    <add fileExtension=".lddprototype" allowed="true" />

                    <add fileExtension=".exclude" allowed="true" />

                    <add fileExtension=".refresh" allowed="true" />

                    <add fileExtension=".compiled" allowed="true" />

                    <add fileExtension=".msgx" allowed="true" />

                    <add fileExtension=".vsdisco" allowed="true" />

                    <add fileExtension=".exe" allowed="true" />

                    <add fileExtension=".vbs" allowed="true" />

                </fileExtensions>

                <verbs allowUnlisted="true" applyToWebDAV="false" />

                <hiddenSegments applyToWebDAV="false">

                    <add segment="web.config" />

                    <add segment="bin" />

                    <add segment="App_code" />

                    <add segment="App_GlobalResources" />

                    <add segment="App_LocalResources" />

                    <add segment="App_WebReferences" />

                    <add segment="App_Data" />

                    <add segment="App_Browsers" />

                </hiddenSegments>

            </requestFiltering>

PXE error: PXE-T01:File not Found & PXE-E3B: TFTP Error – File Not Found

 

You might get the below error..

 

 

The above problem will come When you don’t Have the files in DriveLetter:\RemoteInstall\SMSBoot\  

In fact the below article address the issue, However I have approached in different way as just copy the Missing files & folders from other Remote Install Folder and past on the Problem system.

 

http://www.kozeniauskas.com/itblog/2008/02/26/sccm-pxe-t01-file-not-found-and-pxee3b-tftp-error-file-not-found-errors/

ClientIDManagerStartup.log Error: 0x80040225 & Error 3

Failed to send registration request message. Error: 0x80040225

also when you see in the error 3 in ClientIDManagerStartup log

RegTask: Server rejected registration request: 3    ClientIDManagerStartup    26/01/2012 1:07:43 AM    7904 (0x1EE0)

 

You might also see (not in all cases) in ccmexec.log

System task 'ClientRegistrationStartup' returned error code 0x80040222.    CcmExec    26/01/2012 1:10:03 AM    7904 (0x1EE0)

Solution: Remove the Client authentication and SMS certificates Certificates of from Certificates console and request new certificates

PXE-T00: Unspecified file opening error detected

Found the error: While deploying 7 with the SCCM 2007 and MDT 2010.

sccm PXE-T00: Unspecified file opening error detected
PXE-E36:Error Received from TFTP server

 

Solution:This is not related to SCCM / WDS Issue.. it was with Symantec Ghost caused the issue, once the service was stopped the issue is resolved.

The program for advertisement "CEN20199" has not been run yet ("CEN0018E" - "*"). Software Distribution is currently paused on this computer, and it has to be resumed before this program can begin.

You may get above (The program for advertisement "XXXXXXX" has not been run yet ("XXXXXXXX" - "*"). Software Distribution is currently paused on this computer, and it has to be resumed before this program can begin. ) error and your advertisement will never run…  because system required a reboot to continue further any installation……

 

 

Solution: Reboot the system

MPcontrol.log error in native mode call to http SendRequestSync Failed for port 443 with status code 403, text : Forbidden

 

after all struggles  found this was due to communication issues with the PKI and SCCM Server and required a Reboot (PKI Server then SCCM Server both) was resolved the issue.

 

Also noticed if we show the client authentication – Computer certificate then it should work… how ever I recommend to go for reboot

Confuse - USMT & MDT & SIM

The confusing parts …

1) USMT: Will have below files

MigApp:- To migrate the Application settings like Outlook dictionary

Miguser:- To migrate the Local Users membership

MigDoc:- TO migrate the File types that you wanted to migrate

Custom.XML: the above three can be overwriten if you want any of above or apart from that to migrate.

Config.XML: You can migrate the configurations of Applications also with file

2) In MDT: - Will have this file

Customsettings .ini :- customize it to show or hide screens when running through the deployment wizard, this file is found in the Control folder

3) What is SIM? System Image Manager

SIM will be useful to create Unattended .XML file

Error information 0xC1030104

Add the following to your DHCP scope options:if you want to use DHCP Scope options
066 Boot Server Host Name - DNS name of PXE server
067 Bootfile Name - smsboot\x86\wdsnbp.com

For not to listen the DHCP on Ports (WDS Port & DHCP Ports are same so you must execute this registry change),...............

WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE

Set the registry value to:

UseDHCPPorts = 0

For the new configuration to take effect run the following command on the co-located DHCP and WDS server:

WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes
then i got below error 0xC1030104..........


When the error 0xC1030104 i encounter i executed below and resolved this error.

This error was appeared after i configured my SCCM PXE server not to USE DHCP ports

wdsutil /initialize-server /REMINST:"D:\remoteinstall"

even this was not resolved on few servers then i went for clean uninstall and install the PXE point.. then it worked

WMI Fix Batch file to run on multiple systems

@echo off
%windir%\system32\wbem\winmgmt /clearadap
%windir%\system32\wbem\winmgmt /kill
%windir%\system32\wbem\winmgmt /unregserver
%windir%\system32\wbem\winmgmt /reserver
%windir%\system32\wbem\winmgmt /resyncperf
net stop winmgmt /y
if exist %windir%\system32\wbem\repository.old rmdir /s /q %windir%\system32\wbem\repository.old
ren %windir%\system32\wbem\repository repository.old
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
for /f %%s in (‘dir /b /s %windir%\system32\wbem\*.dll’) do regsvr32 /s %%s
for /f %%s in (‘dir /b /s %windir%\system32\wbem\*.mof’) do mofcomp %%s
for /f %%s in (‘dir /b %windir%\system32\wbem\*.mfl’) do mofcomp %%s
net start winmgmt
%windir%\system32\wbem\wmiprvse /regserver

Save above batch file as wmifix.bat and run with the PSexec.exe with below command line

 

psexec @list.txt -c c:\scripts\wmifix.cmd

List.txt

Add list of computers to the list.txt file which you have trouble.

On Windows 2008 R2 with SP1 you may face MP Fatal error 1603 Problem

This could happened because of not supported versions to fix this you need to apply a patch  KB2489044. (I ran into this problem today at a customer place and fix is below)

 

Ms Link http://support.microsoft.com/kb/2489044/en-us

common problems for Software Update Points

It is worth noting that Windows Software Update Server (WSUS) is a key dependency for the Software Update Point (SUP). When WSUS isn't happy, the SUP is also going to have a bad day... Along with this it’s crucial to allow WSUS to be configured by Configuration Manager - as independent configuration of the WSUS Server usually ends in tears, or at least an unruly conflict.

 

 

Online Content:

The online TechNet library for Configuration Manager has a plethora of topics covering Software Update Point (SUP) configurations so please explore the relevant links at need.

Before beginning, ensure your familiar with the core topics: About the Software Update Point http://technet.microsoft.com/en-us/library/bb632674.aspx

Some of the common problems found with Software Update Points:

WSUS Dependencies

Two dependencies in WSUS loom large for Configuration Manager and lead the way for call drivers in this area. Being aware of these two issues might save you time and suffering down the line. I will also note that while not yet released (and thus subject to change) WSUS 3.0 SP2 should provide relief from both of the following problems. Please keep in mind that until WSUS 3.0 SP2 is released, tested with, and supported for use by Configuration Manager, it may introduce problems which cannot be anticipated.

1. Issue per KB 954960. This first common problem is an issue which results in some clients failing to pull down updates from the WSUS Server (SUP). This problem is documented in KB 954960 and occurs due to a recent revision to a Microsoft Office 2003 Service Pack 1 (SP1) update that causes some WSUS 3.0 servers to incorrectly synchronize the revised update with the update’s approvals. When the affected client computers communicate with such a server, the Web service is unable to process the approvals. Therefore, the detection is unsuccessful.

Resolution: The WSUS KB 954960 article provides a download link for the update directly.

2. WSUS Server Uninstalls. Continuing to drive support calls is the problem where the WSUS Server underlying the SUP is found to have been deinstalled.. Forums posts correlate this problem with Server Reboots as well as being linked to SMS Site Backup operations. What is understood is this occurs when WSUS is installed on the Site Server, and an MSI repair call is made to WSUS which fails.

While there is no current fix for this problem it is expected to be resolved by WSUS 3.0 SP2 (This is indeed fixed with Service Pack 2) - which is still in beta at this time. Fortunately there are two widely discussed workarounds to be found on the forums which should help:

Workarounds:

· Move the WSUS server off of the Configuration Manager Site server. Note: To date this issue has only been confirmed when WSUS and Configuration Manager are installed on the same machine.

· A manual registry edit can be implemented to prevent the WSUS repair from launching. For more on this please reference various forums postings such as this one: http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/ec73565a-93df-48d6-b411-35ffec7d25e4/

Synchronization with Microsoft Updates

When the SUP fails to sync with Microsoft Updates the support hotline rings. There is really only one flavor of problem seen with regularity, so please check this out and potentially save yourself some coin.

Note: This same problem impacts Upstream/Downstream and related Server Sync operations.

1. Port and Proxy Configurations and Authentication. Whether the proxy is hardware, software, on the SUP or on the network, the results are the same. Incorrect configurations equal a sync failure. This includes omitting a proxy, defining one when not needed, WPAD configurations, as well as incorrect authentication, filtering, or port details. It’s recommended you work with your Networking Team to identify any proxy configurations which might exist. I regret that tools and approaches to investigating this type of issue are beyond the scope of this blog. Find more here:

• How to Configure the Proxy Settings for the Software Update Point
• How to Configure a Firewall for Software Updates
• How to Configure Software Updates Synchronization
• How to Configure Proxy Settings Used When Downloading Software Update Files

Configuration Manager SUP Configurations

When external dependencies are in hand the next common call driver involves configuration choices for the Software Update Point. These are common enough to represent an ongoing class of issues and to be worth identifying here.

1. Active SUP - With all the configuration details necessary it's not uncommon to overlook defining an Active SUP. Fortunately it's quick and easy to do. Find more here:

• How to Create and Configure an Active Software Update Point
• How to Create and Configure an Active Internet-Based Software Update Point
• How to Create and Configure an Active Software Update Point on a Secondary Site
• How to Configure the Active Software Update Point Component to Use an NLB Cluster

2. Ports on the SUP - Bringing up the tail end of common issues is the configuration of the SUP Ports. This is a simple task yet is often overlooked and not validated. It's easy to correct when incorrect as well. If your SUP is involved in a problem, please make this simple check which may be part of the puzzle. Find more here:

• How to Determine the Port Settings Used by WSUS
• How to Configure the WSUS Web Site to Use SSL

General Information:

The following are resources you may find of use when approaching Software Update Pont issues and strategies:

SuperFlows for Software Updates: http://technet.microsoft.com/en-us/library/ff385001.aspx

Software Update related TechNet Forums: http://social.technet.microsoft.com/Forums/en-US/configmgrsum/threads/

WSUS Homepage on TechNet: http://technet.microsoft.com/en-us/wsus/default.aspx

WSUS Team Blog: http://blogs.technet.com/wsus/default.aspx

state messages for some reason is not being updated correctly Causes Updates Compliance Report Issue

run the below script to get the actual system state. this will help to report back actual compliance of patch level to SCCM Server

 

Option Explicit
On Error Resume Next

Call RefreshServerComplianceState

' WScript.Echo "Finished"

Sub RefreshServerComplianceState()

    ' Initialize the UpdatesStore variable.
    dim newCCMUpdatesStore
    ' Create the COM object.
    set newCCMUpdatesStore = CreateObject ("Microsoft.CCM.UpdatesStore")

    ' Refresh the server compliance state by running the RefreshServerComplianceState method.
    newCCMUpdatesStore.RefreshServerComplianceState
    ' Output success message.
'    wscript.echo "Ran RefreshServerComplianceState."

End Sub

SCCM: Content Download to Cache Issues – 2008 / 2008 r2 / IIS 7 and IIS 7.5 and Webdav Issues

Issue

The issue that was reported to me was that the content was not downloading. My datatransferservice.log, my CAS.log, and ContentTransferManager.log all looked good. The client found a local DP to download the content from. However when I looked at my cache folder, I saw that only a couple of MB of data was downloaded and it never increased in size.

 

BITS was the culprit here !!!

 

In order to see what jobs are currently downloading, type in:

bitsadmin /list /allusers

This will give you output similar to the following:

BITSADMIN version 3.0 [ 7.5.7600 ]
BITS administration utility.
(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions of Windows.
Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.

{19A1D938-E1E9-437F-882E-1BFAABB707CB} ‘CCMDTS Job’ ERROR 146 / 3805 4752558 / UNKNOWN
Listed 1 job(s).

Notice how in this picture I have the following line:

{19A1D938-E1E9-437F-882E-1BFAABB707CB} ‘CCMDTS Job’ ERROR 146 / 3805 4752558 / UNKNOWN

This is no good. This basically means there’s an error somewhere in the transfer job.

Before we get into the next step of the solution, you must first understand what an SCCM distribution point is. An SCCM DP is simply a glorified web server. If you look at the Datatransferservice.log file on any of your SCCM clients, you’ll see a lot of URLs that look like the following:

http://DOMAIN:80/SMS_DP_SMSPKGF$/CEN00119/System32/Redist/MS/System/msvcrt.dll

What your client is basically doing is grabbing the files from these URLs and storing them into your local cache directory underneath the package ID.

So back to BITS. Since we saw an error in our bitsadmin /list /allusers, we need to find out exactly what that error is. The following command will show just that:

bitsadmin /info {19A1D938-E1E9-437F-882E-1BFAABB707CB} /verbose > c:bits2.txt

So what this command is doing is giving us the information about the failed BITS job that we saw before. The verbose command gives us the status of each file in the job. We then pipe this out to a file. Inside of that file, we see the following:

BITSADMIN version 3.0 [ 7.5.7600 ]
BITS administration utility.
(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions of Windows.
Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.

GUID: {19A1D938-E1E9-437F-882E-1BFAABB707CB} DISPLAY: ‘CCMDTS Job’
TYPE: DOWNLOAD STATE: ERROR OWNER: NT AUTHORITYSYSTEM
PRIORITY: LOW FILES: 146 / 3805 BYTES: 4752558 / UNKNOWN
CREATION TIME: 5/12/2010 11:31:04 AM MODIFICATION TIME: 5/12/2010 11:33:18 AM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: REGISTERED NOTIFICATION FLAGS: 11
RETRY DELAY: 60 NO PROGRESS TIMEOUT: 2419200 ERROR COUNT: 147
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://DOMAIN:80/SMS_DP_SMSPKGF$/CEN00119/Program Files/Hummingbird/Connectivity/9.00/HostExplorer/SDK/Samples/OHIO/Visual C++ Samples/HEOhioSample/MyTabCtrl.cpp -> C:Windowssystem32CCMCacheCEN00119.1.SystemProgram Files/Hummingbird/Connectivity/9.00/HostExplorer/SDK/Samples/OHIO/Visual C++ Samples/HEOhioSample/MyTabCtrl.cpp
ERROR CODE:    0×80190194 – HTTP status 404: The requested URL does not exist on the server.

ERROR CONTEXT: 0×00000005 – The error occurred while the remote file was being processed.

DESCRIPTION:
JOB FILES:

 

also check for Client side BITS Policy settings

Package not downloading due to some IIS File filtering blocking issue

Check with these commands

 

 

BITSADMIN /LIST /ALLUSERS

 

C:\>BITSADMIN /geterror {7D46DE5B-3911-40B1-A72B-607737DB06F9}

BITSADMIN version 2.0 [ 6.6.3790.3959 ]
BITS administration utility.
(C) Copyright 2000-2004 Microsoft Corp.

ERROR FILE:    http://sccmserver.mydomain:80/SMS_DP_SMSPKGD$/SMSPKG/HCC00
05F/AdminImage/x86/en-us/acad/Acad/Program Files/Root/HelpHtml/contexthelp/+CONSTRAINTSETTINGS.htm -> C:\WINDOWS\system32\CCM\Cache\HCC0005F.1.System\AdminImage/x86/en-us/acad/Acad/Program Files/Root/HelpHtml/contexthelp/+CONSTRAINTSETTINGS.htm
ERROR CODE:    0x80190194 - The requested URL is not found on this server.
ERROR CONTEXT: 0x00000005 - When processing the remote file error has occurred

/LISTFILES job                     Lists the files in the job
/SUSPEND job                       Suspends the job
/RESUME job                        Resumes the job
/CANCEL job                        Cancels the job
/COMPLETE job                      Completes the job

 

BITSADMIN /INFO job [/VERBOSE]

BITSADMIN /geterror {B2826EF6-C78B-4D1C-A386-94D0D36DC107}

BITSADMIN /LIST /ALLUSERS

 

Where job =

{B2826EF6-C78B-4D1C-A386-94D0D36DC107}

SMS 2003 Major issues in MS PSS