OpsMgr, SCE And MOM Blog : Hotfix for Essentials 2007

Operations manager 2007 Sp1 / Essentials 2007 SP1 support for windows server 2008 announced

CliveEastwood — Sat, 26 Jul 2008 03:19:37 GMT

Windows Server 2008 support has been announced. Please see the following resources for more information

The Knowledgebase article KB953141 announces our support of OpsMgr SP1 and SCE SP1 running on Windows Server 2008

The above article discusses 4 required Windows Server 2008 hotfixes which may have to be installed depending on the OpsMgr/SCE role installed on Windows Server 2008

The above article also provide a link to a required OpsMgrSP1/SCESP1 hotfix rollup which is described in Knowledgebase article KB954049

The hotfixes referenced are all available from the Microsoft download center.

The Support Configurations details for Operations Manager 2007 SP1 have been updated to reflect supported Windows Server 2008 roles http://tnstage.dns.microsoft.com/en-us/library/bb309428.aspx

Management Pack Releases for Windows Server 2008 will take place shortly.

The hotfix provided in KB954049 can be installed on localized OpsMgrSP1/SCESP1 installations as it does not provide any localized fixes. The hotfix MSI installer is currently provided in English, localized versions will be provided in the coming weeks.

NOTES:

Please take careful consideration of the OpsMgrSP1/SCESP1 installation notes within KB954049 , particularly:

The OpsMgrSP1/SCESP1 hotfix must be applied after installation of OpsMgr/SCE on Windows Server 2008 or after in-place upgrade of the OS to Windows Server 2008 of an affected OpsMgr/SCE role. This will ensure correct performance counter registration on RMS, SCE Server, Management Server, Gateway server roles.
If User Account Control (UAC) is enabled on Windows Server 2008 when you apply the OpsMgrSP1/SCESP1 hotfix, you MUST execute SystemCenterOperationsManager2007-SP1-KB954049-X86-X64-ENU.MSI from an elevated command prompt. Failure to do so will not allow the display of the hotfix applicaton dialog once the MSI has completed installation of the staging bits on the server.
Read carefully the Known issues section of KB954049. There are a number of requirements and known issues, several still under investigation (Issues 6/7). As more information on Issues 6/7 becomes available and hotfixes developed the KB article will be updated and details provided.

New Knowledge Base articles for Operations Manager 2007 / System Center Essentials 2007

CliveEastwood — Fri, 22 Feb 2008 23:32:48 GMT

Finally we have some content released I've been waiting for (better late than never). The KB article 944443 (List of issues that are fixed in System Center Operations Manager 2007 Service Pack 1 Release Candidate) will be updated shortly (crossing my fingers - not under my control) to reflect the list of changes in Service Pack 1 RTM. I'll post the fixlist separately as SP1 will likely hit the Web before the article gets re-published (not my fault, honest). (Yes, SP1 RTM is close, very close!)

KB948069 - Error message when you try to run reports in System Center Operations Manager 2007: "Cannot open Database 'OperationsManagerDW' requested by the login" - http://support.microsoft.com/kb/948069

KB939769 - You experience a delay in fetching "Actions for Tasks" and "Actions for Reports" for a selected row in System Center Operations Manager 2007- http://support.microsoft.com/kb/939769

KB941307 - A health monitor may display state changes in an incorrect order in System Center Operations Manager 2007 - http://support.microsoft.com/kb/941307

KB938507 - Report scheduling fails in System Center Operations Manager 2007 when the regional settings on the client computer differ from the regional settings on the server - http://support.microsoft.com/kb/938507

KB940224 - The Optimized Performance Counter Collection rule collects multiple values of 0 (zero) in System Center Operations Manager 2007 - http://support.microsoft.com/kb/940224

KB941943 - The HealthServiceStore.edb file size grows to several gigabytes over time in an agent that is running System Center Operations Manager 2007 - http://support.microsoft.com/kb/941943

KB938510 - You cannot obtain elevated user rights in management servers and in agents in System Center Operations Manager 2007 or System Center Essentials 2007 environments - http://support.microsoft.com/kb/938510

KB943111 - Description of System Center Essentials 2007 post-release hotfix rollup

CliveEastwood — Fri, 12 Oct 2007 01:25:14 GMT

