1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

PDQ forcing me to enable SMBv1!

Avatar
Stuart Raper

Just configured a number of Windows 10 workstations (1809) in a domain with server running Windows Server 2012.

Just wasted days trying to get PDQ Deploy to run deployments on these new machines. It seems from the server that IPC$ and ADMIN$ were not available, Even from a command line \machine-name\c$ would give error "The specified network name is no longer available.".

Tried all sorts of firewall related settings and nothing worked. I have checked on the sever using powershell and got: `PS>Get-SmbServerConfiguration

RequireSecuritySignature : True

***EnableSMB1Protocol : True

EnableSMB2Protocol : True***

Smb2CreditsMax : 2048

Smb2CreditsMin : 128

SmbServerNameHardeningLevel : 0 `

So SMBv2 is enabled as it is on the workstations. However refused to communicate until I enables SMBv1 on the workstations.

Anyone have any thoughts how I cant get PDQ to work without enabling SMBv1 on my Windows 10 Workstation.

Running PDQ Deploy 17.1.0.0 in Enterprise Mode!

0

Comments

1 comment
Date Votes
  • Avatar
    Dakota Clark

    Hi Stuart,

    The PDQ products have no reliance on SMB v1. The error you are receiving is a DNS / NetBIOS issue outside of the products themselves. You may find the same error occurs if you attempt to connect to the ADMIN$ share using the FQDN but not the IP address.

    I suggest submitting a ticket to support@pdq.com for help on this.

    Thanks, Dakota

    0