Client upgrade package

Hello,
I did a fresh install of SCCM2012 R2, for some reason I do not see CM Client Upgrade package in the Packages view, but see it in the Monitoring\Content Status with status that package was distributed to DP. Why? How can I recreate it?

That's a hidden package that won't show in the packages view.
If you need to recreate it, which is not really the case I think, you can create an empty file named
client.acu in the inboxes\hman.box folder at the top-level site. This will cause a new package to be created.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

Configuration Manager client upgrade package failing to download to DPs

Hello,
I am receiving the following error in distmgr.log "Failed to get RDC signature path for for package SF100004 version 1. Error = 2"
"SF100004" is the "Configuration Manager client upgrade package"
Is there a way to rebuild/repair this package?

Yes, I did find out how to fix the problem. I had to use a power shell script to call WMI on the site server to manually force a refresh of the package having problems.
$SiteCode = "SF1"
$PackageID = "SF100004"
$distpoints = Get-WmiObject -Namespace "root\SMS\Site_$($SiteCode)" -Query "Select * From SMS_DistributionPoint WHERE PackageID='$PackageID'"
foreach ($dp in $distpoints)
$dp.RefreshNow = $true
$dp.Put()

Multiple duplicate Configuration Manager Client (Upgrade) Packages

We have 14x Configuration Manager Client Package / Configuration Manager Client Upgrade Packages in our SCCM2012R2cu1 environment.
We tried deleting all of the packages that were not linked to deployments/task sequences, but a few days later these were re-created with new PackageIDs.
Any ideas what could be causing this? are there some logs we should be checking?
http://oi61.tinypic.com/5nx4.jpg
Thanks!

FROM hman.log:
CheckSQLServiceRestart : SQL Service hasn't been restart since last time we check, skip it.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:54 AM   1936 (0x0790)
Handle auto-upgrade client configuration changes   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:54 AM   1936 (0x0790)
Update auto-upgrade client configurations   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:54 AM   1936 (0x0790)
INFO: Full client package id XX1001EB exists.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Client upgrade package id XX1001EC exists and upgrade package flag is set to 1.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Client upgrade program Configuration Manager Client Upgrade Program in package id XX1001EC exists and its currently disabled.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Client upgrade advertisement id XX1203B8 exists for package XX1001EC and program Configuration Manager Client Upgrade Program. Deployment is targeted to collection SMS00001.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM
1936 (0x0790)
INFO: All client auto upgrade related objects exists. No objects are to be created.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
INFO: Successfully added client upgrade packages XX1001EC and XX1001EB to all 31 distribution points from site XX1.   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)
Wait for site control changes for maximum 3600 seconds...   SMS_HIERARCHY_MANAGER   7/07/2014 6:03:55 AM   1936 (0x0790)

Client upgrade package deployment error (yet successfull)

Hello,
I've been deploying my-self created package of a upgrade installation file I have found in the installation directory of SCCM 2012.
I have run a test deployment on a test collection on my two colleagues and the deployment showed 100% compilance with no error and installation went great.
So, I thought that it's ok to deploy it on more populated collection (Office computers only) and see what happens.
What actually happened is that after one day later there was 0% compilance on that deployment and every installation seem to have failed with ID 10021 stating "Program failed (unexpected restart)" so I assumed the installation failed and the upgrade
wasn't installed. Yet, I have checked some of the workstations and the client version number and it matched the R2 version. (which we are using)
Can anyone explain this to me?
The file used for the test upgrade and the pilot upgrade is located here:
...\ConfigMgr\ClientUpgrade\ccmsetup.exe (1,577 KB)
it does the trick when launched manualy and on a small collection, but on the large one, it "fails" the way I have described above.
I don't get it...
The IT guys from LukOIL

the answer from the below thread will answer your question
http://social.technet.microsoft.com/Forums/systemcenter/en-US/0e8749a3-9c2d-4a7d-ae16-80474912bd8f/trying-to-deploy-sccm-client-upgrade?forum=configmgrswdist
Kindly mark as answer/Vote as helpful if a reply from anybody helped you in this forum. Delphin
Now I understand!
Thank you all for your time!
The IT guys from LukOIL

ARD 3.1 client upgrade issues

It seems that upgrading clients from the Admin console after installing the 3.1 upgrade is hit or miss. I am unable to upgrade more than 4 or 5 clients at a time. In some cases it won't even upgrade one. The error I get is when it's copying the client upgrade package to the clients selected and at some point during the copy they all fail at the same time. I am able to upgrade each of these failed machines one at a time however.
Anyone else having this issue?

