Search the Community

Afternoon, Fail over cluster if Cluster managed voting is Enabled do you still need quorum witness? The reason i ask is because we set up a 3 node cluster but still get the "The cluster is not configured with a quorum witness. As a best practice, configure a quorum witness to help achieve the highest availability of the cluster." on validation even though Cluster managed voting: Enabled if a witness is needed for 3 nodes how is that different from 2 nodes with a share witness? This will be used for SQL.Thoughts? This will be used for SQL.

Good morning We use VMware templates to create servers. We noticed that after installed windows server 2022 the recovery partition is after the C: drive.This can create issues when the C drive needs to be expanded. IS it safe just to delete and remove the recovery partition so C: can have room to expand?Would doing this cause ay future issues? Aside from needing the recovery partition. And could one just make a bootable DART disk if it was really needed?We never use the recovery drive, because we have snapshots backups and most of the time we would just rebuild the server. Thoughts?

Setting up failover Clusters using windows Server 2022.Both nodes are server 2022 fully patched.Both nodes are running on VMware ESXI/vSphere Validate Switch Enabled Teaming ConfigurationsDescription: Validate that Switch Enabled Teaming configuration, if present, is consistent between cluster nodes.Start: 1/31/2022 12:34:31 PM.Validating Switch Embedded Teaming Settings.An error occurred while executing the test.Unable to connect to SQL22-DEV-N01.DOMAIN.org via WMI. This may be due to networking issues or firewall configuration on SQL22-DEV-N01.DOMAIN.org.Invalid namespaceStop: 1/31/2022 12:34:31 PM. Is Microsoft requiring Teams for Clusters using server 2022 or is this a bug? Thoughts on how to work around this issue? EDIT: i found this is similar to the issue we are having.. https://docs.microsoft.com/en-us/answers/questions/589879/server-2022-cluster-validation-network-invalid-nam.html

Currently running 2012 on a single physical server with a number of VMs that has had most, if not all, of it's disks replaced over the years. More disks getting dodgy, so going to get a new (to us) box. Lots of questions (in bold) to follow! Basically, going to do a similar setup to the existing one: 2 SSDs RAID 1 to run the OS and possibly the VEEAM VM on with the other disks in RAID 5 for everything else. Does this make sense? Next up: 2022 or 2019? Time at that site is VERY limited, so I was considering cheating and just copying the existing VMs as VEEAM replicas in case the old machine dies - that way everything should be running from Day One. Feasible? Finally, I was planning on setting up 2022 (or 2019) "fresh" VMs and moving data and roles across at my leisure. Eventually there will be the same sort of setup but with all the servers on 2022 apart from probably the SIMS server that will remain as a replica (no longer use SIMS) and plan to remove it completely after 5 years. Or should the SIMS data be retained longer? Does the slow replacement idea sound viable? Once everything is hunky dory, the old server would have it's dodgy disks removed and used for offsite backup. Expect a lot more questions in September!

I can't activate, I've used my MAK key with 45 activation but the server insists that MY activation server is uncontactable. The help is: contact your administrator. FML done the slmgr /ato the result was: NO KMS could be contacted? (I do have a KMS server but I don't have that setup for server 2022 and didn't want to bother it) ((and I didn't use a KMS client key with the datacentre servers)) what is wrong, I've put a proxy in and can surf the web?!!

I just took over KMS from another admin that is leaving, I got the basics from him, but wanted to ask some questions to make sure I understand what’s going on here, as I have never managed a KMS server before. We needed to add the key for server 2022, from my understanding this will also activate win11 win10 and previous versions of server and desktop. For example, “the KMS host key Windows Srv 2019 allows you to activate all previous versions of Windows, starting from Windows 7/Windows Server 2008 R2.” I would assume the same for win server 2022 standard key form VLSC? When Guides/blogs refer to KMS host key, they are talking about the Host key one gets from the VLSC? So, if I want servers and desktops to be activated I just get the key for Windows Server 2022 standard and import that? The commands I used was the below, is this standard procedure on how to do this? And I fell like those command is for KMS/DNS not KMS/AD. .\cscript.exe slmgr.vbs /ipk 12345-33333-55555-ZZZZZ-XXXXX .\cscript.exe slmgr.vbs /ato .\cscript.exe slmgr.vbs /dlv Mostly Followed this guide: https://theitbros.com/activate-windows-with-kms-server/ If the above is for KMS/DNS what are the commands for KMS/AD (Yes, I know I need enterprise admin). I know one can use “Volume Activation Tools” to add the Key for AD, but how does one do it from the command line? I know we use both KMS/DNS and KMS/AD, as we can find records for both. After running the above commands my test windows server 2022 did activate after a reboot. However why do I hear some people say you need to run 5-25 clients before the KMS will activate them. For example, I would need to spin up 25 windows 2022 server before KMS would kick in? A question about he VLSC, we are EDU So how long before Windows 11 ISO is released on there? I already see it in SCCM an servicing update… Thanks in advance, just need some these cleared up to have a better understanding. -AA

On any/all servers running Microsoft Windows [Version 10.0.20348.1607] the BPA scans fail due to the execution policy being overridden by one on a more specific scope. I've checked Group Policy, and Local Policy, neither set anything for Windows PowerShell in either the computer settings or the user settings. As further proof that it's not Group Policy, servers in the same OU (same user logged in) run the BPA without issue. Has anyone else experienced this? Searches haven't turn up anything useful. (This was particularly useless.)

Hey everyone, I am having a few issues with Windows Update and Adding/Removing Roles and Features on my Server 2022 DC. When I try to install any updates (even offline), I get error 0x800f0831 (image attached of log) and I get error 0x80073701 when I try to add or remove features (image of log also attached). Here is a list of things I have tried: Ran sfc /scannow, it did nothing. Ran DISM /online /cleanup-image /restorehealth, which didn't complete successfully, due to some error where it couldn't find source files Tried to install Windows Updates manually using WSUS Offline, which resulted in the same 0x800f0831 error. I would be appreciative of any help, this issue is driving me insane and I can't seem to find a solution. What I found strange about this issue is that it just started randomly happening one day, and I'm not quite sure why. Thanks in advance, Lewis