Hello.

I need that Everest will run in the background for every person in the company once the computer loads up.

I tried running Everest with the following command:

\\server\Everest\everest /silent /acceptbg

when writing this command manually, locally it working perfectly smooth.

When creating a batch file (file.bat) that has the exact command written inside, and putting it as a start up script on my domain controller, so once a computer on the network will load the script will be running before logging on to windows.

On windows XP workstations - its working smoothly, and the application is running after 1 seconds in the background and the user wont even notice.

On Windows 2000 - It get stuck even before the LOGON screen.

And I cant figure out why. its the same script for both.

Would be great if you could help me fix this problem so the entire company will be able to use it.

Thanks in advance.

Ace

1) What happens if you add /SHOWS to your command-line ?

2) What happens if you change /ACCEPTBG to /ACCEPTMIN ?

3) What happens if you add /SAFE to your command-line ?


Regards,
Fiery

Ok, let me explain myself better.

On the domain network environment its going like this:

There's a Startup script and there's a LOGON scripts.

Start up script - the script will run when the computer loads, getting to windows, Its running 5 seconds _BEFORE_ the LOGON screen (the one with username / password / domain field) are shown.

LOGON scripts - The script will be running after the user wrote the LOGON information (username, password, domain field). the user writing all of that and then the desktop and the user profile starts to load, and also with that , the logon script I've created.

I'm using the following line:

\\server\Everest\Everest /silent /acceptbg

Because I want it to run in the background without showing the Icon in the taskbar.



When writing this line in the STARTUP script, when getting to the point its loading it, before the logon screen, it get stuck! its writing " Loading startup script" and it get stuck there.

If I'm adding the /show to this line. and restart. when it gets to the "loading startup script" its showing me the the loading bar of Everest, it finishes the loading but the "Loading startup script" still stuck.

same thing when adding the /show

even if I just run it with /acceptbg or /acceptmin, doesn't matter how I run it in the Startup script that comes before the LOGON screen, it doesn't work and get stuck.

ONLY ON windows 2000 it get stuck, for windows XP it works fine with STARTUP script.



Now the funny part is, that if I write the same line or any other line and use it for LOGON SCRIPT, that will load after the user will write his details and log on to windows. it works just fine on XP and 2000.

I have no idea what disturbs Everest to run before the logon screen on windows 2000.

thank you for your time, hope you could find a solution.

Ace

...maybe your computer is to fast - think the network connections still are not present, so everest share$ can't be found.
What happend when you use the /Delay option, example:

\\server\Everest\everest /ACCEPTBG /IDLE /DELAY 10 /SILENT /SAFE

Harr(y)

May be there's an .msi package file so i could distribute everest as an agent to all workstation.

just so it will be installed on each computer and will be running in the background?

Thanks.

1) I'm sorry, but EVEREST cannot be launched before the user logon.

2) I recommend you to not distribute EVEREST to all your computers. Simply because it would be a terrible job to modify any EVEREST-related options/settings (would you redistribute the modified EVEREST.INI file to all your computers again? would you update all startup settings on all your computers?), and it actually works quite smooth from the central logon script.

Most our corporate users use the logon script way, and they have EVEREST only in one place in a LAN (on the file server). Easier to update EVEREST (from v1.xx to v2.xx for example), easier to modify any settings, easier to modify the startup parameters, etc. etc.


Regards,
Fiery

can EVEREST be launched as service?

i have launched EVEREST before logon this way:
SC CREATE EVEREST BINPATH= "C:\Program Files\Lavalys\EVEREST Corporate Edition\EVEREST.EXE /ACCEPTBG /SILENT /SAFE" TYPE= OWN START= AUTO ERROR= IGNORE

it works but the Service Control Manager generate an error with ID 7009

there is another one way to launch EVEREST before user's logon:
schtasks /create /tn "Everest StartUp" /tr "C:\Progra~1\Lavalys\EVERES~1\everest.exe /acceptbg /silent /safe" /sc ONSTART /ru ""

this comand schedules a task ;-)

...as Fiery said...

Your method - it's a bad idea - and it funny to see, that your domain and all workstation/server you've to administrate based on Windows XP - schtasks (original exe) are only available in Windows XP - and runs not in W2k, by the way.

But the idea is good (not new, but good) - try to implement the call from an UNC-path - be happy, when all works well...

Maverick

EVEREST can be launched as a service, but it doesn't fully work that way. So you can either create a scheduled a task to launch it, or else you can use the logon script: that is fully supported by EVEREST, unlike the service method.


Regards,
Fiery

I need to launch EVEREST before any users logon that's why I've decided to launch it this way

Then the scheduled tasks method could work. Give it a try


Regards,
Fiery

May be it will be a good idea to run everest at logoff or at system shutdown, not at logon?

I don't see a reason why it would be better than at logon Can you explain why do you think so?


Regards,
Fiery

1. Users are usually don't like to wait for PC. And starting to nerveous when it is loading too slowly. When they switching off PC's it's ok, they can go home without waiting for a computer.
2. Servers. Usually nobody logon to server at all. But it will be nice to control servers too.

1) You can use the /IDLE command-line option to fix such issues.

2) You don't turn off servers either, so on those machines a scheduled task would be best maybe.


Regards,
Fiery