Right now, the automatic Client upgrade scheduled Task is not aware of any running installations. So if appenforce.log shows a running Installation and at the same time the randomly timed scheduled tasks kicks in, the Installation cannot finish without error and will randomly leave the Installation or the SCCM Client itself in a unhealthy state. A reinstallation is the only way out.

Repro steps
- Activate automatic Client Upgrade in Hierarchy settings
- Exclude some test clients from automatic client upgrade
- Create an Application with a deploymenttype using a custom script
- As the script, use a batch file pinging localhost with parameter -t so that the dummy installation will newer end. That gives you time for the test.
- Deploy the app to the excluded test clients
- Let the installation run
- Set the clients to not be excluded from automatic client upgrade, so that the scheduled task for the upgrade will be created locally
- run the scheduled task manually to simulate the client upgrade
- you will see some errors in appenforce.log telling you that the installation could not be finished without error

Expected behaviour:
- The automatic client upgrade function should not run if an installation is allready running
- instead of scheduling a scheduled task you should schedule a package install, so that the sccm client can only start the package/upgrade if no other installation is running

I am looking the issue/design from SMS 2003 to SCCM 2012 version. I am not sure if any purpose must be behind of this design of collection default query select * from sms_r_system.
Whenever a user create the query based device collection, if there is any modification in the query
He/she shouldn’t remove the entire query and apply OK.
If user applies ok, its automatically select * from sms_r_system query will enabled, it will targed to all system which is “All system” as limiting collection.
It has serious issue in most the companies, deployment is performing by L1 or L2 engineers.
It is nowhere document in the MS TechNet or in Blog.
I would strongly recommend to have some kind of mechanism to avoid this kind of changes in upcoming released.
You can reach me on email : kannancs@hotmail.com if you need any clarification.

SCCM 2005 was very accessible to system administrators who are blind. However, Versions after this from 2008 on are not usable. This has resulted in any system administrator who is blind who requires access to SCCM to perform his or her duties to find alternative responsibilities. Up to 2013 I happily worked as a system administrator. I loved this part of the IT industry. However, because so much of my job revolved around using SCCM I had no choice but to leave and refocus my efferts somewhere else. I ask Microsoft to redouble your committment to accessibility to include improving access to SCCM. There are over a hundred blind system administrators around the world. We work like everyone else to pay bills, keep a roof over our heads and provide for our children. Please keep this in mind when considering the priority of this request. In Visual studio, at the top of the properties list you will find attributes for improving / addingaccessibility to controls. Microsoft have developed this brilliant technology so that accessibility is easily added. All I am asking is that you use the functions you have developed. Thanks for reading.

Replace the OSD Boot Image "Enable CMD Support (testing only)" feature with something that is more robust, helpful, and useful outside of testing like the F8 Troubleshooting Environment Steroids (F8TES).

Info: Display full name of task sequence and its ID
Info: Display full name of TS Deployment and its ID
Info: Display full name and type of error step
Info: Display error code
Info: (Stretch Goal) Display useful error message for top 10 errors

Button: “Open Command Prompt”
- Launches the command prompt
- Defaults to Insert instead of Overwrite (it currently defaults to overwrite in the WinPE phase)

Button: “Open SMSTS.log”
- Launches CMTrace and opens SMSTS.log
- Knows where the current log file is so you don't need to know where it bounces around to
- Includes CMTrace.exe in the task sequence environment so it persists in target OS phase
- Stretch goal: just include CMTrace in the client package so it always gets installed to windows\system32\ during client setup (in OSD and standard client install)

Button: “Show TS Variables”
- Simple out-gridview style view of variable name and value
- Allows filtering of built-in, non-built-in variables
- Hides the built-in variables for storing passwords, other long/garbage-looking variables

Buttons: "Retry Step" & "Skip Step and Continue"
- Stretch goal... Maybe a v2 goal.
- Would it try to download policy again and resume from step with same name?
- Would it check if the content has been updated and redownload if needed?

Feature: When launched, the built-in error message box should stop being modal. Mouse support in RDP to VM scenario is bad... can't move modal box out of the way to see the step name, and don’t want it blocking this UI. Bring modal back up when closing.

Feature: The task sequence reboot countdown should be paused while F8TS is displayed so it doesn’t reboot while troubleshooting.

Feature: Allow setting a password so that it can be lightly controlled (it would be just as insecure as a Network Access Account but better than security-through-obscurity).

Feature: Have the F8 Command line be a Boot Image feature, but have this F8 Troubleshooting Environment Steroids thing be a Task Sequence Deployment feature so it could be more selectively enabled.

Feature: Maybe for version 3: Include the ability to easily integrate and launch DaRT. Needs easy way to integrate into WinPE, target OS.

Feature: Maybe for version 4: Is there a way to enable the Remote Control features on the client during target OS phase so you can remote in without DaRT.