0

I'm trying to install the "SMB 1.0/CIFS client" feature on an Azure based Windows Server 2019 VM but it can't find the source. Normally, on a physical server or a private VM, I'd mount the original ISO and browse to the "Sources\SxS" folder. However one never gets to "see" the install medium on an Azure provisioned server - I'm guessing it's cloned from a template.

I've got a copy of the Windows Server 2019 evaluation ISO - can I use that?

There is a similar question here but the answer is "try" so not certain and also the question was about W2012: Access Installation Disc from Azure-hosted Windows Server 2012 R2 VM

UPDATE: this doesn't appear to be a problem with source as mounting a Windows Server 2019 ISO doesn't help - there are not related files in the SXS folder.

Rob Nicholson
  • 1,707
  • 8
  • 29
  • 56
  • It seems like this would be simple enough to test. Mount the ISO and try it. – joeqwerty May 22 '20 at 11:54
  • Always get twitchy on production servers but I have just tried it and sources still not found. So suspect source missing message might be a bit of a red herring... – Rob Nicholson May 22 '20 at 12:06
  • It sounds like it is a red herring. I don't recall seeing the prompt for alternate source when installing SMBv1 on Windows Server 2019. Are you able to install any role or feature? – joeqwerty May 22 '20 at 12:08
  • Yes I was able to install the DFS namespace role. Just looked in the sxs folder on the ISO and there is nothing to suggest it's got the SMB feature: https://i.imgur.com/cNqMfzD.png – Rob Nicholson May 22 '20 at 12:09
  • I've got a test W2019 VM lurking around on VMware Workstation - will give it a go there – Rob Nicholson May 22 '20 at 12:09
  • Looks like SMB 1 is not allowed in new Azure VMs: https://azure.microsoft.com/en-gb/blog/smb-version-1-disabled-azure-gallery-windows-operating-system-images/ – Rob Nicholson May 23 '20 at 13:02

2 Answers2

1

Microsoft actively prevents the SMB v1 feature being enabled on Windows Server 2019 when running on the Azure platform for well documented security reasons.

I was trying to enable SMB v1 to diagnose why a QNAP NAS was unable to mount a share from Windows Server 2019 but could from Windows Server 2016. The reason is because this particular NAS is still using SMB v1 to mount remote shares and can't be reconfigured otherwise. Therefore this operation is impossible with W2019 in Azure.

Rob Nicholson
  • 1,707
  • 8
  • 29
  • 56
1

SMB 1.0 is disabled in Azure VM’s since August 2017 when Microsoft established that this is a bug, a third-party application issue or a by-design behavior.

So you won't be able to install it in Azure VM. I was struggling with same issue until I found this article.

https://toptechnotes.com/smb-1-0-disabled/

Manish Chandra
  • 11
  • 1