Client Update Packages (SCCM CUs)

What is the proper way of deploying these? I have the x64 package deployed to a dynamic collection which consists of x64 clients. It's configured to install as soon as possible. This is causing issues with new client installs since the
SCEP install and client update seem to interfere with each other. How can I ensure clients receive the client update in a timely manner but don't interfere with the SCEP install?

A common approach is to make collections with queries that target x86 and x64 OS architectures.
Then deploy the x86 and x64 client update packages (that get created for you when applying the CU) to those collections.
When you say new client installs do you mean during OSD? If this is the case then you should be patching your client at the point of installation during your OSD Task Sequence.
If you mean that the Client Update package is attempting to install before the major client update - i.e. your on SCCM 2012 SP1 and you have upgraded to 2012 R2 CU1 - then you should be adjusting your queries so they only target clients with the R2 version.
This way you will not have the Client Update package trying to run before the full client upgrade has occurred.
As an example - this is the query I have used to upgrade my SCCM 2012 CU1 client to CU2:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId
where SMS_R_System.Active = "1" and SMS_G_System_SYSTEM.SystemType = "X64-based PC" and SMS_R_System.ClientVersion < "5.00.7958.1303" and SMS_R_System.ClientVersion >= "5.00.7958.1000"
There are plenty of blogs which talk about client updates using queries.
Cheers
Damon
I have a dynamic collection built already. I guess my question revolves around how you should configure the available/deadline part of the deployment. My issue is that the SCEP install after a client is upgraded from 2007 -> 2012 is kicking
off at the same time as the client upgrade. The FEP client gets uninstalled, the client upgrade gets stuck in "Waiting for install" and nothing continues until I restart the SMS service.

Similar Messages

FEP and SCEP Client updates

There multible versions of client deployed at same time. I'm using stadard software updates deployment process to keep clients up to date. NOT talking about definitions, but client version!
I have FEP and SCEP clients out there. When I go to All software updates and search for "endpoint protection client" I will have four FEP (4.1.552.0, 4.3.215.0, 4.5.236.0, 4.6.305.0) updates and three SCEP updates (4.3.215.0, 4.5.216.0, 4.6.305.0)
to client deployed in the same update packages! All of them with various number of Required and Installed status.
The obious reason for this is that older client update packages are not marked as superseeded updates. Any thoughts on why? I am going to exclude old ones with custom severity method, but is there a automatic method available?
.Marko

Multiple SCEP/FEP updates are required, because SCEP/FEP agent can update only N-2 versions e.g. you cannot install SCEP version 4.6.305.0 to a computer with SCEP 4.3.215.0. You need first to upgrade 4.3 to 4.5 and then to 4.6.Because there might be earlier
versions in the environment, there must be multiple SCEP/FEP versions available.
Check the following blog article for more details:
http://blogs.technet.com/b/configmgrteam/archive/2014/03/27/anti-malware-platform-updates-for-endpoint-protection-will-be-released-to-mu.aspx
Panu

Adobe Reader 11.0.04 SCUP update causing SCCM 2007 SP2 R3 client to crash

When we started deploying the 11.0.0.4 update for Adobe Reader provided for System Center Updates Publisher (SCUP), we started having failures with our Operating System Deployments. When the 11.0.0.4 update installs during the Install Software Updates (via WSUS) step, it stops the SCCM client, causing the SCCM client to crash and uninstall. When the SCCM client uninstalls, it breaks the OSD process and the image process fails. Our current .wim file has Adobe Reader 11.x patched to the 11.0.0.3 level. We are using SCUP 2011. Everything was working ok until this update came out. We even tried creating an SCCM software distribution package to deploy the update and it still crashes the SCCM client when installed that way. Has anyone seen similar issues in their SCCM environments? Does Adobe have a support number available to get help with these types of issues? Thanks.

Try using the Adobe doc: 1 Introduction — Enterprise Administration Guide
Also, you'll find installing and updating via bootstrapper is easier than AIP over the long haul.
hth,
Ben

Endpoint Protection clients no getting updates from SCCM 2012 in new Secondary Site

