You are browsing the archive for 2010 June.

Upgrading SCE 2007 to SCE 2010 … the long story part 4

6:13 pm in Uncategorized by mikeresseler

Hey All,

After a rather long upgrade, a disaster OS upgrade, an easy prerequisites flow and an almost flawless SCE upgrade in the end, I’m happy to say that everything is running again.  Next stop will be the upgrade of all the agents, but if I have issues there, I will post them separately.

Before I end this post series, I would like to give my conclusion:

1. Make sure you are prepared.  Upgrading an Windows Server 2003 R2 64-bit physical server to Windows Server 2008 R2 64-bit wasn’t that easy after all.  Even taking everything in consideration, doing the assessments etc… seemed not to reveal possible issues.  So be aware and make sure that you have a very good, tested, backup of your server.

2. Never upgrade your OS to 2008 when it is still 2003 server on it.  I made the mistake by thinking that I had to do that just because otherwise I couldn’t install the virtualization component.  I learned afterwards that you can add that as a separate component.  By the way, Microsoft, I also didn’t read that on your upgrade technet page, which can be better anyway because there is not much to find there 😉

3. Don’t forget to change the config file otherwise you will have issues when he validates your reporting services.

So, if I ever need to do an upgrade again, I will keep my workflow from post two but adapt it so that the upgrade process of SCE 2010 comes first, then the OS upgrade and finally the Virtualization component installation.  This will give me much less issues.  Second thing I have learned, when your OS upgrade fails, and windows detects it, you can do a rollback to the original state which is pretty cool.  And by the way, it actually works because we had to do that 2 times (not that you have a choice at that moment but hey… who’s complaining).

If you only consider the SCE upgrade, you can say that the team did a good job (well at least at first sight) and that I only had one small problem which it told me during the installation wizard so I can’t complain there.

The next post or posts will be about possible issues that I have encountered and the solutions (hopefully) for them. So if I am lucky, I won’t be posting anymore :-) And otherwise

Till then


Mike Resseler

Upgrading SCE 2007 to SCE 2010 … the long story part 3

6:11 pm in Uncategorized by mikeresseler

Hey All,

Part 3, the actual upgrade.  After a lot of issues with the OS upgrade and the easy part for the prerequisites and “pre-jobs” it is time for the real upgrade.

Before I describe the attempt that actually worked, I should mention that I had also an issue.  During the installation wizard, I got this error:


Unable to use HTTP site from the http://servername:80/Reportserver_instancename Internet Information Services (IIS) node. Please select HTTPS binding

This was easily fixed, I had to change the following line in the rsreportserver.config to Value=”0” coming from value=2


I already started to feat that this would become the same as an OS upgrade, but after that, everything went fine, so here is the installation procedure.

Start SetupSCE.exe (for your information, and because of bad experience, I opened a command prompt as administrator and ran SetupSCE.exe from there…)


Choose Install and make sure that you choose Download the latest updates to System Center Essentials 2010 during setup.  I advice this because the customer I did this for downloaded the RTM version a day after it appeared on their volume license site and yet it already downloaded an update



So next window says it has detected an existing SCE installation and asked if it wanted to upgrade.  Yep, that’s the idea so let’s go for it



Next screen the username, organizaton and serial key.


The Microsoft license agreement.  I accept (do we ever have a choice :-))


The installer is now checking for the prerequisites


Now the system wants to know on which database it needs to be installed.  It shows me actually two database instances on that server which is normal since I have my running 2005 environment for SCE 2007 and installed an 2008 instance for the upgrade.  You can also that the 2005 instance can’t be chosen so I need to work with the 2008 instance.  (Not that I ever was planning on trying out the 2005 instance in a production environment but in a test environment I probably would be tempted :-))


Next up, select the reporting instance.  Selected the new reporting instance that I installed earlier on so that’s also ok.  When you press Next he will start validating that and here I got the error I described above and I think it is rather good that the essentials setup checks already here for possible issues.



The setup asks me for the management account credentials.  Since I already have a management account in 2007, I need to use the same one.  So remember that if you have forgotten your password :-)

And finally you get the configuration overview and then you can start the installation.  Note that you can make changes to your decisions on this page.



Here he is started.

Some time later (it was pretty fast, but takes more time then a new installation as he has to copy the databases from the SQL 2005 to the SQL 2008 instance and so on)


So, I left the checkbox on to open the console to see if everything was running and that seemed no problem.

Next step: Install the virtualization component

So I started the SetupSCE.exe again (yep, again from the command prompt) and choose Install again.  Then the next page popped up


So here I choose Add a component


The system shows me Virtualization and Reporting.  I already installed reporting so that’s grayed out but I can install the Virtualization Management


No choosing for an instance this time, and also check that it requires 7 GB which is quite a lot


Here he is asking me for the location where (in the future) the templates should be installed.  So I choose a directory on a volume and went Next


Review time and install




Opened the console and yep, everything running.

The last thing I did was reran over all the prerequisites I had done and changed them again.  I re-enabled the subscriptions but did not imported the management packs again but that is for another post.

Next step: My conclusion


Mike Resseler

Upgrading SCE 2007 to SCE 2010 … the long story part 2

6:05 pm in Uncategorized by mikeresseler

Hey All, after part 1, here is part 2.

