Notes

System Center Essentials

In een Active Directory omgeving waar de NETBIOS naam van het domein niet gelijk is aan het eerste deel van de FQDN van domein kun je tegen het volgende probleem aanlopen:
Nadat de installatie bij het rapportage onderdeel is aangeland, krijgt dat onderdeel op een gegeven moment een rood kruis en worde de rest van de installatie teruggerold.

Foutmelding in log na gefaalde installatie:

Property(S): UnableToGetUserNameFromManagementServerActionAccount = SetPropertiesToManagementServerActionAndSDKAccountCA error: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException : The specified domain does not exist or cannot be contacted.
Property(S): UnableToGetUserNameFromManagementServerSDKAccount = SetPropertiesToManagementServerActionAndSDKAccountCA error: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException : The specified domain does not exist or cannot be contacted.
MSI (s) (E8:D0) [16:37:42:692]: Note: 1: 1708 
MSI (s) (E8:D0) [16:37:42:692]: Product: System Center Operations Manager 2007 Reporting Server -- Installation operation failed.

De hotfix die genoemd wordt in You cannot install the System Center Operations Manager 2007 Reporting feature in a disjointed namespace environment zit in de rollup package die te krijgen is op Description of System Center Essentials 2007 post-release hotfix rollup. Maar deze verhelpt het probleem nog niet. De hotfix die genoemd wordt in 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" zou het probleem wel moeten verhelpen, maar deze moet aangevraagd worden.

Bronnnen:
Installing MS System Center Essentials 2007 fails at Reporting item
SCE2007 Install Fails With "The specified domain does not exist or cannot be contacted"

Operations Manager 2007 and System Center Essentials Reporting features will fail to install in a disjointed DNS namespace
System Center Essentials post RTM Hotfix Rollup released to the Web

Dit komt doordat de (oude) System Center server een item in AD heeft staan.

Oplossing:

1. On the Domain Controller, download Windows Server 2003 Service Pack 1 32-bit Support Tools from this website

Install the tools, then open ADSI Edit (Start – Run – Adsiedit.msc).

2. Right click on the “Domain” tree and select New – Query.

3. In the New Query window, enter the following:
Name: SCESCP Query
Root of Search: DC=litware,DC=com
Query String: (&(objectCategory=serviceConnectionPoint)(cn=SCESCP))

4. Click on OK.

5. Expand the Domain node in ADSI Edit and select the “SCESCP Query” node.

6. A “CN=SCESCP” object should be listed in the right-hand pane, with a distinguished name of “CN=SCESCP,CN=OldSCEServer,CN=Computers,DC=litware,DC=com”.
This tells us that the computer account named “OldSCEServer” has the SCE SCP.

7. After confirming that System Center Essentials is not being used on this server, delete the SCESCP object from the “SCESCP Query” node in ADSI Edit.

After deleting the SCP, please restart the server, then Install the hotfix and SCE

Bron: Eric Zhang op Setup SCE 2007 suddenly stops

When importing the Windows Server Operating System Library management pack version 6.0.7026.0 on SCE 2007 SP1 you get the following error:

The requested management pack was invalid. See inner exception for details.
Parameter name: managementPack Verification failed with [1] errors:
-------------------------------------------------------
Error 1:
: Verification failed for Probe Action Module Type : Microsoft.Windows.Server.MaxConcurrentAPI.Probe
Failed to verify Composite Module Type - Microsoft.Windows.Server.MaxConcurrentAPI.ProbeFailed to verify Module Reference (Type=ManagementPackElement=Microsoft.Windows.PowerShellPropertyBagTriggerOnlyProbe in ManagementPack:[Name=Microsoft.Windows.Library, KeyToken=31bf3856ad364e35, Version=6.0.5000.0],ID=Probe) in the MemberModules list.Cannot find ManagementPackElement [Type=ManagementPackModuleType, ID=Microsoft.Windows.PowerShellPropertyBagTriggerOnlyProbe] in ManagementPack [ManagementPack:[Name=Microsoft.Windows.Library, KeyToken=31bf3856ad364e35, Version=6.0.5000.0]]
-------------------------------------------------------
Verification failed for Probe Action Module Type : Microsoft.Windows.Server.MaxConcurrentAPI.Probe Failed to verify Composite Module Type - Microsoft.Windows.Server.MaxConcurrentAPI.Probe Failed to verify Module Reference (Type=ManagementPackElement=Microsoft.Windows.PowerShellPropertyBagTriggerOnlyProbe in ManagementPack:[Name=Microsoft.Windows.Library, KeyToken=31bf3856ad364e35, Version=6.0.5000.0],ID=Probe) in the MemberModules list. Cannot find ManagementPackElement [Type=ManagementPackModuleType, ID=Microsoft.Windows.PowerShellPropertyBagTriggerOnlyProbe] in ManagementPack [ManagementPack:[Name=Microsoft.Windows.Library, KeyToken=31bf3856ad364e35, Version=6.0.5000.0]]

The cause is that the management pack can't find Microsoft.Windows.PowerShellPropertyBagTriggerOnlyProbe in the Microsoft.Windows.Library management pack because that was only added beginning with System Center Operations Manager 2007 R2 so you can't import the management pack on SCE 2007 SP1.

See also: Microsoft TechNet Forums - Cannot get Logical Free Disk Monitor to alert