1FstYota

Wow talk about frustrating, the sccmuser account doesn't work now again. Run the ADR rule and same 403 error.

Yea, done many reboots saw that patch installed it and it didn't work. So I might be a bit confused or it might be the new CU1 update for 2012 R2 but I was always able to use my AD account to run the console and create the ADR and run it with no issues, so I deciced to run it as my SCCMuser just now and it worked. Under accounts I see the sccmuser has various functions tied to it and my normal AD account says not configured.

Hello, this recently started happen since the 11th a few days after CU1 update I believe. The ADR when downloading definition updates fails with Failed to download the update form internet. Error=403. The wsussync log shows it syncs fine. Just when the ADR runs and gets that error. Using MS message analyzer it shows that there is a 403 error while connecting to "wsus.ds.download.windowsupdate.com". SCCM was set with proxy configuration, then I turned it off verified it had straight out connectivity and it worked one time and after that it started to do the same, now it does this with or without proxy. Any help would be greatly appreciated.

Ok, problem solved. The servers had updated to .net 4.5.1. Even after rolling back to .net 4.0 it didn't work but after running the windows updates again and it installed the .net 4.0 updates the patch was able to install. Now gotta finish the Sp1 update. Well both primaries are having the same issue, ms patches is starting to tick me off.

Sorry, can you tell me which specific log I'm looking for? I looked at the CBS log and windowsupdate log. Under event properties it has a errorcode of 2149842967. In CBS folder both CheckSUR, and CheckSUR.persis.log shows no errors detected.

Hello, doing the SP1 upgrade, and I'm stuck at the WMF 3.0 part, it would install but upon reboot it would fail and revert changes. I can't get any further untill I solve this issue, so far .net 4.0 is install and powershell ISE was not but added and still no go. Any help would be great.

Well I was able to fix the issue "The process is not in background processing mode" by doing the suggested fixes, but it stopped working again this morning. Then after checking logs and reboots and everything seemed fine, then it dawned on me that our local policy applies the proxy back to IE9 connection settings after unchecking it, bam it was all good to go with no issues. So hope this helps someone form pulling their hair out.