my personal blog about systemcenter

What have been known and whispered for a while is now out with a fix and workaround (that was allready in use)

Thank you to Rene for showing this Smiley

PATCH and or Disable , personally for now i will suggest PATCH and Disable

HP 3 PAR http://h20566.www2.hp.com/portal/site/hpsc/public/psi/advisoriesResults/?sp4ts.oid=5335712

SUPPORT COMMUNICATION -

Document ID: c04205854

Version: 1

CUSTOMER BULLETIN: HP 3PAR StoreServ Storage – HP 3PAR OS 3.1.2 can Improperly Zero Blocks Beyond the Requested Range When Using Windows Server 2012 ODX Commands

DESCRIPTION

An issue has been discovered with the HP 3PAR OS and the use of Windows Server 2012 Off-loaded Data Transfer (ODX) commands, which may result in a number of blocks incorrectly zeroed beyond the requested range under certain conditions. This issue is not observed with ODX disabled.

Detailed Analysis :

When the Write Using Token requests using Block Device Zero Token is greater than 16 MBs in size, and the size is not a multiple of 16 MBs, a number of blocks may be zeroed beyond the end of the requested range. Disabling ODX eliminates the use of Write Using Token requests using Block Device Zero Token. 

SCOPE

Windows Server 2012 or Windows Server 2012 R2 hosts with ODX in use with HP 3PAR StoreServ Storage running HP 3PAR OS version 3.1.2 GA, 3.1.2 MU1, 3.1.2 MU2, 3.1.2 EMU2, or 3.1.2 MU3.

RESOLUTION

Upgrade the HP 3PAR OS on the HP 3PAR StoreServ Storage to 3.1.2 MU2 or later if running a lower HP 3PAR OS version. Next apply the patch as follows:

  • For 3.1.2 MU2 and 3.1.2 EMU2, apply Patch 11 followed by Patch 36.

  • For 3.1.2 MU3, apply Patch 30.

Workaround

Disable ODX on the Windows 2012 or Windows 2012 R2 hosts. To disable ODX , type the following:

Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem -Name “FilterSupportedFeaturesMode” -Value 1

A server reboot is required for all servers in which the registry value is modified.

After a recent upgrade to R2 we wanted to update all SCOM agents , however push to service with Service Manager Console installed failed (this is mostly admin servers and Citrix servers in our enviroment

The SCOM Agent detect is Service Manager is installed and if its installed the installer exits

THIS IS UNSUPPORTED AND IT WILL KILL YOUR SERVICE MANGER SERVER if you force the install on a server , ONLY do this on admin servers or clients that have both the agent and the console installed NEVER on Service Manager Servers

Action ended 09:18:23: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8. Return value 1.

MSI (s) (40:60) [09:18:23:922]: PROPERTY CHANGE: Adding WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 property. Its value is ‘C:\Windows\’.

Action start 09:18:23: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.

MSI (s) (40:60) [09:18:23:922]: Doing action: FindRelatedProducts

Action ended 09:18:23: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9. Return value 1.

Action start 09:18:23: FindRelatedProducts.

MSI (s) (40:60) [09:18:23:923]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT_SMRTM property. Its value is ‘{FE333322-19E9-4B03-B248-DB327D96A92A}’.

MSI (s) (40:60) [09:18:23:923]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)

MSI (s) (40:60) [09:18:23:924]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)

MSI (s) (40:60) [09:18:23:924]: Skipping action: _Set_OM_AGENT_FOUND (condition is false)

MSI (s) (40:60) [09:18:23:924]: Skipping action: _Set_MOMV3_AGENT_FOUND (condition is false)

MSI (s) (40:60) [09:18:23:924]: Doing action: _Set_CORECOMPONENTPRESENT

Action ended 09:18:23: FindRelatedProducts. Return value 1.

MSI (s) (40:60) [09:18:23:924]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT property. Its value is ‘{FE333322-19E9-4B03-B248-DB327D96A92A}’.

Action start 09:18:23: _Set_CORECOMPONENTPRESENT.

MSI (s) (40:60) [09:18:23:924]: Skipping action: _AbortDowngradeProductAttempt (condition is false)

MSI (s) (40:60) [09:18:23:924]: Doing action: _AbortCoreComponentPresent

Action ended 09:18:23: _Set_CORECOMPONENTPRESENT. Return value 1.

Action start 09:18:23: _AbortCoreComponentPresent.

MSI (s) (40:60) [09:18:23:925]: Product: Microsoft Monitoring Agent — The Microsoft Monitoring Agent cannot be installed on a computer on which the Operations Manager management server, gateway server, Operations console, operational database, web console, System Center Essentials, or System Center Service Manager is already installed.

The Microsoft Monitoring Agent cannot be installed on a computer on which the Operations Manager management server, gateway server, Operations console, operational database, web console, System Center Essentials, or System Center Service Manager is already installed.

Action ended 09:18:23: _AbortCoreComponentPresent. Return value 3.

—-

The workaround is normally to uninstall the Service Manager Console , Install the Agent and Install the Console Again

clip_image002

However if we rename the Service Manager Installer registry key

clip_image004

We can then install the SCOM agent

and then rename the registry back to normal

MSI (s) (40:94) [09:27:48:572]: Note: 1: 1707

MSI (s) (40:94) [09:27:48:572]: Product: Microsoft Monitoring Agent — Installation operation completed successfully.

MSI (s) (40:94) [09:27:48:578]: Windows Installer har installeret produktet. Produktnavn: Microsoft Monitoring Agent. Produktversion: 7.1.10184.0. Produktsprog: 0. Producent: Microsoft Corporation. Installationen lykkedes eller fejlstatus: 0.

As many pointed out 2003 Supported was removed in Data Protection Manager 2012 R2

Steve found a public annoucement that its on its way back

http://www.buchatech.com/2014/03/windows-server-2003-support-coming-back-to-dpm-2012-r2/

Hello Folks, I am the GPM for the DPM product group and sincerely apologize for this. Not supporting an already supported server OS for back-up is DPM 2012 R2 was a mistake. We are fixing this in the next update roll-up for DPM scheduled to be released shortly. Thanks for your patience.

Shreesh Dubey

This is good news as Data Protection Manager wont hold down a suite upgrade all the way around , ITS NOT A FREEE PASS to keep goofing around with 2003 servers , they are close to end of life , upgrade/migrate/power off but until you do at least we can soon again protect 2003 workloads with Data Protection Manager 2012 R2

Now go off and migrate Smiley

Using the Windows Azure Pack Service Management Portal we ran into a issue i tried to reproduct , we was asked to create some NAT rules for a tenant , and we didnt have a admin user in that tenant so we went through Virtual Machine Manager instead , but the rules was not visible but working

This is the steps needed to reproduce

 

edit the all knowing Brian Ehlert suggested ctrl f5 , worked like a charm instead of logout

eidt the also all knowing Marc van Eijk pointed out that clicking Service Management Portal top left refreshed from DB

 

Thanks :)

image

If we go through our Service Management Portal and

 

image

Add a rule the our virtual network

 

image

It shows up in Virtual Machine Manager network config right away

image

If a change is made from Virtual Machine Manager the rule kicks in right away but

 

image

the changes is not reflected in the UI until

image

We log off and on again.