Hello, I am not sure to understand clealry this: 6. Repeat steps 1 through 4 for additional watcher nodes and desired ping targets. IMPORTANT: You may include any combination of desired targets on any number of ping hosts. You may repeat steps 1 – 4 at any time to update the list of targets defined for a given watcher node. Watcher nodes must have an Operations Manager agent installed Watcher node agent must have agent proxy enabled as the step 1 to 4 are: 1. Import the Multi-Host Ping Management Pack using the Operations Console. The file name is SystemCenter.Utililities.MultiHostPing.Proxy.mp . 2. Make a list of target addresses to ping and a list of agent managed computers (Watcher Nodes) from which they will be monitored. Targets can be a combination of NetBIOS names, fully-qualified domain names (FQDNs) and IP addresses. 3. Add the list of targets in semicolon-separated format to the pingtargets.reg file included in the folder where the management pack was unzipped. An example is also shown in the figure below. Figure 1 - Sample pingtargets.reg file Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\SystemCenterMPs] [HKEY_LOCAL_MACHINE\SOFTWARE\SystemCenterMPs\MultiHostPing] [HKEY_LOCAL_MACHINE\SOFTWARE\SystemCenterMPs\MultiHostPing\PingTarget] "Target"="www.google.com;192.168.1.10;server1" 4. Copy pingtargets.reg to the watcher node(s) that will ping the desired targets. IMPORTANT: You may use a unique list of PingTargets in separate copies of this file on each Ping Watcher. Is it mandatory to import the MP on each Watcher node? For now I was copying from a central point the pingtarget.reg file abd updating it locally as needed then clicking on it to place the ciontent in the registry... Do I need more... as it seems my process do not make the new Watcher node available ... is there another step within the MP itself which will add this watcher node to the list in the view of Ping Watcher Role.? Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Dom, You can import an MP only once. You load the registry key with the list of ping targets on host(s) that will serve as the watcher nodes If you want to stop pinging from a particular watcher node. Delete the registry key created there If you want to change the list of computers you need to ping, update the .reg file and run it again on the watcher node to update the list of ping targets. Hope this helps. Feel free to ping me on systemcentercentral.com or offline at pete.zerger [AT] gmail.com if you need more assistance. ;)Pete Zerger, MVP-OpsMgr and SCE | http://www.systemcentercentral.com

Dom, I forgot to tell you about the Multi-Host Ping Configuration Builder! It could make life easier for you as well. Get it from http://www.systemcentercentral.com/Downloads/DownloadsDetails/tabid/144/IndexID/83415/Default.aspxPete Zerger, MVP-OpsMgr and SCE | http://www.systemcentercentral.com

thanks a lot DOmSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, Thanks for the link Pete, i am filling up the spreasheet and it seems a really expensive MP.., isn't it? Maximum # of watchers: 702 Maximum # of unique targets: 999 Maximum # of targets per watcher: 99 As I have a little bit less than 1,500 machines or items (web sites) to watch this will gives me: - I could not watch them from one unique registry(server) as limited to 999 so I need at least two sets of machines with 750 items to watch for each set of machines - 15 Watcher Nodes ??? separated in two set of 750 machines approx... so it might be 8 watcher nodes or items with 99 machines each and another set of 7 machines with 99 machines or items. - so in case I would like the cross-pinging with at least two watcher nodes for each machines i will need 30 machines to do it !!! it seems really expensive !!! Any missing point in my calculation? When filling the spreadsheets at the step 5 I have an error: Cannot run the macro "MultiHostPing_Config_Generator.xlsx!sheet3.GenerateRegFiles'. The macro may not be available in this workbook or all macros may be disabled... Excel 2010 > MutiHostPing_Config_Generator.xlsx > File > Options > Trust Center > Trust Center Settings > Macro Settings > "Enable all macros (not recommended; potentially dangerous code can run)" is the option selected !!! Excel 2010 > MutiHostPing_Config_Generator.xlsx > View > Macros the list is empty I have a doubt... which file should be used for the input xslx or xslm? Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, Thanks for the link Pete, i am filling up the spreasheet and it seems a really expensive MP.., isn't it? Maximum # of watchers: 702 Maximum # of unique targets: 999 Maximum # of targets per watcher: 99 As I have a little bit less than 1,500 machines or items (web sites) to watch this will gives me: - I could not watch them from one unique registry(server) as limited to 999 so I need at least two sets of machines with 750 items to watch for each set of machines - 15 Watcher Nodes ??? separated in two set of 750 machines approx... so it might be 8 watcher nodes or items with 99 machines each and another set of 7 machines with 99 machines or items. - so in case I would like the cross-pinging with at least two watcher nodes for each machines i will need 30 machines to do it !!! it seems really expensive !!! Any missing point in my calculation? When filling the spreadsheets at the step 5 I have an error: Cannot run the macro "MultiHostPing_Config_Generator.xlsx!sheet3.GenerateRegFiles'. The macro may not be available in this workbook or all macros may be disabled... Excel 2010 > MutiHostPing_Config_Generator.xlsx > File > Options > Trust Center > Trust Center Settings > Macro Settings > "Enable all macros (not recommended; potentially dangerous code can run)" is the option selected !!! Excel 2010 > MutiHostPing_Config_Generator.xlsx > View > Macros the list is empty I have a doubt... which file should be used for the nput xslx or xslm? it is the xlsm and it works perfectly !!!! I imported succesfully the same reg files to two servers one node watcher and the RMS. For this test I have only 5 machines to watch (PingTarget) to be sure it is not overloaded... BUT only the RMS watcher node is seen by the RMS??? Should the Watcher node have ONLY the SCOM Agent or should it have also the Management Server role? The registries on both servers have the same information... what else could I check to be sure the Watcher Node Role is installed, running etc... working? Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, Thanks for the link Pete, i am filling up the spreasheet and it seems a really expensive MP.., isn't it? Maximum # of watchers: 702 Maximum # of unique targets: 999 Maximum # of targets per watcher: 99 As I have a little bit less than 1,500 machines or items (web sites) to watch this will gives me: - I could not watch them from one unique registry(server) as limited to 999 so I need at least two sets of machines with 750 items to watch for each set of machines - 15 Watcher Nodes ??? separated in two set of 750 machines approx... so it might be 8 watcher nodes or items with 99 machines each and another set of 7 machines with 99 machines or items. - so in case I would like the cross-pinging with at least two watcher nodes for each machines i will need 30 machines to do it !!! it seems really expensive !!! Any missing point in my calculation? Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

List of Ping Targets empty!!!(( 1.Import MP Multi-host ping 2. Copy reg file to watcher role agent 3. Edit reg file 4. Import reg file to registry 5. Enable proxy on watcher node 6. Restart System Management service on warcher agent 7. Refresh list of tagets on SCOM console Empty:-( ???