In the previous post, I provided tips to have successful and effective SCCM MS RAP data collection in the Real World. In this post, we will see how can we improve ConfigMgr Microsoft RAP Results Real World Tips. As I mentioned in the last post, the MS RAP data collection is the first important step. More details “SCCM MS RAP Real World Tips for IT Pros“.
Microsoft SCCM RAP Results in High Level
The Microsoft RAP assessment for SCCM provides you results grouped in two areas:- health issues and risk issues. Health issues reflect active problems regarding the configuration or proper function of the product and related components. Risk issues cover areas such as change control, monitoring, disaster recovery, service level agreements and other items that if left unresolved increase risk of future problems or worsening problems.
- 1. Health issues
- 2. Risk issues
What is SCCM Microsoft RAP Health Issues
Microsoft SCCM RAP provides results in two areas Health Issues and Risk Issues of the SCCM CB infrastructure. The health issues reflect problems regarding the configurations in the infrastructure, and this also checks proper function of SCCM, and its related components.
One of the most common health issues of SCCM environment is site assignment boundary conflicts. This type of issues could give you a bad rating in Microsoft SCCM RAP engagement. I would also recommend to FIX the health issues related to SCCM MPs, DPs, SUP and other SCCM components.
What is SCCM Microsoft RAP Risk Issues
Risk issues analyzed in Microsoft SCCM RAP confirms whether ITIL processes (like Change, Incident management) are followed in your SCCM environment. This also confirms whether do you have any scheduled disaster recovery plans and procedures for your SCCM infrastructure. MS SCCM RAP also confirms the SLA (Service Level Agreements) followed in your SCCM environment. Microsoft SCCM RAP RISK assessment looks into unresolved SCCM infrastructure HEALTH issues identified during the data collection.
One of the most common and highly rated RISK issues is the lack of documentation of SCCM environment. Some of the other risk issues could be the lack of SCCM DR documentation, lack of SCCM infra monitoring using SCOM or OpsMgr. There will be an assessment of organization’s SCCM service improvements efforts.
Tips from Real world to Keep SCCM Infra Healthy and Risk-Free
Run Microsoft RAP tool 2 weeks before and identify the issues in your SCCM CB environment. Fix the issues highlighted in the RAP reports and rerun the Microsoft SCCM RAP tool 1-2 days before PFE visit. Microsoft PFE will be onsite for 2 days. Try to RESOLVE the issues of your SCCM environment with Microsoft PFE on the first day. This will give you good results for Microsoft RAP. Also, this will help you to have a better SCCM environment.
Another important perspective of Microsoft RAP engagement for SCCM is operational processes followed in the organization. Take Microsoft RAP questionnaire seriously, and the wrong answers to the questions could give you bad score cards. You can retake the questionnaire survey if you think, you had given wrong answers to some questions.
Microsoft RAP tool is free for one year, and you can rerun the tool many times within that one year time frame. To keep SCCM CB infra healthy and risk free, I recommend to run the RAP tool every 3-4 months and look at the reports. This will help you to understand the SCCM environment in a better way.
- RAP as a Service Documentation – PDF Datasheet and Prerequisites for SCCM RAP – here
- RAP as a Service (RaaS) from Microsoft Services Premier Support – Here