whats-coming-in-windows-10s-redstone-4-update-available-march-2018

My big concern here is going to be networking. they are dropping Homegroup, trying to replace with one drive. I don't use one drive and do use P2P network for my small network. Does anyone know what we are going to have to tweak to keep our P2P networks working? I would like to be prepared for this. FCU forced several changes to get our P2P connected again??????

Barman58 said:

Homegroup was a failed attempt to replace the standard network which has not been deprecated as it's an industry standard and is used everywhere Including Microsoft server Client systems.

Homegroup was a simpler system to set-up and designed for those with little of zero networking experience, take up was low due to complexity and numerous unforeseen issues and so it is no more

The workgroup based system is still available as Onedrive is useless in a lot of markets where net access is not up to required standard and will be for many years

I agree completely that homegroup and one drive are useless at least for me and my applications Each of my computers has its own purpose and setups and syncing them to my cell phone would be a pure nightmare. LOL

My post was I'm hoping to find what hoops we are going to have to jump through with SCU to keep our WorkGroup P2P networks up and running so I can prepare, before upgrading this time.

Thanks for the reply Barman58, This is good news, my reference was the FCU turned off SMB1 which we have to find and turn on things like this is what I was asking about. It took me a few days to find the info about turning back on SMB 1.0 and Homegroup services also had to be turned on and set to autoload for P2P networking to work. hoping not to have to go through the same long process to keep my network up and running?

Barman58 said:

SMB1 is an unfortunate side effect of those who want to steal from normal users. SMB1 is a depreciated and very insecure protocol and would have been removed from use even if it was not done in the FCU Upgrade, The unfortunate side hit me too as my smart TV uses it for some content provision, now I have to decide if the content is worth the risk of some malware getting on the local network via the TV - I still run SMB1 on the TV when I need it but have professional AntiMalware to mitigate the risk

The risk is over my head technology-wise, but if they remove it completely what will we replace it with to maintain our networks without a dedicated server. I too to continue to use SMB 1.0 as that is the only path I found to maintain my WorkGroup network.

I run Norton and Malwarebytes both paid full versions and an up to date Router Asus RT-AC68U up to date firmware. With D-link 615 wireless entry points these are old but are only used for entry anything coming in still has to go through my router for access.

Barman58 said:

SMB2 and SMB3 are both in use and active they were introduced with Vista and Windows 10 respectively - so unless you are using XP or earlier you should be using SMB2 and for a Windows 10 based network SMB3



The issues that do arise concern other devices that we find connecting to or home networks these days which still utilise the older SMB1 protocol, the Wanacry malware attacks that caused issues last year for some Government organisations who were not fully patched, (or were still using XP! ), utilised the flaws in SMB1 to get into systems and although the use of a good Anti-Malware will (or should) prevent this, and all the top ones have now hardened the defence now, the best technique is to not use it at all if you can.

One of the common issues was due to some NAS setups using SMB1 in their controllers to allow compatibility with as many operating systems as possible

Further Reading
http://www.thewindowsclub.com/disable-smb1-windows
https://support.microsoft.com/en-gb/...r-version-1709

Hmm, my 4 computers 2 workstations 1 all in one Win 8.1 and 1 notebook. After Smb 1.0 was turnoff I only had a connection to the 8.1 desktops from it could not see any of the other computer and the other computers couldn't see each other. Turning on SMB 1.0 solved the issue. None of these are really older equipment. So it sounds then like those of us using Workgroups are going to have to find workarounds again after SCU.

I think this subject might need to have a thread in Networking & sharing so we possible can have a workaround sorted out before we update?