Advertisement

FIX Issues with SCCM RBA and Clear Required PXE Deployments Options

Clear Required PXE Deployments is regularly used option in SCCM / ConfigMgr. What I recently found is that Operating System Deployment Managers (default security role) are not able perform the above mentioned function by right clicking on a device. Full Administrators won’t face this issue. Clear PXE option is available in SP1 beta. I’m not able replicate this issue in Service Pack 1 version of ConfigMgr 2012.

image

The Clear Required PXE deployment option is available in the ribbon menu. However, this will clear the required PXE boot deployments of all the members assigned to this site in this collection.

The members NOT assigned to this site will not be affected.  So basically, it’s collection based clear PXE deployments and we don’t normally use this option because it will clear the PXE for all the members of that collection.

imageimage

I’ve done some analysis on this. Following are steps that you need to follow to get this option available for Operating System Deployment Managers or any other security roles.

1. The security role should have “Modify Resource” access on Collection. Collection –-> Modify Resource –> Yes.

2.

imageAdministrative User/s (for e.g Operating System Deployment Manager)  should be part of “All Systems” and “All Users and User Groups” collections irrespective of Security Scopes.

Note :: If you remove any of those (above mentioned) collections from the administrative user then the option to clear the PXE will get removed. Providing modify access to “All Systems” and “All Users and User Groups” is not a good idea.

The work around for this issue is to create a separate collection for PXE clear devices. If you want to clear PXE advert of a device then move that device into that collection and then do “Clear Required PXE Deployments”. This collection would act as temporary holding place for the device/s which we need to clear PXE adverts. I know there is slightly more administrative work involved in this method. However, it better than providing “modify resource” access to all the systems and users.

No need for much worry, as I can see this issue is not there in System Center 2012 Configuration Manager SP1 version (beta).

To know more about other issues we normally face during RBA implementation and How to fine tune RBA in your organization, you can go through my posts – Post 1 and Post 2

About Author 

Anoop is Microsoft MVP and Veeam Vanguard ! He is a Solution Architect on enterprise client management with more than 13 years of experience (calculation done on the year 2014) in IT. He is Blogger, Speaker and Local User Group Community leader. His main focus is on Device Management technologies like SCCM 2012,Current Branch, Intune. He writes about the technologies like SCCM, SCOM, Windows 10, Azure AD, Microsoft Intune, RMS, Hyper-V etc...

    Find more about me on:
  • googleplus
  • twitter
  • facebook
  • linkedin
  • youtube
Posted in: ConfigMgr (SCCM), Configmgr2012, Console, Service Pack 1, System Center 2012 Configuration Manager, System Center 2012 Operation Manager

2 Comments

  1. SCCMentor says:

    Cheers Anoop. Another great reason to move to SP1 and beyond

Leave a Comment and Contact Anoop