Farlop's questions

I'm learning how to configure a simple W2012R2 Cluster for a AlwaysOn Basic Availability Group. I have this VM scenario: - 1 DC (outside the cluster) - 2 SQL Server Standard 2016 (in a Cluster)

I've created a File Share in the DC to set it as File Share Witness (FSW). When trying to configure the witness, I get the following error:

There was an error configuring the file share witness '\testbagdc\fsw'.

Unable to save property changes for 'File Share Witness'.

The system cannot find the file specified

If I get inside the share, I can see a guid-named folder with nothing inside. I've also granted full control over the cluster computer.

Any idea?

I've one computer in our network which I first named PC029. Shortly after I changed its name to PC021. This was more than a year ago. Today I've found (thanks to Wireshark) that this computer is flooding the network with NetBIOS and LLMNR queries like

A pc029 (LLMNR)
AAAA pc029 (LLMNR)
NB PC029 (NetBIOS)

I've search through registry and files and I don't know how can I prevent this from happening. Any idea?

Recently I've found the need for allowing access to external people to my TFS server, but I have to be sure that they can't access others servers. This is what I've tried so far:

• Created a security group in domain called: 'external users - no login'
• Changed domain group policy 'Deny log on locally' to include this group
• Created a security group in domain called: 'external users - no network'
• Changed domaing group policy 'Deny access to this computer from the network' to include this group.
• Created the user and added to the two groups created before

All restrictions work fine, but also TFS server has become inaccesible to these users. Is there a way to simply deny access to any computer in the network, but let connect to TFS, like an exception, or something like that?