SCCM Report for all machines with IE9

If you know the steps to create a report then the SQL query you could use would be somthing like:

SELECT DISTINCT a.Name0 AS [Machine Name],
c.FileVersion AS [IE Version],
d.Caption0
FROM v_GS_SoftwareFile c INNER JOIN
v_GS_SYSTEM a ON c.ResourceID = a.ResourceID INNER JOIN
v_GS_OPERATING_SYSTEM d ON a.ResourceID = d.ResourceID INNER JOIN
v_FullCollectionMembership b ON a.ResourceID = b.ResourceID
WHERE     (c.FileName = 'iexplore.exe') AND (c.FileVersion like '9.%')
ORDER BY a.Name0

Please note this has a little bug where it will report multiple instances of the same machine due to the fact that SCCM will have polled every version of IE9 (each incremntal update etc)

It would be better to export this data in to Excel and then delete the duplicates in the name column...

ifM63x64.sys file missing or corrupt - SCCM OSD (X1 Carbon)

Building a new Lenovo X1 Carbon with the new integrated LAN adapter (no more guessing which USB port to use!) via SCCM 2007 and I came across this little blinder.

After the first reboot to OS I was presented with this error screen:

I spotted that is was driver in my driver pack (taken from Lenovo's SCCM pack) for the  Intel Ethernet FCoE Virtual Storport Miniport Driver.

I located the driver in my driver pack and removed it - left he check box UNTICKED to update the distribution point and then manually when and updated it after myself. 

Once I was happy that the source had incremented by one version I kicked off the build again.

Sure enough it sailed through and we are all happy....

 

Microsoft Error Codes seen during SCCM software deployments

I may have posted this before - I can't remember.

Error code               Value  Description
---------------------------------------------------------------------------
ERROR_SUCCESS               0   Action completed successfully.
ERROR_INVALID_DATA         13   The data is invalid.
ERROR_INVALID_PARAMETER    87   One of the parameters was invalid.
ERROR_INSTALL_SERVICE_
 FAILURE                 1601   The Windows Installer service could not be 
                                accessed. Contact your support personnel 
                                to verify that the Windows Installer 
                                service is properly registered.
ERROR_INSTALL_USEREXIT   1602   User cancel installation.
ERROR_INSTALL_FAILURE    1603   Fatal error during installation.
ERROR_INSTALL_SUSPEND    1604   Installation suspended, incomplete.
ERROR_UNKNOWN_PRODUCT    1605   This action is only valid for products that
                                are currently installed.
ERROR_UNKNOWN_FEATURE    1606   Feature ID not registered.
ERROR_UNKNOWN_COMPONENT  1607   Component ID not registered.
ERROR_UNKNOWN_PROPERTY   1608   Unknown property.
ERROR_INVALID_HANDLE_
 STATE                   1609   Handle is in an invalid state.
ERROR_BAD_CONFIGURATION  1610   The configuration data for this product is 
                                corrupt. Contact your support personnel.
ERROR_INDEX_ABSENT       1611   Component qualifier not present.
ERROR_INSTALL_SOURCE_
 ABSENT                  1612   The installation source for this product 
                                is not available. Verify that the source 
                                exists and that you can access it.
ERROR_INSTALL_PACKAGE_
 VERSION                 1613   This installation package cannot be 
                                installed by the Windows Installer 
                                service. You must install a Windows 
                                service pack that contains a newer version 
                                of the Windows Installer service.
ERROR_PRODUCT_
 UNINSTALLED             1614   Product is uninstalled.
ERROR_BAD_QUERY_SYNTAX   1615   SQL query syntax invalid or unsupported.
ERROR_INVALID_FIELD      1616   Record field does not exist.

ERROR_INSTALL_ALREADY_
 RUNNING                 1618   Another installation is already in 
                                progress. Complete that installation 
                                before proceeding with this install.
ERROR_INSTALL_PACKAGE_
 OPEN_FAILED             1619   This installation package could not be 
                                opened. Verify that the package exists and 
                                that you can access it, or contact the 
                                application vendor to verify that this is 
                                a valid Windows Installer package.
ERROR_INSTALL_PACKAGE_
 INVALID                 1620   This installation package could not be 
                                opened. Contact the application vendor to 
                                verify that this is a valid Windows 
                                Installer package.
ERROR_INSTALL_UI_
 FAILURE                 1621   There was an error starting the Windows 
                                Installer service user interface. Contact 
                                your support personnel.
ERROR_INSTALL_LOG_
 FAILURE                 1622   Error opening installation log file. 
                                Verify that the specified log file 
                                location exists and is writable.
ERROR_INSTALL_LANGUAGE_
 UNSUPPORTED             1623   This language of this installation package 
                                is not supported by your system.
ERROR_INSTALL_TRANSFORM_
  FAILURE                1624   Error applying transforms. Verify that
                                the specified transform paths are valid.
ERROR_INSTALL_PACKAGE_
 REJECTED                1625   This installation is forbidden by system 
                                policy. Contact your system administrator.
ERROR_FUNCTION_NOT_
 CALLED                  1626   Function could not be executed.
ERROR_FUNCTION_FAILED    1627   Function failed during execution.
ERROR_INVALID_TABLE      1628   Invalid or unknown table specified.
ERROR_DATATYPE_MISMATCH  1629   Data supplied is of wrong type.
ERROR_UNSUPPORTED_TYPE   1630   Data of this type is not supported.
ERROR_CREATE_FAILED      1631   The Windows Installer service failed to 
                                start. Contact your support personnel.
ERROR_INSTALL_TEMP_
 UNWRITABLE              1632   The temp folder is either full or 
                                inaccessible. Verify that the temp folder 
                                exists and that you can write to it.
ERROR_INSTALL_PLATFORM_
 UNSUPPORTED             1633   This installation package is not supported 
                                on this platform. Contact your application 
                                vendor.
ERROR_INSTALL_NOTUSED    1634   Component not used on this machine.
ERROR_PATCH_PACKAGE_
 OPEN_FAILED             1635   This patch package could not be opened. 
                                Verify that the patch package exists and 
                                that you can access it, or contact the 
                                application vendor to verify that this is 
                                a valid Windows Installer patch package.
ERROR_PATCH_PACKAGE_
 INVALID                 1636   This patch package could not be opened. 
                                Contact the application vendor to verify 
                                that this is a valid Windows Installer 
                                patch package.
ERROR_PATCH_PACKAGE_
 UNSUPPORTED             1637   This patch package cannot be processed by 
                                the Windows Installer service. You must 
                                install a Windows service pack that 
                                contains a newer version of the Windows 
                                Installer service.
ERROR_PRODUCT_VERSION    1638   Another version of this product is already 
                                installed. Installation of this version 
                                cannot continue. To configure or remove 
                                the existing version of this product, use 
                                Add/Remove Programs on the Control Panel.
ERROR_INVALID_COMMAND_
 LINE                    1639   Invalid command line argument. Consult the 
                                Windows Installer SDK for detailed command 
                                line help.
ERROR_INSTALL_REMOTE_
  DISALLOWED             1640   Installation from a Terminal Server
                                client session not permitted for 
                                current user.
ERROR_SUCCESS_REBOOT_
  INITIATED              1641   The installer has started a reboot.
                                This error code not available 
                                on Windows Installer version 1.0.
ERROR_PATCH_TARGET_
  NOT_FOUND              1642   The installer cannot install the
                                upgrade patch because the program
                                being upgraded may be missing, or the
                                upgrade patch updates a different
                                version of the program. Verify that 
                                the program to be upgraded exists on
                                your computer and that you have the 
                                correct upgrade patch.
 
                                This error code is not available on
                                Windows Installer version 1.0.
ERROR_SUCCESS_REBOOT_
 REQUIRED                3010   A restart is required to complete the 
                                install. This does not include installs 
                                where the ForceReboot action is run. Note 
                                that this error will not be available until 
                                future version of the installer. 
    

Operating System Deployment with USB Dongles (Lenovo in my case)

With the advances in technology we have seen in recent years, devices have become smaller, thinner and lighter than ever before.

With this we are finding that some devices are loosing functionality - ie. Some devices are having ports omitted to retain their slender profile.

The Lenovo X1 Carbon adopted this approach and required a USB dongle which I posted about the pitfalls of PXE boot here: Lenovo X1 PXE Issues

I've seen an increase in the issues these dongles are causing us deployment techs, one of those being that each of these dongles have their own MAC address.  In true tech style when we see this new wizardry the first thing we say is "MINE"... Well actually the first thing we normally say is "Ooh Shiney" but then there's a Smeagle like "My Precious" when we claim the Shiney as our own.

I did this.  I had my very own dongle.  It worked great.  ONCE!  Every subsequent build failed.  I did a bit of research and found that it had it's own MAC that was registering in SCCM so I had to surrender my Shiney and give it on to the user.

I now use the supplied dongles for each build as it isn't worth the trouble but I have it on good authority that with the latest gen of Lenovo kit they are shipping certain models with on-board NICs (therefore unique MACs) and the dongle is purely a port extender utilising USB to present an Ethernet port.

If you have fallen prey to this (and insist on using one dongle to rule them all) you need to read my earlier post to search SCCM for machines by their MAC address.

Have fun...

DocN

There may be too many steps in the task sequence object.

So this was a new one on me.  Before you ask; no, we hadn't made any changes to our system - it just happened.  Yes - it just happened, just like I'm guessing has happened to you if you're reading this.

I fired up my SCCM console locally on my machine.  I went to edit a Task Sequence and then got this little gem:

 

Good one uh?  I then jumped on the server and tried the server console.  Still the same.

A bit of twitchy bum moments, log file seaching and a touch of Googling I found that this could be caused by MDT going; what we in the industry call; "Tits up".

Do you have MDT integrated into SCCM too?  You do?  Good - read on...

Try re-running the MDT integration as per the start menu folder location for MDT on your SCCM server and you should find things fine and dandy.

It didn't work?  Oh... Sorry - try this link here.

Upgrade Microsoft OCS 2007 to Lync 2013 in a Windows 7 x86 environment using SCCM 2007: Part 2

Continued from Part 1

Compressing the Lync Client (cont...)

You will now have a folder called Microsoft_Lync_2013_x86_01 containing:

• This is now the source folder we will point our SCCM package to.  

•  You will now need to create a program in the package and point it to the TSINSTALL.bat

Creating the Task Sequence

There were several factors involved in my choice to use a task sequence to do this.  Mainly because we can run command lines directly from the TS rather than having to come up with a massively long boring script.

• Create a new task sequence under the Operating System Deployment section of SCCM
• Choose "create a new custom task seqeunce"
• Name it Install Lync 2013 x86 and click finish
• Add an Install Software step and call it Install Microsoft Lync 2013 x86
• Choose the package and program you created earlier (an assumption)
• Create a run command line step to kill of the Communicator process.  Name it Kill Communicator Process and use the command: taskkill /im communicator.exe /f
• Create a run command line step to kill of the Outlook process.  Name it Kill Outlook Process and use the command: taskkill /im outlook.exe /f
• Create a run command line step called Remove Live Meeting with the command: MsiExec.exe /X{A98AFBC7-D5A7-46A1-8795-EABE2F55A7D6} /qn REBOOT=ReallySuppress
• Create a run command line step called Remove OCS 2007 with the command: MsiExec.exe /X{E5BA0430-919F-46DD-B656-0796F8A5ADFF} /qn REBOOT=ReallySuppress
• Create a run command line step called RemoveOutlook Plugin using the command: MsiExec.exe /X{1DE3088D-E607-4EB0-9223-106E7B5AF2F1} /qn REBOOT=ReallySuppress
• Create a run command line step called Delete Source Files with the command del c:\lync2013x86 /F /Q - run this step with an admin account as per the tick box at the bottom.

Your Task Sequence should look this this.

*I ticked "Continue on error" in the options tab on every step EXCEPT the install Lync step.

Click OK to save the Task Sequence.

Now advertise the task sequence out to a collection - I advise not populating the collection yet - just test this on 1 computer for now and then add a few more once your happy it's working the way it should.  Tailor the advertisment in as way to suit you; Silently or with an on screen prompt etc. ASAP or a timed schedule...

I AM NOT RESPONSIBLE FOR YOUR CHOICES OF TARGET - DON'T BLAME ME IF YOU TRASH YOUR ESTATE WITH THIS METHOD!!!

This is what will happen.

1. Target computer will recieve policy from SCCM
2. TS will launch and copy over source folder
3. Program will run which will create the extract source, extract the 7z install and run setup.exe
4. Once Lync has installed the TS will kill off OCS & Outlook
5. It will remove Live Meeting, OCS and the Outlook Plugin
6. Source files are deleted.

I really hope this works for people and I welcome any constructive comments....

docN

Upgrade Microsoft OCS 2007 to Lync 2013 in a Windows 7 x86 environment using SCCM 2007: Part 1

As part of our ongoing commitments to optimise our users desktop experience; our infrastructure team are currently implementing a Lync back end.  Of course it comes to me to package and deploy the client out to our estate.  As we are currently running a mixture of XP and Win7/8 there is a different method required for XP.

In this post I will explain how I went about packaging up Lync so it would remove any legacy installs of Office Communicator and replace it will Lync.

This is going to be a lengthy one so make coffee - LOTS of coffee.  Hopefully though it will help other people to achieve the same as me should that be what they require.

You will need the following:

Lync 2013 x86 client (I downloaded the ISO from our VLSC)
7zip (executable AND command line) http://www.7-zip.org/

Assumptions:

• You are proficient in SCCM 2007 packaging and deploying

• you have used the OCT to customise Office installs

• You require a silent install 

Packaging the Lync client

Customising the install

Assuming you have the above we will first setup the Custom.MSP file via the OCT.  Once you have extracted the ISO your file structure will look like the above.  You will not have the "Admin" shortcut so we create that now.

1. Right click "setup.exe" and click "create shortcut"
2. Rename "setup.exe - shortcut" to "Admin"
3. Right click "Admin" and at the end of the Target path you need to add "/admin".  Mine looks like this: "\\MYSCCMSERVER\Packages\Microsoft_Lync_2013_x86\setup.exe" /admin
4. Click OK
5. Double click Admin and you will be prompted to create or open an MSP file - just click OK to create a new one.
6.  Under Setup, click Install location and organisational name - enter your org name here.
7. Under Licensing & User Interface choose your method of entering the product key - I use KMS.
8. Click I accept the terms... box, change display level to "none" and tick suppress modal
9. Under "Additional content" click "Add registry entries" and add the following:
10. Machine setting
    1. Root : HKEY_Local_Machine
    2. Type: DWORD
    3. Key: Software\Policies\Microsoft\Office\15.0\Common\General
    4. Name: ShownFirstRunOptin
    5. Value: 0×00000001
11. User Setting
    1. Root : HKEY_Current_User
    2. Type: DWORD
    3. Key: Software\Microsoft\Office\15.0\Common\General
    4. Name: ShownFirstRunOptin
    5. Value: 1

Once you are happy that you have customised your install accordingly click "file" "save as" and save the file into the "updates" folder of the Lync package as "custom.msp".

Compressing the Lync Client

Using 7zip we will now compress the source folder.  Simply right click the folder that contains your install and select 7-Zip>Add to "(foldername).7z"

Create a second folder and add the resulting 7z file - this is the folder that will be deployed over to the clients machines.  For this example mine is called "Microsoft_Lync_2013_x86_01"

Add the 7za.exe command line tool you downloaded (you did download it right?)

Create a batch file called "TSINSTALL.bat".  In the batch file add the following lines:

md c:\lync2013x86

7za.exe x Microsoft_Lync_2013_x86_01.7z -oC:\lync2013x86
cd c:\lync2013x86
setup.exe

Continue to PART 2

SCCM Client Center

The new version (2.0.4.2) of this invaluable tool by Roger Zander is now available for download from here.

HP DC7800 will not boot from USB Boot Pen

First model I came across in the roll out was a HP DC7800.  My first task was to deploy our Windows 7 image and then check which drivers were missing.

I came to boot from USB by pressing F9 to get to the boot menu and choosing "USB"

My pen fired up and flickered away whiles loading the initial boot file.  The progress bar galloped across the screen like a trusty steed on Derby Day until it reached the end and froze.

3 pens and 2 machines later I discovered there is a BIOS setting under security that required disabling:  Data Execution Prevention.

As soon as this was disabled, subsequent boots worked like a charm.

SCCM OSD Log File Locations

I may be late with this but it's for my reference more than anything.  SCCM OSD can be a hair tearing process at the bet of times.  Should you ever need to troubleshoot it MS don't exactly make it easy finding the files either.

He is where you will find the log files at various points throughout the whole OSD process as they do move dependant on which stage you are up to...

WindowsPE, before HDD format:              x:\windows\temp\smstslog\smsts.log
WindowsPE, after HDD format:                 x:\smstslog\smsts.log
Windows, SCCM agent not installed:       c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Windows, SCCM agent installed:               c:\windows\system32\ccm\logs\Smstslog\smsts.log
Windows x64, SCCM agent installed:       c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
Task Sequence completed:                           c:\windows\system32\ccm\logs\smsts.log
Task Sequence completed x64:                   c:\windows\sysWOW64\ccm\logs\smsts.log

Don't forget - use Trace32 to view these log files - it makes it miles easier....

Client Center 2012

I've just seen the new Beta for Client Centre 2012 is out and can be downloaded here:

http://sccmclictr.codeplex.com/

Looks ok - sluggish but it is still beta...

X1 Carbon Incorrect Hash Errors during OSD

I was fighting with this one for a couple of days.  Lenovo X1 Carbon - deploying Windows 7 x64.  All drivers were fine and dandy but I was getting randon "Incorrect hash value" errors when the OSD was failing.

This was determined by looking in the SMSTS.log once the OSD had failed.

It transpires that if the USB to Ethernet adapter was plugged in to the right hand USB socket it was dropping loads of packets.  Plugging it into the left hand side worked a treat.

As simple a solution as it sounds this may be far too obvious for some tecchy to even try.  I managed to replicate this on 3 different units so it wasn't just faulty parts.

Felt like a complete numpty once I discovered the fix!

This program cannot run because a reboot is in progress or software distribution is paused.

Really quick post here.  You may find when running an SCCM2007 task sequence from Run Advertised Programs that you get an error regarding another program is installing please try later. 

when examining the execmgr.log you will see This program cannot run because a reboot is in progress or software distribution is paused.

This worked for me - not claiming it to be a fix for everyone but you could try it.  On the problematic machine go to either:

• x86 – HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\Software Distribution\State\
• x64 – HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\Mobile Client\Software Distribution\State\

Set both "Paused" keys in there back to "0" if they are on "1" and then reboot.  Fixed it for me!!!

Lenovo X1 Carbon PXE Boot Issues

I  was recently given the nice new shiny Lenovo X1 Carbon to play with and deploy our corporate Windows 7 image to it.  To maintain its slim physique it hasn't got a built in Ethernet adaptor and is supplied with a Lenovo USB 2.0 to Ethernet Adapter.  Obviously we now had to track down the driver to inject to our Boot Image.

Initially we used the Lenovo USB 2.0 Ethernet Adapter Driver 5.4.3.0 which PXE booted but then seemed to fail and hang once WinPE loaded up.

I then downloaded the Lenovo X1 Carbon SCCM Driver Pack which came with v5.12.4.0 which also seemed to give me problems.

Eventually I found that it was the manufacturers Vista driver that worked for me.

From the AXIS website you can download the AXIS AX88772B Vista Driver which worked a treat.  With the SSD this was a dream to image and was quite quick in comparison to others.

Hope this helps.

Chris.

Create a bootable USB pen for SCCM Windows 7 Build Deployment

If you are ever in a situation where deploying your OS by SCCM's more conventional methods (ie PXE or LAN based deployments) isn't feasable (bandwidth/no connectivity) then you can prepare a USB pen and deploy to machines via a USB boot.

I've found the SCCM built in method of making a USB pen to be quite unreliable so I opt for the manual method.

Just a few heads up first:

• I'd recommend at least an 8GB drive but in reality your build (if corporate) will eventually exceed this.
• The pen will be totally wiped clean - all data will be lost.

Step 1:  Preparing the USB pen

1. Open command prompt
2. Type diskpart and press enter
3. Type list disk and press enter
4. Find your disk in the list
5. Type select disk * (* being your number)
6. Type clean and press enter - you should see "DiskPart succeeded in cleaning the disk."
7. Type create partition primary and press enter - you should see "DiskPart succeeded in creating the specified partition."
8. Type select partition 1 and press enter - you should see "Partition 1 is now the selected partition." 
9. Type active and press enter - you should see "DiskPart Marked the current partition as active."
10. Type assign and press enter - you should see "DiskPart successfully assigned a drive letter ..."
11. Type detail disk and press enter.  For this example we will work with a drive letter "U" for USB
12. Type exit to leave the Diskpart command and return to a standard prompt

Step 2:  Formatting & Copying

We are still using a drive letter "U:" so we want to type:

format U: /fs:fat32 /q YOU WILL LOSE EVERYTHING ON THE PEN HERE

Enter a label for the drive - this is how it will show in "Computer"

I copy the files manually - it works - but if you want to do it "properly" use this command:

In command prompt navigate to the location of your build files - this is what would have been extracted from the ISO that was produced in SCCM when you "Created Removable Media" from the OSD task sequence - if you need a guide on this mail me or leave a comment...

Type xcopy \*.* /s/e/f \ 

With our extracted ISO in C:\Win7Build and our pen being U:\ This would look like:

Type xcopy c:\Win7Build\*.* /s/e/f U:\ 

Don't forget you may/will need to adjust the boot order in the BIOS to accommodate booting from USB - you can find a guide here: http://bit.ly/TvndIW

Java Deployment (x86)

I've spent many hours searching the net for a definitive guide on how to successfully deploy Java across a network and to newly deployed machines.

In this instance I'm trying to add Java to an Operating System Deployment using Microsoft SCCM with two particular settings automated into the deployment.

I want the automatic updates to be disabled as this is constantly screwing up our clinical systems that get delivered to the users desktop as an update of Java resets several settings we have to configure post install.

The other is the Proxy set to "Direct Connection" as again our clinical systems hate any interference from the Proxy settings.


I've decided to repost my steps here in hope that it will help a fellow tecchy one day:

• Download your choice of Java - I'm using 1.6.0.31.

• Run the.exe and run to C:\Users\\AppData\LocalLow\Sun\Java\jre1.6.0_31

• Copy the Data1.cab and jre1.6.0_31 files out of there into a folder of their own.

• I already have a working WIM image I captured last week and didn't want to go through another capture so using the DISM GUI tool  I mounted my WIM and added a folder structure and the deployment.properties file to: C:\Users\Default\AppData\LocalLow\Sun\Java\Deployment.  Other settings for the deployment.properties file are available here.

• Within deployment.properties was the following - it's actually one I created by manually altering the settings from the Java control panel and capturing the file from C:\Users\[username]\AppData\LocalLow\Sun\Java\Deployment

#deployment.properties
#Tue Apr 13 13:59:54 BST 2010
deployment.version=6.0
deployment.proxy.type=0
deployment.javaws.autodownload=NEVER
deployment.javapi.cache.update=true
deployment.security.mixcode=DISABLE
deployment.browser.path=C\:\\Program Files\\Internet Explorer\\iexplore.exe
#Java Deployment jre's
#Tue Apr 13 13:59:54 BST 2010
deployment.javaws.jre.0.product=1.6.0_31
deployment.javaws.jre.0.registered=true
deployment.javaws.jre.0.osname=Windows
deployment.javaws.jre.0.platform=1.6
deployment.javaws.jre.0.path=C\:\\Program Files\\Java\\jre6\\bin\\javaw.exe
deployment.javaws.jre.0.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.0.enabled=true
deployment.javaws.jre.0.osarch=x86

• I committed the changes to the Wim and uploaded it back to our deployment server :::EDIT::: DON'T FORGET TO UPDATE THE DISTRIBUTION POINT!!!
• Created a package for Java 31
• Used the command line for the package program: msiexec.exe /i jre1.6.0.31.msi /qn
• Hey presto - I'm now getting a Java deployment that automatically uses the settings defined in the deployment.properties file I created! BOOM !!!

OnContentAvailable program 0x80091007

Symptoms:

When deploying software to a collection the client execmgr.log shows the following error:

OnContentAvailable program 0x80091007

You will notice a hash mismatch also " SoftDistAdvertHashMismatchEvent" - when checking the CAS.log you will see

"Hash matching failed."

Cause: 

SCCM is a temperamental bitch

Solution:

Goto the package in question and right click on Distribution Points and click "Manage Distribution Points".  Choose "Update all distribution points with a new package source version" - and thats exactly what happens.
Kick of a hardware policy cycle on the client and watch the magic.