RE: Setup.exe & SetupVSE.exe hanging when pushed from ePO 3.

[Former Member]

The agent tries to contact the server on netbios name, then FQDN and at last at ip address stored in the agent config files. If the DNS settings of the client appears to be incoorect, the agent is getting an IP address when asking the DNS with the FQDN.
If it cannot contact the DNS server at all, it is trying the IP stored in the config files.

In your case, the DNS server was not been able to point to the correct IP. The sensors can therefore not connect to the server and checking if the agent has been installed..

Remember, the sensor is not deployed to rough machines, it should be deployed on managed machines. It's task is to detect the rough machines and then, depending on the settings, installing the ePo agent on the rough machines.

[Former Member]

I've run into the same problem when trying to deploy the ePO agent to supposedly managed machines. If someone installs a machine - a rogue - and hangs it on my network, I want to get a virus scanner on it as soon as possible & make sure it updates. I'm discovering, if they haven't joined my domain - what rogue would - I have no way of getting a scanner onto the machine.

[Former Member]

It is not possible to install an agent on a machine when there is no correct username and password known. This could especially the case when a machine from a salesman or a technician of another company is connected to the network.

If RSD was possible to install without knowing this information, it would bypass the machine's security and become an unwanted program by itself...

The only thing RSD can do is inform you when a machine has been detected and an agent installation has failed, so you can check it out...

[Former Member]

yes - I know. I was hoping it used system.

In the meantime - now that I have the sensor installed on the server it still won't accept a deployment of VSE8. I still see the Setup.exe and SetupVSE.exe as hung in task manager, so I'm back where I started.

[Former Member]

Could you post the last part of the VSEInst.log from a client where the setup hangs ?

Cheers Tom

[Former Member]

As I am reading this call again, you don't have any problems installing the same package manually. However, pushed out frome PO the package is not installing correct, am I right?

Check the framework services and the account which is running this service. This should be localsystem.

Otherwise, open a case at primesupport, so they can investigate, as this is becoming a weird issue...

[Former Member]

Framework service is running as LocalSystem. I opened a trouble call open with prime support about the same time I opened this thread. I was hoping other eyes would help find a solution quicker.

I'd worry far less about these 2 test machines if I hadn't seen the same sort of behavior from some of my production machines. I've not been able to identify any commonality so far. I thought the DNS thing might be it until I tried pushing out VSE8 to the test machine. I can see my mis-typing the local admin password once, maybe twice, but six times in a row is a bit much to believe.

I'm seeing more odd behaviors from the production environment since I pushed out CMA 3.5 - have any communication problems been reported with it?

[Former Member]

using ePO3.5 with 2000 clients NT4
having 150 clients which don´t want to install from ePO
setup.exe and McScript_InUse.exe hangs, no action anymore.
running setup.exe manual from current folder runs ok.

any ideas?

[Former Member]

We are now having the same issue. When manually installed we are fine, but when pushing, we get a setupvse.exe error, and it hangs there. Until we log on and manually run out install. Any new ideas?