Here is the KB article referencing the recently released hotfix rollup for System Center Essentials 2007 http://support.microsoft.com/kb/943111/en-us

Also see my previous post on the subject here http://blogs.technet.com/cliveeastwood/archive/2007/09/28/system-center-essentials-post-rtm-hotfix-rollup-released-to-the-web.aspx

System Center Essentials post RTM Hotfix Rollup released to the Web

CliveEastwood — Sat, 29 Sep 2007 01:14:00 GMT

In an aid to specifically resolve the issue http://support.microsoft.com/kb/936481/en-us (The installation of System Center Essentials 2007 fails during the Reporting part of Setup and the following information is logged: "The specified domain does not exist or cannot be contacted") in which the whole installation of System Center Essentials 2007 will roll back (fail), and to allow address several other top issues (see below), a hotfix rollup package has been released and is available here http://www.microsoft.com/downloads/details.aspx?FamilyID=c9f977e4-d26f-4038-88b7-b70b13aa8e3d&DisplayLang=en

What specifically this rollup package fixes:

936481 You cannot install the System Center Operations Manager 2007 Reporting feature in a disjointed namespace environment
936339 Windows-based computers are not displayed in the Network Topology diagram view in System Center Essentials 2007, and WSUS component parts fail on the Essentials 2007 agents after you deploy the agents
937467 Update files not getting downloaded to the Essentials 2007 server when importing updates from a partner catalog

