Great news! Veeam released the newest version of their SCOM 2012 management pack, what used to be known as Nworks, and is now called Veeam Management Pack. Version 6 is yet another big step forward in the evolution of this management pack.
The news release can be found over here:
I am very excited, as I have always been excited about this specific product, as it provides great insights into your VMware infrastructure and adds great value to any SCOM monitoring solution where VMware is being used in an infrastructure.
I will probably blog more about this later. However I have to fly soon, so no more time left for today
For one of my customers I have been fooling around with a clean SCOM 2012 SP1 install through command line. I ran into some issues and workarounds that you might want to be aware of. There are probably more to come, but I thought it better to post this piece first.
First of all we would start with the TechNet page about installing operations manager by using the command prompt window:
Also pay attention to the end of the article where there are specific references to different scenario's, such as installing on a single server, installing first management server, the web console and so on.
Of course there are prerequisites we can script as well, such as .net Framework 4 installer and the Report Viewer 2010 installer and the IIS prerequisites. Take them along.
When installing the FIRST management server (or when it is the only one..) you need to accept the end user agreement. This is done through the "/AcceptEndUserLicenseAgreement" switch. However the documentation is currently wrong (as are the examples in the referenced example pages). The option you should use is "/AcceptEndUserLicenseAgreement:1".
I still do not know where this came from, but I had a few runs during the initial testing where it did not want to accept
multiple entries for the "/components:" switch, but I attributed that to the environment and the script. Because later after having re-written the script anyway, it did not give these errors anymore. When in doubt just type the commands again on a separate line and throw out the old one.
This is a longer lesson, as it is multi part
When using the command line install, there is no option to change the database and log paths for each database. These options are available in the setup wizard. Of course we ran into this because of a known issue (read release notes!!) where setup tries to create files without a file name and only an extension for the datawarehouse database (so ".mdf" and ".ldf" are created).
There is a solution to this if the files are created already by using a solution as mentioned here:
And when using the setup wizard GUI you can work around this by "using the error" in the script to circumvent this by adding the file name you want without a trailing "\" at the end of the line as blogged here:
However, as stated earlier the command line does not give an option for this. So what happens? Well, that depends on your settings in SQL and rights and the version of SQL as it turns out!
First of all if you can not specify the database and log paths, it will take the default paths defined on your SQL instance. For fun open the SQL Management Studio and take a look at the properties of the server and go to the "database settings" tab. Near the bottom you will see the default paths. This should be where the command line wizard tries to place the files for both databases. Now take a look at the very end of those paths and determine if your SQL is using a "\" at the end of the line. I found that SQL 2008 R2 is not using it and that SQL 2012 is using it. And I can not change the bahavior by manually adjusting this setting (remember that this is a registry setting in the end, so you need to restart SQL to get it active).
This has an effect, due to the error in the sql creation script for the datawarehouse. That script looks at the path variable, either from the setup wizard GUI or from SQL default settings as discussed above. Due to the error in the script it expects the last thing in the path to be a trailing "\", otherwise it will see the last characters after the last "\" to be the file name you want for the datawarehouse. In many cases this would be something like "X:\Program Files\blabla\blabla\MSSQL\Data" and for the SQL 2008 R2 version I found the path to be like this without the trailing "\". So what does it try to do in this case? It tries to create a database file called data.mdf in the MSSQL folder one level up. In my case this gave an immediate access denied and of course a roll-back of the whole installation.
In SQL 2012 the above problem does not exist as far as I know, because it keeps adding a trailing "\" to the end of the folder path. So in that case we are back to http://www.bictt.com/blogs/bictt.php/2013/01/25/scom-2012-sp1-strange-file
In SQL 2008 R2, if you run into this you could work around this by assigning the SQL service account enough rights (lets go for full control for now) in the folder one level higher. Run the installer again and it will create data.mdf and data.ldf in my example in the MSSQL folder. And from there you can also both move and rename the file as in http://www.bictt.com/blogs/bictt.php/2013/01/25/scom-2012-sp1-strange-file
Of course you can script the moving and renaming of these files as well, however it depends on the environment you are in to determine how to do those things. Stuff like paths and if you first want to check those paths and such require some thinking script-wise, but it can be done.
Yeah, it seems I can still install SCOM faster by hand *grin*.
I will probably have more lessons learned soon, but thought to post this set first.
Update 7 May 2013: Lessons learned addendums to Lessons 2 and 4 are posted in the post "SCOM 2012 SP1 command line install lessons learned update 1". The update to lesson 4 contains additional switches to manipulate the database file paths!
First of all my apologies to all non-Dutch readers of this blog. A part of this posting will be in Dutch since it’s mainly targeted at the Dutch audience. It’s is all about a new User Group in the Netherlands, Windows Management User Group Nederland (WMUG).
WMUG is founded by Marnix Wolf, Peter Daalmans, Kenneth van Surksum and myself Bob Cornelissen. WMUG is aimed at everything involved with managing IT environments based on Microsoft technology. WMUG will serve as a platform for everyone involved with Microsoft technology. Besides the Microsoft technologies there is also room for other mainstream technologies like VMware and Citrix to name a few. It also creates the possibility not only to attend sessions but also to present sessions on topics people excel in. So WMUG is all about the community and for the community.
With the user group we want to provide a platform for and by people involved with managing the Microsoft Windows platform. Our first session will be held on the 22nd of May this year.
Nieuwe gebruikersgroep ziet het levenslicht
Op 22 mei zal de eerste bijeenkomst van de Windows Management User Group Nederland (WMUG NL) plaatsvinden. De WMUG NL zal zich richten op alles wat met het beheren van Microsoft Windows te maken heeft en wil een platform bieden voor iedereen die zich met het management van Microsoft Windows bezig houdt. Of je nu kennis wilt delen door evenementen bij te wonen of tijdens een evenement een presentatie wil houden, de WMUG NL biedt het platform.
Wat kan je van de WMUG NL verwachten?
Periodiek zal de WMUG NL bijeenkomsten in Nederland organiseren, tijdens deze bijeenkomsten zal het laatste nieuws en specifieke kennis over een product met de aanwezigen gedeeld worden. Natuurlijk zijn de avonden interactief zodat u uw ervaring ook met de aanwezigen kunt delen. Tevens zal de WMUG NL webcasts en een Nederlandstalig forum hosten.
Over wat voor producten wordt gesproken?
De focus van de WMUG NL beperkt zich niet alleen tot Microsoft producten zoals de System Center 2012 suite, de Windows familie en de virtualisatie oplossingen van Microsoft. Wij willen juist ook de combinatie maken met andere producten van bijvoorbeeld VMware en Citrix, denk dan aan VMware ESX of Citrix XenServer als virtualisatie platform ten opzichte van Hyper-V.
Wie of wat is de Windows Management User Group?
WMUG NL ben jij! Opgericht door een viertal actieve community leden, wil je echter meehelpen om dit nieuwe platform tot een succes te maken neem dan gerust contact met ons op, je bent van harte welkom! Want zoals gezegd, de community is er voor iedereen.
Hopelijk zien we je tijdens ons eerste evenement, je kunt je hier inschrijven. Wees er snel bij want de beschikbare plaatsen zijn beperkt. Meer informatie over ons eerste evenement op 22 mei vindt u hier.
Neem contact op via firstname.lastname@example.org
We hopen u tijdens onze eerste bijeenkomst te ontmoeten,
Kenneth van Surksum
This user group is for the community and by the community!
A few days ago Microsoft uploaded some updated SCOM 2012 tools.
The first one is the monitoring pack for Java EE. The Second is the Operations Manager Sizing Helper.
Here is an excerpt of the downlaod page with a description:
The downloads can be found over here:
System Center 2012 - Operations Manager Component Add - On
I have been off the blog for a few weeks due to visiting the MVP Summit 2013 last month and being sick for a few weeks. I am almost OK though, so starting to get back to all this as well.
Right before the MVP Summit my friends at Savision asked me if I would write something about the MVP Summit 2013 this year. Of course a lot of what is actually told and shown during the MVP summit is NDA (non disclosure agreement, so secret). However I did write up a piece during and right after the event and Savision posted it over here:
For all those who want to know what it is about, just have a look and gain a little insight.
My good friend and MVP Kevin Greene put out a blog post here with details on how you can win a copy of Mastering System Center 2012 Operations Manager by downloading and evaluating System Center. Look here for his blog post.
In the case you have done a clean install of SCOM 2012 SP1 you might want to take a look at the file names of the OperationsManagerDW database and log files. They might look like this:
So empty names for the files and ending up with ".mdf" and ".ldf" for the file names.
However, my good friend Marnix Wolf also found that when using custom database and log file paths, the file names can take on the name of the directory they are in!
In the Release Notes of SCOM 2012 SP1 this known issue is mentioned (well, at least the part where the file names can be empty):
There are multiple ways to overcome the issue, and it would be best to solve this right after installation of the first management server before you install the other management servers.
One of the ways to fix this is to "Detach - Rename - Attach" the database. I will describe this process below with screenshots and all for those who like the step by step guides.
First of all some work before we get started:
- BACKUP your database before you play around with it!!
- Stop the System Center * services on the management servers before you do the next steps
- Perhaps you want to make sure where your database files live, because you want to be able to find these files. Open SQL management studio. Right-click on the database OperationsManagerDW and select Properties. On the left click the "Files" tab and find the Path and File Name of the database. Remember these.
This procedure uses the Detach - Rename - Attach method.
- Open SQL Management studio and connect to the database instance where the SCOM databases live.
Find the OperationsManagerDW database and right-click it. Go to Tasks - Detach...
- If there are still any connections just use the "Drop Connections" option
- After a succesful detach the database will be gone from the SQL management studio.
- Next go to the Windows Explorer and on your file system find the database files and rename them to what you want them to be called. In general the default would be OperationsManagerDW.mdf and OperationsManagerDW.ldf .
- In SQL management studio, right-click on Databases and select Attach...
- Click the Add button to select the database file.
- Select the mdf file belonging to the OperationsManagerDW database in the file path where it lives
- The resulting screen shows some information on how it wants to attach the database and information about the files. There are a few problems in this screen (red circles). The first is the Owner might not be the one you want and the second is that it can not find the two files it expects.
- To change the owner just click on that field and a dropdown list will appear where you can select from known logins and take the one you want.
- Next we have to go to the Not Found files. This is because the database file knows which files it relies on (at least one database file and one log file) and it only knows about the old file names in the old file paths. So we need to change both and point them to the correct files. The first one points to the database file (mdf), so click the small button next to it.
- Go to the correct path where the database file is located and select the database file OperationsManagerDW.mdf in my case.
- Next do the same with the second file and point it to OperationsManagerDW.ldf for the log file.
- Now attach the database
- when opening the properties of the OperationsManagerDW database and going to the Files tab you will now see the correct paths and file names for both files belonging to this database.
- Do not forget to start the System Center * services again on the management servers!
The management servers and databases should be fine now.
Like I mentioned before my friend Marnix Wolf used another method and that is the backup - Restore method, whereby you can define the path location and file names of the files. You can find that post here: http://thoughtsonopsmgr.blogspot.nl/2013/01/om12-sp1-known-issue-data-warehouse.html.
Thanks to our SQL DBA David Scheltens for the procedure!
Well, I hope this helps and enjoy your monitoring!
Because Microsoft released CU7 for SCOM 2007 R2 in January 2013 as explained in a previous post about this subject, it was time to also update the checking scripts I had made before for CU5 and CU6 and make them work for CU7.
As I explained in the previous post on how to check for CU5 installation on SCOM 2007 R2, the way to check for successfull implementation of Cumulative updates has come up as questions in the community a number of times and I found a need as well to have this scripted. So I created a number of scripts for SCOM 2007 R2 CU5 which I discuss in the other blog post here. The method for CU7 is exactly the same as mentioned in that article with two differences.
- The names of the scripts are with a 7 in it
- scripts are located on another TechNet Gallery page (see below for the link)
Refer to the post on CU5 check scripts for SCOM 2007 R2 on the procedure and screenshot.
This is the link to the TechNet Gallery page where the CU7 check for SCOM 2007 R2 is located.
Good luck and enjoy!
Microsoft released SCOM 2007 R2 CU7 last night.
The relating KB article can be found here: Cumulative Update 7 for System Center Operations Manager 2007 R2 http://support.microsoft.com/kb/2783850/en-us
The update contains the following fixes (and this is a screenshot from that KB article):
Also interesting to note is that there are a few security vulnerabilities for SCOM 2007 R2 fixed within this CU7 as you can find explained over here: http://technet.microsoft.com/en-us/security/bulletin/ms13-003
Please pay close attention to the installation order and steps as described in the KB article. It is basically the same story as CU4+5+6 for the ones informed on the process of those.
Funny things this System Center 2012. As you probably know by now Service Pack 1 for System Center 2012 is available for some, but not yet in GA (General availability) status. Expecting that to be soon, and please watch for announcements on the System Center blogs... I really will not tell you anything more than this.
However last night some people found with the WSUS/SCCM updates of this months patch-Tuesday a number of additional updates called something like Update Rollup 1 for Microsoft System Center 2012 SP1 - [product] (KB1111111).
Say what? UR1 for SP1 already?
Yes, it has to do with the quarterly cadence of updates coming from the System Center team. Even though the SP1 is not yet available to everybody, of course the product team is moving forward.
If you do not see all these updates yet in WSUS and are applicable to you check in your WSUS server settings.
In WSUS go to Options -> Products and Classifications. In the popup scroll down to the System Center products. Here you will see both the System Center 2012 and System Center 2012 SP1 type of product categories.
As you see in my case I still needed to select them and synchronize again to get to see all the updates related to SP1 as well.
And now we see a list of updates released 8 January 2013 relating to System Center 2012 and up.
The following KB article contains the Description of Update Rollup 1 for System Center 2012 Service Pack 1.
In the Article there are fixes describer for App Controller + DPM + SCOM + SPF + VMM.
Interesting is that it talks about UR1 for VMM 2012 SP1 and in WSUS it shows both that one and UR4 for VMM 2012. Not all links to all the KB articles seem to be active or available yet. Well perhaps its just waiting for a few hours/days more until all the info is up on TechNet.
The article also contains important information on how to install the updates and where to find stuff. Do not think that for all products you simply need to approve stuff in WSUS and be ready with it! As SCOM is still my main thing I will post a note below for SCOM admins. Check in the article for extended notes for SCOM and other products!!!
Note for SCOM admins: After installing the update on management servers, gateways, web console and agents and so on, you need to import the new management packs! These are according to the KB article the following: (By the way, please read further below first before you start clicking on things)...
You can find them in the following location:
%SystemDrive%\Program Files\System Center 2012 SP1\Operations Manager\Server\Management Packs for Update Rollups
However, I found the following two mpb management packs to be present in the mentioned folder (and in my case the folder name did not have SP1 in the path name):
And these also sound more like the mentioned issues actually.
Update 23 January 2013: The KB article seems to have been adjusted. It now mentions to only install the Microsoft.SystemCenter.AlertAttachment.mpb management pack! The IntelliTrace management pack contains a number of dependencies that seem to be as yet impossible to resolve and I read somewhere that it would actually contain nothing new over the version included in the SP1 bits. So only import the one mpb file!
For UNIX/Linux monitoring there are also updates. You can find them by going to this location: http://www.microsoft.com/en-us/download/details.aspx?id=29696 and download the MSI and guides.
Install the MSI to extract the contents. You will find updated Microsoft.Unix.Library management pack in the Microsoft.Unix.Library\2012 SP1 folder and the Microsoft.Process.Library management pack bundle and platform library management packs that are relevant to the Linux or UNIX platforms you are monitoring which you can import.
Good luck updating your System Centers!