Solus 3 - COM error while pushing SIMS to a virtual machine

[OffAndOnAgain]

Full disclosure - I'm a fairly junior IT tech so may be making some incorrect assumptions here and most likely not giving you all the details you need!

 

SIMS currently deploys fine on our machines, however we're trying to push it out to a virtual machine. We're getting a COM error almost immediately in the Message field on the Agents tab.

 

Can anyone enlighten me as to the cause and possible solution to this please?

 

Many thanks for any advice!

[LeMarchand]

What OS is the machine, and does it have access to the SIMS drive?

 

We have it running on a VM, so it's definitely possible!

[CJLane]

Another simple question is can the VM ping the host name (rather than IP) of where SOLUS is, and vice versa?

 

As well as that, are you able to access \\host name\c$ to the VM (from the SOLUS host), and vice versa?

[OffAndOnAgain]

Thanks for the super speedy reply!

 

It's on Win10 - we did just now make the SIMS drive visible for it but unfortunately it's still throwing a COM error when attempting a reinstall.

[OffAndOnAgain]

Another simple question is can the VM ping the host name (rather than IP) of where SOLUS is, and vice versa?

 

As well as that, are you able to access \\host name\c$ to the VM (from the SOLUS host), and vice versa?

 

Pinging both ways seems to be okay, and I can access the VM's c$ from the SOLUS host.

[CJLane]

Are the SOLUS3 firewall exceptions in place on the VM?

 

52965:TCP:*:Enabled:SOLUS 3 Deployment Server

52966:TCP:*:Enabled:SOLUS 3 Agent

8739:TCP:*:Enabled:SOLUS 3 Agent Notifier UI

[LeMarchand]

SIMS currently deploys fine on our machines, however we're trying to push it out to a virtual machine. We're getting a COM error almost immediately in the Message field on the Agents tab.

 

Have you tried removing the client and trying again? (Targets>Clents>Remove)

 

Might just be me, but the only reliable way to add a new device seems to be using the "Network" radio button.

 

Welcome to the forum, btw!

[OffAndOnAgain]

Are the SOLUS3 firewall exceptions in place on the VM?

 

52965:TCP:*:Enabled:SOLUS 3 Deployment Server

52966:TCP:*:Enabled:SOLUS 3 Agent

8739:TCP:*:Enabled:SOLUS 3 Agent Notifier UI

 

Thanks for your help.

 

Have just set those up but still giving the same error unfortunately!

 

While I find out if we have any other things blocking such connections, do you know of any more possible causes?

[CJLane]

Hmm it's an odd one for definite.

Do you have a screenshot of the error? I'm sure I'll have SOLUS fix notes somewhere around here...

[Jcx500]

is the solus server working fine ? Have you checked the event log on the vm you are trying to deploy it to and the server side logs

[OffAndOnAgain]

Hmm it's an odd one for definite.

Do you have a screenshot of the error? I'm sure I'll have SOLUS fix notes somewhere around here...

 

I'm guessing there's somewhere I can go for a more verbose version of this error? I realise this screenshot is not especially helpful...

[OffAndOnAgain]

Have you tried removing the client and trying again? (Targets>Clents>Remove)

 

Might just be me, but the only reliable way to add a new device seems to be using the "Network" radio button.

 

Welcome to the forum, btw!

 

Thanks!

 

Yes, I've tried removing and re-adding the client and also removing/adding it from all the places it shows up in Solus with no luck

 

You're right, I definitely have more success with adding devices from the Network radio button than I do from typing the name, but in this case it doesn't seem to help.

[dobbyit]

I have had something similar and the windows firewall was stopping it being deployed