3.1 fixes some significant issues with Intel-based Macs, among other things, so those who run ARD on an Intel-based Mac want to update to see if it will fix the problems many have been experiencing. It also fixes (or purports to fix) some other significant bugs. So many people have been anxiously awaiting this update.

Client Upgrade tool - run-time error on client?

Hello,
Iu2019m facing an issue sending out Client Upgrade Packages. The package arrives on the client, but it the install process gets stuck immediately with the Run-time error 35603.
Have you got this error below u2013 or do you have any idea what I should look for?
BR MC

Hi,
in case you are running 5.0 SP9 the note 1106147 should help.
Regards,
Wolfhard

Redistribute Configuration Manger Upgrade Package

Hi Guys,
Just some questions regarding this post (http://social.technet.microsoft.com/Forums/en-US/11df0f63-d146-434d-91f3-c4e826fee92c/redistribute-configuration-manager-client-upgrade-package-xxx00003?forum=configmanagermigration)
We are seeing a "Failed to update content properties" on all our DP's for the configuration manager upgrade package (XXX00002)
With the below PS snip:
Am I correct in assuming that this command will redistribute the upgrade package to all DP's?
"$SiteCode" should be the Primary server's sitecode even if we have a Central administration site in our enviroment?
Does anyone know what distribution priority the upgrade package is set to?
$SiteCode = "XXX"
$PackageID = "XXX00003"
     $distpoints = Get-WmiObject
-Namespace "root\SMS\Site_$($SiteCode)"
-Query "Select * From SMS_DistributionPoint WHERE PackageID='$PackageID'"
        foreach
($dp in $distpoints)
                $dp.RefreshNow
= $true
                $dp.Put()
Thanks in advance,
J.

Hi Torsten,
Thanks for your reply.
So run the Powershell command on CAS and use the sitecode for CAS here:
$SiteCode = "XXX"
And run your query to see the priority of the upgrade package?
Am I understanding you correctly?

Upgrade packages(mups) are not sent to ALL mobile clients

Upgrade packages are not sent to all mobile clients even though there are
subscriptions assigned. There are 3 sites(A,B,C) with these
subscriptions. Only one site(A) receives the package. The other two
sites(B and C) doesnt receive the package and their outbound queue doesnt
show the messages.
The subscriptions were earlier removed for these sites (B and C) and then
added back.
Generated all the bdocs in smoggen, gnrwb and sent the package again but in vain.

the generation did the trick. the queue has been stopped in between and that is the reason why the packages were not sent after the bdocs were generated.

Config Manager 2012 client upgrade (via package with batch commands)

Hello all,
I would like to kindly ask for your help with my question regarding a SCCM 2012 R2 client upgrade (from RTM to R2)
Recently, we have upgraded from RTM version of SCCM2012 to R2 (with the PXE hotfix applied)
During the process, I have choose not to upgrade clients when the SP1 was applied and go straight for the R2, which is not a problem I believe.
My question is regarding the pre-created packages, that are showing up in the console. I believe, that they are the easiest way to upgrade clients via packages in SCCM. (we can't push the installation due network policy)
This hotfix is stored here: \\"FQDN_site_server"\SMS_TSP\hotfix\KB2905002\Client\x64 (in case of x64 version, x86 is the same but x86 in the end)
The executed file from this path is this with this command following:
msiexec.exe /p configmgr2012ac-r2-kb2905002-x64.msp /L*v %TEMP%\configmgr2012ac-r2-kb2905002-x64.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous
Anyway, when we install the clients when we deploy it for the first on a machine, that has no client or we reinstall it, we do it with help of this batch command:
set curdir=%~dp0
%curdir%ccmsetup.exe SMSSITECODE=TSP /NoCRLCheck /UsePKIcert /forceinstall SMSMP=HTTPS://CML.LTSPRAGUE.CZ CCMHOSTNAME=CML.LTSPRAGUE.CZ
I just need to know, if I can use the prepared package from the console in our case and if it will keep the settings when the package is deployed.
I belive I have found a similar questin here on the forums:
http://social.technet.microsoft.com/Forums/en-US/c9b40687-1843-44c7-b61b-fd26d53ab90b/cumulative-update-3-and-agent-upgrade?forum=configmanagerdeployment
The second answer might the answer I'm looking for, but can you explain that to me like I'm five years old? :)
Please, let me know.
The IT guys from LukOIL

I'm not sure, because of my short time at the company, but there are historical security reasons for setting the push installation off.
Second reason are strict firewall rules used here. SCCM Agent may contact site server through HTTPS - that is a one way communication, so push installation isn't possible.
Don't mix "client push" and "automatic client update". See
http://blogs.technet.com/b/configmgr_geek_speak/archive/2013/09/09/using-configuration-manager-automatic-client-upgrade-to-upgrade-to-the-latest-system-center-endpoint-protection-client.aspx for further details. (And yes, the article talks about SCEP, but
it also tells details about the entire process)
Torsten Meringer | http://www.mssccmfaq.de
Thank you for the article and your, but I find it easier to deploy packages right now.
I have found out, that there is a folder named "ClientUpgrade" in ConfigMgr installation folder.
I used this and made a package out of it. Deployment went fine as well as the installation of the upgrade for the client, but there is a problem now, that I don't see any software in the "Software Center" in "Available Software" - and there should be, since
I have may SW pointed to me and the list was populated before I have done the upgrade to the new version.
This may be a simple problem, but I really don't know what's wrong.
The IT guys from LukOIL

