Hi!
Just a short post for reference.
In my line of work I sometimes need to find the product description or version (build) number of a product.
While searching for them I stumbled upon a perfect website for most regular Microsoft products!
https://buildnumbers.wordpress.com/
Products like AX, CRM, Exchange, Office, SCCM, SCDPM, SCOM, SCSM, SCVMM, Sharepoint, SQL Server, TMG/ISA
I don’t know who is behind the site but a great cheerio for him/her or them! 🙂
/Stephan
This post will describe the setup that is needed in order for your OpsMgr 2012 SP1 environment to monitor your ConfigMgr 2012 SP1 site.
First download the MP via this URLÂ http://www.microsoft.com/en-us/download/details.aspx?id=34709
Execute the installer and you will end up with 4 files:
Import the 3 Management Pack Files for ConfigMgr.
So go the Administration tab –> Management Packs –> choose the Add button from disk.
Then make an Override Management Pack for this MP!
After importing and installing you get a new monitoring view (System Center 2012 Configuration Manager)
For the Configuration Manager monitoring pack to discover objects, you must turn on Agent Proxy on every site server except for the primary site and the central administration site.
It might take some time before your ConfigMgr 2012 SP1 components appear in the OpsMgr 2012 SP1 environment…
After that is done, you can go back to the monitoring tab and choose under SCCM 2012.
Hierarchy Diagram. This will give you a diagram over your SCCM site.
Any alerts (RED X’s) can be clicked and you can drill down to your problem. The MP looks very good and complete.
Be sure to read the manual, a lot of rules are disabled by default. Also performance monitoring is disabled by default.
All Management Packs can be found in Pinpoint:
http://systemcenter.pinpoint.microsoft.com/en-US/applications/search/operations-manager-d11?q=
Here is an overview of Server 2012 MPs:
While working with the ComTrade Management Pack (XenApp) for OpsMgr 2012 there was an alert about the User Logon Process.
The alert:
Well oké that takes a while!
But what are the phases they talk about?
The phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).
Reasons for slow logon phase can be:
Additionally, monitoring of Windows user profiles for the presence and amount of the specific file categories is important. Various file categories should be tracked: executable files, media files, and custom files.
During this phase, the server applies user settings defined on the Domain Controller.
Reasons for the slow logon phase can be:
During this phase, network connections are restored and profile settings, such as fonts and screen colors, are loaded. Also, if this is the first time this profile is being used, some extra initialization is applied. The default profile is created, first time use settings are applied for the shell (Explorer), Internet Explorer, Office (particularly Outlook), and any other application that uses Active Setup.
Reasons for the slow logon phase can be:
This phase is measured by how long the USRLOGON.CMD script (located in %SystemRoot%\system32) is being executed. The script’s original function is to address issues with legacy applications that were not written with a multi-user environment, such as Terminal Server, in mind. It uses application compatibility scripts (located in  %SystemRoot%\Application Compatibility Scripts) in conjunction with the %ROOTDRIVE% variable to address these issues. USRLOGON.CMD script is also used as a starting point for custom profiles.
Reasons for the slow logon phase can be:
You should differentiate between Terminal Server (RDP client) and Citrix (ICA client) logon. If the user used the RDP connection to log on to the server, this will be the last phase of the logon process.
This phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers, and ICA client update process.
Reasons for the slow logon phase can be:
Original source: here.
So you got Operations Manager 2012 installed.
The console looks fine and you can select which Management Packs (MP) you want to see and which ones you don’t.
Every admin who logs in to the console will have to do this and this is fine for sealed MP’s.
But what about your own, unsealed, MP’s?
They also appear in the console and you can select them whether to display them or not. But the MP’s you will add are most of the time ‘Override’ Management Packs, containing your overrides (per Management Pack…).
Of course this is possible:
But it is also possible to hide these MP’s from everybody while keeping all the benefits from having them!
Here we go:
Administration Ă Management Packs Ă
Your MP Ă ‘Export Management Pack…’
(and Yes those 3 dots are there ;-))
This will produce a XML file with all your override parameters in it.
The high-lighted part will have to be removed.
and Install the MP.
But not here:
Or here:
Be sure to back up your Management Pack before you edit them… Just in case.
When you install Operations Manager 2012 (SP1) you may notice is that there is no request for a product key when you install Operations Manager 2012. Once the install is complete and you open up the console the following is displayed:
When you click Help Ă About Ă will show that you are running an Evaluation copy.
The way to do it is described here: http://support.microsoft.com/kb/2699998, and here is the visual version.
To register your product key with Operations Manager 2012 and move from the Evaluation edition to the Retail edition you will need to launch the Operations Management Shell and run a PowerShell cmdlet.
So start up the Operations Manager Shell:
And type:
Set-SCOMLicense –ProductId {YourProductKey}
(Tip: type the first letters and then push <TAB> for PowerShell to complete the command)
On completion restart the Operations Manager 2012 server for the key to validate.
After the reboot, check back in Help Ă About you will see it is now a Retail version.
Strange way to activate a Microsoft product but this is how it works!