Clarification of "Automatic Client Upgrade" in Hierarchy Settings

Hello all, I am looking for clarification of "Automatic Client Upgrade" in Hierarchy Settings. I am SCCM 2012 R2 CU1. It says the latest version is "5.00.7958.1000" My CU1 version is actually "5.00.7958.1203".
From reading various other users forum questions regarding this issue I have learned that this upgrade will only work for "Major versions". That should be why I don't see the same versions. My question relates possibly more generally.
I am in the process of building and configuring the SCCM 2012 R2 CU1 (site code: IT1) environment. I have a running production SCCM 2007 R3 (site code: IT0) environment, with a different side code. I am not ready for these older SCCM 2007
R3 clients to be upgraded to SCCM 2012 R2 CU1 as I am still testing and finalizing things.
If I enable the "Automatic Client Upgrade" in Hierarchy Settings for 2012 R2 CU1, could someone better explain which clients this affects?
Will it upgrade my old SCCM 2007 R3 clients to SCCM 2012 R2?
Will it upgrade anything outside of the SCCM 2012 site IT1 (if I had two SCCM 2012 sites with different names)?
Will it upgrade an SCCM 2012 client to SCCM 2012 R2?
Will it upgrade an SCCM 2012 SP1 CUx client to SCCM 2012 R2?
Will it upgrade an SCCM 2012 R2 client to SCCM 2012 R2 CU1? (from what I have read, NO)
Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

Will it upgrade my old SCCM 2007 R3 clients to SCCM 2012 R2?
No
Will it upgrade anything outside of the SCCM 2012 site IT1 (if I had two SCCM 2012 sites with different names)?
Since we cannot have two sites with the same name in a hierarchy I assume these are two different hierarchies. The setting is for a hierarchy wide and works by creating a scheduled task for client to get the package via policies. Though I have not tried
this but logically it should not.
Will it upgrade an SCCM 2012 client to SCCM 2012 R2?
On the same hierarchy,Yes!
Will it upgrade an SCCM 2012 SP1 CUx client to SCCM 2012 R2?
On the same hierarchy,Yes.
Will it upgrade an SCCM 2012 R2 client to SCCM 2012 R2 CU1? (from what I have read, NO)
You are correct. CUs are not a major release and a separate client package is created and you need to manually target them to the clients to get it upgraded.
Umair Khan | http://blogs.technet.com/umairkhan

Similar Messages

SCCM 2012R2 Automatic Client Upgrade - mandatory / forced restart?

We've upgraded our SCCM environment from 2012 sp1 to 2012R2.
If I check the box under site settings (Hierarchy settings) for "Upgrade client automatically when new client updates are available." What is the installation / restart behavior? Will it only occur during a maintenance window if one
exists and will it force a restart?
# When I wrote this script only God and I knew what I was doing. # Now, only God Knows!

Automatic upgrade is a great feature, but not much in this World is perfect.
Clients in slow or unreliable boundaries, are not upgraded automatically.
Here is a brief overview over what happens when you enable this feature:
http://www.ronnipedersen.com/2014/08/sccm-2012-how-does-automatic-client-upgrade-work/
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

Automate Client upgrade from 7.0 to 7.5

How can you automate the ZAM Client upgrade from 7.0 to 7.5? If I run the setup.exe for 7.5 it generates an error saying a previous version was detected, please uninstall it first. I would have thought there would be some kind of upgrade switch.
Thanks
Lenny

lennyd,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Exclude Servers for Automatic Client Deployment/Upgrade

We have 2012 SP1 and are planning the move to R2. We have automatic client upgrade enabled in the site settings. Is there a way to exclude Server OS client upgrades while this feature is enabled? In my reading there are times when the client
upgrade will reboot the systems at will due to a pre-requisite installing such as a security update.
We cannot have the servers rebooting at will. It will be difficult enough to have workstations do it.
Thank you

No. There is no way of excluding specific systems from the automatic client upgrade. It's all or nothing.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

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

SP1 to R2 Client Upgrade via SUP

Hi,
Currently planning an upgrade to R2. We currently only deploy clients via SUP (SP1) then update clients to the CU by using SCUP. A WMI filter then disables Windows Updates for clients where the installed version of the client is >5. This
is to prevent auto updates interfering with software updates delivered by CM.
I am planning to roll out the R2 upgrade also via SUP by amending the WMI filter so that it looks for clients less than the R2 version, which will re-enable automatic updates and pull down the new client.
I am aware that I could also use the automatic client upgrade option, but where servers have maintenance windows I could see this never running during a MW.
Any comments/thoughts on this approach?
Thanks

Hi,
Could this maintenance windows work fine when you deploy other updates to the same clients?
Please examine MaintenanceCoordinator.log, ScanAgent.log and ServiceWindowManager.log on the client.
Best Regards,
Joyce Li
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.
Yes, they will, because other updates are deployed with a deadline. The automatic update method uses a scheduled task which may not tie in with the MW, and so will never run.

Automatic Site Wide Client Upgrade To R2

