aqrawi.nl

Download Cumulative Update 6 for System Center Operations Manager 2007 R2

Cumulative Update 6 for Operations Manager 2007 R2 resolves the following issues:

• RMS promotion fails if NetworkName and PrincipalNames are not in sync for agents.
• UI is limited to only 100 MB for the Memory Usage field in the wizard.
• Additional OIDs in auth certificate are not processed correctly.
• AEM creates duplicate computer objects in OpsMgr based on Agents NetBIOS name.
• Cannot open reporting pane on OpsMgr 2007 R2 remote console.
• Cannot view schedule for scheduled report.
• ManagementServerConfigTool with the option "promoterms" fails because it stops polling the SDK Service.
• OpsMgr reports are failing on Windows 7 with the error: "Cannot initialize report."
• ACS events have "n/a" as their category in the ACS database.
• Watch agentless monitoring listener to detect failure to respond.
• SCOM SDK memory leak on cryptography keys and cryptography contexts.
• After you click Edit Schedule, a message box appears, and you cannot save the change value.
• Audit events can be lost when the AdtServer process crashes.

Cumulative Update 6 for Operations Manager 2007 R2 resolves the following cross-platform issues:

• The installation process for the IBM AIX 6.1 agent incorrectly checks for AIX 5.3 packages.
• After a system restart, the OpsMgr agent for Solaris may start to run before local file systems are mounted.
• On Red Hat Linux version 4 and SUSE Linux version 9, LVM disks are not discovered and cannot be monitored.
• The OpsMgr agent for AIX does not report the arguments for monitored processes.
• When Microsoft security update MS12-006 is installed on an OpsMgr management server, that management server can no longer communicate with the OpsMgr agent on any Linux or UNIX server.
• On HP-UX, OpsMgr cannot discover and monitor a logical volume that is composed of more than 127 physical volumes.

Cumulative Update 6 for Operations Manager 2007 R2 adds the following cross-platform features:

• Support for IBM AIX 7.1 (POWER).
• Support for Oracle Solaris 11 (x86 and SPARC).

Note The new agents for IBM AIX 7.1 and Oracle Solaris 11 are included in Cumulative Update 6 for Operations Manager 2007 R2. You can download the management packs for these new operating system versions by going to the following Microsoft website:

System Center Operations Manager 2007 R2 Cross Platform Monitoring Management Packs

Last week I got a question from one of my customers, he was getting in SCOM the alert “Logical Disk Not Available” from one of his Windows 2008 r2 servers  while there was is nothing wrong with the disk.

so I started envestigating the problem and started first as usual with the SCOM console, looked at the Alert and the alert knowledge:

Summary

The logical disk volume is not available. The data stored on the volume is inaccessible.

Causes

A logical disk may become inaccessible due to a number of reasons some of which include:

•

Related physical disk has been removed

•

Physical disk has become corrupt (for example; bad sectors) or inoperable

•

Problem with physical disk driver

Resolutions

Check the status of your hardware for any failures (for example, a disk, controller, cabling failure). In most cases, the system log contains additional events from the lower-level storage drivers that indicate the cause of the failure.

After you have isolated and resolved the hardware problem:

1. Open the Disk Management snap-in.

2. Rescan the disks and then reactivate any disks with errors.

Resynchronize or regenerate the volume as necessary if the disk was a member of a mirrored or RAID-5 volume.

3. Run chkdsk on any reactivated volumes.

I went through all the steps, and  this did not solve the problem. I decided to see what exactly the monitor does. The alert come from the Windows Server  Operating System  2008 Management pack

after further  research I found that  there is a Script that checks if the disk has a dirty bit flag and if that is true then you will get this alert in SCOM

If (Not IsNull(sDriveLetter)) And (Not IsEmpty(sDriveLetter)) Then
Dim DirtyBitSet
If IsVolumeInfoSupported Then
DirtyBitSet = oWmiDisk.DirtyBitSet
Else
DirtyBitSet = oWmiDisk.VolumeDirty
End If
Set oBag = oAPI.CreatePropertyBag()
oBag.AddValue “DiskLabel”, sDriveLetter
If IsNull(DirtyBitSet) Then
oBag.AddValue “State”, “OK”
Else
If DirtyBitSet = True Then
oBag.AddValue “State”, “BAD”
Else
oBag.AddValue “State”, “OK”
End If
End If
oAPI.AddItem oBag
End If
Next

dirty

A volume’s dirty bit is set, this indicate that the file system may be in an inconsistant state. To check that, I loged in to the server, opend CMD and typed  “fsutil dirty query E” the results has confirmed what is found:

To solve this you have to run to commands in cmd:

CHKNTFS /X E:  then reboot the server

CHKDSK /f /r E

This should solve the problem

Have you been tired from getting this warning workflow failure?

This error come from the Official Citrix XenApp version 6.0.0.0. the rule fail when it trys to run a WMI query using the the Citrix WMI provider.

Citrix has published a KB article about this problem:
http://support.citrix.com/article/CTX122283

Use the steps below to complete the task. Back up citrixProv.XP10FR3.mof, metaframeProv.XP10FR3.mof, and mgmt.XP10FR4.mof files before you proceed.

1. Traverse to <Programfiles>CitrixSystem32CitrixWMI

2. Edit citrixProv.XP10FR3.mof, metaframeProv.XP10FR3.mof, and mgmt.XP10FR4.mof files to set the Hosting Model as “SelfHost” in the following sections of each of the files:

a. citrixProv.XP10FR3.mof – Registers Framework Provider, Registers Citrix Event Provider, Registers Citrix Event Purge Provider

b. metaframeProv.XP10FR3.mof – Registers Framework Provider, Registers MetaFrame Event Provider, Registers MetaFrame Event Happenings Purge Provider

c. mgmt.XP10FR4.mof – Registers Framework Provider, Registers Mgmt Happenings Provider, Registers Mgmt Event Provider

Example:-
//*************************************************************
//*** Registers Framework Provider ***
//*************************************************************
instance of __Win32Provider as $P
{
Name = "MgmtProv";
HostingModel = "SelfHost";
ClsId = "{0201D664-2253-4ca8-88EE-B2E6E78D8CAE}";
};
instance of __InstanceProviderRegistration
{
Provider = $P;
SupportsGet = TRUE;
SupportsPut = FALSE;
SupportsDelete = FALSE;
SupportsEnumeration = TRUE;
QuerySupportLevels = NULL;
};
instance of __MethodProviderRegistration
{
Provider = $P;
};

the only problem is that this issue is only addressed to windows 2003, but what to do when you have Citrix XenApp installed on Windows 2008?

I did search the whole web for a solution and can’t find anything !

I did try everythins till I found a very simple solution for this problem, the only thing you have to do is to Restart the Citrix WMI service under services and the whole problem
will disappear and you can go on with your normal life