nullpoynter

I just updated to 1511 last week and I'm getting the same error on the primary site server. I also installed the console on another server (not related to SCCM) and got the same error. So, is this a known issue? The console seems to work okay besides the critical error logged under the application log.

Well, if I disable the last three steps of my task sequence (Prepare Configuration Manager Client, Prepare OS, and Capture the Reference Machine) the task sequence doesn't leave the C:\SMSTSLog directory or the smsbootsect.bak file behind. I've also tried running the task sequence with these three steps disabled again and using ISO capture media. The ISO capture leaves this folder and file behind as well. What about these three steps would cause this issue to happen?

I have what seems like a stupid question. After running a build and capture task sequence, the C:\SMSTSLog directory and C:\smsbootsect.bak are left behind on the image captured? I don't ever remember seeing these on the previous (and first) image I built. Do the existence of these on the root C: drive signify that an error has occurred? Thanks...

I have a question for all of the SCCM 2012 SUP masters out there First of all, let me describe my current setup. I just setup SCCM 2012 R2 CU1 for the first time, so I'm definitely a SCCM noob. I have followed the recommendations according to an excellent book I found on Amazon. Basically, I have software update groups setup for each of the previous years that I could possible need updates from (i.e. 2008, 2009, 2010, 2011, 2012, etc.). Along with each of these groups I have a deployment package for each year that contains these updates. Starting in 2014, I created a 2014-1 group to contain the updates for the first 6 months. My automatic deployment rule (which just ran for the first time this month) is setup to use a 2014-2 package for the next 6 months so as to avoid the potential 1000 update limit. Now for my question. My ADR is setup to run on the second Tuesday of the month and retrieve any updates that have been release or revised in the last month. Several updates that were originally released (not expired or superseded) on the second Tuesday of June had a revision, there was one from May, etc. My ADR has grabbed these updates and downloaded them to the 2014-2 package. So, now not only do these updates exist in the 2014-1 package, but they've been downloaded again to the 2014-2 package. How do you handle this type of duplication? Am I just over-thinking this? I would appreciate any help or suggestions.