As described in Social Technet Forum the console crashes in SCCM 1710 when trying to create an Office 365 Installer when typing anything in the UNC Path.

See eventlog:
Faulting application name: Microsoft.ConfigurationManagement.exe, version: 5.1710.1010.1000, time stamp: 0x59f7248f
Faulting module name: gdiplus.dll, version: 6.3.9600.17055, time stamp: 0x53292632
Exception code: 0xc00000fd
Fault offset: 0x0003383a
Faulting process id: 0x778
Faulting application start time: 0x01d3892fc2359de8
Faulting application path: C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe
Faulting module path: C:\Windows\WinSxS\x86microsoft.windows.gdiplus6595b64144ccf1df1.1.9600.17056none_dadc5d1c5bc8ab48\gdiplus.dll
Report Id: 0e7661db-f523-11e7-80ca-00505689324d
Faulting package full name:
Faulting package-relative application ID:

I have SCCM version 1710
The console version is 5.00.8577.1100
And the site version is 5.0.8577.1000

There are a lot of common failures right at the beginning of the task sequence that cause a lot of anger. Can we please allow a retry for these three common scenarios that happen right at the start?

No Network Connection
- If you hit “Next” before the network has started… or before your network cable was plugged in, it should give you an error that you can retry after the network situation is fixed.

No Task Sequence Found
- This often comes up because there really is no task sequence targeting the device, even though you thought it should be (eg – only deploying to unknown, but this device is known).
- For bonus points: The stupid known Unknown computer objects… When this failure is seen because there is a known Unknown object, blow away the Unknown object and auto-retry.

Could Not Validate Content
- Allow the admin to distribute the content to a DP you have access to, and then try again.
- For bonus points: Improve the error dialog box so it shows you the FRIENDLY NAME of the content item or at least step. Today it is a GUID.
- For extra bonus internet points: Display the name of the Boundary Groups the client is in (and the boundaries).

This is really a pet peeve but bear with me. When I want to search Devices within Assets and Compliance section of the Admin console, a message appears that says "Configuration manager returned a large number of results. You can narrow your results by using search. Or, click here to view a maximum of 100000 results." The functionality of this is great, however the placement of it is EXACTLY where the search box was right before it appeared. More times than not, I'll try to click in the search box and end up clicking on this message instead and the console will slow down a LOT while loading up to 100000 objects into the GUI.

It would be great if this dialog/button/whatever it's called could appear somewhere else in the window instead of where I'm almost always about to click anyway.

Thank you.

Android for Work has been actively integrated in to the web Intune Portal, I have not heard when this would make its way to the Hybrid SCCM instance so wanted to push this to uservoice since this will be very helpful in all with hybrid deployments. We are primarily iOS but having this functionality could allow companies to standardize on iOS or android devices with OS 6.0 or higher to support the work profile. Utilizing Intune with SCCM allows infinite customizability and the use of dynamically changing queries, along with multiple domains in my environment is critical in order for ease of operation along with anyone else that may be built off multiple acquisitions.

The 30 Day Rollback option is available for all windows 10 users, but currently can not be automated using SCCM.

This should change, as this feature closely integrates with Microsofts testing strategy of using different branches which grow bigger in size as the rollout of a new build progresses.

When planing to integrate a similar scenario, in our case, we anticipate errors which have not been cought in testing of the previous branch and need to be able to quickly restore operations.

I am well aware that if all our applications were packaged this would not pose much of a problem but as you all know this is rarely the case.
Because of that a reinstall of the previous build (and local applications) would cause a massive loss of time (and money).

Since MS is pushing Enterprise Customers to become part of their testing chain and offers reasonable support times only with LTSB this feature - available even for home users - should be automated using SCCM.

At the moment when cmtrace is opened, it extracts the appropriate architecture version to AppData\Local\Temp<temporary file name>.tmp and executes it. Customers often put cmtrace in the system32 directory of computers to aid with troubleshooting.

With recent randsomware attacks, companies are starting to look at blocking programs from executing from AppData with AppLocker and Device Guard.

A workaround so far has been to copy the tmp file and rename it to cmtrace.exe and placing it in approved directory for executing applications, but this sort of extra effort could easily be solved by providing an update to the tool that simply includes the x86 and x64 versions of the application natively.

This goes for all new Add/Set-CM*DeploymentType but for my example, I'll refer to Add-CMScriptDeployment.

An example below is my generic Script Deployment Type.

Add-CMScriptDeploymentType `

    -ApplicationName "$PublicName" `

    -DeploymentTypeName "$AppName Client" `

    -ContentLocation "$AppLocation" `

    -InstallCommand "$InstallStr" `

    -UninstallCommand "msiexec /x $MSICode /qn" `

    -MaximumRuntimeMins 720 `

    -LogonRequirementType WhereOrNotUserLoggedOn `

    -UserInteractionMode Hidden `

    -ProductCode

    -ScriptLanguage PowerShell `

    -ScriptText $scriptDetect

When this is run, the DT is created with the Installation Behaviour set to the default value of "Install for system if resource is device; otherwise install for user"

The previous version of this cmdlet - Add-CMDeploymentType had the parameter available to configure this option, but it seems to have been removed from the parameters available in the new cmdlet.

My Current workaround is to call the now deprecated "Set-CMDeploymentType" like the below command shows.

Set-CMDeploymentType -DeploymentTypeName "$AppName Client" -ApplicationName "$PublicName" -MsiOrScriptInstaller -InstallationBehaviorType InstallForSystem

Can we please get the "InstallationBehaviourType" parameter added back to the new Add-DeploymentType cmdlets.