Windows 8.1 official offline upgrade package & GPO question related to Metro & UAC

Hello!
I am testing pre-deployment of Windows 8.1 in our 2008R2 domain. So far only my workstation is upgraded to win8x64 (from win7x64) and I am assessing if all of our LOB aps and servers will work fine with it. A few questions
1. We use workstations coming with OEM win8 license (all currently running win7 downgrade). I noticed that oficially there is no win8.1 offline upgrade package! Does that mean that Microsoft officially wants people to sing into Windows Store with a Microsoft
account to perform online upgrade with administrative privileges? That's pretty awkward ...
I figured that I could use win 8.1 installer ISO/UFD that I created in past (for home computer actually), but am not sure if that works out with our win8 OEM license keys tied to BIOS/UEFI on each desktop computer.
Was actually expecting an 8.1 Service Pack package that I could publish to WSUS, so it could take care of upgrade on win8 computers, but there is no such thing ... and no official package for 8.1 offline deployment either ... weird ...
Currently I am actually about to upgrade my own/test workstation to 8.1 (from 8.0, using Windows Store online), then sysprep it and create a reference WIM image and see if I can deploy 8.1 thick image (with all updates and company apps installed) this way
via WDS. anybody tested if it works this way? any gotchas?
2. win8 GPOs
Can somebody enlighten me where in Group Policies I can find a setting to re-assign ALL file/media extensions (e.g. jpg, tiff, png, bmp, mp4, WMV, etc.) back to Desktop applications instead of the horrible Metro UI equivalents?
We are actually about to bypass Metro UI completely on each computer so it boots straight to desktop and all file upon double-click must open an application within Desktop (no Metro UI for end users).
I know how to do this manually one by one via Group Preferences, but am asking if there is some specific GPO ADMX setting that would replace Metro UI apps with Desktop application in any and all file associations.
Personally I see no point in using the clunky Metro UI without a touchscreen.
3. is UAC enabled required for Windows Store to work?
Seems like it needs at least the Low security setting, so the Windows Store and Metro UI stays operational. no workaround for that for disabled UAC environment?
Just asking, it's not a big deal, people can learn to live with UAC, but am curious if that's by design.
Thanks for answers!

