Hi,
Deployments created by phased deployments aren't viewable to any administrative user that doesn't have the
All security scope.
Use security scopes to provide administrative users with access to securable objects. A security scope is a named set of securable objects that are assigned to administrator users as a group. All securable objects must be assigned to one or more security scopes.
Configuration Manager has two built-in security scopes:
The All built-in security scope grants access to all scopes. You can't assign objects to this security scope.
The Default built-in security scope is used for all objects, by default. When you first install Configuration Manager, all objects are assigned to this security scope.
If you want to restrict the objects that administrative users can see and manage, you must create and use your own custom security scopes. Security scopes don't support a hierarchical structure and can't be nested. Security scopes can contain one or more object
types.
For more information, see:
Security scopes
This MECM Forum will be migrating to a new home on Microsoft Q&A<Link>,
please refer to this sticky post<Link>
for more details.
Best regards,
Larry
"MECM" forum will be migrating to a new home on
Microsoft Q&A!
We invite you to post new questions in the "MECM" forum's new home on
Microsoft Q&A!
For more information, please refer to the
sticky post.
