#This is a sample .csv file for bulk import of monitors. #1. Header should start with #Header: followed by the Input Field names. It is already coded for you. Note: Do not modify the header. #2. From the second line onwards, give the input values according to the column names in the header. #3. You can remove the example entries in this file from the second line onwards and add your own monitor input information. You can add comments by including # symbol in the beginning of the line. #4. Save the file in any computer but upload it to the Applications Manager webclient using bulk import monitor form. #5. After uploading, click on Next, the entire monitor input information will be shown in a table format for your reference. #6. If everything is OK, click on Start Discovery. The monitors will be scheduled for discovery. It would take few minutes to complete the process. When the monitors are scheduled for discovery, simultaneously the uploaded file will be deleted from Applications Manager (as this file contains security information) #7. If you want to cancel the process in midway, delete the uploaded file from Applications Manager machine. #8. Fields MonitorGroupID and PollInterval are Optional.If PollInterval is not specified, the default value for it will be 5 minutes #9. PollInterval should be given in Minutes. #10.Values with embedded commas can be given inside "". #11.Use CredSSP Authentication - (Yes / False) Specifies if CredSSP Authentication should be used, only when the monitored AD Server is a non-primary Domain Controller and is present in a different domain other than that of the Applications Manager server domain. To enable credssp the value should be Yes. #12.Enter the credentialID, if you wish to use preconfigured credentials details from Credentials Manager. #13.ManagedServerID and ManagedServerGroupName can be specified only if bulk import is being performed from the Admin Server in the Enterprise Edition.If these field values are not specified, then the new monitor will be added in the in least loaded Managed Server. #14.The existing MonitorGroupID have to be specified and it will not create new Monitor Group if the ID specified is not existing.
#Header:DisplayName,HostName,Use CredSSP Authentication,UserName,Password,Timeout,MonitorGroupID,PollInterval Production,Server1,False,Administrator,Biryani,300,10000095,5 Testing,Server2,Yes,Administrator,Biryani,300,10000095,10