You are browsing the archive for Sms 2003.

Configmgr2007 : Change your packages source path after SCCM site migration with a script

6:39 am in AdminUi, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Installation, migration, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, script, SMS, Sms 2003 by Kenny Buntinx [MVP]

A few days ago , I explained in this blogpost ““ on how I was busy migrating one SCCM 2007 Primary site to another , because we wanted to start with a complete new environment (w2k8 x64) .As there is no supported direct upgrade path, I built an entire new SCCM server with SP2 -R2.I made it a child site of the existing SCCM primary site and let all the packages replicate.

After I solved a problem with locked padlocks on my packages in this blogpost :””, I needed to make sure that I would change all my old packages source paths ( a.e \\SCCM01\G$\src\<package folder> into my new package source paths (a.e \\Fileserver1\SCCMSRC\<package folder> that was residing on a DFS share .

To do that I needed a script , as doing +- 100 packages was a little to much work for a lazy admin :-)

I thought I had a great script from the site of Brian S. Tucker , as I used it already multiple times. It turned out that it was useless in this project as I needed to change not only the server name , but the complete path.

Script 1 : If you only need to change the server name in the package source path. Otherwise use my script “script 2” in the section under “script 1” below .

Copy code below this line—————————————————

Dim oWbemServices
If UCase(Right(Wscript.FullName, 11)) = "WSCRIPT.EXE" Then
    Wscript.Echo "This script must be run under CScript."
End If
If WScript.Arguments.Count <> 1 Then
    WScript.Echo "Wrong number of arguments were passed."
End If

For Each oPackage In oWbemServices.execquery("select * from sms_package")
  sOldPathString = oPackage.pkgsourcepath
  If InStr(sOldPathString,"\\") Then
                iStart = InStr(3,sOldPathString,"\")
                sNewPathString = Right(sOldPathString,(LEN(sOldPathString)-iStart))
                sNewPathString = "\\" & WScript.Arguments(0) & "\" & sNewPathString
                WScript.Echo "Setting Package Path for " & oPackage.Name & " from " & sOldPathString & " to " &  sNewPathString
                oPackage.pkgsourcepath = sNewPathString
  End If

WScript.Echo "Done"

  Set oWbemLocator = CreateObject("WbemScripting.SWbemLocator")
  Set oWbemServices = oWbemLocator.ConnectServer(".", "root\sms")
  Set oSCCMProvLoc = oWbemServices.InstancesOf("SMS_ProviderLocation")

  For Each oLoc In oSCCMProvLoc
        If oLoc.ProviderForLocalSite = True Then
            Set oWbemServices = oWbemLocator.ConnectServer(oLoc.Machine, "root\sms\site_" + oLoc.SiteCode)
        End If
End Sub

Copy code above this line—————————————————

Thanks to my fellow Belgium MVP ”Kim Oppalfens” , I was able to alter the above script to my needs and change the complete source path , except for the package source folder .

Script 2 : If you need to change the complete package source path , except the package folder name.

Copy code below this line—————————————————

on error resume next
Dim oWbemServices
Set fs = CreateObject ("Scripting.FileSystemObject")
Set logFile = fs.CreateTextFile ("pkg_log.csv")

For Each oPackage In oWbemServices.execquery("select * from sms_package")
  sOldPathString = oPackage.pkgsourcepath
  If InStr(sOldPathString,"\\") Then 
  arrsrcPath = Split( soldPathString, "\")
  snewpathString = "\\Fileserver1\sccmsrc\" & arrsrcPath(Ubound(ArrSrcPath)-0)

                logFile.Write "Setting Package Path for " & oPackage.Name & " from " & sOldPathString & " to " &  sNewPathString
                logFile.WriteLine ""
                oPackage.pkgsourcepath = sNewPathString
  End If

WScript.Echo "Done"

  Set oWbemLocator = CreateObject("WbemScripting.SWbemLocator")
  Set oWbemServices = oWbemLocator.ConnectServer(".", "root\sms")
  Set oSCCMProvLoc = oWbemServices.InstancesOf("SMS_ProviderLocation")

  For Each oLoc In oSCCMProvLoc
        If oLoc.ProviderForLocalSite = True Then
            Set oWbemServices = oWbemLocator.ConnectServer(oLoc.Machine, "root\sms\site_" + oLoc.SiteCode)
        End If
End Sub


Copy code above this line—————————————————


Hope it helps ,


Kenny Buntinx

Upgrading an SMS 2003 SP3 with remote SQL server to SCCM 2007 SP1 is giving a lot of “failure audit” events on the remote SQL server

6:05 am in ConfigMgr, ConfigMgr 2007, sccm, SCCM 2007, SMS, Sms 2003 by Kenny Buntinx [MVP]


After the upgrade was done from SMS 2003 SP3 , we had a lot of “failure audit” events on the remote sql server (every 20 min).

Warnings are logged for an account that wants to access the SQL server. (Account is specified as network access account and Push installation account)

This is also logged in the ccm.log file on the SCCM 2007 SP1 primary site.

We have identified a cause for the errors being logged in the CCM.LOG. It appears to occur due to the SMS_CLIENT_CONFIG_MANAGER key in the registry, this key doesn’t appear
to be created in a fresh install of SCCM (checked on the fresh installed SCCM server in my sandbox)

Deleting this key will make the errors go away, the errors don’t cause any harm or functionality issues.


Actions taken:

-       Delete the registry key HKLM\Software\Microsoft\SMS\Components\SMS_CLIENT_CONFIG_MANAGER

-       Restarted the smsexec service and no failure audit anymore

-       Wait for another 20 min and no failure audit warnings anymore.


The Environment we worked on :

– SMS 2003 SP3 with remote SQL server.

– Server 2003 SP2 server OS


Thanks to Kurt Van Hoecke for putting this to our attention !

However , this method is NOT supported by Microsoft !

This posting is provided AS IS with no warranties !

Hope it Helps ,

Kenny Buntinx

Keyboard Layout values for use in Task Sequences & Collection Variables

9:13 am in AdminUi, ConfigMgr, ConfigMgr 2007, OSD, sccm, SCCM 2007, SMS, Sms 2003 by Kenny Buntinx [MVP]

I just needed to find a list with Keyboard variables to customize my Windows XP Build in SCCM. It could become handy for people needing them when building international images.
[“Keyboard Layout”]
0000041C = “Albanian”
00000423 = “Belarusian”
00000813 = “Belgian Dutch”
0000080C = “Belgian French”
00000416 = “Brazilian (ABNT)”
00000402 = “Bulgarian”
00010402 = “Bulgarian Latin”
00001009 = “Canadian English (Multilingual)”
00000C0C = “Canadian French”
00010C0C = “Canadian French (Multilingual)”
0000041a = “Croatian”
00000405 = “Czech”
00010405 = “Czech (QWERTY)”
00000406 = “Danish”
00000413 = “Dutch”
00000425 = “Estonian”
0000040B = “Finnish”
0000040C = “French”
00000407 = “German”
00010407 = “German (IBM)”
00000408 = “Greek”
00050408 = “Greek Latin”
00010408 = “Greek (220)”
00030408 = “Greek (220) Latin”
00020408 = “Greek (319)”
00040408 = “Greek (319) Latin”
0000040E = “Hungarian”
0001040E = “Hungarian 101-key”
0000040F = “Icelandic”
00001809 = “Irish”
00000410 = “Italian”
00010410 = “Italian (142)”
0000080A = “Latin American”
00000426 = “Latvian”
00010426 = “Latvian (QWERTY)”
00000427 = “Lithuanian”
00000414 = “Norwegian”
00000415 = “Polish (Programmers)”
00010415 = “Polish (214)”
00000816 = “Portuguese”
00000418 = “Romanian”
00000419 = “Russian”
00010419 = “Russian (Typewriter)”
00000C1A = “Serbian Cyrillic”
00010C1A = “Serbian Latin”
0000041B = “Slovak”
0001041B = “Slovak (QWERTY)”
00000424 = “Slovenian”
0000040A = “Spanish”
0001040A = “Spanish variation”
0000041D = “Swedish”
0000100C = “Swiss French”
00000807 = “Swiss German”
0001041F = “Turkish F”
0000041F = “Turkish Q”
00000422 = “Ukrainian”
00000809 = “United Kingdom”
00000409 = “US”
00010409 = “US-Dvorak”
00030409 = “US-Dvorak for left hand”
00040409 = “US-Dvorak for right hand”
00020409 = “US-International”

Hope it helps ,


Kenny Buntinx

SCCM : How to avoid that SCCM or SMS will place components on the c:\ or any other drive

10:45 pm in ConfigMgr, ConfigMgr 2007, sccm, SCCM 2007, SMS, Sms 2003 by Kenny Buntinx [MVP]

Place the “NO_SMS_ON_DRIVE.SMS” file on the drive you want ( aka c:\ ) to prevent that SMS/SCCM  places any components on one of the forbidden drives in the future. Simple but effective

Thats it !

Hope it helps !

Kenny Buntinx

Sccm, Scom, Remote SQL 2005 & the Windows server 2008 firewall

7:49 pm in ConfigMgr 2007, MOM, Operations Manager 2007, Opsmgr 2007, SCCM 2007, SCOM 2007, SMS, Sms 2003 by Kenny Buntinx [MVP]

Hi All,

Let’s start by saying that this blog post is probably more OpsMgr related, but all topics are valid for a remote SQL Install for Sms, SCCM or any of the other System center products, so I guess it’s still ok to post it here.

Look, I am not all that good with popular quotes, never seem to be able to remember them just right. But this is one of them that I have never had trouble remembering. “It is all fun and games until someone throws a firewall into the mix”.


Not sure who the quote is from, but I am pretty sure he was refering to my lab environment. Yesterday, I redeployed my Opsmgr 2007 environment, to test the installation on windows server 2008. I figured, install a new sql server on 2008 on one machine, then install opsmgr 2007 on another, shouldn’t take more than a single evening. I’ll start rolling out agents and importing management packs the day after. Seemed like a plan at the time.


So I installed, powershell, IIS, the II6 compatability tools in short all the requirements to install SQL 2005 reporting services on a Windows Server 2008 as listed here:

Then I installed SQL 2005, the database engine and a default install of SQL reporting services, followed by applying SP2.

Next, I installed the Scom database, no problem at all, I am on a role here.


Then I started the management server and console install on the remote box. Err.

The root management server complained that it couldn’t find the database. I splapped myself on the forehead, sure you silly you still need to enable The Tcp/ip protocol in the SQL Server configuration. I checked, and found that Tcp/ip was already enabled as a listening protocol.

Hum, strange, opened a dos box, and ran netstat -a -n -p tcp to see whether my sql box was listening on port 1433. Lo and behold, it wasn’t. You see, I know it was something like that. Still took me a while to figure out that my SQL Server, which was running in a specific named instance was listening on dynamic ports. (If anyone knows how that could have happened just let me know).

Now, I wasn’t going to let something silly as that stand between me and my plan, so I configured the SQL tcp/ip protocol for this instance to listen on port 1433, and restarted the SQL Server service as listed here:

I subsequently ran netstat -a -n -p tcp again and tada, the server was listening fine on port 1433.


Back to the original task at hand install the OpsMgr management server. Err.

Database still not found, ok, I am getting fed up with this, I download microsoft’s portqry tool, and verified whether I could access port 1433 from the remote machine. The portqry -n sqlserver01-e 1433 came back with a response of Filtered. Another slap on the forehead, you nitwit, you have the Windows Server 2008 firewall running. So I went to the Sql box, and decided NOT to disable the firewall but to configure it to open port 1433, as described here:

Once done, I ran my portqry again, and it showed up as listening, great, we’re back on track.


I launched the Opsmgr management server installation again, and the darn thing failed on me again.

Luckily for me the log file came around telling me that a custom action in the msi had close the handle to soon, and that it should be configured not to do that. _SetRootHealthService_Wizard unexpectedly closed the hInstall handle was the error message at hand. So after telling the setRootHealthService_Wizard that it wasn’t allowed to close the handle so soon, or that I would put it in the naughty corner, I retried the installation.


Apparently my authority, that still works on my 3-Year old soon, didn’t impress the setroothealthservice_wizard. In a illuminated attempt to still get this to work I went back to the Sql server box and configured the firewall to log dropped packets. Retried the installation again, which obviously failed, and went back to analyze the windows server 2008 firewall log on the sql box. This revealed dropped packets on udp port 1434. Oh, now that’s easy enough to fix, let’s just open that port and we’re set. Erm wait a minute, I thought all sql database engine communication went over tcp port 1433, what’s up with this 1434 udp port all of a sudden.


Great after having this miracle idea of deploying sql on a box with the firewall still running, I’ll have curiousity kick in, this is going to set back my planning on this a couple of hours, or at least that’s what I thought, but Live search and Sql Magazine to the rescue the udp port 1434 reportedly is needed to access a named instance:


Now, that I had settled my curiousity, I was free to open udp port 1434 in the SQL Server firewall, and retry the opsmgr root management server installation, and kadadzing the install completed with success.



“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS

Building a custom Configmgr 2007 admin console

9:15 pm in ConfigMgr 2007, SCCM 2007, SMS, Sms 2003 by Kenny Buntinx [MVP]

The work that needs to be done in the Configuration manager 2007 admin console is often spread out amongst different team members. Not all of these team members require access to the full admin console. Most environments do configure the permission set in a somewhat restrictive member so that team members only have the permission they need, but what is often forgotten is building a custom minimal admin console with just access to the features people need.

This shouldn’t be done from a security point of view, the additional security this brings is neglectable, but more from a usability point of view. It makes the admin console easier to use, and avoids access denied errors, or empty detail panes because someone clicks on a heading in the admin console for which he doesn’t have permission.


Now how do you build such a custom Configmgr 2007 admin console you might ask.

Step 1) You launch mmc.exe

Step 2) In the File menu, you select Add/remove snap-in

Step 3) Add the system center configuration manager snap-in, and select the “Select console tree items to be loaded (custom)” radio button.


