FEP 2010 Update Rollup 1

Update Rollup for FEP 2010 has been released so go read about it as it will enhance your FEP expericne with Config Mgr for update management. It also has some new OS uspport

TechNet Whats New ! – http://technet.microsoft.com/en-us/library/hh211541.aspx

Download – http://www.microsoft.com/download/en/details.aspx?id=26583

New Hotfix for SP2 (Distribution Manager)

Consider the following scenario:

• You install the distribution point role on a Microsoft System Center Configuration Manager 2007 Service Pack 1 (SP1) site server.
• You customize the retry settings on the Distribution Point tab for the distribution point. Or, you use the default value for the retry settings.
• A retry is required after a package distribution fails.

In this scenario, the Distribution Manager does not honor the retry settings on the Distribution Point tab when the Distribution Manager retries the distribution.
Note Before each retry, there is a 10-second delay.

http://support.microsoft.com/?kbid=978875 

Source: http://blogs.technet.com/configurationmgr/archive/2010/01/26/new-hotfix-the-distribution-manager-does-not-honor-the-number-of-retries-and-delay-before-retrying-minutes-retry-settings-on-sccm-2007-sp1-site-servers.aspx

Resetting Windows update Agent on Windows XP

Sometimes you need to reset the Windows update Agent to get it working like it should. If you haven’t updated to the SP2 version of WSUS i strongly recommend doing that on your Software Update Point as allot of fixes where released in that Service Pack. Below is a set of commands you can use to reset a Windows update Agent, the easiest way is to save the commands in a bat file and launch it on your XP clients in proffered way manually of with software distribution.

net stop bits
net stop wuauserv
Del "%ALLUSERSPROFILE%Application DataMicrosoftNetworkDownloaderqmgr*.dat"
Ren %systemroot%SoftwareDistributionDataStore *.bak
Ren %systemroot%SoftwareDistributionDownload *.bak
Ren %systemroot%system32catroot2 *.bak
sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
cd /d %windir%system32
regsvr32.exe atl.dll
regsvr32.exe urlmon.dll
regsvr32.exe mshtml.dll
regsvr32.exe shdocvw.dll
regsvr32.exe browseui.dll
regsvr32.exe jscript.dll
regsvr32.exe vbscript.dll
regsvr32.exe scrrun.dll
regsvr32.exe msxml.dll
regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll
regsvr32.exe actxprxy.dll
regsvr32.exe softpub.dll
regsvr32.exe wintrust.dll
regsvr32.exe dssenh.dll
regsvr32.exe rsaenh.dll
regsvr32.exe gpkcsp.dll
regsvr32.exe sccbase.dll
regsvr32.exe slbcsp.dll
regsvr32.exe cryptdlg.dll
regsvr32.exe oleaut32.dll
regsvr32.exe ole32.dll
regsvr32.exe shell32.dll
regsvr32.exe initpki.dll
regsvr32.exe wuapi.dll
regsvr32.exe wuaueng.dll
regsvr32.exe wuaueng1.dll
regsvr32.exe wucltui.dll
regsvr32.exe wups.dll
regsvr32.exe wups2.dll
regsvr32.exe wuweb.dll
regsvr32.exe qmgr.dll
regsvr32.exe qmgrprxy.dll
regsvr32.exe wucltux.dll
regsvr32.exe muweb.dll
regsvr32.exe wuwebv.dll
netsh reset winsock
proxycfg.exe -d
net start bits
net start wuauserv

NO_SMS_ON_DRIVE.sms

How do I prevent Config Mgr from putting files on certain drives ? By default Config Mgr chooses the the NTFS drives that has most available space, and in many ways you dont want this behaviour. So to keep some kind of hygiene on your server you can put a file named in a specific way just like the blog title says. NO_SMS_ON_DRIVE.sms , You can read more about this its an old trick from back in the days  in this KB article http://support.microsoft.com/kb/871234

FCS + Config Mgr = True

As some of you has seen before I have been referecing to some ways of distributing Forefront Security Patches within a Config Mgr integrated WSUS.

There is now an offical KB for this 958491 Supported configurations for using WSUS to distribute Forefront Client Security Definition updates within SCCM 2007

Links wehre you can read more on this !

http://support.microsoft.com/default.aspx/kb/958491

http://blogs.technet.com/smsandmom/archive/2008/10/16/supported-configurations-for-using-wsus-to-distribute-forefront-client-security-definition-updates-within-sccm-2007.aspx

Configuration Manager 2007 – Hotfixes included in SP1

Yesterday the KB953649  was published and here you can find more information the Hotfixes that is included in SP1.

http://support.microsoft.com/kb/953649/en-us

Excluding machines from Client Push installation

Sometimes you have machines that cannot be touched by anything other then manual work for legal or busniness critical applications. And then you might dont want the sms/sccm client to be installed automaticlly. So my question is: It it possible to exclude machines from getting the client via client push ?

The answer is yes !.

What you need to do is to a the computer to the following registry key HKEY_LOCAL_MACHINESoftwareMicrosoftSMSComponents SMS_DISCOVERY_DATA_MANAGER

Double click  the ExcludeServers and type in you servers in the box separated by space.

If you want a client to be installed again after it has been excluded you need to take certain actions. All information related to this is found in this KB: http://support.microsoft.com/kb/207729

SCCM December Hotfix : Offer Status Summarizer fails to process status

Please refer to KB945898 for more information.

System Center Configuration Manager 2007 (SCCM) site servers installed prior to December 1, 2007 will fail to process advertisement status summary data, also referred to as offer status summary data. Status (.SVF) files will being to accumulate under the inboxesoffersum.box folder on the site server. By default in a new installation this path will be Program FilesMicrosoft Configuration ManagerinboxesOfferSum.Box. For Site Servers upgraded from SMS 2003, the path will likely be SMSInboxesoffersum.box.

Site servers installed after December 1 may not process any status messages, as the offersum.box folder does not get created, which blocks the status message system.

This occurs with either the evaluation or licensed versions of the RTM product.

If you are using the International Client Packs (ICPs), please go to the English page to download the hotfix for these files.

http://www.microsoft.com/downloads/details.aspx?familyid=8b910427-c591-466b-83d3-6632099ac186&displaylang=en&tm