- Flexera Community
- :
- App Broker
- :
- App Broker Forum
- :
- Re: App Portal / Broker and SCCM Deployments
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- How does App Broker initiates the Machine Policy update when an install is requested. It appears we have an issue on a very large install from a network drive is not kicking the script off to do the install at the policy update step and SCCM is not getting notified to start the install. Other applications are working fine.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am not sure how its sent! I have encountered similar issues with policies and under Site Management > Setting > Deployment > ConfigMgr/SCCM2012 > Check the radio box to "Use SCCM server for machine policy refresh"
I dont believe its enabled by default, and that has given us better response times with installs.
This thread has been automatically locked due to inactivity.
To continue the discussion, please start a new thread.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am not sure how its sent! I have encountered similar issues with policies and under Site Management > Setting > Deployment > ConfigMgr/SCCM2012 > Check the radio box to "Use SCCM server for machine policy refresh"
I dont believe its enabled by default, and that has given us better response times with installs.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There can also be inherent delays if using an SCCM environment with a CAS. App Portal will communicate with the CAS and update the collection membership rules there for the appropriate catalog item collection. The collection rules then have to replicate to each primary site where collection evaluation is run. After each primary site has evaluated the collection membership, that membership is replicated back to the CAS. The problem with policy evaluation is that we use the SCCM client notification channel (when that box is checked) to notify the client that it should check for new policies. If that client notification happens before the collection evaluation is completed (and policies updated accordingly), then the client won't get the new policy until the next standard client polling interval (normally an hour). Is that what you've been seeing, or is it something different?
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Checked with packaging and they are not using CAS.
Currently it seems to be possibly a cache for the large file download full issue.
I will return to this questions when I have more details.
