70-243 · Question #89
You have a System Center 2012 Configuration Manager environment. You have an application named App1. You modify the Package Access account on the App1 software package to prevent read access for all…
The correct answer is B. Refresh the package on all distribution points. Changes to Package Access accounts in ConfigMgr are only stored in the database until the package is refreshed on distribution points, which propagates the new permissions without retransmitting package content.
Question
You have a System Center 2012 Configuration Manager environment. You have an application named App1. You modify the Package Access account on the App1 software package to prevent read access for all users. Users are still able to access the package. You need to ensure that users cannot read the package, and minimize bandwidth utilization. What should you do?
Options
- ACopy the package to all distribution points.
- BRefresh the package on all distribution points.
- CUpdate all distribution points with a new package source version.
- DDelete and re-create the software package.
How the community answered
(21 responses)- A14% (3)
- B76% (16)
- C5% (1)
- D5% (1)
Why each option
Changes to Package Access accounts in ConfigMgr are only stored in the database until the package is refreshed on distribution points, which propagates the new permissions without retransmitting package content.
Copying the package to distribution points retransmits the full package content to every DP, consuming unnecessary bandwidth when only access permission changes are needed.
When Package Access account permissions are modified in Configuration Manager, the changes are not automatically applied to content already distributed to distribution points. Refreshing the package on all distribution points pushes the updated access control settings to the content folders on each DP without resending the full source files, satisfying the security requirement while minimizing bandwidth consumption compared to redistribution options.
Updating distribution points with a new package source version is the procedure for when source files have changed on disk, not for propagating access account permission changes.
Deleting and re-creating the software package is destructive, loses associated deployment history, and causes a full redistribution of content across all distribution points which wastes bandwidth.
Concept tested: ConfigMgr Package Access account permission propagation to DPs
Source: https://learn.microsoft.com/en-us/mem/configmgr/apps/deploy-use/packages-and-programs
Topics
Community Discussion
No community discussion yet for this question.