SOLUS "Install Failed". Cannot browse to PC

[Gongalong]

Hi folks,

 

I've got two new PCs running Win 10 1709.

 

SOLUS cannot deploy to them, gives an "Install failed" error. The domain firewall is off. Oddly I cannot browse to these PCs from the SIMS server e.g. \\hostname\c$, although I can ping them. I can browse to other PCs without issue.

 

Any ideas why I can't browse to these PCs?

 

Thanks

[Gongalong]

Just to add, I have another 2012 R2 server (file server) which can browse to these PCs without issue.

[Gongalong]

The specific error when I try to browse to these PCs is "Windows cannot access. Error code 0x80070035." I get this even before I try and access a share to the PC, this is just browsing to it under Network. If I enter the IP address of the PC I get the same error.

 

Found a lot of things on this e.g. disabling IPv6, ensuring various protocols are in place, TCP/IP NETBIOS helper is running, but nothing has worked so far.

[robsonma]

In your Network settings on the PC's input the ip address/gateway and DNS and re-boot then try and ping them or browse to them and let us know the results.

Is it Solus 3 you are using?

[Gongalong]

The client is currently DHCP, and the SIMS server has a static address. I can ping both ways, but I can't browse to the machine in Explorer, either by name or IP address. When I try to do that I get the error above. I can try a static address on the client, at least for testing.

 

These machines are a little odd from a network perspective, in that they were built with a wired connection, but will then have USB wireless. We're going to try building a third machine, and test if the SIMS server can access it before we switch to wireless.

[robsonma]

Just check your Sims Share on your server looks as it should, just for testing add the machines,

right click share>Properties>Sharing Tab>Advanced Sharing>Click permissions>Add>Object types>tick Computers>Add Computer Names and add

Test Again can you browse?

[Gongalong]

The SIMS server itself though can't browse to these machines, and apparently that's a key requirement of being able to deploy with SOLUS (sorry, meant to confirm we're using SOLUS3).

 

I will test whether the SIMS share is visible.

[Esteban_Child_of_the_Sun]

I had something similar to this at one school, it turns out their network was configured with VLANs and the new server was put on a different VLAN to the rest of the servers. Because of the configuration, I was unable to see/ping some machines form the new server but I could form the old one. Edited November 9, 2017 by Esteban_Child_of_the_Sun

[Gongalong]

We do have VLANs, but this server would be on the default VLAN.

 

@robsonma My colleague had already checked, and both the problem machines could see the SIMS server and map the SIMS share. So it's just the SIMS server that has a problem seeing these two PCs.

 

Just built a third machine, so will see what happens...

[MrBrow]

Until I read that the SIMS server cannot access the new clients, I was going to say that Solus3 will fail to deploy on fresh builds of 1709 as SMB v1 is disabled by default. Solus3 uses SMB v1 it seems and will need to be installed on the client for it to deploy the agent.

 

Only done basic testing so far but it failed before and installed post SMB v1 installation.

[Gongalong]

Ah-ha! That explains it!

 

We did some testing this morning, and it will install on 1703.

 

Now we have another problem, when we try and update we get "Cannot deploy SIMS Summer 2017 Full Release (7.176.43) as the update is missing from repository. Please ask your SOLUS3 deployment manager to download the update again." Aaaaaagh!

[mavhc]

Until I read that the SIMS server cannot access the new clients, I was going to say that Solus3 will fail to deploy on fresh builds of 1709 as SMB v1 is disabled by default. Solus3 uses SMB v1 it seems and will need to be installed on the client for it to deploy the agent.

 

Only done basic testing so far but it failed before and installed post SMB v1 installation.

 

And I thought SOLUS couldn't get any worse, such genius, much wow.

[MrBrow]

I actually came looking for verification for the issue ourselves (wondering why Capita haven't fixed it knowing it was announced a while ago so Solus needs to be fixed).

 

Then found this: http://www.edugeek.net/forums/windows-10/189880-win-10-1709-sims.html

 

 

No comment on the new issue :/

[mavhc]

I actually came looking for verification for the issue ourselves (wondering why Capita haven't fixed it knowing it was announced a while ago so Solus needs to be fixed).

 

Then found this: http://www.edugeek.net/forums/windows-10/189880-win-10-1709-sims.html

 

 

No comment on the new issue :/

 

You wonder why Capita hasn't fixed something that's 20 years old and they knew it was being phased out? Have you met Capita?

[Gongalong]

Not sure what's up with this server. It cannot browse its own shares e.g. its own SIMS share! This is preventing SIMS from deploying.

 

Anyway, not sure if it's a server issue, so have posted it here http://www.edugeek.net/forums/windows-server-2012/190265-cant-browse-its-own-shares.html#post1626644

[Esteban_Child_of_the_Sun]

This is what Capita had to say in regards SMBv1

From: SIMS Support [mailto:[email protected]]

Sent: 10 November 2017 13:19

Subject: Capita Incident Reference: 1711-3707451 

Thank you for contacting the help-desk,

I can confirm that Solus 3 will work fine with SMB2 if SMB1 has been correctly disabled and removed and SMB2 has been activated.

2^nd Line Technical Analyst

Capita SIMS

[Gongalong]

Odd, because all the evidence suggests not. As far as I can see there isn't a way to remove SMB1, it just gets enabled or disabled.

 

I've asked our county support to confirm this was Capita, but nothing so far.

[MrBrow]

This is what Capita had to say in regards SMBv1

 

So, do we think this is referring to the server or the client? I agree with @Gongalong as SMBv1 is disabled by default on the client and you can't fully remove it, just uninstall, which it is already.

 

It makes sense if it were needing to be disabled on the server if SOLUS is attempting a connection at v1 first and and working its way up. Don't know what else may break in SIMS though if SMBv1 is disabled. Knowing SIMS......

[mavhc]

Windows 10 1803 will disable smb v1 by default

[MrBrow]

Introduced in 1709 but going forward this issue will be there for any new installs.

[Gongalong]

County said it's a problem with Windows on our server, so won't support it. The difficulty is that with SMB v1 disabled on the server I can't deploy SIMS. I've done a bit of digging and there seem to be various issues e.g. registry entries, that can cause SMB v2 to break. Aaaaaaagh! I'll have to troubleshoot over the Summer hols.

[MrBrow]

Ah, so you have disabled it on the server too? I only witnessed what happens with it disabled on the client only. The next thing was to try the server as well but if you have done that and it really fails, then I wont bother!

[Gongalong]

I think what happened is the server received an update that disabled it, so "out of the blue" SIMS would no longer install. Eventually we figured out that v1 had been disabled, and that enabling it again fixed the issue. It's a faff though because we need to enable it on new PCs, and it's also a security issue having it enabled.

 

- - - Updated - - -

 

Presumably others here have v1 disabled on their server (and clients) and SIMS is deploying happily with v2?