Today, when you install the CM Console, the PowerShell module will be placed under the %CMInstallDirectory%\AdminConsole\Bin\ConfigurationManager.psd1

This makes sense given where the user is choosing to install the console, and that's fine. But placing it here off the beaten path means that it is not importable using PowerShell's module autodiscovery features. For instance, if a module is found in any of the standard user or system paths (or registered under the $ENV:PsModulePath) the user can easily import the module without having to specify the full path, a big user quality of life win. This is the way that SQL Server handles their modules, and they are the golden child, beloved by all PowerShell nerdoes like me.

So, my suggestion is to continue placing it where it is today, and also register the path using the standard mechanism, excerpted below.

https://msdn.microsoft.com/en-us/library/dd878350(v=vs.85).aspx

In SCCM 2007 we utilized package with multiple programs. One install program that was silent to be used in a task sequence. One with interaction (appdeploy toolkit e.g.) for distribution to existing PCs. Once we moved to application we created multiple deployment methods with the appropiate filters. However if one of the deployment methods does contain the 'allow interact' option the application can not be added to a task sequence even though there are deployment methods that would apply to a OSD situation were it would pick the non-interactive one. Would like to see a logic check in the task sequence editor or the option to force a specific deployment method(s).

When the user received the 'Software changes must be applied to your computer' there are two radio options:
'Apply all required changes now (recommended)'
'Apply all required changes outside my business hours'

There is also an checkbox that say 'Restart my computer automatically if needed'. However, this checkbox is disabled when the first radio option is selected. I would ask that it remains enabled for both options. We are trying to train users to take an active role in installing updates according to their own schedule. The reboot process has become a large portion of the update process. So if they take the 'install now' option when they go to lunch or a meeting they come back to a machine that needs 5-10 minutes worth of reboot to finish. It would be preferable to give them the option to reboot as well so they come back to a fully patched machine ready for use.

When you only use ConfigMgr to install updates, the date on the Windows Update control panel applet often reflects something that is really inaccurate as ConfigMgr doesn't update it. This often leads to a very negative reaction of "I thought those darn ConfigMgr admins were updating our workstations and servers!?!" And then we have to explain that we are, but that date doesn't get changed.

Can we please just ensure that when Software Update Management installs any updates, the Windows Update control panel applet gets set to the current date?

I stole the screenshots from this thread: https://social.technet.microsoft.com/Forums/en-US/b33dd5b2-64b3-476d-8fc5-232cbafced47/sccm-updates-are-installed-but-windows-update-status-wrong?forum=ConfigMgrCompliance

And I stole the idea of submitting the feedback from this thread:

https://social.technet.microsoft.com/Forums/en-US/812eef00-bdef-4c8d-a8ea-1d4424f1941e/software-updates-does-not-change-last-update-install-date-in-windows-update?forum=ConfigMgrCompliance

Thank you for your help!

When I started working with SCCM years ago I was told that you're not really an SCCM admin until you accidently deployed MS Office to the whole company. Through my years of working with SCCM I've seen many people update a collection not knowing that there was a mandatory deployment attached which resulted in the deployment getting sent to systems that were not intended.
I would like to see a check/notification box added when a query based collection is updated that reminds you of the required deployments attached. This message will only show if an unexpired required advertisement is still set. This would ensure that admins understand the potential impact of their collection change.

Software normalization built into SCCM reporting. An integrated solution to manage software inventory, software intelligence and license management. As a SCCM administrator it has been difficult to provide accurate reporting on installed software packages without purchasing third party normalization tools like BDNA or SNOW. Software normalization capabilities would be a great addition to SCCM.
1. Software Recognition Service that recognizes software requiring a license.
2. Software title normalization.
3. Ability to import all owned software licenses and then compare against what is actually installed.
4. Ability to recognize when software has been removed or upgraded. Example: if Office 2010 has been upgraded to Office 2013, will SCCM reporting show both Office 2010 and 2013 installed, same with Visio?
5. Ability to detect software version information. Example: SQL Server 2014 version, is it Standard or Enterprise?
System Center Configuration Manager has a good inventory agent, normalization would make it great!
Thank you and Regards

I would like to thank Microsoft to allow their customers to share new and innovative ideas and I would like to present mine from my experience as Desktop Management Engineer in my company.
Initially we were using a comparative tool called LANDesk Management Suite and on the beginning of this year we have moved to SCCM 1511, since then I had received many complains about remote control comparing to the past experience.
I really like SCCM as a whole and I think it is really good tool and really nice features and constant updates, but not the remote control.
I have known many companies using SCCM with 3rd party remote tool like DreamWare, SolarWinds, LANDesk,…etc. because of the SCCM remote limited options and performance issues.
The below is the list of some really good features to have in SCCM remote control tool:
1- Ability to remote control the machine with permission even if the no user is logged in. sometime this option is really required when the client has a problem with logging in to the machine like if the machine is out of domain, the Helpdesk guys are not able to control the machine and rejoin it again considering unattended remote control option is not allowed because it is without permission for security reasons.
2- Ability to configure remote control or remote view access for SCCM users in which some users will have view access only and others to have control access only to the same machine.
3- Multiple Screens switching in which the user can move between screens to make it easier in supporting the client.
4- Screen Quality control when remote control the machine. For some site the speed of the network is very slow, the remote control will be very slow and will cost time to service the client.
5- Option to ask for Reboot.
6- File Transfer loading bar to show the progress of copying a file and remaining time.
7- Current logged in user name to the remote machine and the IP Address as well while remoting a machine and it is good to place them on the top of the remote control green bar.
8- Having a web console for remote control will increase the likability of SCCM.
Finally it really be appreciated to consider the above which will improve user experience and will make customers to like and to use SCCM remote control more than any other tool.

For complex software deployments, we regularly use Task Sequences to sequence reboots and installation orders, as well as containing logic on the various steps to only run when certain conditions are met. This allows for much more complex and flexible deployments.

The problem is, if a reboot step is initiated, no Task Sequence progress is displayed to the user to let them know that installations are taking place behind the scenes. To them, the reboot occurs and then they return to the CTRL+AT+DEL screen.

It would be great if a new class of Task Sequence could be created that would show progress to the interactive user after a reboot. Call these "Application Task Sequences"