More information on the rollup package will be available shortly in the form of a KB article which, when available (I'll post an update here), will be on http://support.microsoft.com/943111/en-us

Does the hotfix rollup apply to you?

If you already have Essentials installed this hotfix rollup does not apply to you.

If you already have Essentials installed and you experience the symptoms referred to in KB936339 or KB937467 please refer to those KB articles on how to obtain the hotfixes separately so that you can apply them in your environment.

If you currently don't have Essentials installed and believe you will be affected by symptoms referred to in KB936481, KB936339 or KB937467 then this rollup package can certainly help you.

Also for those users registering to download the 90-day evaluation version here http://technet.microsoft.com/en-us/bb738028.aspx , the English downloads (aka US English) include a download of the rollup.

Can this hotfix rollup be applied to a SCE localized version?

Yes it can. However, you will have to download the rollup package from http://www.microsoft.com/downloads/details.aspx?FamilyID=c9f977e4-d26f-4038-88b7-b70b13aa8e3d&DisplayLang=en if you intend using the 90-day trial version and my be affected. The hotfix rollup UI is also not supplied in a localized version.

How do I install the System Center Essentials 2007 Hotfix Rollup?

Firstly, as mentioned this applies to a fresh install of SCE. If you have SCE installed don't continue from here unless you plan on installing another SCE environment in a situation where you will need this rollup.

Requirements:

Have a copy of the original source SCE media available to you on the proposed SCE Management server computer (best to map a drive to a network resource where it is located or have it available on DVD. Do not have it located on a local hard drive which will be the same drive the rollup package will create a patched version to.)
Have a copy of the SCE hotfix rollup package available locally on the proposed SCE Management server computer.

What does the hotfix rollup do?

The hotfix rollup package SCE2007RTMHotfixRollup.exe when executed will unpack its hotfix payload to a folder beneath the current users Temp folder and then present the following UI.

When using the Browse buttons make sure you select a source and destination which are different drives. The utility will not allow the source and destination hard drive for example to contain C:.

The "Select Essentials 2007 RTM media location" is a mapped network drive or local DVD media location (or a local hard drive which will not be the same as the "Select local directory.... option"

The "Select local directory to copy Essentials RTM media" is a local hard drive directory (empty) where the entire source media will be copied. When "Apply QFEs and start setup" button is clicked the source folder and file structure is copied to the destination folder and then the first of the hotfixes KB936481is applied to the destination (required because this is a patch to the reporting msi in order to install SCE in a disjointed DNS namespace). System Center Essentials 2007 Setup is then executed and you can begin the installation of SCE. During the installation the other two hotfixes will be applied automatically by the Setup infrastructure.

Once installation has completed successfully the directory chosen as "Select local directory to copy Essentials RTM media" can be removed.

Can I use the new media folder created as a result of the rollup package be used to install other SCE servers?

Yes, and No :)

If the destination folder is copied to DVD, network, etc for use in installing other SCE servers, note that only the hotfix for KB936481 will apply when installing using the updated media (ie. you can install in a disjlointed DNS namespace). Due to the way the other hotfixes are applied during Setup if you need them installed at install time run the hotfix rollup on the indended Management server itself. You can of course install the other two hotfixes after install (you can obtain them separately, or on the machine that SCE2007RTMHotfixRollup.exe was run the installing users %TEMP%\IXP0000.TMP folder will contain the MSI's).

KB936339 - Windows-based computers are not displayed in the Network Topology diagram view in System Center Essentials 2007, and WSUS component parts fail on the Essentials 2007 agents after you deploy the agents (System Center Essentials)

CliveEastwood — Fri, 31 Aug 2007 07:22:01 GMT

KB936339 Windows-based computers are not displayed in the Network Topology diagram view in System Center Essentials 2007, and WSUS component parts fail on the Essentials 2007 agents after you deploy the agents has been released and is available http://support.microsoft.com/kb/936339

A hotfix for System Center Essentials 2007 is available for this problem.

The hotfix may be requested via online submission via http://support.microsoft.com/kb/937470/en-us

Essentials 2007 Hotfix for KB937831 (The installation of System Center Essentials 2007 fails during the Reporting part of Setup and the following information is logged: "The specified domain does not exist or cannot be contacted") has been re-rel

CliveEastwood — Fri, 24 Aug 2007 20:47:32 GMT

If you previously requested, have, and successfully installed Essentials using the previous hotfix you do not need to request it again.

However, if you meet the following criteria the SCE installation can fail as discussed the article.

• You are installing a distributed installation of Essentials where the SCE Management server role and SQL Database role are on separate servers

• The computer on which you try to install Essentials 2007 has a domain suffix that does not match the fully qualified domain name (FQDN) of the domain. For example, the computer has a domain suffix of department.contoso.com. However, the domain is named contoso.com.

• The computer on which you try to install Essentials 2007 has a NetBIOS domain name that does not match the first part of the FQDN of the domain. For example, the NetBIOS domain name is CONTOSO-XYZ. However, the domain is named contoso.com instead of contoso-xyz.com.

The updated hotfix can be requested via the following link : http://go.microsoft.com/?linkid=6294451 using the KB article reference KB931831

Operations Manager 2007 and Essentials Hotfixes released to solve Reporting install issues covering: (1) Install failure when SDK account is Local System KB936219 , 2) Failure to install in a disjointed namespace

CliveEastwood — Fri, 25 May 2007 20:55:00 GMT

Two hotfixes have been released and are currently only available through Microsoft Customer Support Services (CSS). You will not be charged for the support incident.

System Center Operations Manager 2007 Hotfix details

The forthcoming KB article (unpublished at the moment) will be KB936481. When requesting the hotfix from CSS please mention that you are in need of the hotfix for KB936481.

Here are essentially the details that will be covered in the KB for installing the hotfix. NOTE: This hotfix does resolve two issues as in the title.

Summary
The computer's primary DNS suffix does not match the fully qualified domain name (FQDN) of the domain where it resides. For more information on identifying this issue please read http://technet.microsoft.com/en-us/library/aa998420.aspx.

Symptoms
Installation of Operations Manager 2007 reporting fails with the error message “The specified domain does not exist or cannot be contacted” in the setup log file found in the Temp folder on the computer on which you are installing Operations Manager 2007 reporting.

Installation
This hotfix must be applied to each computer that meets any of the following criteria:

Is a System Center Operations Manager Reporting Server

Is a System Center Operations Manager Root Management Server

To apply this hotfix, you must first:

1. Copy the file SystemCenterOpsMgr07-RTM-KB9356481-X86-AMD64-ENU.MSI to either a local folder or to an accessible network shared folder.

2. Run SystemCenterOpsMgr07-RTM-KB936481-X86-AMD64-ENU.MSI on each applicable computer that meets the predefined criteria.

3. On the computer where you plan to install the reporting server component, first copy Reporting2007.msi (RTM build 5000) to local writable disk; for example, the root or C:\ folder. The Reporting2007.msi file can be found in the reporting folder on the CD image. Copy the Reporting2007.msi file from either the i386 or amd64 folder, depending on which correctly matches your system architecture.

4. When the hotfix package is run, specify the location where the Reporting2007.msi file was placed. On the reporting server, run the VBscript file WiUseXfm.vbs with the full path to the reporting Windows Installer file as the first argument and full path to the .mst file as second argument. This can be done by opening a command prompt window and specifying for example C:\>WiUseXfm.vbs Reporting2007.msi ReportinXfm86.mst. For this example the VBscript, Windows Installer (.msi), and .mst files were placed in the C:\ directory

5. The Reporting2007.msi file size should have increased from 11,383 to 11,427 KB. Run this modified Reporting2007.msi which is on the local disk and installation should succeed.

6. NOTE: When specifying the target RMS Server it must be the Full Qualified Domain Name(FQDN) of the RMS Server for this modified version of the install to succeed.

This hotfix impacts the following installed files:

Microsoft.EnterpriseManagement.OperationsManager.dll

ReportingCAManaged.dll

ReportingCAManagedPac.dll

ReportingCAPack.dll

System Center Essentials 2007 Hotfix details

The forthcoming KB article (unpublished at the moment) will be KB937831. When requesting the hotfix from CSS please mention that you are in need of the hotfix for KB937831.

Here are essentially the details that will be covered in the KB for installing the hotfix. NOTE: This hotfix does resolve two issues as in the title.

Summary
The computer’s primary DNS suffix does not match the fully qualified domain name (FQDN) of the domain where it resides. For more information on identify the issue please read http://technet.microsoft.com/en-us/library/aa998420.aspx.

Symptoms
Installation of System Center Essentials 2007 fails with the error message “The specified domain does not exist or cannot be contacted” in the setup log file found in the Temp folder on the computer on which you are installing System Center Essentials 2007.

Installation
This hotfix must be applied to each computer that meets the following criteria:
Is a System Center Essentials 2007 Management Server.
To apply this hotfix for interactive setup, you must first:
1. Copy the file SCE07-RTM-KB937831-X86-AMD64-ENU to either a local folder or accessible network shared folder.
2. Run SCE07-RTM-KB937831-X86-AMD64-ENU locally on each applicable computer that meets the predefined criteria.

Note: You can run SCE07-RTM-KB937831-X86-AMD64-ENU from either Windows Explorer or from a command prompt.

3. During installation of the Windows Installer the following file is copied to the %temp% directory: Setup.exe.config.
4. During installation of the Windows Installer the following files are copied to the %temp%\TempQFE directory:
SystemCenterOpsMgr07-RTM-KB936481-X86-AMD64-ENU.MSI
qfelist.xml
SCE 2007 hotfix supplemental notice.rtf
QFEHandler.dll
5. Start Essentials 2007 setup normally using SetupSCE.exe.

To apply this hotfix for silent setup, you must first:
1. Copy the Essentials 2007 installation media to a writeable location, such as locally to the server you are installing Essentials 2007.
2. Copy the file SCE07-RTM-KB937831-X86-AMD64-ENU.MSI to either a local folder or accessible network shared folder.
3. Run SCE07-RTM-KB937831-X86-AMD64-ENU.MSI locally on each applicable computer that meets the predefined criteria.

Note: You can run SCE2007SCE07-RTM-KB937831-X86-AMD64-ENU.MSI from either Windows Explorer or from a command prompt.

4. During installation of the Windows Installer the following file is copied to the %temp% directory: Setup.exe.config.
5. During installation of the Windows Installer the following files are copied to the %temp%\TempQFE directory:
SystemCenterOpsMgr07-RTM-KB936481-X86-AMD64-ENU.MSI
qfelist.xml
SCE 2007 hotfix supplemental notice.rtf
QFEHandler.dll
6. Copy the QFEHandler.dll to the local copy of the Essentials installation media’s Setup\i386 or Setup\amd64 directory, depending on the processor architecture of the server.
7. Start Essentials 2007 silent setup using setup.exe with the appropriate command line options.
This hotfix impacts the following installed files:
Microsoft.EnterpriseManagement.OperationsManager.dll
ReportingCAManaged.dll
ReportingCAManagedPac.dll
ReportingCAPack.dll