Have you guys tried to install everest on client pcs over the network with PSEXEC?

I would like to know what is the command line to do that.

Thanks!

It's a bad Idea to install Everest local on each client. You only need a servershare where you placed all files of Everest package.
Then set a GPO, a login script with the parameter you need like

\\server\share\everest.exe.....

So you can update very easy, if a new version comes out.

If you want Everest runs with an admin account to get sensor information, smart status, serial of ide-hdd as example you can use 3rd party to set Everest as a scheduled task or as a service...

Maverick

PS: 3rd party includes a script using psexec to get different reports without doing anything on the clients. just scanning and get a report you can select like simpel report, detail report, xml or csv report, ...

Sorrry my English is bad.

I can run Everest with PSEXEC

Create hosts.txt in EVEREST folder:


Create Collect_Info.bat in EVEREST folder:


Create 1.bat in EVEREST folder:


Create start.bat in EVEREST folder:


create folder "work" in everest folder

RUN Collect_Info.bat

Reports wold be in \\server\everestfolder\work

Thanks a lot R.I.V. I'll try that, but does this procedure install everest on the client machine or it just runs the software?

The question of the topic is wrong, I don't really want to install everest on each client machine, I just want to get it to work, but the clients don't have admin rights so I can't get everest to work on the client's machine, that's why I want to learn how to use PSEXEC.

EVEREST can work without admin rights...

That's correct - but you must explain following, too:

If Everest is runnning without admin rights you CANNOT get information about:

1. sensor properties and temperature
2. SPD - no memory module properties (serial numer for ram module as example)
3. ATA - no ATA device properties (serial numer for HDD as example)
4. SMART - no attributes (having info getting Support change HDD before user can't work anymore...)

Maybee that's all? IPMI (if available) ?

You see - if you need only one info from my list - you must be install it as scheduled task/as a service

With regards

Harr(y)

IPMI is also not available, so as chipset information (memory timings).


Regards,
Fiery

Everest is already running on the client's machine, but can I get their pc information without having to manually click on Remote -> "Accept Incoming Remote Connections"?

When launching EVEREST on the remote systems you can use the command-line option /ACCEPT or /ACCEPTBG for such purposes.


Regards,
Fiery

This collection of scripts is processing the computers sequentially (one by one). Could you think of a way to launch everest on all those machines simultaneously? Then I could get the results 50x faster (I have 50 computers )