SCCM 2012 Import computer Information and Security Role. Which allows?

Question

_{Friday, May 25, 2012 1:08 PM}

Hi!

SCCM 2012 "Import computer Information" in "Security Role" Which allows ?

Perhaps it is a resource which describes all possible entries in "Security Role"?

cenubit

All replies (9)

_{Friday, May 25, 2012 1:29 PM ✅Answered | 1 vote}

http://blogs.technet.com/b/inside_osd/archive/2012/04/30/custom-role-based-administration-for-importing-computers.aspx

Torsten Meringer | http://www.mssccmfaq.de

_{Thursday, May 31, 2012 7:12 AM}

Ok  It works. I see the "Import Computer Information" section of the Devices. But when I do the "Import single computer" introduction to "Computer Name" and "MAC address" and will add a "Collection", it can not do this because the list do not see any Collection. While the SC2012 console I can see the necessary collections. What rights are missing?

Complementary:

If I Making as described, then the account can see the entire collection. Is it possible to allow the "Import Computer Information" and not let it see the entire collection?

There is a detailed description for what and how and what to do "Security Scopes"? As well as a law affects the Collection Properties option "Add Rules"

cenubit

_{Thursday, July 26, 2012 12:55 PM}

I am bumping this because I have been unable to get this to work. The option is still grayed out for our users who want to import computers.

The only difference in my application is the users have a modifed version of the OSD Manager role (I removed access to OS installers, drivers, and boot disks, which should not affect this). I tested it by adding the standard OSD Manager role and that failed too. Any idea where I am going wrong?

_{Thursday, July 26, 2012 1:05 PM}

The problem is when the OSD small admin is not available in a collection of "All Systems".

cenubit

_{Thursday, July 26, 2012 2:06 PM}

I am not sure what you mean by this. When I tried the OSD Manager it did not work either.

How could I rectify this?  Add All Systems to the small admin? That would defeat the purpose of our roles.

_{Wednesday, September 19, 2012 3:45 AM}

for computer imports, you need to assign to the security role the following:

security scope : default

collections : any collections (or ones based on it) for which you want the import to be able to put the computer in

the security role will have following rights

site - import computer & read

collection - read & modify resource

If you import a computer you will be able to add it to the collections which are based on the collection you assigned to the security role.

_{Monday, January 28, 2013 8:58 AM}

Hi ,

Default Security scope is assigned to all applications, packages and other admistrative tasks, so create a other Security scope.

collections created based on the requirements and assigned permissions on Site and collections as described above.

but still import computer information is disabled. Request you to provide me more details to enable Import computer information using RBAC.

thanks

_{Monday, January 28, 2013 2:38 PM | 1 vote}

Hi,

the problem is the limiting collection setting. This is in most cases "All systems" and this collection your OSD administrator isn't allowed to use. Create a new collection which contains all devices for your administrator and use this for limiting collection on your existing deployment collection. When you start the "Import Computer Information" wizard using the OSD administrator, your will only be able to select the specified deployment collection. It seems that the wizard is only checking permissions on the used collection and the limiting collection, so this is a feasible workaround. Assign the OSD administrator permissions on both collections.

Disadvantage of this approach is that the added computer must be a member of the limiting collection, before it can be added to the collection with the deployment task. The easiest way to automate this, is create a membership rule based on a query on e.g. computername for the used limiting collection.

I hope this helps.

Regards

_{Thursday, November 7, 2019 12:17 PM}

Is it Still like this?

MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.