wanderer Posted July 1, 2014 Report post Posted July 1, 2014 I'm running SCCM 2012 SP1 on Server 2008 r2 in a lab. Everything else seems to be working OK except that the "Automatic Client Upgrade" settings are all greyed out. I've seen a post which suggests logging on to the console as the user who originally installed SCCM on the server but doing so makes no difference. I'm sure that's the right user - I only use one for these purposes and I've got it confirmed in my installation notes. Does anyone have any ideas? I don't want to start from scratch so I'm wondering how important this setting is, as presumably if I needed to upgrade the client I could create a package to do so? I'm more worried that this might indicate a more serious problem with the server. Thanks in advance for any suggestions, Stephen Quote Share this post Link to post Share on other sites More sharing options...
Jorgen Nilsson Posted July 1, 2014 Report post Posted July 1, 2014 Hi, I have only seen it in the scenario where you don't have permissions to all instances. http://ccmexec.com/2013/03/configmgr-2012-automatic-client-upgrade-grayed-out/ Have you verified that? Regards,Jörgen Quote Share this post Link to post Share on other sites More sharing options...
wanderer Posted July 1, 2014 Report post Posted July 1, 2014 Jorgen, I've been looking at this and the only account that has "Security Scope" set to "All" is an account I created at the time of installation, this was used for the SQL server database installation and for Client Push, network discovery etc. When I try and logon with this (domain) account it fails (I must have written the password down incorrectly - it's two years ago). I think I've read that SCCM and SQL store their passwords not sync them to AD so I'm worried that if I reset the AD password everything will break. Of course this is my fault but I'm wondering if someone has come across this before, is there any info on where I'll have to store the new password in SCCM and SQL if I reset it? Many thanks, Stephen Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted July 1, 2014 Report post Posted July 1, 2014 The site server itself has also all the rights. I backdoor I sometimes use is starting the console by using PSEXEC. Quote Share this post Link to post Share on other sites More sharing options...
wanderer Posted July 2, 2014 Report post Posted July 2, 2014 Peter, Thanks for the suggestion, I think I must be missing something. If I start the console using psexec from a remote PC running as System I get an error that the console can't connect to the site (Account has insufficient permissions). If I start it as my normal admin user then the option to turn on automatic client updates is still greyed out. Thanks, Stephen Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted July 2, 2014 Report post Posted July 2, 2014 Should have mentioned that you have to perform that action on the site server itself (as that's the account with the rights). Quote Share this post Link to post Share on other sites More sharing options...