So in the last part, I finally got a working SCE 2007 on Windows Server 2008 R2.  I know this has nothing to do with System Center Essentials, but it learned me something very valuable.  First upgrade SCE 2007 to SCE 2010, and then do the upgrade to windows server 2008 R2 :-).  But anyway, I got through and now I looked at all the things I needed to do before starting the upgrade from SCE 2007 to SCE 2010

So here is the flow I’ve used (this includes hw and sw compatibility checks but as said, the flow will need to change for the next time)



Removing incompatible management packs

I removed the the Windows Vista Management pack (Microsoft.Windows.Client.Vista.MP) and checked if KB960569 was applicable for me.

Take backups

Then I opened the SQL 2005 management studio and took backups of the following databases:

– OperationsManager

– OperationsManagerDW


Backups of the certificates

According to the technet documentation, I also had to take backups from the certificates so I did:

From technet:

· To back up the WSUS code signing certificate, on the taskbar, click Start, and then click Run.

· In the Run dialog box, type mmc, and then click OK.

· In the Console1 window, click File, and then click Add or Remove Snap-ins.

· In the Add or Remove Snap-ins dialog box, click Certificates, and then click Add.

· In the Certificates snap-in dialog box, select Computer account, and then click Next.

· In the Select Computer dialog box, make sure that Local computer: (the computer this console is running on) is selected, and then click Finish.

· In the Add or Remove Snap-ins dialog box, click Close.

· Expand Certificates (Local Computer), expand WSUS, and then click Certificates.

· Right-click WSUS Publishers Self-signed, point to All Tasks, and click Export.

· Complete the Certificate Export Wizard, choosing the option to export the private key, and then save the exported file to a safe location.

· To back up the Certificates folder, go to the System Center Essentials 2007 installation folder (usually C:\Program Files\System Center Essentials 2007) and copy the Certificates folder to a safe location.

Disable subscriptions

I’m not sure why this is necessary, but considering the fact that I already had some serious problems with the upgrade process of the OS, I decided not to take any risk.

I went to the administration node in the Essentials console and disabled all subscriptions.

Last but not least: SQL 2008 WITH SP1

The previous essentials is running on SQL 2005 so I needed to install SQL 2008 with SP1 before I could start the installation.  Please note that this is not necessary when you are running SQL 2005 express edition.  Then the installer will create an SQL 2008 express edition instance himself.

So I installed SQL 2008 SP1, again according to the Technet article with only the database engine and reporting engine.

So, in the next post, I’ll be doing the actual upgrade.

Now, this part was already much easier :-)


Mike Resseler

Upgrading SCE 2007 to SCE 2010 … the long story part 1

6:20 am in Uncategorized by mikeresseler

Hey All,

The last weeks I had to work on an upgrade from SCE 2007 to SCE 2010.  I had a lot of issues with it so I wanted to give them here so that you can avoid them if you need to do that

The situation

SCE 2007 is installed on a windows server 2003 R2 x64 physical box.  Because we wanted to use also the VMM part of SCE, we needed to upgrade the server.

So here was the plan I’ve built:

    1. Do a complete assessment (including MAP) of the server and all the software components.  This was not only a SCE box, but also the MDT 2010 box, Lenovo Update box… In other words, a complete management server
    2. Created the upgrade plan for the server to Windows server 2008 R2
    3. Created the upgrade plan for SCE 2007 to SCE 2010

On paper, this looked good :-)

After the MAP assessment, we did some firmware upgrades, removed some non compatible software, placed the drivers of the physical server to the latest available, and finally started with the upgrade.

Problem #1:

We started the upgrade, and find out that the Adaptec Storage software needed to be removed…

Huh? We already removed that because we saw that in the MAP assessment.  Quick look to Add/Remove programs learned us that it was indeed removed. (Started to doubt about myself here ;-))

After quite some time searching, we discovered that the uninstall left one .dll file in the drivers repository of windows.  After manually deleting that driver (actually we renamed it ‘just to be sure’) we could continue with the upgrade.

So we started the upgrade and after the reboot….

Problem #2:

Windows cannot continue because a few drivers are not signed (or something like that).  The good thing here is that you can revert if you want, getting back your original system.  So after a few tries… one of the colleagues said that he knew a way to fix that.  He booted on a winpe cd, went to the c: drive, extracted all the drivers out of a cab file to the windows drivers directory, rebooted, and there you go, everything signed… Well, still don’t know exactly what happened there but hey, I was getting closer to upgrade my SCE. 

Problem #3:

SCE console didn’t start anymore.  Huh? Let’s check the services and yes, services are not started.  Manual start?  Nope, stops immediately with errors.  So, still no upgrade now because I still needed to do the upgrade pre jobs.

After a long time of searching, I finally found out that doing an inplace upgrade from Server 2003 to Server 2008 with SCE 2007 is actually not supported.  Even on the forums I only got answers such as: I reinstalled, recovered etc… Now that wasn’t a plan I liked so I continued to search and suddenly found a clue, where somebody said that there were some dll’s that needed to be “reinstalled” … So here is what I did:

InstallUtil /i Microsoft.Mom.ConfigService.dll
InstallUtil /i Microsoft.Mom.Sdk.ServiceDataLayer.dll
InstallUtil /i Microsoft.Mom.DatabaseWriteModules.dll
InstallUtil /i Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll

And that worked. 

So after a lot of issues, I was ready to do the next step in the plan… Doing the prerequisite tasks… But that’s for next post

Till then