After install SCOM R2, I need to import MPs, but what is the best practice? Install Agent before import New MPs? or install Agent only after import new MPs?

I am always install agents before. It gives me a time to fix all issues like WMI problems, access issues and first tuning all default (imported as a part of installation MPs). Then I am import MPs one-by-one into stable and 'pre-tuned' management group: Read MP Guide - Plan - Import new MP - tune it - check all stuff - stabilize - think about import next MP.http://OpsMgr.ru/

Hi You don't say much about the number of agents or the architecture but in general, this is what I recommend. It is personal but it works for me! And the basis of this is to do one thing at a time and get it right before moving on to the next. 1) Have an alert management process in place before you start. You'll have to fine tune it as the deployment progresses. But if you install Windows, AD, SQL, Exhange, IIS, Cluster, Hardware MPs then the next thing is you'll have a console full of alerts and no process for managing them. A sure recipe for disaster. 2) Deploy slowly - get core components, agents and windows management pack deployed. This means that you are not fire fighting on multiple fronts (e.g. with AD, Exchange etc alerts). Just get the agents in and sorted. Get the windows MP in and sorted. The Windows Management Pack is ideal for this as the alerts it generates are usually actionable, relevant and relatively straight forward to resolve so administrators can get familiar with OpsMgr in a fairly controlled environment that is still providing real benefit to the organisation 3) Proitise other MPs - I like to get SQL in next as it is a relatively stable MP with less noise than AD, Exchange etc but still gives good business benefit. But deploy the MP and spend time fine tuning it. Make sure you are happy that the alerts you get are actionable. Then move on. 4) Repeat slowly .. MP by MP ... the AD alerts you get might be relevant, they might not be. Even the relevant ones might take time to resolve. Same with Exchange. Expect it to take a few weeks to a couple of months to deploy rather than days. As for fixing alert versus override - that is part of the alert management process. It might be an issue that is very real but sadly can't be fixed in the short term. You have options - create an override to stop the alert but have a separate "To do" list that you work through and remove the override when the task is done. Or you can create a resolution state of "On going"and rather than create an override put the alert into that state. It depends very much on the alert and how quickly the underlying problem can be resolved. Hope it helps GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/