I know if I run the wizard manually to I can select "Always install the client software" to upgrade the client from SP1 to R2 but if I turn on site wide push will existing SP1 clients upgrade to R2?

Hi,
See the automatic upgrade section here for how to enable this:
http://technet.microsoft.com/en-us/library/gg712298.aspx
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

SCCM client upgrade

Hi,
What are the previous versions of SCCM 2007 client will upgrade by SCCM 2012 R2 client? I mean, if my environment having different versions of SCCM 2007 client installed on the machines and I want to install now SCCM 2012 R2 client by using client push method
to these machines, will it upgrade or not?
Thank you,
RR

To upgrade SCCM Client automatic, In the Configuration Manager 2012 Console, browse to the Administration workspace, click on Site Configuration, Sites and select your Configuration Manager Site. Next you need to select Hierarchy Settings and browse to the
Client Installation Settings tab and select the option “Upgrade client automatically when new client updates are available”.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Client Upgrade issue in Oracle Lite Database 10g 10.3.0.3.0

Hi all,
Details: My Environment is Oracle Database 11g R1(11.1.0.6.0) With Oracle Lite Database 10g R3(10.3.0.3.0) on Windows 2003 Server R2 SP2.
Recently i have upgrade my oracle lite database from 10.3.0.2.0 to 10.3.0.3.0 and also applied recent opatch (p12812978_103030_Generic.zip). Upgrade and installation of opatch got successfully completed. When i tried the client synchornization for the very first time (FCS and Data Download) FCS and Data Download got Successfully completed but the problem is usually Once the FCS and Data Download Got Completed , Screen goto webtogo home page but in my case i am getting a screen name called "client upgrade" with options yes or no if choose yes it prompting please wait screen nearly for 1 hours i am not getting any response from the screen. if choose no simply it goto my webtogo home page. Please Note before choosing the yes option i have checked what version i am currently having it show 10.3.0.3 i don't know why it asking for the client upgrade. Please Advice me on this how to avoid this screen (Client Upgrade).
Thanks
Shan

Hi,
i am not upgrading the existing environment of Oracle Lite Client i am creating a new environment which doesn't have the Oracle Lite Client. In the document itself they have mentioned like this "These steps assume that you have a 10g Release 1 or 2 Branch Office environment already configured and synchronized. If you do not have this environment currently configured, you do not need to upgrade." To be Clear What i am doing is with help Oracle Lite Branch Office i will be downloading a user from Mobile Server for that i have to do the following
1.FCS(Fresh Client Setup for that i have to run the setup.exe which is coming for Oracle Lite Branch Office) and
2.Data download (Data will be get download from Mobile Server in the form of odb),
3. Usually Once the FCS and Data Download got completed, the screen will goto the webtogo home there i can see my branch offlice applications.
4. But in my case i am getting prompted by screen and the screen name called "Client Upgrade" with options yes or no if i choose yes screen got hanged else if i choose no then only screen moving the webtogo home page. Say can u r having existing environment in your machine due to some reasons u have upgrade or u have installed optach on the mobile server in that case while doing the client synchronication we can do the client upgrade by running the update.exe becasue client side will having the old binary file we need to renew it.
5. But I am not upgrading the existing environment. I am creating a new environment which means i am doing a fresh client setup and synchronization for the very first time. While doing the FCS on my client side for the very first time i will be getting the latest binaries rite then why the screen is moving to client upgarde page i don't have any idea on this.
Please Advice.
Thanks
Shan

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

Semi-automatic update/upgrade; is Arch wrong distro for these boxen?