Step 4) Select the console tree items you want


Step 5) Click Next, Finish and Ok, below is a screenshot of the tree pane of the custom console I created


Step 6) Select “System Center Configuration manager” in the tree pane, right-click it and select “New Window from here”

Step 7) In the File menu select options

Step 8) Name your console “Custom Configmgr admin console”

Step 9) In the console mode select “User mode – Limited access, single window”

Step 10) Clear the checkbox for “Allow the user to customize view”

Step 11) Tick the checkbox for “Do not save changes to this console”

Step 12) In the file menu save your snap-in

Step 13) In the prompt about multiple windows being open click “Yes”


Step 14) Launch your customized mmc console and verify whether everything looks according to plans.

PS: a similar option was already available in sms.





“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS

Back home from the MVP Summit

5:52 am in ConfigMgr 2007, personal, SCCM 2007, SMS, Sms 2003, Training by Kenny Buntinx [MVP]

Hi All,

Just got back home from the Mvp summit in Seattle last week, and it has been a thrilling and exciting event all over again. For those of you that don’t know how the summit works, I ‘ll try to describe what goes on during that week. The first real important part is the summit dinner, which this year was in one location with all mvp’s together instead of the old breakup into regions. This was a nice change as you could mingle with your peers more easily, and well the North american mvp’s are still the largest group of Configmgr mvp’s.

