/build/static/layout/Breadcrumb_cap_w.png
10/23/2017 3038 views
Microsoft has quite rightly disabled SMB1 by default in the WinPE 10 version 1709. Unfortunately, if you are still running SDA v3.7.x then you'll find that your scripted installs fail early-on as they try to mount the SMB1 shares from the SDA. Unfortunately, the copy of DISM built-in does not recognise the command line to enable SMB1.

This suggests Quest needs to update the Media Manager tool to enable SMB1 when creating a KBE with 1709. Alternatively, clarity is needed on how one gets to SMB2 or better. So I think we need a knowledge base article clarifying the situation here, stating the issue exists and how to deal with it.

We're scheduled to update to SDA v4.1.1 this coming weekend. So I will find out after that if SMB2 support is enabled in this newer product. We put off upgrading to 4.x earlier this year because of the 23 remote sites we have that will need their RSA migrated to 64-bit.
5 Comments   [ + ] Show comments

Comments

  • i suggest upgrade K2000 Server to 4.0
    migrate your RSA to 64 bit as explained here:
    https://support.quest.com/kace-systems-deployment-appliance/kb/211383
    Upgrade all to latest 4.1.1148 (SP1)
    then upgrade to 5.0 K2000
  • That new ADK 1709 seems to be a single ISO all-together, almost 4GB, so I would try to hold off on doing any Windows 10 1709 until we have official support or maybe someone with a good-working path forward...

    This is not the first time MS does this with ADKs, in older Windows editions I have had issues with the K2000 and it's all-in-one ISO
    • I think you’re talking about the next problem after this one. I didn’t even get that far. I was looking forward to figuring out how to select the correct edition. Although the license key may be enough to do it.
  • I was able to complete a Win7x64 scripted install with a KBE PE10 1709, ADK version is 10.1.16299.15

    I am using K2 SDA version 5.0
    • 5.0 is too new for us. We’re going to 4.1.1 on Saturday. Hopefully it has SMB2 enabled too.
  • Support recommended I wait to move to 1709 as there were a couple issues that they were trying to resolve. I forgot what the exact issues are but they said they should be appearing in the news feed in the near future on the home page of the KACE
  • It's purely experimental for us at this stage. We've got until next Summer to have a production Windows 10 deployment. So I just wanted to get Quest moving quickly on this. I have been unable to submit a tech support case. It hangs at the final stage. So I came here and saw no one was talking about 1709. Somebody's got to go first!

All Answers

0
ADK 1709 and higher has disabled smbv1 support, so if your company doesn't support it, it won't work.  In KBE Manipulator 5.0, we will include the ability to include smbv1 if you choose.  Beta version is already underway and looking good!!
Answered 06/25/2018 by: cserrins
Red Belt