Wow, these images have issues…
Firstly, Server 2008 is not activated. This is not a huge deal as you can use the images for 60 days before needing to activate the OS and you can rearm the activation period several times which you must do since MS will not give a 2008 license for courseware. See below for how to do it:
http://support.microsoft.com/kb/948472
The major issue is SQL 2005 which has a 120 day evaluation copy that was installed last July. I have not really wrestled with backdating but I believe that would need to be done at the BIOS level before turning on your VMs and that has it's’ own set of complications…
How to fix?
Well, SQL 2005 cannot be upgraded from evaluation copy to full release based on my research. It must therefore be uninstalled and a full release installed. You are out of luck if you have no access to licensed software.
You must back up your SCOM databases BEFORE reinstalling. These are (OperationsManager, OperationsManagerDW and associated logs). You cannot backup the DBs with SSMS, you need to work with the files so take appropriate steps (stop SQL services, etc).
Forget about backing up the ReportServer and ReportServerTemp DBs or the configuration for SQL Reporting services since that (SRS) is also time bombed. I tested backing these databases up and restoring them to the new full release but there are DB versioning issues anyways so don’t bother…
Once SQL has eval has been uninstalled and full release installed, I ran into WMI exception issues working with the SRS Config utility and needed to service pack the entire installation to get this working right.
Now, configure SRS and get that working right: http:localhost/reports and http://localhost/reportserver need to work fine…
When done, restore your backups of the DBs and start SQL. You should be mostly good except for SCOM reporting.
After the restore, I ran into an issue with the SQL broker not enabled (which I have frequently seen when I need to move the OperationsManager DB). Use the post below to fix that issue:
http://scug.be/blogs/scom/archive/2008/11/22/the-sql-server-service-broker-for-the-current-opsmgr-database-is-not-enabled.aspx
Lastly, you will have an issue with the reports populating, to fix that, reinstall ONLY the SCOM reporting piece…
In SCOM 2007 R2 at least ( I don’t remember if it was like that before) the Data warehouse and SCOM reporting pieces are split as separate elements which you install when you run OMSETUP.EXE and choose to install SCOM reporting.
Once that is done (no reboot required) you should be off to the races!
Of note: I would like to thank Islam Gomaa and Edwin Sarmiento for their part in saving me time and helping me with some of the more tedious issues. These are my resident SQL experts!
I know I skipped a bunch of steps. For instance, I had rights issues reinstalling SRS and a heck of a time reinstalling SQL but I have been fighting with this issue for 4 days to get it working so I don’t remember all of the smaller steps. If someone wants to leave a comment with the missing steps, I would be grateful…
Happy hunting!