Unable to read server queue performance data
Has anyone started seeing this on Windows Server 2016? Unable to read Server Queue performance data from the Server service. The first four bytes (DWORD) of the Data section contains the status code, the second four bytes contains the IOSB.Status and the next four bytes contains the IOSB.Information. We have this on two of our Cluster at the moment. The same two nodes also end up having issues draining and will lock resources. The other 2 nodes are fine as far as I can see
How to change the IP of Windows Faiolver clustering
Hello We have windows server 2012R2 STD Host Failover clustering with 10 nodes and 20 roles inside. How should it change the ip address of network and management, heartbeet, so that we can seamlessly start the process. Please suggest the step wise ip changing process. From Mitesh
Windows Server 2019: The component store has been corrupted. Error 0x80073712
Hi all, I'm trying to install the Server Backup feature on our 2019 Server, but it results in this error: Any ideas on what may have caused this, and how to solve it? The server was installed about 5 months ago, and the installation is basically stock, not much changes made. Thanks in advance.2 node failover cluster cant ping cluster network name from not owner node
Hello I have 2 node failover cluster based on server 2016 server. node1 is owner of cluster. I cant ping cluster network name only from cluster's owner. So I cant ping cluster name from node2 and on node2 Server Manager shows error to communicate to cluster object. But cluster status is ok. If I change node's owner ping behavior will be contra versa. I have checked on another cluster, the same. //Alexander
HCI - Storage Spaces Direct - Two nodes
Find a powerful, economical HCI solution that is suitable for small and medium environments. The idea : 1. a small hyperconverged server with 4 hot-swap 2.5 NVMe + bi proc + 4x10Gbps (rdma support) + 2 M.2 ssd for os + etc... / per Node ---------------------------- 2. A good adapted sizing for Storage Space Direct --------------------------------- 3. Configure Quorum of this little cluster on Azure. --- Your opinion on the solution ? 🙂 EDIT --> 18/06/2020 : HCI - Cluster - Storage Spaces Direct - Two nodes (V2)Access Denied to Failover Cluster Manager after Windows Upgrade
I'm working on upgrading a Hyper-V Failover Cluster from Windows Server 2016 to 2019 as documented by Microsoft. (https://learn.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade) After upgrading the first node in the cluster to 2019, it rejoins the cluster and accepts roles and cluster volumes. However, two major issues remain: 1. The upgraded server is unable to host any VMs that are powered on. It reports "The virtual machine '[VM-name]' is using processor-specific features not supported on physical computer '[HV-name]'. To allow for migration of this virtual machine to physical computers with different processors, modify the virtual machine settings to limit the processor features used by the virtual machine." However, changing the setting to limit processor features does not fix it as it reports the same issue after changing it. 2. The upgraded server is unable to connect to the cluster in the Failover Cluster Manager as it fails with "Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))". I am logged in to the server with the same domain admin account that I was using before the upgrade with no issues. The issue is the same as is described in this forum post but the resolution listed here did not work. (https://learn.microsoft.com/en-us/answers/questions/1076915/getting-error-hresult-0x80070005-(e-accessdenied)) I also tried `netsh winsock reset catalog` as suggested here (https://social.technet.microsoft.com/Forums/windowsserver/en-US/b1be178e-ae61-4a80-b880-b84b251a2d98/cant-connect-to-cluster-in-failover-cluster-manager?forum=winserverClustering) Also tried manually applying additional updates post-version upgrade and rebooting, manually adding domain admins to have full control of cluster, and evicting and re-adding the upgraded node to the cluster. Running `Get-ClusterAccess` on both upgraded and non-upgraded nodes yield the same output.Which Windows Server 2019 Installation Option should I choose?
Windows Server 2019 will bring several installation options and tuning options for virtual machines, physical servers as well as container images. In this blog post I want to give an overview about the different installation options of Windows Server 2019. Find out more here: https://www.thomasmaurer.ch/2019/03/which-windows-server-2019-installation-option-should-i-choose/
