I need to update all our machines with KB2819745 using WSUS, but the program doesn't exists in the update catalog.  Is there a way to import it.  I even searched online through the import command and no luck.  I am trying to deploy PowerShell 4.0 to my computers via the WMF 4.0 update.  Any ideas?

If it's not part of the catalog you could take a look here:

http://sourceforge.net/apps/mediawiki/localupdatepubl/index.php?title=Distributing_Hotfixes_and_MSUs_with_LUP

Alternatively you could deploy this via a Software Distribution tool with the commands:

• On x86-based computers that are running Windows 7 SP1 or Windows Server 2008 R2 SP1, run Windows6.1-KB2819745-x86.msu /quiet.
• On x64-based computers that are running Windows 7 SP1 or Windows Server 2008 R2 SP1, run Windows6.1-KB2819745-x64-MultiPkg.msu /quiet.
• On computers that are running Windows Server 2012, run Windows8-RT-KB2799888-x64.msu /quiet.

Hi,

Many updates are already available to you using the synchronizing capability in WSUS, SCE, and SCCM. Security updates, critical updates, service packs, update rollups, definition updates, and critical drivers can be configured to synchronize with your server automatically. You can still import these updates into your application by using Microsoft Update Catalog; however, depending on how you configure WSUS, SCE, and SCCM, you may not need to import the updates.

 

Some updates require users to accept Microsoft Software License Terms or perform other update-specific installation steps. These updates can be imported, but you will be warned while importing them that they may require additional administrative support. For example, because updates require additional user interaction, the user can cancel the installation; the updates cannot be installed automatically at a scheduled time.

 

Some updates are not compatible with the version of WSUS you are running. Additionally, some updates may not have the needed applicability information (in other words, the logic that determines whether an update should be installed). These types of updates cannot be imported.

If you have any feedback on our support, please click here

Its a shame that so many moderators on this site cannot read.

This dose not answer his question.

How can we get KB2819745 into WSUS? simple question.

Is it possible? yes? no?

Hi,

Sorry for my inaccurate description.

I should say that  we can use the following methods to deploy updates or hotfix, which would be useful for this question.

1.The Deploy Software Updates Wizard in Configuration Manager  allows you to create or modify a software update deployment, which deploys software updates to clients in the target collection. The software updates can be selected from several different locations and the wizard can be initiated in different ways. When a software update deployment is created or modified, clients will receive the deployment policy on their next machine policy cycle and the updates will be available for installation anytime after the configured start time.

For more information, we can refer this article:

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

2.We can use the Psexec tool to  deploy hotfixes or other patches that support a noninteractive interface across your network. To make this task even easier, PsExec takes multiple computer names, the name of a text file containing a list of computer names, or the special name of \\* that results in an enumeration of all the computers in the current domain.

Here is a detailed description about Psexec:

http://windowsitpro.com/systems-management/psexec

About WSUS, I should make it more clear specifically, here is a reference about similar discussion:

http://social.technet.microsoft.com/Forums/windowsserver/en-US/24d975a6-2f75-4786-9557-77d83054cc1e/how-do-i-do-a-manual-import-of-an-update-into-wsus?forum=winserverwsus

I would apology for my rude reply, regarding the deployment question, we should have more discussion.

How can we get KB2819745 into WSUS? simple question.

Is it possible? yes? no?

No, not with standard WSUS and Catalog functionality.
You will need to extend WSUS with a 3rd party publishing extension, or use another toolset/method.
Alex's posts detail some of the available alternative toolsets/methods.

Side Note: WSUS discussions are usually best, in the dedicated WSUS forum :)

Also note that WMF4.0 has the same warnings as WMF3.0 (impacts other components/products), and that impact is one of the reasons why WMF3.0 was withdrawn from the MU catalog. (and my theory is that's why WMF4.0 hasn't been published into the MU Catalog)
Those impacts are mentioned on the WMF4.0 download page (System Requirements): http://www.microsoft.com/en-us/download/details.aspx?id=40855

I guess it's possible that WMF3.0 and/or WMF4.0 *could* be (re)published into the MU Catalog at some time in the future, if MS are able to re-work the detection logic or the package payload.

thanks.

Part one of Alex's answer is not relevant as this update is not able to be added to WSUS.

Part two is more relevant. 

The answer to the question lies in part 3. 

Laurence explains - This is a =HOTFIX=.

Hotfixes are not available in the catalogues;

Hi Joey Jo-Jo Junior Shabadoo,

This mistake is caused by my careless action, I should provide the most appropriate reply in first place. Thanks for pointing it out.

If anyone is interested the way I rolled this out with ConfigMgr 2012 was to create a package with Windows6.1-KB2819745-x64-MultiPkg.msu in the source directory.

I then created a program with the command line as - 

wusa.exe Windows6.1-KB2819745-x64-MultiPkg.msu /quiet /norestart"

Installed nicely with no disruption to users but needed a reboot before PowerShell reported it as version 4.

If your not sure what version of powershell your running type -

$PSVersionTable

into PowerShell to see currently running version.

Joey,

where is "Windows Management Framework 4" described as a HotFix?  

Also note that WMF4.0 has the same warnings as WMF3.0 (impacts other components/products), and that impact is one of the reasons why WMF3.0 was withdrawn from the MU catalog. (and my theory is that's why WMF4.0 hasn't been published into the MU Catalog)

Those impacts are mentioned on the WMF4.0 download page (System Requirements): http://www.microsoft.com/en-us/download/details.aspx?id=40855

"Windows Server Update Services" is not able to detect Exchange, nor "System Center Configuration Manager", nor "System Center"  and make the user add a '-force' switch if they want to install anyway on those systems.  Sad.  Very Sad.

Its not a hotfix, its a major functional update to the management framework.

Don't be misled that simply because its a KB that this denotes patch/hotfix, there are a lot of actual product variants available as KB items as well.....

Its not a hotfix, its a major functional update to the management framework.

Don't be misled that simply because its a KB that this denotes patch/hotfix, there are a lot of actual product variants available as KB items as well.....

It's described as a hotfix within the specific KB article http://support.microsoft.com/en-au/kb/2819745

(Although, I think the term "hotfix" does often get mis-interpreted/mis-used fairly commonly)
(and, "hotfix" is apparently not an "update type", according to this http://support.microsoft.com/en-us/kb/824684 )