I recently stood up a secondary site behind a PCI firewall to manage PCI in-scope systems. All of my boundaries are properly configured and there are no overlaps. I am able to push packages to these clients and the clients are reporting as healthy however
I am not able to get updates to the SCEP clients. There is no internet access from these systems so I have to rely on updates from SCCM. From what I can see in the WindowsUpdate log it is only trying to go to Microsoft for the definitions. Here is the Log:
2014-04-30 11:05:09:739
828 da8
Misc WARNING: Send failed with hr = 80072ee2.
2014-04-30 11:05:09:739
828 da8
Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
2014-04-30 11:05:09:739
828 da8
Misc WARNING: Send request failed, hr:0x80072ee2
2014-04-30 11:05:09:739
828 da8
Misc WARNING: WinHttp: SendRequestUsingProxy failed for <HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=41&L=en-US&P=&PT=0x7&WUA=7.9.9600.16422>.
error 0x80072ee2
2014-04-30 11:05:09:739
828 da8
Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2014-04-30 11:05:09:739
828 da8
Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2014-04-30 11:05:09:739
828 da8
Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
2014-04-30 11:05:09:739
828 da8
SLS FATAL: GetResponse failed with hresult 0x80072ee2...
2014-04-30 11:05:09:739
828 da8
EP FATAL: EP: CSLSEndpointProvider::GetWUClientDataAndInitParser - failed to get SLS data, error = 0x80072EE2
2014-04-30 11:05:09:739
828 da8
EP FATAL: EP: CSLSEndpointProvider::GetEndpointFromSLS - Failed to get client data and init parser, error = 0x80072EE2
2014-04-30 11:05:09:739
828 da8
EP FATAL: Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL, error = 0x80072EE2
2014-04-30 11:05:09:739
828 da8
Agent WARNING: Failed to obtain the authorization cab URL for service 7971f918-a847-4430-9279-4a52d1efe18d, hr=0
2014-04-30 11:05:09:739
828 da8
Agent FATAL: Caller <NULL> failed to opt in to service 7971f918-a847-4430-9279-4a52d1efe18d, hr=0X80072EE2
2014-04-30 11:05:09:739
828 da8
SLS Retrieving SLS response from server...
2014-04-30 11:05:09:739
828 da8
SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=41&L=en-US&P=&PT=0x7&WUA=7.9.9600.16422
2014-04-30 11:05:30:742
828 da8
Misc WARNING: Send failed with hr = 80072ee2.
2014-04-30 11:05:30:742
828 da8
Misc WARNING: Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <None>
2014-04-30 11:05:30:742
828 da8
Misc WARNING: Send request failed, hr:0x80072ee2
2014-04-30 11:05:30:742
828 da8
Misc WARNING: WinHttp: SendRequestUsingProxy failed for <HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=41&L=en-US&P=&PT=0x7&WUA=7.9.9600.16422>.
error 0x80072ee2
2014-04-30 11:05:30:742
828 da8
Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2014-04-30 11:05:30:742
828 da8
Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2014-04-30 11:05:30:742
828 da8
Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
2014-04-30 11:05:30:742
828 da8
SLS FATAL: GetResponse failed with hresult 0x80072ee2...
2014-04-30 11:05:30:742
828 da8
EP FATAL: EP: CSLSEndpointProvider::GetWUClientDataAndInitParser - failed to get SLS data, error = 0x80072EE2
2014-04-30 11:05:30:742
828 da8
EP FATAL: EP: CSLSEndpointProvider::GetSecondaryServicesEnabledState - Failed to get client data and init parser, error = 0x80072EE2
2014-04-30 11:05:30:742
828 da8
Agent   * WARNING: Online service registration/service ID resolution failed, hr=0x80248014
2014-04-30 11:05:30:742
828 da8
Agent   * WARNING: Exit code = 0x80248014
2014-04-30 11:05:30:742
828 da8
Agent *********
2014-04-30 11:05:30:742
828 da8
Agent ** END ** Agent: Finding updates [CallerId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB) Id = 9]
2014-04-30 11:05:30:742
828 da8
Agent *************
2014-04-30 11:05:30:742
828 da8
Agent WARNING: WU client failed Searching for update with error 0x80248014
2014-04-30 11:05:30:742
828 da8
IdleTmr WU operation (CSearchCall::Init ID 9, operation # 99) stopped; does use network; is not at background priority
2014-04-30 11:05:30:742
828 da8
IdleTmr Decremented PDC RefCount for Network to 0
2014-04-30 11:05:30:742
828 da8
IdleTmr Decremented idle timer priority operation counter to 0
2014-04-30 11:05:30:743
576 12c0
COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2014-04-30 11:05:30:743
576 12c0
COMAPI   - Updates found = 0
2014-04-30 11:05:30:743
576 12c0
COMAPI   - WARNING: Exit code = 0x00000000, Result code = 0x80248014
2014-04-30 11:05:30:743
576 12c0
COMAPI ---------
2014-04-30 11:05:30:743
576 12c0
COMAPI -- END -- COMAPI: Search [ClientId = System Center Endpoint Protection (DDEFDD14-250E-4DC8-A0B3-9D667EC5D8EB)]
2014-04-30 11:05:30:743
576 12c0
COMAPI -------------
2014-04-30 11:05:30:743
576 1254
COMAPI WARNING: Operation failed due to earlier error, hr=80248014
2014-04-30 11:05:30:743
576 1254
COMAPI FATAL: Unable to complete asynchronous search. (hr=80248014)
The log is from a Server 2012 R2 Client. The only thing I was able to find was this Article which did not resolve my issue. Anyone else encounter anything similar? Any help would be appreciated.
Regards, Evan Mills - Systems Administrator

Every two hours is too aggressive for the ADR. Definitions are only released 2-3 times a day so every 8 hours is what most consider best practice. Is your WSUS sync occurring every two hours as well? If not, then the ADR wouldn't have anything new to pick
up anyway. It's best to set the WSUS sync for every 8 hours and then set the ADR to run after any successful WSUS sync.
So the EP definitions are caching but not installing? What does the WUAHandler.log show? One of my machines shows the following which indicates a successful installation from the ConfigMgr delivered update:
1. Update (Missing): Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.173.933.0) (0a156122-d4f8-4215-9e63-8f0f1e32c9c6, 200)   WUAHandler   4/30/2014 6:49:33 AM   11080 (0x2B48)
Async installation of updates started.   WUAHandler   4/30/2014 6:49:34 AM   11080 (0x2B48)
Update 1 (0a156122-d4f8-4215-9e63-8f0f1e32c9c6) finished installing (0x00000000), Reboot Required? No   WUAHandler   4/30/2014 6:50:23 AM   8664 (0x21D8)
Async install completed.   WUAHandler   4/30/2014 6:50:23 AM   8664 (0x21D8)
Installation of updates completed.   WUAHandler   4/30/2014 6:50:23 AM   11032 (0x2B18)
It sounds like if you set "Check for Endpoint Protection definitions at a specific interval" to 0 then it would prevent the WindowsUpdate.log activity you're seeing when the EP client tries to reach out for updates.

