Page 1 of 15

SAP enhanced monitoring on Hyper-V

Jan 2012

Author

Hermann Daeubler, Senior Program Manager, Microsoft

Page 2 of 15

Walk-Through

Configuration of SAP enhanced monitoring on Hyper-V

Figure 1 according to SAP note 1409604 one has to call transaction ST06, OS07 or

OS07N depending on the NetWeaver version. In this sample ( kernel 720,

NW 730 ) transaction ST06 was called. By default it’s using “Standard View”.

It obviously realized that SAP is running within a virtual machine ( …5006 )

and also found the hostname ( …6443 ) of the underlying physical host. But

some important information is missing

Page 3 of 15

Figure 2 after switching to “Expert View” in ST06 one should see information about the

physical host on which the VM is running. For this screenshot the CPU

snapshot was selected. But no details about the physical host are available

Figure 3 SAP enhanced monitoring isn’t activated / configured yet. Therefore important

information about the physical host is missing. But where does then the

hostname come from ? Well – this can be found in the registry within the VM.

SAP enhanced monitoring uses this hostname to do remote WMI calls over

the network. Now the key question is which settings are necessary on the

host to allow these remote WMI calls ?

Page 4 of 15

Figure 4 first step of the settings on the physical host for SAP enhanced monitoring is

the entry of the VM hostname in two user groups via Computer Management.

It’s necessary to add the VM hostname to the Performance Monitor Users

group. First one has to add “Computers” to the list of object types. It’s not

selected by default. Otherwise the dialog won’t be able to identify the VM

Figure 5 after adding “Computers” to the list of object types one has to enter the

hostname of the VM including a Dollar sign at the end

Page 5 of 15

Figure 6 then the VM hostname including the domain name should appear in the

Performance Monitor Users group.

Figure 7 afterwards one has to repeat the steps to add the VM hostname also to the

Distributed COM Users group

Page 6 of 15

Figure 8 next part of the SAP enhanced monitoring configuration is WMI Control. To

make the appropriate entries one has to open the WMI Control properties in

the Server Manager

Figure 9 select “CIMV2” under the “Security” tab and the click on the “Security”

button

Page 7 of 15

Figure 10 in the security dialog for ROOT\CIMV2 highlight the VM hostname and check

the permissions in the little window below. “Remote Enable” must be

selected otherwise SAP enhanced monitoring won’t work. When it’s done

one has to click on the “Advanced” button

Page 8 of 15

Figure 11 in the advanced security dialog highlight the VM hostname and edit the

entry

Figure 12 select “This namespace and subnamespaces” and also mark the checkbox

at the bottom on the left side. Then press “OK”

Page 9 of 15

Figure 13 then all the steps done for “CIMV2” have to be repeated for “virtualization”

Figure 14 last but not least some settings are necessary to be done via azman. First

it’s necessary to check the path for the current authorization XML file. It can

be found in the registry of the physical host under

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization

In this sample the file name is “HyperVAuthStore.xml”

Page 10 of 15

Figure 15 start the “Authorization Manager” by running “azman.msc”. Then open the

file which was found in the registry in the step before ( figure 14 ). As

described in the SAP note the path might look different in case SCVMM is

not used. In this example one has to add a new role definition under

“Virtual Machine Manager”. The role was simply called

“SAP enhanced monitoring”

Page 11 of 15

Figure 16 after the new role was created just do a right-click on the entry and select

“Properties”. In the properties dialog some definitions have to be added

- see next figure

Figure 17 when adding the new definitions choose the “Operations” tab and select

three operations out of the big list – see next figure

Page 12 of 15

Figure 18 the definitions for the new SAP enhanced monitoring role must have the

three operations which can be seen on the screenshot :

- Allow Output from Virtual Machine

- Read Service Configuration

- View Virtual Machine Configuration

Figure 19 once the new role is defined it also has to be added under

“Role Assignments”

Page 13 of 15

Figure 20 after adding the new SAP enhanced monitoring role under “Role

Assignments” the VM hostname has to be assigned. Just do a right-click

on the entry and then select “Assign Users and Groups” and afterwards

“From Windows and Active Directory …”. The following dialog works like

before when adding the VM hostname to the DCOM user group

Figure 21 finally the VM hostname + domain shows up like a user assigned to the new

SAP enhanced monitoring role. This was the last important setting. Now let’s

try transaction ST06 again

Page 14 of 15

Figure 22 after changing the settings on the physical host the saposcol or

SAPHostExec service should be restarted before trying ST06 or OS07

again.

Yippee !! It works ! Now we see e.g. the information about the CPUs in the

VM ( 4 CPUs ) as well as on the physical host ( 8 CPUs ) !

Page 15 of 15

Figure 23 on the last screenshot we see that now we also get the memory

configuration information as expected : 3GB within the VM and 16GB on the

physical host.

q.e.d.