Day 2 and day 3 are exteremely exciting days, where we get to spend the full day with the Configmgr product team. On day 2 this was closed off with an informal dinner at a very good steak house. During these 2 days we got to talk to the product team about the near and not-so-near future of our beloved configmgr product. If you would ask me what the main benefit of being an mvp is, than this would definitely be it. They can take everything else away, but don’t mess with my summit :-). The event was finally closed of with one of Balmer’s enthusiastic speeches, but I was on my way back home and to work at that point.

Side note1: I bought me a bose QC2 noise canceling headset on the way back to make sure I could get some sleep at the airplane. These things are amazing by any standard and have had an incredible contribution to my beauty sleep at the airplane and making sure I could get a day worth of work in on Friday.

Side note2: The sms 2003 to configmgr 2007 course I will be teaching next week is approaching rapidly, and we only have 3 seats left, if you want to be part of this course that will heavily focus on real-life hands on labs you’ll have to be quick. More info on this course can be found here: Upgrading your sms 2003 admin skills to SCCM 2007

“Everyone is an expert at something”

Kim Oppalfens – Configmgr expert for lack of any other expertise.

How to transition from sms 2003 to Sccm 2007 – Notes from the field Tips & Tricks

11:09 pm in ConfigMgr 2007, migration, SCCM 2007, script, SMS, Sms 2003 by Kenny Buntinx [MVP]

