Just a very quick blog to let you know how you can force an Object Discovery instead of waiting the desired amount of time specified in the Discovery rule which can sometimes take up to 24 hours.
You can just restart the “System Center Management” service and the discovery will kick in straight away 
We came across an issue recently when trying to create a test mailbox for our SCOM monitoring.
On the Exchange Sever we ran the following script to create the test mailbox “New-TestCasConnectivityUser.PS1”
However the command produced the following error “CreateTestUser : Mailbox could not be created. Verify that OU ( Users ) exists and that password meets complexity requirements.”
To resolve this we specified the DN name of the OU in the New-TestCasConnectivityUser.PS1 script by editing the following line in the PS1 script.
$OrganizationalUnit = “Users”
We changed this to
$OrganizationalUnit = “CN=Users,DC=Domain,DC=CO,DC=UK”
We then re-ran the script and all worked fine 
Just a quick useful command to find out which SCOM agents in your environment are proxy enabled.
If you run the following command in SCOM PowerShell.
get-agent | fl Displayname ,Proxyingenabled
This will give you an output like below.
DisplayName : Servername.domain.com
ProxyingEnabled : False
We came across an issue today where the following two alerts were exceeding there thresholds “”The AD General Response is above the configured threshold” and “AD Op Master response is above the configured threshold”. The DC in question was a x64 windows 2008 machine and interestingly enough we had x86 DC in the same site which did not exhibiy any of the issues.
So we had a look at what version of oomads (AD Management Helper Objects) on the x64 DC only to find the x86 oomads installed , so we simply removed the x86 version and installed the x64 version of oomads and the alerts just disappeared 
Daniel Davies
We came across an issue recently where we had placed a few servers into maintenance mode and when we stopped maintenance mode the servers did not change back to a healthy state, they were in a not monitored state.
We left it for an hours to see if the agent would sort itself out to no avail.
It appeared that the agent seemed to be stuck in the not monitored state, so what i did next was to try and refresh the agent was to put it into maintenance mode for 10 minutes and then stop the maintenance mode and within minutes the state changed to healthy again
Hope this helps
Daniel Davies
Currently at this point in time you will be unable to monitor your Exchange 2010 environments via SCOM R2. If you install the MP you will come across the below errors and if you go install the required KB you will hit a problem as this update has not current been released.
“Critical hotfixes required for reliable operation of the Exchange Server 2010 and other management packs are not installed on this server. Please see the appropriate KB article for more information, and to download the required hotfix.
For Operations Manager 2007 SP1, install KB 971541 (http://go.microsoft.com/fwlink/?LinkID=167911)
For Operations Manager 2007 R2, install KB 974144 (http://go.microsoft.com/fwlink/?LinkID=167912 “
This is Due to the KB update for SCOM R2 currently not being released, so for the time being you will not be able to monitor your Exchange 2010 environments via SCOM R2.
After speaking to Microsoft the KB should be released before the new year.
Thank You
Daniel Davies
It is always important to have up to date Management packs, this is because in updated management packs their can be new monitors and rules which are not included in the current version of the management pack and therefore making you miss potential issues. Bug Fixes may also be included in updated MP’s so updating can also reduce the amount of noise from SCOM.
The task of updating SCOM R2 Management Packs is fairly Straightforward.
Upgrading Management Packs
1, If we firstly go to the administration tab on SCOM console
2, Now if We Right Click Management packs on the windows on the left and choose import management packs
3, Next if choose the add option and then the add from catalog option. The Add from catalog option, basically checks for new MP’s from the Microsoft Management Pack catalog.
4, If we change the View drop down to update management packs. This will then compare our MP version to Microsoft catalogues and let us know what MP’s we need to update when we hit search.
5, You will now see the management packs you need to update. If you choose what management packs you want and press the add option and then finally hit ok.
6, Then Install the MP’s and you’re done.
Daniel Davies
I have come across an issue recently where Servers with a SCOM Agent installed are running at 100% CPU, and when you look at task manager on the server you can see multiple CSCRIPT.exe processes running.
CSCRIPT.exe is what SCOM uses to run scripts on the SCOM agents.
The simple fix for this is to upgrade WSH to version 5.7 and the issue with the CPU just simply goes away.
Daniel Davies
