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

 

 

“The network path was not found" error on Win XP sp3”

The problem
You are unable to connect to any network resource (network shares, printer, etc) on a Windows XP machine, from a Win XP client.
A solution (there could be several causes)

• On the target machine (the one you're trying to connect to) open up Services, under Administrative Tools in the Start Menu.
• Scroll down to the Computer Browser service.
• If it is Disabled or set to Manual, set it to Automatic.
• Then start it. It may stop immediately again, but this is OK.
• At this point try to connect to the target machine.

If it still doesn't work, you can try the following:

• open up Network Connections, under Control Panel.
• Right click on your network adapter and click on Properties.
• Click on Internet Protocol (TCP/IP), then click on Properties.
• Click on Advanced, and click on the WINS tab.
• Even if it is set to Default, set the radio button to Enable NetBIOS over TCP/IP.
• Press OK on each screen until everything's closed.
• Go back to the client machine and try again.
• You should be able to connect!

If it still doesn't work:

• Go back to the Services window and find the service named Routing and Remote Access.
• Double-click on it, set it to Manual, and stop it.
• Close Services and try to connect from your client machine again.

OSD Task Sequence : Formatted the drive, dropped the image on the PC

Issue:  When trying to perform an OSD Task Sequence using SCCM 2007, the deployment fails, usually after it has successfully formatted the drive, dropped the image on the PC, and scanned for drivers.

Looking at the SMSTS.log, the following error is logged:

Task sequence cannot continue after reboot because TS Manager is not configured to auto-start or GINA is not installed    TSManager
CheckForRebootRequest(&bRebootInitiated), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\engine.cxx,274)    TSManager
Fatal error is returned in check for reboot request of the action (Restart Computer).
Unspecified error (Error: 80004005; Source: Windows    TSManager
An error (0x80004005) is encountered in execution of the task sequence    TSManager

Cause:  This issue is caused because the "Setup windows and ConfigMgr" task has either been removed, disabled, or has been moved to the wrong place in the Task Sequence.

The "Setup windows and ConfigMgr" task performs several tasks that prepares the PC from going from WinPE to the Windows Setup, including modifying boot managers to boot to the correct partition. Once it finishes preparing the PC, this task then reboots the PC at the proper time to start Windows Setup or Mini-Setup. If this task is removed, it will cause the deployment to fail because the PC was not properly prepared.

Resolution: For these reasons, the "Setup windows and ConfigMgr" task should never be removed, disabled, or moved to another place other than the default in the Task Sequence. Moving it to another place in the Task Sequence may cause the PC not to be prepared or rebooted at the correct time, causing the deployment to fail.

The "Setup windows and ConfigMgr" task should also not be marked as Continue on Error because if this task does error out, the deployment will probably fail anyway.

SCCM Client Services and applets

If SMS/SCCM Client is installed we will get SMS Agent host (ccmexec.exe ) service will be installed all the related information log file is ccmexec.log file

if client installed it will come in Control Panel

 

if the client OS version is 32 bit then you can find the applets in the control panel directly, if it is 64 bit OS then you will get in 32-bit Control Panel items (The reason is sccm is a 32 bit application) also client will be installed in windows\ccmsetup for client installation

and for client logs in 64 located in

 

64 bit client log files location screenshot is below

 

SMS / SCCM console not connecting

Above is a example screenshot

There are 3 areas of consideration when troubleshooting access to the SMS provider and the site server. 

1. Do you have the necessary privileges to the SMS provider on your site server?

2. Do you have the necessary security rights to the database?

3. Do you have the necessary privileges as far as WBEM is concerned?

4. Is WBEM working? 

http://www.myitforum.com/articles/6/view.asp?id=250
http://support.microsoft.com/kb/317872

Verify that this computer has network connectivity to the SMS Provider

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

 

 

Check the adminui.log and smsprov.log and smsdbmon.log