Hi all,

I delivered my session at the Belgian Techdays, and I promised on my blog and during the session that I would share the scripts with all of you. So here they come. Most of these scripts were used during a side-by-side upgrade transition. The side-by-side upgrade transition process looks like this:

  1. Install SMS 2003 SP2 on new server
  2. Attach new SMS 2003 SP2 site as a child site
  3. Let objects replicate
  4. Break Parent – Child relationship
  5. Upgrade new Site to Configmgr 2007
  6. Install KB945898
  7. Migrate clients to new site
  8. Remove boundaries from original site
  9. Add boundaries to new site
  10. Decommission original site
  11. Migrate non-replicating objects (queries/reports)


This method provides a smooth transition without impacting your current sms 2003 infrastructure until your new Sccm 2007 environment is fully up and running and has been tested successfully. This makes it one of the lowest transitioning methods available.

Challenges / manual steps to perform in this method are

  1. Verify all objects have migrated
  2. Configure Site Settings
  3. Migrate Folders and folder membership
  4. Make Software distribution functional in new site without boundaries
  5. Optional: Modify package source path
  6. Migrate hardware inventory customizations (SMS_def.mof)
  7. Export / Import queries
  8. Export / Import reports
  9. Configure security rights
  10. Non-Replicating Software Metering Rules