APPV folder on client pc after pushing Updated package

1. Currently published package is 125MB.
2. Updated that package in sequencer. One file of 250KB was changed.
3. Published updated package to the test computer. Application works fine after update.
4. Under Program Data\Appv in package GUID folder second folder appears.
So now there are 2 folders : for previous and updated one. They are about the same size
The question:
as I know unpublished package will always "sit" on the user's HD, unless we'll manually remove it.
I have a recommendation link that should help with automation of removal of unpublished package (have to return to it).
Now I have 2 folders in package GUID (about 220MB each). What will happen if I will do another 3 updates with only one 250KB file replaced.
Would it bring another 660MB (3x220) in package GUID folder?
5. in current situation: if I will unpublish original package from APPVMAN console, can I remove it from the client machine?
Or it will be still necessary for updated folder in package GUID folder.
My question is related to UPDATED packages only.
Thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Deets wrote
"Yes, each version of the package that you publish will add another 220MB folder."
Sorry, but I disagree. When an update is loaded (i.e. the Package GUID remains the same, but the
Version GUID changes), only the modified data (~250) are really added to the new subfolder. All the 'unchanged' other files and folder are just hard links or so to the original file. The bad thing is, that most tools to show directory sizes aren't smart enough
to see the difference.
When you use a tool like TrueSize (http://www.heise.de/download/cttruesize-d097978e369c27b107b751624dbce77b-1422025920-2650272.html),
German web site) you should see a difference.
When you remove the original version (using the App-V client or even just deleting the folder), NTFS is
smart enough to correct the file tables - so now the 1st folder disappeared, and the new folder _really_ counts 220 MB
Falko
Twitter
@kirk_tn   |   Blog
kirxblog   |   Web
kirx.org   |   Fireside
appvbook.com

