You are browsing the archive for SCE 2007.

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 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



SCE 2007: Agent deployment issues

6:55 pm in Uncategorized by mikeresseler

Hey All,

Today I was with a customer and they told me that the system administrators weren’t able to deploy an agent to a certain workstation.  This workstation was just deployed clean with MDT.

The error they got is the following:

The MOM Server could not start the MOMAgentInstaller service on computer <computername> in time

Also, I received error 80070102.

Since I never saw this error, and the logs didn’t really told me a lot, except somewhere in the installation log file that the firewall exceptions couldn’t be made.

This was quite strange since I deployed the firewall exceptions through GPO (it is not only for SCE so I used 1 GPO for all firewall exceptions).

So I started surfing on the net for solutions.

Not much info there, but finally I came across a blog post from Kevin Holman

Ok, since this was one isolated case, I could have gone to the user and installed it manually, as many people advised on the internet, but since I’m quite lazy I didn’t feel like it.

According to Kevin, and I quote:

Sometimes – the Windows Firewall service – even if disabled – will have a stuck rule. Run: (netsh advfirewall firewall delete rule name=”MOM Agent Installer Service”)

So I fired up psexec from my workstation and checked if this could be true.  And yes, there was a rule that called Mom Agent Installer Service.

Since the program wasn’t installed, it was not necessary so I used the command to delete the rule.

Tried the remote installation again, and it worked.

Thanks Kevin :-) I didn’t had to leave my chair today



SCE 2007: Monitor ISA Server 2004 or 2006

8:57 am in Uncategorized by mikeresseler

Hey All,

Last week I was working on a system center essentials 2007 project.  One of the things that had to be done was placing an agent on the ISA server, that was residing in a DMZ zone.

So a few thing had to be done:

1) Work with the certificates to ensure communication between the SCE server and the ISA server.  (I followed the great manual from

2) Make sure that the SCE server’s security is changed so that it can Review new manual agent installations in pending management view. (under administration, settings, server, security, properties)

3) Manually install the agent on the ISA box.

4) Create the access rules for the ISA firewall to allow the traffic to the SCE server.  Ports are:

  • 5723 healthservice
  • 8530 updateservices
  • 8531 updateservices
  • 51906 AEM (if applicable)

5) Tadaa, it should work.

Unfortunately, it didn’t.  After investigation, I found out that one of the servers refused a certificate that I just created.  Hmmm, not good, so I decided to do the whole thing again.  After that, again, the same error.

Because I did this before with the manual, I decided to delete the certificates that I created the first time, and then restarted the health service.  And now everything worked.  One important thing learned.  Remove the old certificates before starting over again 😉