I went about doing this today and to be honest, the instructions are non-existent.Â You’ll need a bunch of updates.Â Note that the hotfix rollup includes X64 and X86 updates and there are individual downloads for the x86 and x64 versions on the other KB’s.Â Here’s how you can get an Operations Manager 2007 agent working on W2008:
- Download and "install" KB954049 (a hotfix rollup).Â This "install" is a messy extraction.Â Note where it installs and copy the contents to somewhere safe.Â You can "uninstall" the hotfix now.
- Upgrade all of your OpsMgr server components to service pack 1.
- Install KB951116, KB952664, KB953290 onto the W2008 server that you want to install an agent on to.
- Reboot the destination agent server.
- Install the OpsMgr Agent.Â Make sure it is the SP1 agent!
- Stop the OpsMgr Health Service.
- Browse to where you saved the contents of KB954049.Â Install the update.
- Restart the server.
Your agent should now be able to communicate with the management server assuming that all the security side of things is OK (the same rules apply).
You’ll also find that you need to install the Windows Server 2008 Discovery Management Pack in order to be able to manage the OS on these new servers.Â This management pack also appears to be a pre-requisite for role/feature management packs for Windows 2008, e.g. you’ll be unable to import those other management packs.Â This is probably quite logical, i.e. there is a discovery dependancy for Windows Server 2008 objects.
Note that there’s a 4th fix (KB951327) required for any machine running a OpsMgr console on Windows Server 2008.
This is all a very manual thing.Â You can probably script this pretty easily.Â If you have System Center Configuration Manager 2007 (SCCM / ConfigMgr) or SMS then you can create a sequence of package programs with prerequisites to take care of this for you.Â I’ve an example of this in my SCCM 2007 beta whitepaper on software management.
Remember that Windows Server 2008 has its firewall turned on by default and that it blocks both inbound and outbound traffic.Â You’ll need to configure rules to allow your required traffic (e.g. TCP 5723) either manually, by script or by Group Policy.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
No related posts.