SOLUS3 - installing agents through SOLUS3 UI

[AlexB]

Manual installs of the client then allow Sims.net and FMS to be installed fine. It is just the first push.

 

I'm imaging a new machine and going to kill the AV (even though it is the same AV from last year) and see. You never know, an update might have caused an issue.

[AlexB]

Just had another thought, going to install a machine from disc, join domain in a folder without and policies and see what happens.

[AlexB]

So, fresh Windows 7 x64 SP1 Ent install, no patches, no AV, no etc...

 

Domain joined into OU=NewComputers,DC=???,DC=???

Added user group to enter into SOLUS3 to local admins

Turned off firewall for domain

 

Same result in SOLUS3 "Access denied to the remote machine"

Can access \\\c$

Can WMI remote connect

 

Pretty sure that makes it a server issue

[Steve21]

Stupid question, but if this is a new server have you actually tested if you can connect to it remotely on SQL Management/SIMs etc? Just wondering if it's an issue server side with connections rather than client.

 

Steve

[AlexB]

While I'm not entirely sure what you are asking...

 

Once SOLUS 3 client is installed on a client the SOLUS 3 server can deliver Sims.net and remote clients can use Sims.net

I can connect to Sims server SQL management interface from another server with the MI installed.

[matt40k]

Stupid question, you are entering a domain administrator username and password with the user fqdn - such as domain\administrator when deploying the s3 agent to the workstations via the s3 ui?

[AlexB]

I am using the domain\ format. However, this is not a domain admin account. It is, however, a local admin on the clients being deployed to.

[sparkeh]

Stupid question, you are entering a domain administrator username and password with the user fqdn - such as domain\administrator when deploying the s3 agent to the workstations via the s3 ui?

First thing I asked

 

Ok another stupid question, I see that you have checked the firewall on the clients, but what about on the server itself?

[matt40k]

Try a domain admin, if that works, then try creating a domain user and adding to the local admin group

[AlexB]

I have tested with the firewall off on the server.

 

If I could try a domain admin account I would, but I have the joy of a county wide domain and no domain admin access. Don't even get me started.

[Steve21]

If I could try a domain admin account I would, but I have the joy of a county wide domain and no domain admin access. Don't even get me started.

 

I thought you had used domain admin account as that's what first post said?

 

If not, have you checked within Solus SQL for permissions as to who can edit the databases etc? ie do you actually have permissions to modify it?

 

Steve

[matt40k]

They are separate, cause your domain admin, does mean you have access to sql. He must have correct sql access to configure and setup s3.

 

Just thought I'd say that before someone potential messes up the sql permissions

[AlexB]

We do not use domain accounts to authenticate against the SQL server.

[Bubbles]

I am using the domain\ format. However, this is not a domain admin account. It is, however, a local admin on the clients being deployed to.

 

In that case, try \ rather than \ when trying to install the agent.

Edited August 27, 2015 by Bubbles
Spelling.

[AlexB]

I have tried \administrator and used the local admin password, no joy

[AlexB]

Just an update to say the issue is resolved, but unfortunately, no one really knows why, so anyone visiting with the issue in future... this thread can't help