Changes

From SME Server
Jump to navigationJump to search
118 bytes added ,  13:47, 5 October 2021
Line 6: Line 6:  
==Background==
 
==Background==
 
Windows 10 was released in July 2015. Due to changes in the way that trust relationships are established with domain controllers, some modifications to the windows registry need to take place.
 
Windows 10 was released in July 2015. Due to changes in the way that trust relationships are established with domain controllers, some modifications to the windows registry need to take place.
 +
 +
(Note: Windows 11 is due soon. This will be revised in the light of experience for Windows 11).
    
Microsoft [https://support.microsoft.com/en-sg/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and How To detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows]
 
Microsoft [https://support.microsoft.com/en-sg/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and How To detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows]
   −
==Join a Window 10 client to SME Server 9 or 10==
+
==Join a Window 10 client to SME Server 10==
Previously you needed to edit your Win10 registry to facilitate the joining of a SME Server Domain, however this can more easily be achieved by importing win10samba.reg fix by using either a usb key or by the network with http.
+
Previously you needed to edit your Win10 registry to facilitate the joining of a SME Server Domain, however this can more easily be achieved by importing win10samba.reg fix either by using a usb key or by the network with http.To proceed:
    
*Save the Win10 registry patch (win10samba.reg) from https://your-server-ip/server-resources/regedit/ with your favourite web browser
 
*Save the Win10 registry patch (win10samba.reg) from https://your-server-ip/server-resources/regedit/ with your favourite web browser
Line 19: Line 21:     
'''Using PowerShell'''<br>
 
'''Using PowerShell'''<br>
As seen on https://forums.contribs.org/index.php/topic,54125.0.html there is another way (maybe both changes are needed - needs verification):
+
As seen on https://forums.contribs.org/index.php/topic,54125.0.html there is another way (maybe both changes are needed - needs '''verification'''):
    
Start Powershell:
 
Start Powershell:
Line 60: Line 62:     
If you want to be automatically signed into Microsoft's Cloud services (like you would when you login to Windows 10 with a Microsoft Account) you can add your Microsoft Account to your Domain account:
 
If you want to be automatically signed into Microsoft's Cloud services (like you would when you login to Windows 10 with a Microsoft Account) you can add your Microsoft Account to your Domain account:
* Go to: <tt>Start > Settings > Accounts > Your account</tt>
+
 
* Scroll down to the section: '<tt>Other accounts you use</tt>'
+
*Go to: <tt>Start > Settings > Accounts > Your account</tt>
* Click on the '<tt>Add a Microsoft account</tt>' link and supply your credentials
+
*Scroll down to the section: '<tt>Other accounts you use</tt>'
 +
*Click on the '<tt>Add a Microsoft account</tt>' link and supply your credentials
    
===Setting up network drives===
 
===Setting up network drives===
Line 92: Line 95:  
  "ProtectionPolicy"=dword:00000001
 
  "ProtectionPolicy"=dword:00000001
   −
==Notes concerning Window 10 and SME Server 10==
+
==Notes concerning Windows 10 and SME Server 10==
As reported  in [[Bugzilla:9555]], with a default configuration while samba 4.4.4-12 should be able to use the SMB3_11 protocol and Windows 10 should ask for it, it could occur that the negotiation fails, if so, please report. However, there seem to be two ways to work around this. First by editing the server config:  
+
As reported  in [[Bugzilla:9555]], with a default configuration, while samba 4.4.4-12 should be able to use the SMB3_11 protocol and Windows 10 should ask for it, it could occur that the negotiation fails, if so, please report. However, there seem to be two ways to work around this. First, by editing the server config:  
 
   
 
   
 
   config setprop smb ServerMaxProtocol NT1  
 
   config setprop smb ServerMaxProtocol NT1  
Line 103: Line 106:  
   service smb restart
 
   service smb restart
   −
An alternative would be to patch the registry of every windows 10 client with the following:
+
Second, an alternative would be to patch the registry of every windows 10 client with the following:
    
  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\ParametersRegistry]
 
  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\ParametersRegistry]

Navigation menu