In this section I will go over these challenges, and when available introduce a script to tackle these challenges. If a script is available I will first explain what the script does, give an example command line, and add some comments/remarks.

Challenge 1: See Script1 later in this post

Challenge 2: This is left as manual exercise for the reader

Challenge 3: See Script2 & Script3 later in this post

Challenge 4: See Script5 later in this post

Challenge 5: See Script4 later in this post

Challenge 6: See Challenge 2

Challenge 7: Use the export and import wizard, my experience has been that importing the mof file in one pass tends to be error-prone. I usually cut the mof file into 200KB chunks and import the chunks one by one, this has resulted in a much less error-prone import process. Run the script to move the queries into the correct folder, see script 3 later in this post.

Challenge 8: See Challenge 7

Challenge 9: See Challenge 2

Challenge 10: Software metering rules can be configured to apply to this site, or to this site and all child sites. If your software metering rules are configured to only apply to the current site than they will obviously not replicate. This setting is unfortunately not configurable after the rule has been created.

Scripts to Tackle the challenges:

Just for the record these Scripts do not come with any form of support or guarantee, the scripts have served me well but should be tested in your environment as your mileage may vary!!! Furthermore the script aren’t always the cleanest code, they don’t log a lot of data and do use some hardcoded parameters that would be more appropriate in an argument.

Script1: Countobjects.vbs


This script counts the number of Queries, Reports, Packages, Advertisement, Software Metering Rules, Collections and folders.


Usage: Cscript Countobjects.vbs


You run this script on both the old and new sms 2003 servers and compare the numbers, once all numbers match up you can perform step 4 and break the parent – child relationship.

Script2: SmsContainers.vbs


This script allows you to export and import the folder structure from one sms 2003 environment to another.


Usage: Cscript SmsContainers.vbs export s01folders.txt or Cscript SmsContainers.vbs import s01folders.txt


Because Sms 2003 does not replicate the folder structure to child sites we need a script that duplicates this folder structure. At import time this script creates a file called conversionarray.txt that allows us to translate old folder id’s into new folder id’s. We will need this file in later scripts to move the objects back into the correct folders.


Script3: xyzfoldermembership.vbs


There are multiple scripts with this filename where xyz is either adv for adertisements, pkg for packages, rprt for reports, qry for queries and swmtr for software metering rules. These script move the respective objects into the correct folder.


Usage: Cscript.exe xyzfoldermembership.vbs export S01xyzfolders.txt or Cscript.exe xyzfoldermembership.vbs import S01xyzfolders.txt


These scripts need the conversionarray.txt to be available to find the correct folderid to place the objects in.


Script4: Modifypkgsource.vbs


This script modifies the packagesource of all packages to a new server.


Cscript Modifypkgsource.vbs


If the sourcefiles for your packages are stored locally on the site server, you’ll need to modify the package sourcepath of all packages to a new server. First copy the source package folder structure to the new server and then edit the script to replace the oldserver and newserver strings with the values needed for your environment.


Script5: ModifyAdverts.vbs


This script configures all advertisements to run from a remote distribution point.


Cscript ModifyAdverts.vbs


