Changes

==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 needs 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.

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]

'''Using PowerShell'''<br>

'''Using PowerShell'''<br>

As seen on https://forums.contribs.org/index.php/topic,54125.0.html there are another way (maybe both are needed - need 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:

</gallery>

</gallery>

=====MS Windows workgroup configuration=====

=====MS Windows Workgroup configuration=====

Go to the "start menu", right click on computer, select "System", select the link "System Info", then click on "Change settings" Tab. In the field for "Computer name, domain and workgroup settings", type your "workgroup".<br />

Go to the "start menu", right click on computer, select "System", select the link "System Info", then click on "Change settings" Tab. In the field for "Computer name, domain and workgroup settings", type your "workgroup".<br />

If you are using SME Server as a domain controller and the workstations have joined the domain

If you are using SME Server as a domain controller and the workstations have joined the domain

you can automate drive mapping and syncronise the PC time with the netlogon.bat file  

you can automate drive mapping and synchronise the PC time with the netlogon.bat file  

Note: [[:SME_Server:Documentation:Administration_Manual:Chapter13#Workgroup |Chapter 13]] has a method for admin to edit the netlogon.bat file without using the command line. You can consider also the [[SME_Server:Documentation:Administration_Manual:Chapter7|chapter 7]] on Configuring the Computers on Your Network

Note: [[:SME_Server:Documentation:Administration_Manual:Chapter13#Workgroup |Chapter 13]] has a method for the admin to edit the netlogon.bat file without using the command line. You can consider also the [[SME_Server:Documentation:Administration_Manual:Chapter7|chapter 7]] on Configuring the Computers on Your Network

  nano -w /home/e-smith/files/samba/netlogon/netlogon.bat

  nano -w /home/e-smith/files/samba/netlogon/netlogon.bat

===Outlook 2016 on Win10===

===Outlook 2016 on Win10===

for both SME9 [[Bugzilla:10106]] and SME10 [[Bugzilla:10169]] a registry modification has been added to the default win10samba.reg. While setting up an email account on a windows 10 computer joined to a domain

For both SME9 [Note: SME9 is obsolete as of 30 November 2020] [[Bugzilla:10106]] and SME10 [[Bugzilla:10169]] a registry modification has been added to the default win10samba.reg. While setting up an email account on a windows 10 computer joined to a domain

(with roaming profiles) you would get an error code: 0x8004011c without this.

(with roaming profiles) you would get an error code: 0x8004011c without this.

  "ProtectionPolicy"=dword:00000001

  "ProtectionPolicy"=dword:00000001

==notes about Window 10 and SME Server 10==

==Notes concerning Window 10 and SME Server 10==

As reported  in [[Bugzilla:9555]], with default configuration while samba 4.4.4-12 should be able to use SMB3_11 protocol and Windows 10 should ask for it, it could occurs that the negotiation fails, if so, please report.However, there seems two way to workaround this. First by editing the registry of windows clients:  

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 registry of windows clients:  

   

   

   config setprop smb ServerMaxProtocol NT1  

   config setprop smb ServerMaxProtocol NT1  

   service smb restart

   service smb restart

An alternative would have been to patch the registry of every windows 10 client with the following:

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]

==reverting win10samba.reg changes==

==Reverting win10samba.reg changes==

If you need to revert back the win10samba.reg changes, this is the batch to do it:<br>

If you need to revert the win10samba.reg changes, this is a batch file to do it:<br>

  @echo off

  @echo off

  reg delete HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters /v "DNSNameResolutionRequired" /f

  reg delete HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters /v "DNSNameResolutionRequired" /f