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

Similar Messages

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

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/

SCCM 2012R2 multihomed client, Wake on LAN unreliable

We are seeing a strange problem related to Wake on LAN on client computers with both wired and wireless network interfaces.
All clients are initially imported with the wired MAC address, booted via PXE and image installed. The client then boots up and contacts SCCM. End users then typically use them via wireless and one would expect SCCM to "learn" both the IP/MAC configuration
of the wired and the wireless interfaces. (These networks use separate vlans and IP subnets)
SCCM and our routers are configured for directed broadcasts.
Network sniffing has confirmed that for these clients, SCCM attempts to send the broadcast to the wifi subnets instead of the wired subnets. All directed broadcasts sent to wired subnets have been confirmed to arrive as expected and those clients wake up
as expected.
However, over time the wired network interface appears to be dropped by SCCM, causing Wake on LAN to fail because it obviously won't work using the IP/MAC information for the wireless adapter. When checking the client properties in Configuration Manager,
some clients are incorrectly listed without a wired network interface.
How should we proceed to troubleshoot this issue? Any pointers/ideas/suggestions are welcome.

"one would expect SCCM to "learn" both the IP/MAC configuration of the wired and the wireless interfaces."
Why would one "expect" this?
ConfigMgr uses heartbeat discovery to discover IP address information. What is your heartbeat discovery interval set to?
Jason | http://blog.configmgrftw.com | @jasonsandys

SCCM 2012 Automatic Client Approvial Risks?

Hi,
Currently we have some clients that are in a not trusted forest. And we have the Client Approval method set to “Automatically approve computers in trusted domains (recommended)”.
The problem is clients will eventually appear in this folder and unapproved. I can see there is an option to set this to “Automatically approve all computers (not recommended)”. Which we are considering changing this to.
These clients we are building btw via a OSD task sequence that joins the remote domain when finished.
Can somebody please elaborate a bit more on why this is not recommended and what the risks of turning this on?
Thanks,
Ward

Well, do you 'trust' the machines? If you do, go a head and auto approve all... It's a good thing that if you for example have 10 domains and your ConfigMgr main site is on one of them that's the 'main' domain and you want to configure all of those domains,
they're all differently configured, they all have a bit different apps installed on their computers and so on. In this scenario, if you have collections that use queries that populate the collection with like all the workstations, meaning all the workstations
in the whole ConfigMgr site, you may have some problems at the client end, IF you don't know exactly what you want to do with all the machines. Now if this scenario exists and you do not configure the auto approve all machines, the computers will show up in
your collection but they are not managed yet, so if there's a deployment targeted to that collection, it will not start with those machines that are not approved.

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.

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.

Have delay to deliver updates to client in sccm 2012r2

Hi
that's a few month that I'm working with sccm 2012r2 in order to keep my organization updated and patched .but the problem is after discovering a new computer and triggering that computer to get updates from SUP It doesn't show any updates in software center
,in fact after 2 hours those updates appear and start installing .I searched the internet a lot .all settings are right according to microsoft documents .recently I doubt to my automatic deployment rules .those rules are working fine but I think the delay
could be because of the number of my rules ,I have 35 automatic deployment rules that start at the same time .this is the screen shot of the rules . is this configuration suitable ?
if the number of update rule is too much what should to do with maximum number of updates in each rule(1000 update per each rule) ?
thanks a million

Yes. That's a lot of update rules (as a side question, why are being so granular with them?); however, it has nothing to do with what you've described. Update Rules have nothing to do with enforcing updates on clients. ADRs merely create (or update) update
groups, update packages, and update deployments. Update deployments perform the actual work of enforcing updates on clients. Also, there's no 1,000 updates per rule requirement. Update groups however are limited to 1,000 updates. Still, none of this truly
has anything to do with what you've described.
ConfigMgr is not an instant gratification system -- it is an enterprise client management tool and certain actions and activities take time to happen. Can you please walk us through *exactly* what you're doing when installing a new system including the timing
and what your expectations are?
Jason | http://blog.configmgrftw.com | @jasonsandys
thank you very much .
but my expectation is when I install a new os ,Sccm detect that as soon as possible and give client the updates asap again even when I use the Action tab in configuration manager Item in control panel.
of course it detect my new client but it takes time to give them updates (about 2 hours).Before I was using wsus ,updates was sent to client and was installed immediately after client detection(of course using Check for Update in control panel).
I want to decrease my rules .but whats the best solution and categorization ?now I have 4449 Updates in sccm database .
in Update classification I just selected critical,security,rullup,update.
I would be glad if you masters give me a helpful solution .
thanks

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

