[sims] SOLUS 3 install on Windows 10

[AJWhite1970]

Morning all

 

I'm getting the dreaded "access denied" when I try and roll SOLUS client out to Windows 10 PC's, all my 7 PC's work perfectly.

 

I've clearly forgotten to do something in my new 10 build but I've allowed all the firewall ports on the PC's using my usual batch file, default admin share is contactable, using the same domain\username I use for my 7 PC's etc

 

Anyone want to direct me away from stupid street and point out what I've missed?

 

Ta

Andrew

[jthompson]

The user account seems like the most likely reason for that error. If the firewall rules aren't in place on the client, we see something along the lies of "remote system could not be contacted".

 

You could try redeploying to a working Win7 system but using a domain/username that you know won't have sufficient privileges, and compare the error message.

[techy32]

Check if UAC is disabled......Create a test folder on Windows 10 "C" drive with the same account you are trying to install solus 3 client.

 

Check if this is successful.......

[3s-gtech]

You're remembering to do domain/username, aren't you?

[AJWhite1970]

Urgh, just found out what it was, SMB 1.0 is disabled on Windows 10 PC's and my 2012 server can't connect to it through \\W10NAME

 

Nothing to do with SOLUS....

 

Thanks for the sanity check though, much appreciated

 

EDIT: Yup, works first time after a reboot...

 

Edited July 11, 2018 by AJWhite1970

[Arthur]

Urgh, just found out what it was, SMB 1.0 is disabled on Windows 10 PC's and my 2012 server can't connect to it through \\W10NAME

Did you disable SMB 1.0 on the server too (as opposed to re-enabling it on Windows 10)?

 

 

All of our Windows 10 PCs and servers have SMB 1.0 disabled and SOLUS still works.

[darkstar_bam]

Which build of Win 10 do you have? Because for us it works with SMB 1.0 off with 1607 but on 1709 it doesn't work with it disabled.

[Arthur]

1703 currently.

[subway_lunch]

Also remember that SMB1 is not installed by default on clean installs of windows 10 from version 1709. So if your machines were fresh builds of version 1709 or later you will need to install it. Microsoft documenting it here ---> https://support.microsoft.com/en-gb/help/4034314/smbv1-is-not-installed-by-default-in-windows

[3s-gtech]

Did you disable SMB 1.0 on the server too (as opposed to re-enabling it on Windows 10)? All of our Windows 10 PCs and servers have SMB 1.0 disabled and SOLUS still works.

Same here, also on 1703 site wide. I disabled SMBv1 while we were still on 7, but I made sure I went through every policy and fix first.

[jthompson]

SOLUS3 is happy for us here too, with SMBv1 having been long disabled on server and clients (mix of 7 and 10). We use a GPO to configure Windows firewall and didn't need to adjust anything for Win 10 (1709) to work.

 

As @Arthur says, if SMBv1 is enabled on your server, that might explain why it's trying to use it to reach clients.