Hi,

I am using Application catalog for making the applications available for the users to install as and when they are in need of. By default, user can set more than one device as his primary device and any approved application can be installed on any/all of those machines.

While checking the available option to automatically install an app to users primary device (In case of OS reinstallation or Hardware refresh) using appcatalog, it gets installed on all primary devices.

It becomes difficult to manage this scenario since there are many licensed applications which will get installed on multiple machines.

Is there any possibilities wherein we would get an option to restrict the users to set only one device as his primary device?

Regards
Nikhil S

Dear All,

we are using more than one detection rule for all our applications(script installer) that are created in our environment.

During installation, the detection rule (AND condition) works fine and we face no issues.

But there are cases when the uninstallation fails in the middle of the script, we get the message as REMOVAL FAILED in the software center, and out of 3 detection rule one or two get removed (partly uninstalled) , but not the whole application is uninstalled from the machine. And when we run the RETRY for removing the application, SCCM check for installation status based on the detection rules and the detection rule returns false, which makes SCCM to believe the application is no more installed in the machine and vanishes from the software center without even executing the uninstallation again.

This brings inconsistency in the application uninstallation, and few application are partly uninstalled and broken. And when we try to reinstall the application on the same machine, it even fails to install the application, since it has a broken application because of this partial Uninstall.

And this can be rectified only when the detection rule work vice versa for Uninstallation, i.e all the detection rule values must be removed from the machine , only then sccm should declare the application is removed from the machine or by creating custom scripts for detection rule (which we don’t want to). But sccm doesn’t work that way.

So the detection logic can be changed to make it work the other way during uninstallation.

In the Microsoft portfolio a complete User Environment Management (UEM) solution is missing. Yes, there is Group Policy + Preferences and User Environment Virtualization (UE-V), but a solution like RES One Workspace or AppSense is missing. Why's that? Lot's off customers like to have a Microsoft-only or Microsoft-unless policy, which can't be using Microsoft solutions alone.

Think about a solution which combining user settings like start menu, desktop, folder redirection, taskbar, application control, application security, license management, drive mappings and printer offering. Where delegating of control is possible. With integration in Configuration Manager, and what else you can think of. How's everyone in the world doing this without using a 3rd party solution?

Hope that Microsoft will come some day with a solution like this. On-premises isn't dead. Hybrid is the future, and local systems still needs to be managed.

/Henk

Please incorporate the option to execute a Program without elevation (least amount of privileges).

Background:
We sometimes receive requests to automate some process via Configuration Manager. This is frequently done by creating a Package with a Program that executes a script.

Use case:
When automating the OneDrive sync client (or various other commands / programs), a simple script works well.

Problem:
When the same script is executed with elevation, it doesn't work as expected.
Configuration Manager elevates the session when the currently logged on user has admin privileges on the machine.
Some troubleshooting is required to find the root cause. After that, additional scripting, testing and verification is needed to make the script work as expected.

Workaround:
Additional scripting.

I would like to see the ability to easily link a deployment type to a deployment. here is why with the deployments you can point them to a collection. it would be nice to be able to say, "hey i want this deployment type to go to this production collection. However, i want to test this update for this application and have the target collection be the pilot group." i know there are probably global conditions you can make to query collection membership but it seems like it would be a small task to have that simple feature to have an option to have a 1-1 link between a deployment type and deployment

Web Application deployment types in their current incarnation are not very usable. The main issues with using them are that:

1. There is no control over where the shortcut to the Web App gets placed; they always go to the start menu. We would like the option to put the shortcut on the desktop or in the user's favorites menu. To do this currently we have to write a script and cannot use this deployment type.

2. The icon for the Web Application should use the icon imported into the software center. Nondescript icons make finding the application you want to launch much more difficult that it needs to be.

Today the only deployment type for Mac is to use the ".cmmac" packages.
These packages are far from on par with what is available for Windows.
The most basic option to uninstall the app is not present.

It would be very usfull to have the "Mac Script Installer" deployment type where we can simply add a .pkg file or bash script with media and execute install and uninstall with custom commands. Some of the packages require more then just the .pkg file and will therefor be incomplete.
Having a uninstall command will also allow for propper supersedence where now application would trigger uninstall of old.

also to this deployment type there should be more options for detection like File, Directory