I wanted to post here a semi-automatic update/upgrade solution I--with a lot of help from someone more knowledgeable--came up with in case it might be of benefit to anyone else. It's been working pretty well for me over the course of the last couple of weeks and should aid me in becoming a better Archer. I also want to ask in this thread for confirmation on whether installing Arch on a couple of machines I have that see fairly intermittent use is inadvisable: if so, I'll look into installing some other distro. First the semi-automatic update solution.
To begin with, what do I mean by "semi-automatic?" Mainly I mean something that's only partially automatic. See, I've come to understand that automating updates/upgrades is a bad idea©™. And I think I understand why. Still, I apparently lack the discipline to be a good Archer, upgrading/updating frequently so as to conform with the philosophy. So I thought I should use my computer to help me be more disciplined: that's partly what they're for, after all, isn't it?
I decided I might make the computer help me be more disciplined, first of all, by making it issue reminders at frequent, regular intervals, that it is time to update/upgrade. Of course cron came immediatelty to mind as part of the solution, though I ended up using the remind program instead. In any case, it seemed like a solution that, not only would remind me at regular, frequent intervals would be desireable, but one that would at the same time initiate the process, would be even better. I thought it must be possible to, for example, cause a terminal to open with a message and corresponding menu that would say something like "System update/upgrade needed: proceed now? 1. Yes 2. No"
This latter would be one of the elements that makes the solution semi-automatic (as opposed to automatic). Answering 2. in that terminal would cause the terminal to simply exit. Answering 1., on the other hand, runs the command sudo pacman -Syu. There is a further level of semi-automation at this stage: you are then prompted to enter the root password before pacman -Syu will run. So, no updating/upgrading happens without input at these two stages.
I should mention as I wrap up this description of my solution that there is yet another important element to it that, while independent of it, is nonetheless related: I subscribed some weeks ago to the Arch news RSS feed. I check that daily, so an even further level of semi-automation is in play here.
This seems to me like it will be a very good solution to bringing my behavior into better conformity with the Arch philosophy. It's worked well so far. That said, I'm certainly open to criticisms. I'm also very open to any improvements that might be suggested. Without further ado, here is the script I run every other day from the remind daemon:
#!/bin/bash
PS3='Begin full system upgrade? '
options=("Yes" "No")
select opt in "${options[@]}"
do
case $opt in
"Yes")
echo "Beginning full system upgrade..."
sudo pacman -Syu
exit
"No")
exit
echo "Please choose the corresponding number"
esac
done
Now, to my question about my other machines as possible Arch install targets. The above applies to the desktop machine in my apt. which is almost always powered on and connected to the 'net: what follows applies to two different machines.
One is a laptop that I use primarily when I travel. It often sits powered off for 1-2 months between uses. The other is an alternate desktop machine in my apt. that is also infrequently used: essentially, when both the wife and I want to work on-line separately--which is not all that frequently (she prefers knitting to computing during her time at home)--it gets fired up. Again, it often sits for 1-2 months without being used.
Now, it seems to me these machines are poor targets for an Arch install because they are far more frequently off-line than on-line, powered down than powered up. Thus they are very unlikely to be updated/upgraded on any kind of regular basis, and certainly never regularly and frequently, as seems to be recommended for Arch machines.
Am I correct in assuming I should be looking for some other distro to install on these infrequently-used machines?
Thanks,
James
Last edited by jamtat (2013-02-11 22:50:09)

I like pacmatic (as suggested at https://wiki.archlinux.org/index.php/Pa … _pacmatic). What is supposed to be wrong with it?
It doesn't ignore updates, by the way. It does two things. First, it checks the news and tells you about important news items as soon as you run e.g. pacmatic -Syu. Then it runs the upgrade in the normal way. For example, a news item today concerned lvm2, dev-mapper and linux being upgraded together. It gave me the news item. Then it did the usual paman upgrade routine and upgraded everything, including those packages. Second, every time you run it, it reminds you of any *.pacnew files you haven't dealt with and asks if you want to deal with them now. At least, it asks about most. It never mentions kdmrc.pacnew for some reason.
It's just a wrapper for pacman. From the script:
Pacmatic is a pacman wrapper that takes care of menial but critial tasks.
These include
Checking the archlinux.org news
Summarizing the arch-general mailing list
Reminding if it has been a while since the last sync
Reporting pacnew files
Editing pacnew files
Personally, I've installed an alternative distro on machines which I'm not sure I will be using very regularly. (Also, I like having distinct distros just in case something goes wrong in one case - even if it is a bit of a faff sometimes.)
Last edited by cfr (2013-02-13 01:49:24)

9.2 Client Upgrade Necessary?

Hello all,
I'm working in a large group, and a decsion has been made to upgrade the SERVER from 9.0 to 9.2. Is it absoluetely necessary (from a JDBC standpoint) to upgrade the CLIENTs on all the dev machines?
In the past, the upgrades haven't mattered all that much... I just wnated to make sure.
Thanks,
Stu

My understanding is that you need to upgrade at least the version of the JDBC driver (which may or may not entail an Oracle client upgrade). The JDBC drivers are backwards compatible, but not necessarily forward compatible as I understand it.
Realistically, you probably won't have any problems running 9.0 JDBC drivers against a 9.2 database, but I tend to err on the side of paranoia.
Justin

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()

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.

Can lync client use internet proxy settings to proxy edge servers, if direct access is not reachable?

Hi everybody I am trying to Login with my lync Client out of my organization. So I am using lync as a remote user. I am in another organization, and I am using their coporate lan wired and wireless, but I cannot Login to lync in my organization.
I see that I cannot Access my edge Server on port 443 to authenticate directly, I know that Client in this organization use Internet Proxy to browse the Internet. they have a .pac in their ie Settings.
my question is; can lync Client use Internet Proxy Settings to reach the Destination? I mean the Access edge on port 443?
or it can use only Client direct Access to reach the edge Servers?
I Think that the answer is that I use tcp protocol and not http, and maybe that is the reason why I cannot use the Internet Explorer Proxy Settings to reach the Access edge Servers, different maybe is the case I Need to reach the reverse Proxy for live Meetings.
Hope my question is clear.
Thanks

Proxy settings are used to tell Internet Explorer the network address of an intermediary server (known as a proxy server) that is used between the browser and the Internet on some networks.
Lync client doesn’t use Internet Proxy Setting. You need to access the Edge service directly.
Lisa Zheng
TechNet Community Support

Clarification of "Automatic Client Upgrade" in Hierarchy Settings

Similar Messages

Maybe you are looking for