I'd also like to see the following scenario:
- I add an executable to the "Install behavior" screen
- I deploy the application as required, but without checking the force close executable checkbox
- I expect the application to wait for the application to close before the install executes, however what happens is the application enforcement fails and it is not retried until the next application evaluation cycle.
What I would like to see in this scenario is the application wait for the executable to close before the application enforcement begins (because I am not force closing the executable). In other words, treat it the same as the user experience logon requirement (Install only when no user is logged on). Simply wait until the executable is closed.
In the case of force closing executables with available deployments, Adam's suggestion makes most sense.
11 votesMatthew DeBoer shared this idea ·
It appears that ConfigMgr does not check the group policy location to detect what updates are required. It does however check the CDNBaseURL at HKLM:\\SOFTWARE\Microsoft\Office\ClickToRun\Configuration
I have tested that deploying a configuration item with the appropriate CDNBaseURL causes the client to detect updates from the desired update channel. These updates also successfully install. I am not certain however if/when these urls change or if this would be supported.
Here are the current CDNBaseURL options for 2016:
'Deferred' = 'http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114';
'FirstReleaseForDeferred' = 'http://officecdn.microsoft.com/pr/b8f9b850-328d-4355-9145-c59439a0c4cf';
'Current' = 'http://officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60';
'FirstReleaseForCurrent' = 'http://officecdn.microsoft.com/pr/64256afe-f5d9-4f86-8936-8840a6a4f5be';
You can verify these by comparing them to the content location of an update from the channel you want the client to install.
This would provide a nice single pane of glass.
If you are interested, rather than using the vendor's install package, you can use devcon.exe from the Windows driver kit to complete a silent install:
1. Get the PCIID from the hardware in WMI:
select * from win32_pnpentity Where Name like 'Intel%Graphics%'
2. Use Devcon to install the appropriate driver for the pciid you found:
devcon.exe update "PathTo.inf" "PCIID"
This will install the inf for the specified PCIID. You will want to be careful as this will upgrade/downgrade any drivers.
I've added my votes to this one in favor of consolidating the idea I created when I didn't find this one....Here is the text of the idea I had posted (since it will probably be deleted now that I removed my votes):
Add "Run As" to Applications
Similar to the Task Sequence "Run this step as the following account". Please add this to application installations as well. We have some "difficult to package" applications that require a user profile in order to install successfully. These applications fail to install as an application because when running as the system there is no user profile path. As a result, we have to resort to task sequences to install these which results in a worse end user experience.