Thanks. In addition to your suggestion, I just found a blog that describes exactly what I *think* I need: http://blogs.technet.com/b/cmpfekevin/archive/2013/11/21/import-computer-does-not-show-up-in-collection.aspx I am going to give this a shot. . . Thanks, Jeff Date: Wed, 10 Dec 2014 15:47:28 -0600 Subject: Re: [mssms] Importing Computers, Limiting Collections, and RBAC From: [email protected] To: [email protected]
You could create a collection with all systems that have no client installed and give them access to it. They will have to wait a few minutes after importing to add the computer to your imaging collection, but they would eventually be able to do it. On Wed, Dec 10, 2014 at 3:30 PM, Jeff Poling <[email protected]> wrote: 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
