Forum Discussion
Solved
Windows Server 2019 Build 17623 SMB1 does no more exists?
Hello,
I tried for a test to enable SMB1 support for the build 17623, but when I give the PowerShell command:
Set-SmbServerConfiguration -EnableSMB1Protocol $true
I have the error:
...
Have you installed the 'SMB 1.0/CIFS File Sharing Support' feature?
Hey Guys
I have a server 2019 data center on azure and I cannot seem to be able to install the SMB 1.0 to be able to connect to my on-prem AD.
I have downloaded the 2019 data center image and mounted it on this server and further added the source path for installing the role. And it didnt fix the issue.
I further tried to install it using Powershell wiht below commands:
Get-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol"
FeatureName : SMB1Protocol
DisplayName : SMB 1.0/CIFS File Sharing Support
Description : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer Browser protocol.
RestartRequired : Possible
State : DisabledWithPayloadRemoved
CustomProperties :
ServerComponent\Description : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer Browser protocol.
ServerComponent\DisplayName : SMB 1.0/CIFS File Sharing Support
ServerComponent\Id : 487
ServerComponent\Type : Feature
ServerComponent\UniqueName : FS-SMB1
ServerComponent\Deploys\Update\Name : SMB1Protocol
When I try to enable it I get the following error that says source file could not be found.
C:\Users\myserver> Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol -source e:\sources\install.wim:4
Enable-WindowsOptionalFeature : The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying
a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
At line:1 char:1
+ Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol -sour ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
+ FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand
I also tried installing it and that didnt work either.
C:\Users\myserver> install-windowsfeature SMB1Protocol -Source wim:E:\sources\install.wim:4
install-windowsfeature : ArgumentNotValid: The role, role service, or feature name is not valid: 'SMB1Protocol'. The name was not found.
At line:1 char:1
+ install-windowsfeature SMB1Protocol -Source wim:E:\sources\install.wi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (SMB1Protocol:String) [Install-WindowsFeature], Exception
+ FullyQualifiedErrorId : NameDoesNotExist,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand
Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
False No InvalidArgs {}
I am really stuck.. I would appericiate if someone could guide me.
I had this problem myself and managed to eventually solve it
The basic problem is that the installation files for SMB1 are not contained within the Server 2019 image that's deployed in Azure. However, you can specify a source for the installation files and continue the install. HOWEVER, if you have updated your Azure VM to the latest updates, you can no longer use the evaluation Server 2019 ISO File as a source.
Here's how I got around the problem:
1. Install a fresh copy of Windows Server 2019 to a temporary server and join it to my domain. Make sure the build number is 17763.737 or lower.
2. Attach the Windows Server 2019 evaluation ISO to the server. Install the SMB1 feature and enter WIM:E:\sources\install.wim:4 as the source.
3. Reboot the server once the feature is installed
4. Install all the latest updates to the server and reboot
5. Share the C:\windows\winsxs folder on the server. Give "everyone" read permission.
6. Go to the server where you are unable to install SMB1. Do the installation but put the source as \\servername\winsxs that you shared in step 5. The installation will complete
It's pretty awful workaround but it worked for me... I guess if you have access to an ISO containing a newer build number, that would also work.
I have the same issue, all the workarounds relate to having a server with the option already installed however this is my first 2019 server.