SCCM Client Downloads Packages from DP on different subnet

Hi
When I deploy a package to PC, SCCM client finds two DPs (DP1 & DP2). I've checked log files...
DP1 is on the same subnet that client, but SCCM client downloads packages from DP2, but DP2 is different subnet.
With SCCM 2007, this was not by this way....SCCM client download packages from local DP (if was posible..)

In CM2012, client content location is defined with two catagories like preferred distribution point and fallback distribution point. These gets listed by MP based on the Boundary configuration and the package deployment methods. If package deployed to look
only preferred distribution points, then that particular preferred (a boundary mapped )DP only listed by MP.
More information of these preferred vs fallback is explained in below article..
http://sccmguru.wordpress.com/2012/05/08/how-preferred-distribution-points-and-fallback-is-working-in-configuration-manager-2012/
Based on your question above, I believe the boundary configuration is not mapped to the DP and could be the case here. Thanks,
Thanks SRee

Client not receiving the software update FROM SCCM 2012 R2

We have SCCM 2012 R2 installed and configured for SUP.and i have synchonice the SUP with WSUS server in the same which is there in the same machine.
Now i can able to deploy the software update from SCCM 2012 R2 without any erro to the windows 7clients, but client side when i check there is no update installed in the clients , but seems there is no error in the client logs

Hi,
I'd start with running a "Software Updates Scan Cycle" from the configuration manager control panel applet and check the log file Windowsupdate.log, WUAhandler.log.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Lync 2013 x64 silent client deployment via SCCM 2012 SP1

Greetings everyone!
I ran into a problem with Lync 2013 x64 silent deployment.
I need to provide every workstation with Lync 2013 client, so i decided to use deployment via SCCM 2012 sp1.
I created 2 msp files with OCT, one based on x86 Office 2013 Proplus, and other based on x64 Office 2013 Proplus.
Added them as applications to sccm software library.
Deployment of Lync 2013 x86 application was a success with over than 80% compliance.
But all Lync 2013 x64 automatic installations finish with different errors.
I created special device collection for workstations with office 2010 x64 and 2013 x64, because i can't install other architecture products once it has x64 product installed.
My membership query-rules for this collection:
Office 2013 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90150000-0011-0000-1000-0000000FF1CE}"
Office 2010 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90140000-0011-0000-1000-0000000FF1CE}"
My application deployment type points to setup.exe in office 2013 x64 installation folder, where i created msp file in updates folder via OCT and edited config.xml file in proplus.ww folder.
So my installation program looks like this setup.exe /adminfile updates\1lync.msp /config proplus.ww\config.xml
The same configuration works with Lync 2013 x86 deployment, except other setup folders.
When i try running installation program setup.exe with /adminfile and /config parameters locally, it installs successfully without errors or warnings.
I'm trying to find out problem source, does anyone have ideas what I am doing wrong?
Also i'm trying to reduce office 2013 installation folder size, what subfolders are necessary for Office 2013 proplus installation (still installing only lync with common files and tools)? Because now 3.5 GB package is quite hard to distribute to sccm secondary
sites with deployment point.
Thanks in advance.

Hi,
Here are some tips and tricks for your reference.
Tips and Tricks: Deploying Lync 2013 client using SCCM 2012 | Lync 2013 Client Customization for SCCM 2012 Deployment Package
http://zahirshahblog.com/2014/01/08/tips-and-tricks-deploying-lync-2013-client-using-sccm-2012-lync-2013-client-customization-for-sccm-2012-deployment-package/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Creating Software Update Packages - Best Practice?