Because you cannot have overlapping boundaries we can only move the boundaries after all of the clients in a boundary have migrated. Because of this, clients in the new sccm infrastructure will not be able to find a local distribution point. So if you want these clients to be able to run advertisements these advertisements have to be configured to allow run from remote distribution point. If you want to change the value back later just change the bit value. Secondly if you already have some advertisements that are configured to run from remote dp, or download from remote dp, this script does not build a text file to store what it has changed, so the script doesn’t allow you to revert back to the original situation. If this is something you require you’ll have to adapt the script to save the original configuration.

The scripts can be downloaded here:


“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS

How to transition from sms 2003 to Sccm 2007 – Notes from the field session at Belgian Techdays

7:54 pm in ConfigMgr 2007, SCCM 2007, SMS, Sms 2003, Training by The WMI guy

Hi All,

I will be speaking at the Belgian Techdays for the second year in a row. The session is aimed at current SMS 2003 administrators that are looking at transitioning to SCCM 2007.

The session is scheduled for Thursday the 13th of March running from 14:30 till 15:45. Because of time constraints the session will not include any demo’s. It will discuss all popular ways to transition from SMS 2003 to Sccm 2007, and introduce you to some scripts that can help you move to Sccm 2007 more smoothly.

Session Abstract:

This session will introduce you to the different methods of transitioning from sms 2003 to sccm 2007. The session will discuss the pro’s and con’s of the Wipe and Load, In-place Upgrade, Side-by-Side Migration and the speakers personal favorite the Side-by-Side upgrade. The session will also show you how you can use scripts to assist you in automating certain tasks during the migration process.

Hope to see you all there.



“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS

Understanding Software Updates in SCCM 2007

7:15 pm in ConfigMgr 2007, SCCM 2007, SMS, Sms 2003 by The WMI guy

Configmgr 2007 comes with a totally new way of deploying software updates. The new method offers some great advantages over the old one(s) available in Sms 2003. It didn’t take me too long to see the benefits the new architecture brings, but it did take me quite some effort in understanding how I could create a working operational process to maximize these benefits, it actually took a fellow mvp (Thanks Pannu) and Wally to set things straight in my head (Thanks Wally). This 2 -series post will try to give you some insight in how the Configmgr 2007 solution stacks up with the sms 2003 implementation. The second portion will explain the objects involved and will guide you through a potential implementation of Software updates in Sccm 2007.

Let’s start by briefly explaining how the sms 2003 infrastructure operates, followed by the currently known issues. Later in this post we’ll review what the Sccm 2007 architecture looks like, and how this new architecture deals with the known issues of the past.

In sms 2003 the backend infrastructure relied on software distribution packages and advertisements to initiate the sofware catalog download, the software update scan and patch installation processes.  The scan process itself, using the final scan engine itmu, was based on the Windows automatic update agent. The scan engines prior to that were sms specific engines like the software update inventory scan tool, the office update inventory scan tool or the extended software update inventory tool. Clients have always reported their software update compliance state based on hardware inventory regardless of the scan engine used.

One of the downsides of the sms 2003 infrastructure was the fact that multiple scan engines were necessary, which complicated the software update management quite a bit. And no matter what engine you used, all engines first downloaded the catalog locally and cached it in a specific folder prior to starting the scan. This caching of the catalog files didn’t always work flawlessly resulting in clients scanning with an old catalog which obviously didn’t report the expected information. Another issue was the fact that the reporting process relied on hardware inventory to do its reporting, this resulted in a slower and not very flexible reporting process. 

Now let’s look at how this all works in sccm 2007. Sofware updates now integrates/relies on a Wsus 3.0 server. The Wsus server is used to download the catalog and to serve as the “scan point” for the Configmgr2007 clients. This eliminates the problem that the sms 2003 engines had with caching the catalog, because the clients now scan directly from a wsus server. Another benefit of this integration is the increased content that can be deployed. The sms 2003 engines only supported security updates whereas wsus 3.0 supports a wide variety of updates ranging from security updates over critical updates, feature pack, service packs, drivers and more. All these benefits come at a fairly low cost, yes you now need to install a wsus server but all management of this wsus server is done from the Sccm 2007 admin console. (This is why you need to install the wsus admin console on the site server if you want to use a remote wsus server).

Another major change afaic is that clients now report their software update compliance state based on state messages. This allows for faster more flexible and more detailed status reporting from the clients to flow up to the server.

That’s it for the first post, stay tuned for a follow-up.

Technorati Tags: , ,

“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS