Windows 10: At wit's end

/u/StarfellWriter · Jan 21, 2020

Ok, so a little while ago, I decided I want to get into game streaming. I'm a stay at home, disabled husband.

I bought a decent pair of headphones, and a professional cardiodid mic.

Everything worked perfectly - until today.

Now, I can't get my mic to work with groups, only the installed mic on the headset. In settings, it shows my cardiodid mic is working fine. Audio recording programs pick everything up just fine. Social apps? Nada.

In addition, the party chat will intermittently start coming out of my speakers. Went into device preference and set every single one of them to headset - still coming out of speakers. As a further test, when the headset is receiving audio, if I set every preference to my monitor, it still comes out of my headset.

I'm about to pull my hair out. What in tarnation is happening?!

submitted by /u/StarfellWriter
[link] [comments]

:)

Brink · Jan 21, 2020

New File Share Witness Feature in Windows Server 2019

This blog discusses a new feature in the upcoming release of Windows Server 2019. Currently, Windows Insiders receive current builds of Server 2019. We urge you to become an Insider and play a part in making Windows Server 2019 the best that it can be. To do so, go to this link and sign up.

One of the quorum models for Failover Clustering is the ability to use a file share as a witness resource. As a recap, the File Share Witness is designated a vote in the Cluster when needed and can act as a tie breaker in case there is ever a split between nodes (mainly seen in multi-site scenarios).

I don’t want to go through the list of all the requirements but do want to focus on one in particular.

The Windows Server holding the file share must be domain joined and a part of the same forest.

The reason for this is that Failover Cluster utilizes Kerberos for the Cluster Name Object (CNO) to connect and authenticate the share. Therefore, the share must reside on a domain member that is in the same active directory forest.

There are scenarios where this is not possible. These scenarios are:

No or extremely poor Internet access because of a remote location, so cannot use a Cloud Witness

No shared drives for a disk witness. This could be a Storage Spaces Direct hyper-converged configuration, SQL Server Always On Availability Groups (AG), Exchange Database Availability Group (DAG), etc. All of which do not utilize shared disks.

A domain controller connection is not available as the cluster has been dropped behind a DMZ

A workgroup or cross-domain cluster where there in no active directory CNO object

We have had a lot of requests over the years for how to get around these scenarios and there wasn’t a good story for it. Well, I am here to tell you we listened, and we produced something better than a workaround.
In comes Windows Server 2019 and the new File Share Witness feature to the rescue.

We can now create a File Share Witness that does not utilize the CNO, but in fact, simply uses a local user account on the server the FSW is connected to.

This means NO kerberos, NO domain controller, NO certificates, and NO Cluster Name Object needed. While we are at it, NO account needed on the nodes. Oh my!!

The way it works is that on the Windows Server you wish to place the FSW, create a local (not administrative) user account, give that local account full rights to the share, connect the cluster to the share.

Let’s take for example, I have a server called SERVER and a share called SHARE I want to utilize as the File Share Witness. For creating this type of File Share Witness can only be done through PowerShell. The steps for setting this up are:

Log on to SERVER and create a local user account (i.e. FSW-ACCT)

Create a folder on SERVER and share it out

Give the local user account (FSW-ACCT) full rights to the share

Log in to one of your cluster nodes and run the PowerShell command:

Set-ClusterQuorum -FileShareWitness \\SERVER\SHARE -Credential $(Get-Credential)

You will be prompted for the account and password for which you should enter SERVER\FSW-ACCT and the password.

Viola!! You are done as we just took care of all the above scenarios. The cluster will keep the name and password encrypted and not accessible by anyone.

Just as an FYI, the original demo of this feature was using a USB thumb drive holding the share plugged into a router. Not that we would recommend doing it, but does show how far you could take this.

Please try out this new feature and provide feedback through the Feedback Hub app.

Thanks,
John Marlin
Senior Program Manager
High Availability and Storage
Click to expand...

Source: New File Share Witness Feature in Windows Server 2019 | Clustering and High-Availability

f14tomcat · Jan 21, 2020

Moving Unallocated Disk Space to End of Disk

Yes I am using the free version 10.2.3. As we previously discussed it was recommended not to change the EFI Partition but to create an unallocated space partition to place at the end of the drive and move the EFI partition to the left............are you saying I should resize the EFI partition creating unallocated space at he end ..not clear on what you are suggesting from your last post
Click to expand...

Was commenting on the pic in post #21. Not suggesting anything. It just looked like the step you were doing was incomplete.

Brink · Jan 21, 2020

New File Share Witness Feature in Windows Server 2019

This blog discusses a new feature in the upcoming release of Windows Server 2019. Currently, Windows Insiders receive current builds of Server 2019. We urge you to become an Insider and play a part in making Windows Server 2019 the best that it can be. To do so, go to this link and sign up.

One of the quorum models for Failover Clustering is the ability to use a file share as a witness resource. As a recap, the File Share Witness is designated a vote in the Cluster when needed and can act as a tie breaker in case there is ever a split between nodes (mainly seen in multi-site scenarios).

I don’t want to go through the list of all the requirements but do want to focus on one in particular.

The Windows Server holding the file share must be domain joined and a part of the same forest.

The reason for this is that Failover Cluster utilizes Kerberos for the Cluster Name Object (CNO) to connect and authenticate the share. Therefore, the share must reside on a domain member that is in the same active directory forest.

There are scenarios where this is not possible. These scenarios are:

No or extremely poor Internet access because of a remote location, so cannot use a Cloud Witness

No shared drives for a disk witness. This could be a Storage Spaces Direct hyper-converged configuration, SQL Server Always On Availability Groups (AG), Exchange Database Availability Group (DAG), etc. All of which do not utilize shared disks.

A domain controller connection is not available as the cluster has been dropped behind a DMZ

A workgroup or cross-domain cluster where there in no active directory CNO object

We have had a lot of requests over the years for how to get around these scenarios and there wasn’t a good story for it. Well, I am here to tell you we listened, and we produced something better than a workaround.
In comes Windows Server 2019 and the new File Share Witness feature to the rescue.

We can now create a File Share Witness that does not utilize the CNO, but in fact, simply uses a local user account on the server the FSW is connected to.

This means NO kerberos, NO domain controller, NO certificates, and NO Cluster Name Object needed. While we are at it, NO account needed on the nodes. Oh my!!

The way it works is that on the Windows Server you wish to place the FSW, create a local (not administrative) user account, give that local account full rights to the share, connect the cluster to the share.

Let’s take for example, I have a server called SERVER and a share called SHARE I want to utilize as the File Share Witness. For creating this type of File Share Witness can only be done through PowerShell. The steps for setting this up are:

Log on to SERVER and create a local user account (i.e. FSW-ACCT)

Create a folder on SERVER and share it out

Give the local user account (FSW-ACCT) full rights to the share

Log in to one of your cluster nodes and run the PowerShell command:

Set-ClusterQuorum -FileShareWitness \\SERVER\SHARE -Credential $(Get-Credential)

You will be prompted for the account and password for which you should enter SERVER\FSW-ACCT and the password.

Viola!! You are done as we just took care of all the above scenarios. The cluster will keep the name and password encrypted and not accessible by anyone.

Just as an FYI, the original demo of this feature was using a USB thumb drive holding the share plugged into a router. Not that we would recommend doing it, but does show how far you could take this.

Please try out this new feature and provide feedback through the Feedback Hub app.

Thanks,
John Marlin
Senior Program Manager
High Availability and Storage
Click to expand...

Source: New File Share Witness Feature in Windows Server 2019 | Clustering and High-Availability

Windows 10: At wit's end

At wit's end

At wit's end

At wit's end

At wit's end - Similar Threads - wit's end

Daily BSODs, Im at my wits end

Daily BSODs, Im at my wits end

Im at my wits end with this machine!

Im at my wits end with this machine!

Im at my wits end with this machine!

Windows 11 version 23H2 refuses to install on my computer-- at wits end

Windows 11 version 23H2 refuses to install on my computer-- at wits end

BSOD - unexpected_kernel_mode_trap - at wit's end

BSOD - unexpected_kernel_mode_trap - at wit's end