I am fly out of Australia for the US for 2 weeks untill the 11th of June and as much as I would love to keep posting and working on new blog postings I am unable to take my SCOM environment with me 
However when I return I will be fresh, hopefuly stress free and full of energy to keep working on the massive world of SCOM!
This is a quick post due to a few questions about where you can record a browser session.
First thing to note is that you need SCOM installed and IE7 as a minimum. This can be on the RMS or preferably your own PC. If you are installing IE7 ensure you reboot the machine after this before you continue as there are a few known issues that arrise when havnt rebooted.
If your the kind of noisy person that like to see exactly where apps are installed and intergrated like I do, you will see that in IE7 under Tools -> Toolbars -> Explorer Bar you will see Web Recorder. While you can see it you need to run it through System Center Operations Manager which I will details now:
1. Open System Center Operations Manager
2. Go to Authoring
3. Under Management Pack Templates select Web Application.
4. You can now either click on Actions or in the Actions tab you will see a new section called Custom Actions from either click Record a browser session.
As for using it, well thats the easy part! Just follow the wizard and select the Watcher Nodes!
SYMPTOMS
You deploy an agent from the Management Server and in the pop-up deployment windows its listed as Successful however the server remains in Pending Management listed as ‘Install in Progress’.
The OpsMgr Health service fails to start and returns the following error: Error 0×8004005: Unspecified Error
CAUSE
This is caused by the Management Group changing and no longer being contactable but with the agent still being deployed and you try to install over the top into a new Management Group.
You will see the following error when you try to start the OpsMgr Health service:
You will also see the following error listed in the Event Viewer of the destination server:
If you the ablity to run a TraceLogSM and get it analised by Microsoft you will see a log similar to bellow. Not the hightlighted sections show the domain, service account and Management Group. If any of there are incorrect then you have found the issue.
You will need to run the TraceLogSM with the follow parameters:
TraceLogSM -start HSCORE -f hscore.etl -b 8 -ft 30 -guid #417B7AE0-9B8F-4E3F-8FCA-19C706EFF3D4 -flag 0xF -cir 100
To stop use: TraceLogSM -x
Send the file hscore.etl to Microsft for analysis.
67 HealthServiceCommon 23900 8856 2 0 05\17\2007-11:04:12:399 Logging informational event with args MGROUP
68 SecureStorageManager 23900 8856 2 0 05\17\2007-11:04:12:430 SSRef 63745834-3e54-936c-1b47-2d632054a177 resolves to 00BD5E70CBE8C70C8ABA7F843EB0BB42BA1920A05C00000000000000000000000000000000000000 : 0(ERROR_SUCCESS)
69 SecureStorageManager 23900 8856 2 0 05\17\2007-11:04:12:446 Account QBEAU\SCOM_AAA logged on : 1(ERROR_INVALID_FUNCTION)
70 SecureStorageManager 23900 8856 2 0 05\17\2007-11:04:12:446 Unable to create logon token : 1(ERROR_INVALID_FUNCTION)
71 SecureStorageManager 23900 8856 2 0 05\17\2007-11:04:12:446 Unable to log on user : 1(ERROR_INVALID_FUNCTION)
72 SecureStorageManager 23900 8856 2 0 05\17\2007-11:04:12:446 Unable to log on account : 1(ERROR_INVALID_FUNCTION)
73 SecureStorageManager 23900 8856 2 0 05\17\2007-11:04:12:446 Unable to retrieve the action account reference : 1(ERROR_INVALID_FUNCTION)
74 SecureStorageManager 23900 8856 2 0 05\17\2007-11:04:12:446 Unable to add store to store hashtable : 1
75 ConnectorManager 23900 8856 2 0 05\17\2007-11:04:12:446 Secure Storage Manager failed during MG notification : -2147467259(E_FAIL)
76 ConnectorManager 23900 8856 2 0 05\17\2007-11:04:12:446 Unable to inform components about management groups : -2147467259(E_FAIL)
77 HealthServiceExecutive 23900 8856 2 0 05\17\2007-11:04:12:446 Start of 1 manager failed with code -2147467259(E_FAIL).
78 HealthServiceExecutive 23900 8856 2 0 05\17\2007-11:04:12:446 ManagerStartup failed with code -2147467259(E_FAIL).
79 HealthServiceExecutive 23900 8856 2 0 05\17\2007-11:04:12:446 ServiceInitialization failed with code -2147467259(E_FAIL).
80 HealthServiceExecutive 23900 8856 2 0 05\17\2007-11:04:12:446 Health service is stopping.
81 HealthServiceCommon 23900 8856 1 0 05\17\2007-11:04:12:446 “Logging success event with args DOMAIN1, SCOM_AAA, MGROUP“
82 HealthServiceHost 23900 22684 1 0 05\17\2007-11:04:12:868 HealthService.exe exiting.
83 HealthServiceExecutive 23900 8856 2 0 05\17\2007-11:04:12:868 Health service entered the stopped state.
84 HealthServiceExecutive 23900 8856 2 0 05\17\2007-11:04:12:868 Start failed with code -2147467259(E_FAIL).
85 ConnectorManager 23900 15272 3 0 05\17\2007-11:04:12:868 GetHealthStatus called after service shutdown.
86 ConnectorManager 23900 7008 0 05\17\2007-11:04:12:868 OnLocalDataAvailable called after service shutdown.
87 ConnectorManager 23900 7008 0 05\17\2007-11:04:12:868 GetHealthStatus called after service shutdown.
RESOLUTION
1. Manually uninstall the agent from the destination server.
2. Using regedit confirm that the following registry entry doesn’t exist:
HKLM\software\microsoft\microsoft operations manager\3.0\Agent Management Groups\%ManagementGroup%
3. Deploy the agent again either via the Management Server or Manually
I have been working with SCOM for a while and I found that when you have a cluster that is being monitored the ScOM Root Management Server slows down with its discovery. I believe this is because when monitoring large clusters with many Databases and Virual Servers these are obviously viewed as Agentless devices. This is slightly contradictory as you actually do have an agent on each cluster node.
Its also becoming obvious to me that agent discovery is setup in a queue. This means that should you add a new system with lots of discoverable entities then this will need to complete first before the next lot of discoveries takes place.
When i mean discoveries I am talking about what the SCOM Agent will monitor, not server discoveries. My best advise to you if you find discovering slow, be patient
This error is an access error, its created when the SDK user account does not have write access to the SCOM database.
If you receive the error: SRS Server Validation Error while installing SCOM Reporting, dont forget you need to Configure Reporting Server first.
To do this you need to go START -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> Reporing Services Configuration. Then on each of the Items that have a Red X or Yellow ! select them and configure them accordingly.
If you see any grey items this means that they cant be validated and even though you have configured another item it could be incorrect. The most common is the Initialisation option, if this is grey then you probably authentication.
Data warehouse storage requirements can vary considerably depending on the data retention requirements so we would need more information in order to make any estimates. As with the ops DB, the single largest factor in DW size is the amount of perf data that will be retained. Since the DW will automatically aggregate performance data on an hourly and daily basis you can dramatically lower storage requirements by grooming out raw perf data aggressively and relying on the aggregated data for long-term trending reporting.
Sizing for the Ops DB is highly variable depending on which Management Packs are installed and what grooming policy is configured. Without knowing the details of the deployment I can give you some “worst case scenario” numbers derived from an MSIT Management Group that manages 3000 servers and has all of the out-of-the-box MPs deployed along with 18 custom MPs and a 4-day retention policy (with the exception of performance signature data which is retained for just 2 days). In this case MSIT allocated 60 GB for the Ops DB, of which they actually use about 35 GB. Performance data accounts for about 75% of the total storage requirement with about 55% being used to store sampled performance data (which is retained for 4 days) and another 20% being used for performance signature data (which is retained for 2 days). After performance data, collected events and monitor state change events account for the next largest category of storage used in the Ops DB with each accounting for about 10% of the total storage requirements. Alerts account for about 1% of the storage requirement. The remainder of the storage used is divided among a large number of tables with no other individual tables or data type accounting for any significant percentage of storage. With over 85% of total storage requirements being derived from the above operational data I wouldn’t spend much time doing detailed calculations of storage requirements for other data types. Unless you have unusual data retention requirements I would recommend using something similar to the MSIT storage allocation which will give you plenty of room for growth and some flexibility in adjusting data retention.
With regards to SQL log file storage requirements, the operational requirements are fairly trivial but you will want to allocate quite a bit more storage than required for day-to-day operations in order to cover the occasional need to delete Management Packs. MSIT uses 16 GB for transaction logs in their 3000-server MG. Under normal operations they rarely use more than a few hundred MB of this space (even while using the full recovery model with 15-minute log dumps) but much more is required on the rare occasions when large MPs need to be deleted. A significant amount of data can be deleted in a single SQL transaction when large MPs are deleted. MSIT has used up to 12 GB of log space while deleting some MPs. I would recommend that you allocate a similar amount of storage to avoid any problems with full transaction logs when deleting MPs.
You get a display error of 80070643
The problem is caused by a bug during the install, with the MSI custom action when it tries to register the agent for receiving updates via Microsoft Update. If the Windows Update/Automatic Update service is disabled install will fail.
This issue is bugged with Microsoft and will be fixed in the future so that the setup will detect this situation and ignore the failure and continue with the install. Unfortunately the only option at this point as a workaround will be to enable Windows Update/Automatic Update on the machine for the purpose of the install.
Bellow is the extracts from the agentinstall.log and momagentmgmt.log
agentinstall.log
MSI (s) (D0:C4) [00:46:55:547]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI150D.tmp, Entrypoint: CanRegisterMU
Action start 0:46:55: _CanRegisterMU.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
CanRegisterMU: WU version is greater than 5.8.0.2469so we can proceed further.
CanRegisterMU: get_Services() failed. Error Code: 0×80070422.
MSI (s) (D0:98) [00:46:55:829]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (D0:98) [00:46:55:829]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 0:46:55: _CanRegisterMU.80B659D9_F758_4E7D_B4FA_E53FC737DCC9. Return value 3.
MSI (s) (D0:98) [00:46:55:829]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (D0:98) [00:46:55:829]: No System Restore sequence number for this installation.
MSI (s) (D0:98) [00:46:55:829]: Unlocking ServerAction ended 0:46:55: INSTALL. Return value 3.
momagentmgmt.log
12:46:42 AM : CServiceModule::SetServiceStatus : State: 4, Error: 0
12:46:43 AM : CMOMAgentFunctions::GetPatches : Entering
12:46:43 AM : CMOMAgentFunctions::GetPatches : MsiGetProductCode failed HResult: 80070647
You get the following error when installing the SCOM Agent on a server.
I have had this issue on Citrix Servers only and at the moment have no fix for this. I have heard of the same error occurring on servers running Microsoft Virtual Server and the fix for this is to stop the VM service, manually uninstall the agent and then re-deploy.
The Debug output from the ‘agentlog’ file folder should look like this:
00000244 137.91078186 [15044] CAStartServices: CAStartServices was passed. HealthService
00000246 137.91197205 [15044] CAStartServices: Attempting to start service. HealthService
00000248 199.14978027 [15044] WaitForServiceState: Failed to get service state within time limits. Error Code: 0×80070102.
00000250 199.15072632 [15044] CAStartServices: WaitForServiceState failed for start request. Error Code: 0×80070102.
HealthService 0×80070102 ERROR_SERVICE_DISABLED – The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Each physical node has to have “Agent Proxy” enabled (in the administration tab -> Agent managed)In case this was not set, restart the agent on each cluster node. The discovery reruns. Check now that each virtual node comes in under “agentless” managed. (in the discovered inventory it will show as “not monitored” which is ok)Now check under Windows Server (state view). Each virtual server has to be discovered. Check the properties, it has to say “Is Virtual Node” true. Now the SQL 2005 should work as well. Check the SQL state views (this may take a moment if the Virtual node was not discovered previously – again you can restart the agent on the cluster node where the SQL is currently active)
Here is a Step-by-step guide on exactly what to do.
Cause
——-
SQL cluster dependencies was missing in cluster node
Resolution
=======
Installing MOM 2007 need to have dependencies criteria met.
In my case disk dependencies are not there so added the disk to the SQL Service Dependency list and OpsMgr 2007 installation went successful.
The install was failing due to a dependency missing on the SQL Service in the Cluster group. In cluster administrator I took the SQL Group offline and then clicked on properties of SQL server, then the dependencies tab and checked whether all disks are listed here.
Only Network name was there as I has added a new SAN disk to the group for the Data Warehouse database.
Now for SQL Server we should have minimum of two dependencies
1. Disk Physical Disk
2. SQL Network name (IP address)
