When running a task sequence to deploy a 1703 based image, the second part of the task sequence: "Setup Operating System" does not display.

The screen saying "Just a moment..." is displayed instead of the SCCM task sequence screen, meaning you cannot see the progress.

If the machine is left, it does actually complete the steps, but it would be nice to see the SCCM screen once again!

We have the need to run a command line in the task sequence and leverage a secret value TS variable ADMACCTPW set with the local admin account password. Example Run Command Line "net user admin %ADMACCTPW%
The issue is in the SMSTS.log the variables are all expanded like the ProgramName = 'net user admin mynewadminpassword' InstallSoftware 7/1/2016 12:58:58 PM 4468 (0x1174)

Thereby exposing the secret value TS variable

When using Peer Cache, if the Peer is no longer online or not available for connect there is a 7.5 min delay to fail to the next system. if the first connection was a validation of the systems online status ("Are you there") the need for this delay would not be needed. the requesting client could attempt to make connection (presumably when it's doing the resource checks for Battery, CPU load, Disk IO and available connections) and if the connection times out (very short reasonable time) it moves to the next peer on the list.

Currently, anytime you run the upgrade OS step, it set the client into provisioning mode, despite the options you're choosing. Could this be changed, that if you pick "Compatibility scan without upgrade" it would NOT put the client into provisioning mode.

I've had users reboot the computer when the scan was running (silently in the background), and then the client was in provisioning mode.

There are many ways to expire standalone media but most involve using a date stamp to compare with system time to determine if the sequence is still supported. Changing the system time circumvents this process. With Windows Servicing, it will be critical that an administrator be able to limit installation at or near the end of a support cycle. A supported process for expiring media programmatically ensures new devices aren't installed outside of a supported servicing window.

Make everything more secure by requiring Multi-Factor auth for console access. Bonus: make it work over the internet securely.

The "More Details" right-click function in the Asset Details view under each monitored deployment currently does not allow you to highlight and copy any of the text. This might sometimes be handy while sending deployment information to colleagues or building hand-made lists of computers with a specific error status, etc.

Deadline randomization is currently in place for software updates only. We were hoping that would expand to both applications and packages as well. This would reduce the demand for applications and package installations in a shared environment (virtual). We currently have this available with software updates. We'd like to see the scope expanded to include package and applications.

To reduce potential for failures due to low battery situations and to minimize the ConfigMgr client's impact to system battery life, introduce a check for certain client actions to allow them to be delayed or bypassed when the system is found to be running on battery or running critically low on battery:
+ Software distribution
+ Compliance settings
+ Inventory
+ Anti-malware scans

Enable appropriate distribution point functions on Cloud DPs like Group Relationships, Content, Boundary Groups, Schedule, Pull Distribution Point, and Rate Limits.

of course, PXE and Multicast would not be appropriate Cloud DP functions.

The "Delete each collection member from the database" tick box clickable field extends to immediately above the "OK" button, making it extremely easy to select on accident. The field should only exist within the space of the box itself, or slightly outside of it.

Add the ability to cache Applications via WinPE PeerCaching. This would allow admins to fully pre-populate a location with content: This would be huge, and a game changer for a lot of organizations that don't own a 3rd party solution.

The WinPE PeerCaching, as it is now, works great, for the content it can do. Adding Applications would make this a complete solution, instead of a stop gap to a 3rd party solution.

Cumulative Updates for Windows Server 2016 sync with a maximum run time of 10 minutes every month. The same cumulative update for Windows 10 1607 is set to 60 minutes.

Could you set the Server 2016 to 60 minutes instead of 10? This update never completes in less that 30 or 45 minutes.

Admins should be able to disable or remove the link to Application Catalog, from an end user viewpoint, we are not using the App Catalog, just Software Center. Since we’re using a 3rd party Shopping instance as well, it would be good to have a configurable option to hide Application Catalogue.

better control weather I want a site to fallback to primary or not.
real bandwith limitation instead of current posibility. Control priority of metadata

Please allow Client Notification actions to be triggered from the Devices node. You currently can only do this from Device Collections.