SCCM 2012R2 Client on workgroup machine

Installing the SCCM client on a workgroup Server installed with Server 2012 is not working ok. I can only see 2 actions in the Config manager control panel item. This means the policies can not be downloaded.
I have configured a boundary for the network range that the client is in.
In SCCM console the client registers as active.
From the agent in control panel the agent
can find the correct SCCM site "the client is already assigned to the site that was found"
I installed the client manually using commandline:
ccmsetup.exe /mp:sccm_mp.domain.local SMSSITECODE=XXX FSP=sccm_mp.domain.local DNSSUFFIX=domain.local
Ony possible issues i see:
Locationservices.log:
- Unable to retrieve AD site membership
- Failed to retrieve DNS service record using _mssms_mp_xxx._tcp.domain.local
It keeps on trying to retreive MP from DNS and keeps failing.
Also in the eventlog:
Warning EventID 1014:"Name resolution for the name _mssms_mp_xxx._tcp.domain.LOCAL timed out after none of the configured DNS servers responded."
Not sure if this is really an issue, but could well be. The DNS record does exist and
can be resolved from the host by using nslookup.
The ClientLocation.log says:
- Workgroup client is in Intranet
- Assigned MP changed from <sccmserver.domain.local> to <sccmserver.domain.local> (shows correct name)
Also reinstalled the client several times, doesn't help. Domain Joined systems work fine with SCCM.

Have you Approved the client in the ConfigMgr console? By default, only systems within the forest of the site server are approved automatically.
Jason | http://blog.configmgrftw.com | @jasonsandys
You are 100% correct. missed that :-(
Its working now.

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)

Forced restart on Upgrades to Maverick

It's just some question on how to ensure my computer working reliably. When upgrading to maverick from Montain lion, the screen seems to freeze on "less than one minute" for some 10 mins. So I took it as a freeze and force restart... And then it turned out that all my personal settings are lost. Glad I had backup with time machine, so I restored my settings and home folder with time machine and the system works normally.
Now the thing is, when I use some apps like Papers 3. The on pdf search is no longer displaying well. And sometimes when I use terminal, it prompted me to install the command-line developer tool which I have done so in mountain lion. I'm not sure whether they are simply some glitches after normal upgrade or because of my forced restart.
I mean, is there any method on mac OS to check the integrity and reliability of my OS? Or should I format and reinstall my system to ensure it?

It's just some question on how to ensure my computer working reliably. When upgrading to maverick from Montain lion, the screen seems to freeze on "less than one minute" for some 10 mins. So I took it as a freeze and force restart... And then it turned out that all my personal settings are lost. Glad I had backup with time machine, so I restored my settings and home folder with time machine and the system works normally.
Now the thing is, when I use some apps like Papers 3. The on pdf search is no longer displaying well. And sometimes when I use terminal, it prompted me to install the command-line developer tool which I have done so in mountain lion. I'm not sure whether they are simply some glitches after normal upgrade or because of my forced restart.
I mean, is there any method on mac OS to check the integrity and reliability of my OS? Or should I format and reinstall my system to ensure it?

Linux SCCM 2012R2 Client - inventorydataitem.xml file growth

I'm running the 5.00.7958.1024 Linux SCCM 2012 R2 client on a RHEL 6.5 x86_64 system. It appears that the file:
/opt/microsoft/configmgr/root/ccm/policy/inventorydataitem.xml
grows without being truncated over time. I attempted to search for information related to this file and came up empty. Can it be removed periodically without borking the whole client? If so, will the client recreate it on the next inventory run? Can
a log rotation management scheme be used with it? Based on the timestamps/contents of the file, it appears that either might work... But, I don't see a recommended practice for managing this particular file.
Thanks.
Jeffrey

This is almost certainly a known problem that is fixed in the upcoming CU3 update to ConfigMgr client for Linux/UNIX. CU3 for Linux/UNIX got delayed a bit for technical reasons, but we expect to have it available on the Microsoft download center
right at the end of October or very early in November. If you install this new version of the client, we think it will shrink the inventorydataitem.xml file back down to a more reasonable size.
Michael Kelley, Lead Program Manager, Open Source Technology Center

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

Similar Messages

Maybe you are looking for