Hi Jeff, We solved this by using the SCCM 2012 R2 SDK to create a post-import DDR populating the OS property so that new devices appeared in the collection limited by a collection targeting specific OS's (desktop/server).
-Stephen > On Dec 10, 2014, at 3:41 PM, Jeff Poling <[email protected]> wrote: > > David, > > We are at R2 CU3..... > > Sent from my Windows Phone > From: David O'Brien > Sent: 12/10/2014 3:37 PM > To: [email protected] > Subject: RE: [mssms] Importing Computers, Limiting Collections, and RBAC > > Hi Jeff, > > I’m pretty sure they fixed that with R2 and some SP1 CU something… > > Cheers > David > > From: [email protected] [mailto:[email protected]] > On Behalf Of Jeff Poling > Sent: Thursday, 11 December 2014 8:31 AM > To: [email protected] > Subject: [mssms] Importing Computers, Limiting Collections, and RBAC > > For a PC replacement scenario, we are manually importing the new PC into > ConfigMgr by MAC address. Unfortunately, in this environment, the PC team > does not have access to All Systems. So, we have a collection for the new > PCs to which a task sequence is deployed for imaging and restoring user > state. The imported PCs only show in that collection if it is limited to All > Systems. But if we limit it to All Systems, then the PC team cannot add > members to the collection. . .seems like a catch 22. . .has anyone > encountered a scenario like this? > > I did find the following article: > http://blogs.technet.com/b/inside_osd/archive/2012/04/30/custom-role-based-administration-for-importing-computers.aspx > but even using those steps, the imported PC does not show up in the > collection when added. > > Any insights or suggestions are greatly appreciated. > > Thanks, > > Jeff > > >