Hi,
1. For upgrading to Win8.1, please refer the following link:
http://windows.microsoft.com/en-in/windows-8/update-from-windows-8-tutorial As I know, Win8 activated using KMS, cannot upgrade to Win8.1
2. No, there is no such GPO settings added into Admin template. You will have to work around this using GPP...
3. There is no way to bypass UAC and allow Windows Store at one time. UAC is headache since Vista times and we have to live with the Protection :) Believe me, it does good to PC safety.
Regards, Brian
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
thanks for the answers!
Yeah, UAC is a bit of a headache especially with legacy software. When deploying our Win7 domain clients however I got away by simply disabling it to make it easier for all users coming straight from XP environment.
for future win8.1 deployments however, I will set the UAC level to Low and keep it there, so modern apps and winstore stays operational if anybody wanted it or needed it. not a big deal, plus an added security layer, I agree with that.
As per default win8 file extension associations ... well, that's a bummer, and yeah, the GPP is what I had in mind to work around that manually.
I am running on upgraded win8.1 right now and so far I like it more or less in work environment, after adjustments that is :)
My only problem is related to win 8.1 clean installation and imaging and deployment however, wanted to use Lite Touch via WDS for w8.1, but problem is that I have no image of win8.1 that can activate with OEM licenses tied to BIOS.
Sysprep doesn't work on upgraded 8.1 (from 8.0), so I can't image that with generalization and on other hand the only generalized image I can take is from bare win 8.0 without the 8.1 upgrade. What I mean is that our computer vendor (HP) switched to OEM
win8 licenses tied to UEFI/BIOS (no more case stickers) and that doesn't activate when I try to clean install 8.1 even though it should, but the build ID string in BIOS must be changed ... need to open a case with HP to work it out, I am sure it's still possible
to achieve even without volume licensing.
We use a Basic Infrastructure model so far with retail+OEM keys (no KMS so far but it's in plans if Office deployment plans get approved by CFO). I thought for 8.1 actually it was a good idea to implement Standardized Infrastructure with thick images, as
manual upgrade to win 8.1 from win 8.0 is painful.

SSIS Oracle 11g 64 bit client upgrade Issue

After the oracle client upgrade from 10g to 11g, the ssis jobs are getting failed for the BadImageFormatException. Attempt to load Oracle client libraries threw This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed.
But the same package with same system requirements and same sql agent configuration is wroking fine in DIT. Please find below the system configuration in both environment.
DIT
Oracle Client - Oracle 11g 64 bit , Microsoft SQL Server - 32 and 64bit, Windows machine - 64 bt SP4, In job there is no configuration in command line to run in 32 bit mode since we are using the are using the .Net Provider/OracleClient Data Provider connection manager to the database .
UAT :
Oracle Client - Oracle 11g 64 bit , Microsoft SQL Server - 32 and 64bit, Windows machine - 64 bt SP4, In job there is no configuration in command line to run in 32 bit mode
In UAT, Everything looks as DIT but the job is not working fine in DIT.
I have gone through all the thread related to 32 64 bit, .Net Oracle client provide but i haven't found any solution for this problem.
Can you please tell me the missed out configuration in DIT and UAT? the exact problem for this issue ? what is the oracle components required for this connection? Its urgent.
What is missing in the oracle end?
Thanks
Satheesh

32 bit apps will need 32 bit Oracle client software installed.
Hope it helps,
Greg

Where can i find Client software package for BOE XI 3.1

Hi
We have BOE Xi 3.1 on a server . I am looking for the client software package for BOE XI 3.1 so that it could be installed on my laptop. I looked in Service. sap.com/SWDC /Business objects portfolio and could not find the same. All i am finding in there is SBOP INTGR for SAP and i am assuming that this is the software for SAP integration kit.
Could you please point me to exact location within SWDC where i can find the Client software package for BOEXI 3.1.
Thanks & Regards
HGS

Did you download the BOEXI3.1 Server Client Tools when you installed the application? If you have, you can simply run the same install package, and select "client" tools during the installation.
If you don't have the install package, you can download it from the SAP web site. You must have a login account in order to do so. The following are the steps...
-- Go to: http://service.sap.com
-- Click on SAP Support Portal
-- Enter your S-number and password
-- You will be redirected to the SAP Support Portal (NEVER ever bookmark this URL because it changes all the time, you should bookmark the first URL I gave you)
-- Click on "Downloads" tab from the top menu bar
-- Click on "BusinessObjects Downloads" from the secondary menu bar
-- In the "Installations and Upgrades" section on the main pane, click on "click here"
-- Click on "SBOP ENTERPRISE" from the list
-- Click on "BOBJ ENTERPRISE XI 3.1" from the list
-- Click on "Installation" from the list
-- Click on "WINDOWS" (or other OS) from the list
-- Select "BOE XI 3.1 (SERVER/CLIENT TOOLS) WIN 1 of 3, 2 of 3, and 3 of 3"
Hope this helps.

Trying to deploy SCCM Client upgrade...

A few days ago I upgraded our SCCM 2007 R2 Site Server with SP2. I did this in preparation for Windows 7 support and deployment. Anyhow, I decided to release the client upgrade via software distribution using the same package that I include with my image deployment (data source is \\server\sms_001\client )
Yesterday, I created an advertisement to distribute the SCCM client upgrade to my entire network but today System Center Console is reporting that out of 1148, 996 have not yet started, 0 succeeded, and 149 have failed. We're a school so most of our computers are off. The issue is that of the computers that are on 149 have failed with 0 reporting a success....or so they say.
I checked a few of my clients and the ccmsetup.log indicates that installation has in fact succeeded. However, what the "status of a specific advertisement" report is telling me is that the client failed with the "last status message name" column indicating "Program Failed (unexpected restart)". It shows the same thing for all clients that have reported a failure.
The software package program function is configured to run the following and I'm not using any client options: "CCMSETUP.EXE /noservice SMSSITECODE=AUTO"
Any ideas why the client appears to have been upgraded but reporting a failure?
Below is the execmgr.log:
Policy arrived for parent package 00100006 program Advanced Client Silent Upgrade execmgr 12/22/2009 8:09:49 PM 3784 (0x0EC8)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramOfferReceivedEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223010949.649000+000";
MachineName = "ADMIN-OFF-TSEC";
ProcessID = 1976;
SiteCode = "001";
ThreadID = 3784;
execmgr 12/22/2009 8:09:49 PM 3784 (0x0EC8)
Requesting content from CAS for package 00100006 version 4 execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Successfully created a content request handle {36479D3C-24C9-4844-BED1-2AB2B0BDD0F1} for the package 00100006 version 4 execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Program Advanced Client Silent Upgrade change to state STATE_ADVANCED_DOWNLOAD content in progress execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from NotExist to AdvancedDownload execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Mandatory execution requested for program Advanced Client Silent Upgrade and advertisement 00120025 execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Creating mandatory request for advert 00120025, program Advanced Client Silent Upgrade, package 00100006 execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistWaitingContentEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223010950.555000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
PackageVersion = "4";
ProcessID = 1976;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 1348;
execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Successfully raised SoftDistWaitingContentEvent event for program Advanced Client Silent Upgrade execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from WaitingDependency to WaitingContent execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Content is available for program Advanced Client Silent Upgrade. execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
CExecutionRequest::Overriding Service Windows as per policy. execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from WaitingContent to NotifyExecution execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Notify user mandatory program Advanced Client Silent Upgrade is about to run execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Execution Manager timer has been fired. execmgr 12/22/2009 8:15:25 PM 1736 (0x06C8)
Executing program CCMSETUP.EXE /noservice SMSSITECODE=AUTO in Admin context execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from Running to NotifyExecution execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Checking content location C:\WINDOWS\system32\CCM\Cache\00100006.4.System for use execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Successfully selected content location C:\WINDOWS\system32\CCM\Cache\00100006.4.System execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Executing program as a script execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ccmsetup.exe" /noservice SMSSITECODE=AUTO execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Command line = "C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ccmsetup.exe" /noservice SMSSITECODE=AUTO, Working Directory = C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Created Process for the passed command line execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\Cache\\00100006.4.System\\ccmsetup.exe\" /noservice SMSSITECODE=AUTO";
DateTime = "20091223011525.457000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
ProcessID = 1976;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 3500;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\WINDOWS\\system32\\CCM\\Cache\\00100006.4.System\\";
execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Raised Program Started Event for Ad:00120025, Package:00100006, Program: Advanced Client Silent Upgrade execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Request in running or report status found for program Advanced Client Silent Upgrade package 00100006 execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Service stopped while program Advanced Client Silent Upgrade is running execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
OpenProcess failed for process 1396, error 80070057 execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Can not continue monitoring the program after service restart because the process exited. Assume failed execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Looking for MIF file to get program status execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramUnexpectedRebootEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223011911.783000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
ProcessID = 3636;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 1700;
execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Raised Program Unexpected Reboot Event for Ad:00120025, Package:00100006, Program: Advanced Client Silent Upgrade execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)