I am setting up our SCCM 2012 R2 environment to begin using it for Windows Updates, however I'm not sure 100% the best method of setting it up.
Currently my plan is to break out the deployment packages by OS, but I read\told that I should avoid creating to many dynamic deployment packages, as every time it changes all the computers will re-scan that package. So What I want to do is create
various packages for OS and years, so I would have a package that contains all updates for Windows 7, older then January 31, 2013 (assuming the package doesn't have 1000+ updates), and are not superseded\Expired. Then I would create Packages for the 2014
monthly updates each month, then at the end 2014, combine them all in 1 package, and restart the process for 2015. Is this a sound plan or is there a better course of action?
If this the best practice method, is there any way to automatically create these packages? I tried the Automatic Deployment Rules, but I can not set a Year of release, only the a time frame of the release,(older then 9 Months), unless I am missing
something. The only way I can see doing this is going into All Software Updates, and filtering on my requirements, and then manually creating the package, but this would less desirable, as after each year I would like to remove the superseded and expired
without having to recreate the package.
Mark.

First, please learn what the different objects are -- not trying to be rude, just stating that if you don't do this, you will have fundamental issues. Packages are effectively meaningless when it comes to deploying updates. Packages are simply a way of grouping
the binary files so they can be distributed to DPs and in-turn made available to clients. The package an update is in is irrelevant. Also, you do not "deploy" update packages and packages are not scanned by clients. The terminology is very important because
there are implications that go along with it).
What you are actually talking about above are software update groups. These are separate and distinct objects from update packages. Software Update groups group updates (not the update binaries) into logical groups that can be in-turn deployed or used for
compliance reporting.
Thus, you have two different containers that you need to be concerned about, update packages and update groups. As mentioned, the update package an update is in is pretty meaningless as long as the update is in a package that is also available to the clients
that need it. Thus, the best way (IMO) to organize packages is by calendar period. Yearly or semi-annually usually works well. This is done more less to avoid putting all the updates into a single package that could get corrupted or will be difficult to deploy
to new DPs.
As for update groups, IMO, the best way is to create a new group every month for each class of products. This typically equates to one for servers, one for workstations, and one for Office every month. Then at the end of every year (or some other timeframe),
rolling these monthly updates into a larger update group. Keep in mind that a single update group can have no more than 1,000 updates in it though. (There is no explicit limit on packages at all except see my comments above about not wanting one huge package
for all updates.)
Initially populating packages (like 2009, 2010, 2011, etc) is a manual process as is populating the update groups. From then on, you can use an ADR (or really three: one for workstations, one for servers, and one for Office) that runs every month, scans
for updates released in the past month, and creates a new update group.
Depending upon your update process, you may have to go back and add additional deployments to each update group also, but that won't take too long. Also, always QC your update groups created by an ADR. You don't want IE11 slipping through if it will break
your main LOB application.
Jason | http://blog.configmgrftw.com

Why distribute Software Update Packages to DP's?

I recently integrated WSUS with SCCM 2012 and deployed my first update package, I distributed it to our DP's at each of our facilities and then deployed the package. I am seeing results but it looks like all my clients are going directly to the Active
SUP for the updates instead of grabbing them from their DP's (which is causing my admins to flip over bandwidth usage). If the clients can only grab the updates from the SUP itself what is the point of distributing the software update package to them?
Is this things running as intended or should they be looking to their DP's for this? I have already investigated the option of setting up secondary sites and creating downstream SUP's but I am seeing conflicting forum posts mentioning that the DP's should
handle to update downloads so I don't want to commit to reorganizing our SCCM infrastructure when there is a simpler solution to this.

