How to enable SAP "enhanced monitoring" via Powershell

Published Mar 13 2019 09:39 AM 467 Views
Microsoft
First published on MSDN on Jul 31, 2012

Update Sep 27 2012


bug fix in PS script. An issue showed up using the script on a Windows 2012 server. The script failed to remove an entry
from the two local user groups due to case sensitivity regarding the VM name.



Status Quo



I published a blog beginning of the year which describes what to do to enable SAP “Enhanced Monitoring” without
the need to give admin permissions to virtual machines :


http://blogs.msdn.com/b/saponsqlserver/archive/2012/01/16/sap-enhanced-monitoring-on-hyper-v.as...


In addition the whole topic is described in SAP note 1409604



Issue



The blog mentioned above describes all the steps which are necessary to enable SAP "enhanced monitoring". But
it is a lot of "clicking" which also holds the risk to make mistakes. And admins who like to automate things won't be
happy about the process no matter how well it is described



Solution




I put together a little Powershell script which does all the necessary security settings to enable SAP "enhanced
monitoring". It handles all necessary security entries on the Hyper-V host in the three areas which are required :

1. local "Performance Monitor Users" group as well as the "Distributed COM Users" group

2. WMI Control security


3. Authorization Manager ( azman.msc )



The script attached is not an official Microsoft product. There is no support. Take it as it is. Focus was NOT on
programming style or performance. Main goal was to make it robust and hopefully easy-to-use. Another goal
was to avoid loading additional modules - just basic Powershell if possible.
It was tested by a colleague from SAP development as well as a few first customers.

Keep in mind that in case of a Hyper-V cluster the script has to be started on every node on which a SAP VM
might wake up. This means that on a 8-node Hyper-V cluster one has to run the script eight times.

In case someone will find a critical bug or has suggestions how to further improve the script - let me know.
While there is no official Microsoft support I am still open to make some changes.

To use the script just download the attached text file, rename it as you like and change the extension to .ps1




Walkthrough


The following section will describe how to use the Powershell script :



Figure 1 : SAP enhanced monitoring on Hyper-V won’t work out-of-the-box. A simple way to check
is by calling transaction ST06 and select “Expert View”. The line of “CPU Virtualization
Host” will not show any details




Figure 2 : clicking on “Processor” in the “CPU Virtualization Host” line as seen on Figure 1 will very
likely cause an error




Figure 3 : once the permissions for the VM ( out of which SAP Enhanced Monitoring will be used )
are set correctly on the Hyper-V host ST06 will show the details about the host CPUs




Figure 4 : just type in the Powershell script name and press RETURN. An error will be reported and
the correct syntax will be shown





Figure 5 : the easiest usage is adding the corresponding permissions for a specific virtual machine.
Use the option “add”, tell the domain and the name of the virtual machine. The script will
display messages about what it did. As long as there are no errors everything will be ok




Figure 6 : adding a VM name the very first time will automatically add a SAP specific role definition
to the azman store. If one adds another VM this role definition already exists and the
script will tell in form of “Information” messages that certain objects already exist.





Figure 7 : use option “remove” to remove the permissions again




Figure 8 : to make life easier when working with many VMs one can create a global
security group on the domain controller


Figure 9 : once the global security group is created add the virtual machines in which SAP
Enhanced Monitoring should be used




Figure 10 : by using the option “-adgrp” it’s possible to use a global AD group as described above
instead of a single VM name





Figure 11 : when removing a specific VM name or an AD group the script will keep the SAP
specific role definition in the azman store. Use the separate option
“remove_azman_role” to get rid of it. In case the script finds existing members
it will ask if the role definition should be really deleted as all member entries will
be gone




Figure 12 : if one will repeat an “add” operation the script will just report “Information”
messages as everything exists already




Figure 13 : the same is valid for operation “remove”. Repeating the same remove call
again will result in Information messages reporting that the entries don’t exist
anymore



Figure 14 : as described in SAP note 1409604 there was an “easy” way to enable enhanced
monitoring in the past by simply giving a VM admin permissions.
In case there are entries using this old method the script is able to assist in
migrating these entries. It will provide a list of entries which are very likely
candidates for SAP enhanced monitoring. The user is then allowed to pick the
ones which should be migrated




Figure 15 : to be on the safe side the script will show the selected list of entries again which
should be migrated






Figure 16 : finally the script will migrate the entries which the user selected. These entries will be
removed from the administrators  group and all the appropriate entries as described
above will be done. It works exactly the same way with all the Information messages
in case the entries should already exist



enhmon_PS_version_1_5_1.zip