This KB article covers the upgrade of the client via hotfixes:
http://support.microsoft.com/kb/2477182
An important thing to note is that the Program needs the following set:
After Running: Program Restarts Computer; this is needed to ensure that any status MIF files are collected after a restart of the client service (ccmexec.exe). No actual restart of the computer should occur.
This enables the SCCM client to detect that it re-started and to process the MIF files for status messages.
Installing the following updates one at a time normally is sucessful:
KB2761938
KB2516517
KB2815223
Other updates such as KB2276865 fail with the Unexpected Reboot Event error (possibly because the MIF is not written correctly) but it has been superseeded by KB2815223 wich is OK.

SP1 Client Upgrade Issue

Hello, i am having an issue trying to upgrade out SCCM Clients from RTM to SP1 versions. I have upgraded the server already sucessfully. I setup a software distribution package with the new client source files, however, when i deploy to clients i get a error message on 98% of them (a handful of clients worked sucessfully): Status Mesasage 10021: Program failed (unexpected restart). My command line is just the default from the definition file (except added a FSP): CCMSETUP.EXE /noservice SMSSITECODE=AUTO FSP:<myserverhere>. I can't figure out what is causing the client upgrade to fail, anyone have any ideas?
Thanks!

That topic was already covered in the forums. See these threads for detailed explanations:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3424297&SiteID=17
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2965261&SiteID=17

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.

Client upgrade package

Similar Messages

Maybe you are looking for