lansweeper "agent" vs. Altiris "agent"

[bferris]

We currently have lansweeper premium deployed.

After many hours of fighting and thinking I had the RPC and WMI errors fixed, they just came back on multiple machines.

Therefore my question is what is the process used on a product like Symantec Altiris who uses an agent on the users machine can capture the hardware and software and report it a SQL database without having RPC and WMI errors, yet Lansweeper's lsclient or the lstrigger command are based on this RPC and WMI to work properly.

I would much rather use Lansweeper over Altiris for cost and ease of use capability, but cannot understand why an agent like the altiris agent couldn't be designed to run on a users machine.

If you know of a way or have a script that could capture the hardware/software and put in an "agent" form that doensn't have to rely on RPC and WMI like the Altiris agent, then you would have most of your competition beat.

Any thoughts on this is appreciated.

Thanks

Brian

[cbwchc]

hi, lansweeper Support/Users,
I have a question.
Is there any security concerns if RPC is enabled via group policy even if I only allow PCs to communicate with the lansweeper server.

Can anyone confirm any possible security risks with opening TCP port 135 and 445? and any ways / workarounds to secure your network if you choose to open them.

Thank you very much.

[Hemoco]

cbwchc wrote:
Can anyone confirm any possible security risks with opening TCP port 135 and 445? and any ways / workarounds to secure your network if you choose to open them.

You should make sure that you always install the latest windows updates (but you should do that anyway)

[Hemoco]

First this : try the 3.5.1 beta, it tries to solve RPC issues and also does a firewall check on port 135
http://www.lansweeper.com/forum/yaf_postst1514_Lansweeper-Service-351-update-1-beta.aspx

About your question:

In my opinion not needing an agent on the workstations is a big advantage.
The RPC problems are caused in 99% of the cases by windows firewall not configured correctly or by dns problems.

If you need to install an agent first you have the same problem: how to install on clients which are firewalled?