Yes the SUP was previously the Upstream server for our stand alone WSUS environment, when we integrated WSUS with SCCM we cleared the GPO directing PC's where to get updates from so that it would not interfere with the default client policies I have set.
Interesting point about the DP on the SUP, it does have a DP role assigned as it was the DP for our corporate office. I know the boundaries are configured correctly because my software packages are downloaded by the clients from their local DP's, I even double
checked this to make sure they were not assigned to this DP for some reason. We have the CAS set as the fallback point as well so I don't think that is why either. Our CAS has a DP role and could serve as this for our corporate office, would it be worth a
shot to clear the DP role from the SUP server and see if this reassigns the WUA managed server for the clients?
<![LOG[Enabling WUA Managed server policy to use server: http://NAME OF SUP.DOMAIN.LOCAL:8530]LOG]!><time="08:36:20.522+360" date="02-26-2014" component="WUAHandler" context="" type="1" thread="3924" file="sourcemanager.cpp:938">
That is an excerpt from the WUAHandler.log on one of the clients at a one of our facilities, would this be the correct place to see where it is downloading the update from? My network admin originally tipped me off to this when he was noticing high bandwidth
utilization from our facilities and traced the packets out to our SUP. I edited out the name of the SUP but I know this is the assigned SUP for my Primary site.

Distribute Customer Updates in SCCM 2012 (CU's) using a Task Sequence

I want to utilize a Task Sequence to Distribute Customer Updates to SCCM 2012 Clients. I currently have 2 collections for pre-CU 4 clients, one for 32 Bit Clients (x86) , one for 64 Bit Clients (x64). I have a package pertinent to each collection
which I use to distribute the updates.
However, instead of segregating them by collection, I would like to have one big collection, and have the Task Sequence sort out which package should load on which collection.
I've tried using the RUN COMMAND LINE, and INSTALL PACKAGE options to no avail. Is there a way to utilize a Task Sequence for this undertaking, or should I just continue the way I'm currently doing it.
Thanks ,
Dan

You can set Collection Variables for the two collections, then add running condition in the Task Sequence Steps for corresponding collections.
Juke Chou
TechNet Community Support

Cumulative Update 3 client update install failed with code 1642

We have SCCM 2012 R2 and recently updated to CU3
Existing client is version 5.00.7958.1000
Pushing update package created during CU3 update failing on some computers
I am trying to update some of laptops using CU3 x86 update and getting following errors
Script for Package:ABC00126, Program: Cumulative update 3 - x86 client update install failed with exit code 1642
I have reviewed many forms but couldn't find relevant.
Update works on about 70% on machines with same image but failed on rest with same 1642 error
Same issues occurs applying client on during TSequence on some of machines.
It is very inconsistent,
Any help would be greatly apprciated
Thanks
RJ
RJ09

I verified package does copied over in ccmcache folder.
Also try to run update package using pstools, got error same as Torsten mentioned.
Here are logs from client.
Checking content location C:\Windows\ccmcache\gt for use
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Successfully selected content location C:\Windows\ccmcache\gt
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Executing program as a script execmgr
13/01/2015 6:56:04 PM 2588 (0x0A1C)
Found executable file msiexec.exe with complete path C:\Windows\system32\msiexec.exe
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Successfully prepared command line "C:\Windows\system32\msiexec.exe" /p configmgr2012ac-r2-kb2994331-i386.msp /L*v C:\Windows\TEMP\configmgr2012ac-r2-kb2994331-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Command line = "C:\Windows\system32\msiexec.exe" /p configmgr2012ac-r2-kb2994331-i386.msp /L*v C:\Windows\TEMP\configmgr2012ac-r2-kb2994331-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous, Working Directory = C:\Windows\ccmcache\gt\
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Created Process for the passed command line
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
AdvertisementId = "ABC212D1";
ClientID = "GUID:f298da2e-dfd1-428e-8b3c-b03602f95719";
CommandLine = "\"C:\\Windows\\system32\\msiexec.exe\" /p configmgr2012ac-r2-kb2994331-i386.msp /L*v C:\\Windows\\TEMP\\configmgr2012ac-r2-kb2994331-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous";
DateTime = "20150114005604.541000+000";
MachineName = "DH-07";
PackageName = "ABC00126";
ProcessID = 3496;
ProgramName = "Cumulative update 3 - x86 client update install";
SiteCode = "abc";
ThreadID = 2588;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\Windows\\ccmcache\\gt\\";
execmgr
13/01/2015 6:56:04 PM 2588 (0x0A1C)
Raised Program Started Event for Ad:ABC212D1, Package:ABC00126, Program: Cumulative update 3 - x86 client update install
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="ABC00126",ProgramID="Cumulative update 3 - x86 client update install", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="ABC00126",ProgramID="Cumulative update 3 - x86 client update install", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
MTC task with id {8EB498C5-71D5-4933-BA80-6EEB8E189F98}, changed state from 4 to 5
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Program exit code 1642 execmgr
13/01/2015 6:56:04 PM 2784 (0x0AE0)
Could some please review and advise..
Thanks
RJ09

Windows 8.1 will not get Forefront Client Updates from WSUS

Recently I noticed that my Windows 8.1 clients were not getting updates from WSUS 3.2. After some searching I found it was an issue with HTTPS and the solution was to disable HTTPS or enable TLS. So I enabled TLS on the Server 2008 R2 WSUS server
and that fixed the issue with my 8.1 clients not getting updates except for Forefront Endpoint Protection 2010. My SCCM server deploys the client fine but it is version 2.1 and normally the client and definition updates come from WSUS with the
latest client version being 4.5. However, my Windows 8.1 machines will not get the client updates even though they are automatically approved for all machines.
I am just wondering what else I can check or change to make sure my Windows 8.1 clients get the Forefront client updates as they should?? I am wondering if I manually install the 4.1 client update if it will take the client updates after that.
I only have about eight Windows 8.1 machines so if I have to do that by hand for now then I will and I think my organization will be moving to Server 2012 and SCCM 2012 this summer sometime.

I reread your post and have another suggestion. If your SCCM 2007 server is still deploying the old 2.1 FEP client version, then you should install the latest anti-malware platform update for the SCCM server so you can deploy it from there instead of WSUS:
http://support.microsoft.com/kb/2952678
http://blogs.msdn.com/b/minfangl/archive/2013/08/15/guidance-on-install-anti-malware-platform-updates-for-fep-2010-su1-and-scep-2012-sp1.aspx
Also, you may be affected by this:
"Anti-malware platform updates on MU will use special detection logic and applicability rules to make the anti-malware platform updates available only on computers with previous N-2 anti-malware platforms installed. For example, on April 8<sup>th</sup>,
anti-malware platform of version 4.5.x will be released on MU, and it will only be offered to computers where anti-malware platform version 4.3.x or 4.4.x is available. If a computer has FEP or SCEP client with version 4.1.x, it has to be upgraded to version
4.3.x first, then to the latest version (4.5.x). If a computer has FEP or SCEP client with version older than 4.1.x, because of the same N-2 rule, it has to be upgraded to 4.1.x first, then to 4.3.x, and then to the latest version (4.5.x). Required updates
will be kept on MU to ensure that this upgrade process is available for computers running older versions of the Microsoft anti-malware platform."
http://blogs.technet.com/b/configmgrteam/archive/2014/03/27/anti-malware-platform-updates-for-endpoint-protection-will-be-released-to-mu.aspx

Deploy Java and Oracle updates using SCCM 2007 Software Updates

Hi Team,
I am using SCCM 2007 to deploy software updates on all my servers. Now i want deploy updates fro third party tools like Adobe, Java etc..Please suggest me on how to deploy these updates using SCCM.
I am looking for other simple solution than SCUP 2011. Please suggest.
Thanks
Siva

Hi,
SCUP 2011 would be the way to do it or a package/program. There are commercial software solutions that plugins to configuration Manager like Secunia
http://secunia.com/vulnerability_scanning/corporate/sc2012_plugin/ ,Solarwinds
http://www.solarwinds.com/patch-manager.aspx and Shavlik
http://www.shavlik.com/products/scupdates/ that offer a subscription of updates for these products for a cost of course.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Remote Desktop Client Update 3.7.0

I'm using a 2012 MacBook Pro with OS X Mountain Lion 10.8.5. When I visited the Mac App Store today, there was an Apple software update available for download - Remote Desktop Client Update 3.7.0. I don't own or use Apple Remote Desktop and to my knowledge, it's not installed on my mac in any way. Has this happened to any other non-users of Apple Remote Desktop?

The Apple Remote Desktop CLIENT is part of the operating system and present on every mac. If you haven't engaged Remote Management in the System Preferences/Sharing pane, it can't be used. But it CAN be updated! Hence the message.
The ARD administrative package used to control a client is not on every mac and is something that must be purchased. But to control other computers the client software must be there, so Apple just has it as part of the OS in case you ever need it.

Client Update Packages (SCCM CUs)

Similar Messages

Maybe you are looking for