%3CLINGO-SUB%20id%3D%22lingo-sub-367431%22%20slang%3D%22en-US%22%3EHow%20to%20enable%20SAP%20%22enhanced%20monitoring%22%20via%20Powershell%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-367431%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Jul%2031%2C%202012%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CH3%20id%3D%22toc-hId-1482455233%22%20id%3D%22toc-hId-1568312837%22%3EUpdate%20Sep%2027%202012%3C%2FH3%3E%3CBR%20%2F%3E%3CP%3Ebug%20fix%20in%20PS%20script.%20An%20issue%20showed%20up%20using%20the%20script%20on%20a%20Windows%202012%20server.%20The%20script%20failed%20to%20remove%20an%20entry%20%3CBR%20%2F%3E%20from%20the%20two%20local%20user%20groups%20due%20to%20case%20sensitivity%20regarding%20the%20VM%20name.%3C%2FP%3E%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId--873188223%22%20id%3D%22toc-hId--787330619%22%3E%3C%2FH2%3E%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId-869622112%22%20id%3D%22toc-hId-955479716%22%3EStatus%20Quo%3C%2FH2%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EI%20published%20a%20blog%20beginning%20of%20the%20year%26nbsp%3Bwhich%20describes%20what%20to%20do%20to%20enable%20SAP%20%E2%80%9CEnhanced%20Monitoring%E2%80%9D%20without%20%3CBR%20%2F%3E%20the%20need%20to%20give%20admin%20permissions%20to%20virtual%20machines%20%3A%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fblogs.msdn.com%2Fb%2Fsaponsqlserver%2Farchive%2F2012%2F01%2F16%2Fsap-enhanced-monitoring-on-hyper-v.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20http%3A%2F%2Fblogs.msdn.com%2Fb%2Fsaponsqlserver%2Farchive%2F2012%2F01%2F16%2Fsap-enhanced-monitoring-on-hyper-v.aspx%20%3C%2FA%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EIn%20addition%20the%20whole%20topic%20is%20described%20in%20SAP%20note%201409604%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId--1682534849%22%20id%3D%22toc-hId--1596677245%22%3EIssue%3C%2FH2%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EThe%20blog%20mentioned%20above%20describes%20all%20the%20steps%20which%20are%20necessary%20to%20enable%20SAP%20%22enhanced%20monitoring%22.%20But%20%3CBR%20%2F%3E%20it%20is%20a%20lot%20of%20%22clicking%22%20which%20also%20holds%20the%20risk%20to%20make%20mistakes.%20And%20admins%20who%20like%20to%20automate%20things%20won't%20be%20%3CBR%20%2F%3E%20happy%20about%20the%20process%20no%20matter%20how%20well%20it%20is%20described%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId-60275486%22%20id%3D%22toc-hId-146133090%22%3ESolution%3C%2FH2%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CBR%20%2F%3E%20I%20put%20together%20a%20little%20Powershell%20script%20which%20does%20all%20the%20necessary%20security%20settings%20to%20enable%20SAP%20%22enhanced%20%3CBR%20%2F%3E%20monitoring%22.%20It%26nbsp%3Bhandles%20all%20necessary%20security%20entries%20on%20the%20Hyper-V%20host%20in%20the%20three%20areas%20which%20are%20required%20%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%201.%20local%20%22Performance%20Monitor%20Users%22%20group%20as%20well%20as%20the%26nbsp%3B%22Distributed%20COM%20Users%22%20group%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%202.%20WMI%20Control%20security%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E3.%20Authorization%20Manager%20(%20azman.msc%20)%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CBR%20%2F%3E%20The%20script%20attached%20is%20not%20an%20official%20Microsoft%20product.%20There%20is%20no%20support.%20Take%20it%20as%20it%20is.%20Focus%20was%20NOT%20on%20%3CBR%20%2F%3E%20programming%20style%20or%20performance.%20Main%20goal%20was%20to%20make%20it%20robust%20and%20hopefully%20easy-to-use.%20Another%20goal%20%3CBR%20%2F%3E%20was%20to%20avoid%20loading%20additional%20modules%20-%20just%20basic%20Powershell%20if%20possible.%20%3CBR%20%2F%3E%20It%20was%20tested%20by%20a%20colleague%20from%20SAP%20development%20as%20well%20as%20a%20few%20first%20customers.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Keep%20in%20mind%20that%20in%20case%20of%20a%20Hyper-V%20cluster%20the%20script%20has%20to%20be%20started%20on%20every%20node%20on%20which%20a%20SAP%20VM%20%3CBR%20%2F%3E%20might%20wake%20up.%20This%20means%20that%20on%20a%208-node%20Hyper-V%20cluster%20one%20has%20to%20run%20the%20script%20eight%20times.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20In%20case%20someone%20will%20find%20a%20critical%20bug%20or%20has%20suggestions%20how%20to%20further%20improve%26nbsp%3Bthe%20script%26nbsp%3B-%20let%20me%20know.%20%3CBR%20%2F%3E%20While%20there%20is%20no%20official%20Microsoft%20support%20I%20am%20still%20open%20to%20make%20some%20changes.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20To%20use%20the%20script%20just%20download%20the%20attached%20text%20file%2C%20rename%20it%20as%20you%20like%20and%20change%20the%20extension%20to%20.ps1%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CH2%20id%3D%22toc-hId-1803085821%22%20id%3D%22toc-hId-1888943425%22%3E%3CBR%20%2F%3E%20Walkthrough%3C%2FH2%3E%3CBR%20%2F%3E%3CP%3EThe%20following%20section%20will%20describe%20how%20to%20use%20the%20Powershell%20script%20%3A%20%3CBR%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87962i094119501B5BE9AD%22%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EFigure%201%20%3A%20SAP%20enhanced%20monitoring%20on%20Hyper-V%20won%E2%80%99t%20work%20out-of-the-box.%20A%20simple%20way%20to%20check%20%3CBR%20%2F%3E%20is%20by%20calling%20transaction%20ST06%20and%20select%20%E2%80%9CExpert%20View%E2%80%9D.%20The%20line%20of%20%E2%80%9CCPU%20Virtualization%20%3CBR%20%2F%3E%20Host%E2%80%9D%20will%20not%20show%20any%20details%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CBR%20%2F%3E%20%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87963iF23A6522E901D095%22%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EFigure%202%20%3A%20clicking%20on%20%E2%80%9CProcessor%E2%80%9D%20in%20the%20%E2%80%9CCPU%20Virtualization%20Host%E2%80%9D%20line%20as%20seen%20on%20Figure%201%20will%20very%20%3CBR%20%2F%3E%20likely%20cause%20an%20error%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87964iE8BC588B6FBE4E74%22%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EFigure%203%20%3A%20once%20the%20permissions%20for%20the%20VM%20(%20out%20of%20which%20SAP%20Enhanced%20Monitoring%20will%20be%20used%20)%20%3CBR%20%2F%3E%20are%20set%20correctly%20on%20the%20Hyper-V%20host%20ST06%20will%20show%20the%20details%20about%20the%20host%20CPUs%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87965i83C7AD834F41181A%22%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EFigure%204%20%3A%20just%20type%20in%20the%20Powershell%20script%20name%20and%20press%20RETURN.%20An%20error%20will%20be%20reported%20and%20%3CBR%20%2F%3E%20the%20correct%20syntax%20will%20be%20shown%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87966i70E8CEE051B5A752%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Figure%205%20%3A%20the%20easiest%20usage%20is%20adding%20the%20corresponding%20permissions%20for%20a%20specific%20virtual%20machine.%20%3CBR%20%2F%3E%20Use%20the%20option%20%E2%80%9Cadd%E2%80%9D%2C%20tell%20the%20domain%20and%20the%20name%20of%20the%20virtual%20machine.%20The%26nbsp%3Bscript%20will%20%3CBR%20%2F%3E%20display%20messages%20about%26nbsp%3Bwhat%20it%20did.%20As%20long%20as%20there%20are%20no%20errors%20everything%26nbsp%3Bwill%20be%20ok%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87967iD80EE9280C72D822%22%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EFigure%206%20%3A%20adding%20a%20VM%20name%20the%20very%20first%20time%20will%20automatically%20add%20a%20SAP%20specific%20role%20definition%20%3CBR%20%2F%3E%20to%20the%20azman%20store.%20If%20one%20adds%20another%20VM%20this%20role%20definition%20already%20exists%20and%20the%20%3CBR%20%2F%3E%20script%20will%20tell%20in%20form%20of%20%E2%80%9CInformation%E2%80%9D%20messages%20that%20certain%20objects%20already%20exist.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87968iC1C6E26A628BCC38%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Figure%207%20%3A%20use%20option%20%E2%80%9Cremove%E2%80%9D%20to%20remove%20the%20permissions%20again%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87969i30953BCCA9F6B140%22%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EFigure%208%20%3A%20to%20make%20life%20easier%20when%20working%20with%20many%20VMs%20one%20can%20create%20a%20global%20%3CBR%20%2F%3E%20security%26nbsp%3Bgroup%20on%20the%20domain%20controller%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87970i5375C6DB1D25A377%22%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EFigure%209%20%3A%20once%20the%20global%20security%20group%20is%20created%20add%20the%20virtual%20machines%20in%20which%20SAP%20%3CBR%20%2F%3E%20Enhanced%20Monitoring%20should%20be%20used%20%3CBR%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87971i54A4BED0E35280DC%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Figure%2010%20%3A%20by%20using%20the%20option%20%E2%80%9C-adgrp%E2%80%9D%20it%E2%80%99s%20possible%20to%20use%20a%20global%20AD%20group%20as%20described%20above%20%3CBR%20%2F%3E%20instead%20of%20a%20single%20VM%20name%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87972i4F1F385142A1BB12%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Figure%2011%20%3A%20when%20removing%20a%20specific%20VM%20name%20or%20an%20AD%20group%20the%20script%20will%20keep%20the%20SAP%20%3CBR%20%2F%3E%20specific%20role%20definition%20in%20the%20azman%20store.%20Use%20the%20separate%20option%20%3CBR%20%2F%3E%20%E2%80%9Cremove_azman_role%E2%80%9D%20to%20get%20rid%20of%20it.%20In%20case%20the%20script%20finds%20existing%20members%20%3CBR%20%2F%3E%20it%20will%20ask%20if%20the%20role%20definition%20should%20be%20really%20deleted%20as%20all%20member%20entries%20will%20%3CBR%20%2F%3E%20be%20gone%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87973i56A76EE27472E00A%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Figure%2012%20%3A%20if%20one%20will%20repeat%20an%20%E2%80%9Cadd%E2%80%9D%20operation%20the%20script%20will%20just%20report%20%E2%80%9CInformation%E2%80%9D%20%3CBR%20%2F%3E%20messages%26nbsp%3Bas%20everything%20exists%20already%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87974i4F6915064AC4F870%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Figure%2013%20%3A%20the%20same%20is%20valid%20for%20operation%20%E2%80%9Cremove%E2%80%9D.%20Repeating%20the%20same%20remove%20call%20%3CBR%20%2F%3E%20again%20will%26nbsp%3Bresult%20in%20Information%20messages%20reporting%20that%20the%20entries%20don%E2%80%99t%20exist%20%3CBR%20%2F%3E%20anymore%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87975iE7C62AAB4B623712%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Figure%2014%20%3A%20as%20described%20in%20SAP%20note%201409604%20there%20was%20an%20%E2%80%9Ceasy%E2%80%9D%20way%20to%20enable%20enhanced%20%3CBR%20%2F%3E%20monitoring%20in%20the%20past%20by%20simply%20giving%20a%20VM%20admin%20permissions.%20%3CBR%20%2F%3E%20In%20case%20there%20are%20entries%20using%20this%20old%20method%20the%20script%20is%20able%20to%20assist%20in%20%3CBR%20%2F%3E%20migrating%26nbsp%3Bthese%20entries.%20It%20will%20provide%20a%20list%20of%20entries%20which%20are%20very%20likely%20%3CBR%20%2F%3E%20candidates%20for%20SAP%26nbsp%3Benhanced%20monitoring.%20The%20user%20is%20then%20allowed%20to%20pick%20the%20%3CBR%20%2F%3E%20ones%20which%20should%20be%26nbsp%3Bmigrated%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87976iC5255442CFF5786D%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Figure%2015%20%3A%20to%20be%20on%20the%20safe%20side%20the%20script%20will%20show%20the%20selected%20list%20of%20entries%20again%20which%20%3CBR%20%2F%3E%20should%20be%20migrated%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CBR%20%2F%3E%20%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F87977i5AF386B3BCFE2F91%22%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Figure%2016%20%3A%20finally%20the%20script%20will%20migrate%20the%20entries%20which%20the%20user%20selected.%20These%20entries%20will%20be%20%3CBR%20%2F%3E%20removed%20from%20the%20administrators%26nbsp%3B%20group%20and%20all%20the%20appropriate%20entries%20as%20described%20%3CBR%20%2F%3E%20above%20will%20be%20done.%20It%20works%20exactly%20the%20same%20way%20with%20all%20the%20Information%20messages%20%3CBR%20%2F%3E%20in%26nbsp%3Bcase%20the%20entries%20should%20already%20exist%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmsdnshared.blob.core.windows.net%2Fmedia%2FMSDNBlogsFS%2Fprod.evol.blogs.msdn.com%2FCommunityServer.Components.PostAttachments%2F00%2F10%2F33%2F52%2F57%2Fenhmon_PS_version_1_5_1.zip%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%20enhmon_PS_version_1_5_1.zip%20%3C%2FA%3E%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-367431%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Jul%2031%2C%202012%20Update%20Sep%2027%202012bug%20fix%20in%20PS%20script.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-367431%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMonitoring%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPrivate%20Cloud%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Evirtualization%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Mar 13 2019 09:39 AM
Updated by: