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).

It would be nice to have the ability to conditionally pre-cache all packages in Upgrade TS and not only OS Upgrade step.

To describe it in more details, in current design we are able to pre-cache only OS Upgrade step to computers based on conditions. This is not enough for companies with 20+ languages as best approach is to create en-us core image and then apply MUI on top of that. Doing this will cause system to report as e.g. de-de so we would need to download and distribute to 150+ DPs all supported Upgrade packages instead of distributing only en-us Upgrade package and them distribute much smaller MUIs.

As SCCM is currently supporting conditional pre-download in OS upgrade step so the function is already there, extending it to whole Upgrade TS will be a great benefit as we can then also put there e.g. Driver packs => so client will download only applicable driver pack, en-us Upgrade and appropriate MUI from one larger Upgrade TS. Right now we have to have 50 different Upgrade TSs to be able to support all languages in our company.

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!

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.

Please make an easy way to query Driver Versions of all drivers on a system from SCCM Hardware inventory without creating a custom MOF or looking at registry files? I found a forum thread on TechNet a few years old that said Microsoft said that using WMI class win32_pnpsigneddriver was unreliable and is why it was not available in SCCM hardware inventory and they were considering removing the class entirely. However the class remains in win 10 and is still the only way to query driver version using a script. It would be really useful to be able to have SCCM compare driver versions on a system verses the drivers in a sccm driver pack so we can ensure systems are compliant.

Scenario: You create a Boot Media or Prestaged Media. Current behaviour is that as long as the boot image version from creation date matches the version inside the infrastructure everything is fine. System is starting Windows PE and executes the Task Sequence. If you add for example a new driver now to the boot image the new version causes Configuration Manager to download the boot image inside Windows PE and another restart into the updated version of the boot image. In case of a Prestaged Media scenario this painful, as UEFI systems might no longer work.

Possible SOLUTION: Add a variable SMSTSPreventRedownloadBootImage and SMSTSBootImageMinumVersion to stich with the boot image currently used.

Purpose of SMSTSBootImageMinumVersion (enforce only if present and boot image ID matches Boot Image ID used in Task Sequence) would be to have still version control.
I think this would enable additional deployment options

When a package fails to distribute to a DP, the only option right now is to 'Redistribute' the package to the DP. This is inefficient for large packages since 'Redistribute' transfers all package content to the DP even if some content may have already been transferred prior to the failure. For large packages, this not only takes a lot of time but consumes more network bandwidth than necessary.

When a package is 'added' to the DP, only the missing files are copied to the DP however there is no way to simulate an 'add' action from the UI.

Having the ability to trigger an 'add' action for a Package/DP will help remediate content transfer issues a lot quicker as it will only require copying the content that's actually missing on the DP instead of 'redistributing' all content.

Add an optional option to provide new source location path for each package, application, ... when importing a Task Sequence that has been exported with content and references. Imagine you have 2 ConfigMgr environment a Test and a Production environment completely isolated from each other and you want an easy way to sync. A cool thing would be to only export "Metadata" of the Task Sequence and all References (Applications, Packages, ...). At the target site you have the same folder structure for content source for example \\sccmsources\share\Applications,\\sccmsources\share\Packages, ... and so on. If you start the import, you will be asked the same way like now for location. The wizard will detect that the folder structure is identical and ask if you want to use it or otherwise change it manually for each reference if needed. Currently the only option is to import everything and change the folder structure in a scripted way, which causes all references to regenerate Hash code, adding a new revision which can be avoided easily.

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"