Lavalys Discussion Forum: Unable to use Remote features of EVEREST - Lavalys Discussion Forum

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Unable to use Remote features of EVEREST

#1 User is offline   cruzolo

  • Newbie
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 27-September 07

Posted 27 September 2007 - 10:13 PM

Hi

I can't connect to any machines in the network. Every time I try to monitor a remote computer I get "Error 10060". What should I do in order to be able to do a remote scan of the computers in the same local network?
0

#2 User is offline   Fiery

  • Lavalys Developer
  • PipPipPip
  • Group: Lavalys Moderators
  • Posts: 10,155
  • Joined: 30-July 04

Posted 27 September 2007 - 10:32 PM

You need to be running EVEREST on your remote computers to let your admin computer connect to them.

For example, add a new line to your central users logon script:

\\server\share\everest\everest.exe /ACCEPTBG /SAFE


Regards,
Fiery
0

#3 User is offline   cruzolo

  • Newbie
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 27-September 07

Posted 28 September 2007 - 06:49 AM

QUOTE(Fiery @ Sep 27 2007, 10:32 PM) View Post
You need to be running EVEREST on your remote computers to let your admin computer connect to them.

For example, add a new line to your central users logon script:

\\server\share\everest\everest.exe /ACCEPTBG /SAFE

Do you mean I should install Corporate Edition on each computer? How and where I can find this script so I can add that line to it?
0

#4 User is offline   Fiery

  • Lavalys Developer
  • PipPipPip
  • Group: Lavalys Moderators
  • Posts: 10,155
  • Joined: 30-July 04

Posted 28 September 2007 - 11:41 AM

You don't need to install EVEREST on all your computers, but you only need to run EVEREST from a central location (e.g. \\server\share\everest). The logon script can be found on the NT domain controller.


Regards,
Fiery
0

#5 User is offline   cruzolo

  • Newbie
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 27-September 07

Posted 01 October 2007 - 12:52 PM

Damn, I'm such a noob I don't know anything about logon scripts nor domain controllers plus my English is not perfect. Could you please tell me in other words how to set up remote features? I've googled logon scripts, domain controllers and as far as I know we don't use any logon scripts. We work with two domains and have two Win2k3 servers. Is there a step-by-step guide for newbies how to make audit via EVEREST? Not every computer is server connectable so is there a way to skip the servers and do audits from my computer which uses the same network?

This post has been edited by cruzolo: 01 October 2007 - 12:55 PM

0

#6 User is offline   cruzolo

  • Newbie
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 27-September 07

Posted 07 October 2007 - 09:50 PM

OK, I've read the article found here and found the Logon Script entry. Does it mean if we have 500 computers in the company there's need to add the script to each user on each computer? I'm not sure if I got it OK, so could you please tell me what do you mean by central users?
0

#7 User is offline   Jaroslaw Dyaczynski

  • Newbie
  • Pip
  • Group: Members
  • Posts: 1
  • Joined: 23-October 07

Posted 25 October 2007 - 08:29 AM

QUOTE(cruzolo @ Oct 7 2007, 11:50 PM) View Post
OK, I've read the article found here and found the Logon Script entry. Does it mean if we have 500 computers in the company there's need to add the script to each user on each computer? I'm not sure if I got it OK, so could you please tell me what do you mean by central users?


It depends on how your network is organized. If you work in NT domain environment you can put this entry to central login script via GPO - if you don't know what I'm talking about just talk wit somebody in your organization who's responsible for network.

In NT domain every user is authenticated via domain controllers - so only one central login script with Everest entry i needed.

If you work in the workgroup (assuming your number of nodes it's less possible) - you can:
1) add login script manually - sorry for you if you have to ...
2) copy using admin shares login script to the every computer - it can be automated by some tools ie psexec from SysInternals - but you need to know the admin credits for every machine.

Regards
Jarek

This post has been edited by Jaroslaw Dyaczynski: 25 October 2007 - 08:30 AM

0

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users