1. Working of Script integrated with SiteScope
Site-Scope Server
End Device 5
Through Net-BIOS it will go and deploy the agent in the Server-B, agent get placed in C:\Sitescope_Monitoring and resides there, until Perl running on Server A can’t tell it to run
Create Agent
Agent Deployed
Checks for Http status code and issue Http command in read-only mode
Create Agent for the port running on host B 10
Through Agent, it gathers the contents and simply inform Perl script about the request that was made 4
Before deploying agent, it will add Net- BIOS entries and develop a Network Path of the server 6
Agent which got deployed on the server, after getting the response, it tells about it to the Server A which now responsible to process and act accordingly 9
Getting into server through Net-BIOS and creates Network Path and its history as well
Calls the internal process to prepare and to get the result of each port
Invoke Windows engine to work accordingly what Agent needs and responds back 3 8 7
Evaluation happens
Compiler compiles Perl Script so to get the required action’s response through processor running at this step
Processed the result and perform the action required for each response 11 2
Checks for required folder and other pre-requisites on Server B , if not present, it will create and deploy the missing components 1
Starts by issuing ICMP query to the host, after receiving the response, checks the response for packet %loss as well
Network Path History of all the Servers
Network Path created between them, and there will be no use of passwords again until Server-A does not get rebooted
Log-File which contains information of the actions
A separate component in the log file which shows the failures with date and time
This whole mechanism works on Read-only permission, and no need to install any utility / software to get this done

2. How Script is integrated with SiteScope