[xennon]

Thanks for taking the time to read this post

I have a Windows 2003 server with 20 client machines all running XP SP2

I have added \\server name\everest\everest.exe /ACCEPTBG /SAFE to a login script which works 100% and starts everest on all machines.

I have created a MYSQL database called everest and imported the table structure and completed the database settings in prefferences.

I am able to do a remote report, it creates the CSV file and then I import it manually to the database.

I would now Like to automate this process by:

making the server that has everest.exe execute a scheduled script to run remote reporting on all the clients and add the data to the database

I have tried to create a batch file that has the following:

EVEREST /RMTREPORT e:\everestreports\$HOSTNAME /RMTHOSTS pc1name /DATABASE /AUDIT

but it just opens up everest on the server (I execute this on the server)

Your assistance will be greatly appreciated

[Fiery]

Your command-line seems to be alright, we've checked it in a similar configuration, so I'm not sure what goes wrong...

Are you sure you launch EVEREST Corporate Edition on your server?

[Evilfish]

Xennon,

The remote report actually connects a local session with a remote session, so the application must be running in background in the machine you want to measure. It can run as silent, so the user do not see the icon in his/her taskbar.

When the report is done, it can be written in a file, or in a remote database. If that is the case, you should install a ODBC connector and set it up to point at your database; i.e. if your Everest "server" is 1.2.3.1 and you want to monitor all machines in 4.3.2.x, all those machines must be running an Everest session before connecting, and should have ODBC installed and properly configured to connect to Everest database.
If you need additional assistance, take a look at the help in Everest, regarding Database settings and Remote reports.

[xennon]

Xennon,

The remote report actually connects a local session with a remote session, so the application must be running in background in the machine you want to measure. It can run as silent, so the user do not see the icon in his/her taskbar.

When the report is done, it can be written in a file, or in a remote database. If that is the case, you should install a ODBC connector and set it up to point at your database; i.e. if your Everest "server" is 1.2.3.1 and you want to monitor all machines in 4.3.2.x, all those machines must be running an Everest session before connecting, and should have ODBC installed and properly configured to connect to Everest database.
If you need additional assistance, take a look at the help in Everest, regarding Database settings and Remote reports.

I have a script running on all the clients to let everest w8 for a connection

So what u are saying is that I cannot run the script to collect remote data centrall just from the server?
Tha I need to run the script on each client and get them to capture the data to mysql through the ODBC connecter.

[Evilfish]

Xennon,

When you run that line as /CSV, it works OK, but nothing happens when you try using /DATABASE, isn't? If that is the case, you should include the ODBC connector in your client machine (the machine you want to measure). The command line is OK, and must be executed from the server. The problem is, if the client machine does not know how to reach the database, the report is not executed at all.

Take a look in the help, Preferences\Database, and check if your machines can connect to the database remotelly.

[SpaceCowboy]

Xennon,

I agree with the assessment so far. If you want the remote machines to enter the data into your database, you need to create the ODBC entry on each machine and set it in the Preferences for each instance of Everest.

I have noticed in my endeavours if the Everest application is open, the batch scripts seem not to work, they just make Everest the active application and not execute the batch script.

If that is what you are experiencing, try exiting the Everest application then running your batch scripts.

SpaceCowboy