ESX / ESXi 4.x Slow Boot with MSCS RDM LUNs

Archive / Legacy Topics, VMware, vSphere
Applies to: VMware ESX / ESXi 4.1 / 4.0 | MSCS or WSFC with shared RDM LUNs Historical: This article covers a legacy ESX/ESXi 4.x boot-delay issue seen on hosts that could access shared Raw Device Mapping (RDM) LUNs used by Microsoft Cluster Service (MSCS) nodes. The host could appear to stop for a long time around messages such as multiextent loaded successfully while storage devices were being discovered. The delay was caused by SCSI reservation conflicts on shared RDM LUNs owned by the active cluster node. In This Article 1. Why the Host Boots Slowly 2. ESX / ESXi 4.1 Workaround 3. ESX / ESXi 4.0 Workaround 4. Current ESXi Behavior 5. Key Takeaways 1. Why the Host Boots Slowly When clustered virtual machines use shared RDM disks, the…
Read More
Fix SSTP VPN Error 0x80092013: Revocation Server Offline

Fix SSTP VPN Error 0x80092013: Revocation Server Offline

Security, Windows Client
Applies to: Windows 11 / Windows 10 / Windows 8.1 / Windows 8 / Windows 7 / Windows Vista When a Windows SSTP VPN client validates the VPN server certificate, it also checks whether the certificate has been revoked. If the Certificate Revocation List (CRL) cannot be reached, the connection can fail with: Error 0x80092013 — The revocation function was unable to check revocation because the revocation server was offline. In This Article 1. What Error 0x80092013 Means 2. Check the CRL Distribution Point 3. Clear the Certificate URL Cache 4. Temporary Troubleshooting Workaround 5. Key Takeaways 1. What Error 0x80092013 Means 0x80092013 maps to CRYPT_E_REVOCATION_OFFLINE. The client is unable to complete the certificate revocation check. Common causes include: The CRL Distribution Point (CDP) URL in the certificate is not…
Read More
How to Migrate SYSVOL Replication from FRS to DFSR

How to Migrate SYSVOL Replication from FRS to DFSR

Active Directory, Identity, Windows Server
Applies to: Windows Server 2025 / 2022 / 2019 / 2016 / 2012 R2 / 2012 / 2008 R2 / 2008 Active Directory domain controllers use the SYSVOL share to replicate Group Policy files and logon scripts. Older domains can still use File Replication Service (FRS) for SYSVOL, while modern Windows Server environments use Distributed File System Replication (DFSR). If your domain still uses FRS, you should migrate SYSVOL replication to DFSR before introducing newer domain controllers. Windows Server 2019 and later cannot be promoted as replica domain controllers in a domain that still uses FRS for SYSVOL replication. In This Article 1. Before You Start 2. Check the Current Migration State 3. State 1 — Prepared 4. State 2 — Redirected 5. State 3 — Eliminated 6. Validate the…
Read More

How to Repair an Outlook PST File with ScanPST

Windows Client
Applies to: Classic Outlook for Microsoft 365 / Outlook 2024 / 2021 / 2019 / 2016 / 2013 / 2010 / 2007 / 2003 The Microsoft Outlook Inbox Repair Tool, SCANPST.EXE, checks Outlook data files for structural errors and can repair many problems in damaged .pst files. The original version of this article was written for Outlook 2010. ScanPST is still included with current classic Outlook releases, although its installation path can vary by Outlook version and Office installation type. In This Article 1. Before You Start 2. Find SCANPST.EXE 3. Scan and Repair the PST File 4. Review Recovered Items 5. PST Versus OST Files 6. Key Takeaways 1. Before You Start Close Outlook before running ScanPST. Back up the Outlook data file before attempting a repair. Make sure…
Read More

Exchange 2010 EWS Proxy Event ID 16: No Applicable Client Access Servers

Archive / Legacy Topics, Exchange
Applies to: Exchange Server 2010 Historical: This article covers the Exchange Server 2010 Client Access Server (CAS) proxy architecture. Exchange 2013 and later use a different Client Access / proxy model, so this specific troubleshooting flow should not be applied to current Exchange Server releases. In a multi-site Exchange 2010 environment, an Internet-facing Client Access Server could proxy Exchange Web Services (EWS) requests to a Client Access Server in the Active Directory site that hosted the mailbox. If Exchange could not identify a suitable Client Access Server in the destination site, the Application log could contain MSExchange Web Services Event ID 16 with a message similar to: Client Access server failed to proxy Exchange Web Services to Active Directory site because there are no applicable Client Access servers in the…
Read More
How to Enable ESXi Shell for Local Troubleshooting

How to Enable ESXi Shell for Local Troubleshooting

VMware, vSphere
Applies to: VMware ESXi 9.x / 8.x / 7.x / 6.7 / 6.5 / 6.0 / 5.5 / 5.1 / 5.0 / 4.1 ESXi Shell, previously called Tech Support Mode (TSM), provides local command-line access to an ESXi host. It is mainly intended for break-fix situations where normal management tools are not available or are not enough. The original version of this article was written for ESXi 4.1, where the message “Tech Support Mode has been disabled by the Administrator” appeared when local TSM was disabled. The same basic concept still exists in current ESXi releases, but the feature is now called ESXi Shell. In This Article 1. ESXi Shell vs SSH 2. Enable ESXi Shell from DCUI 3. Access the Local ESXi Shell 4. Enable ESXi Shell from the…
Read More
Fix WinRM Event ID 10154: Failed to Create WSMAN SPNs

Fix WinRM Event ID 10154: Failed to Create WSMAN SPNs

Active Directory, Identity, Windows Server
Applies to: Windows Server 2025 / 2022 / 2019 / 2016 / 2012 R2 / 2012 / 2008 R2 / 2008 WinRM can log Event ID 10154 when it cannot register the WSMAN Service Principal Names (SPNs) required for Kerberos authentication. A typical event contains entries similar to: The WinRM service failed to create the following SPNs: WSMAN/server.contoso.com; WSMAN/server. In This Article 1. What Event ID 10154 Means 2. Check the Current SPNs 3. Check for Duplicate SPNs 4. Register Missing WSMAN SPNs 5. If the Error Is Access Denied 6. Why NETWORK SERVICE Is Not the AD Account 7. Verify WinRM 8. Key Takeaways 1. What Event ID 10154 Means WinRM uses SPNs for Kerberos authentication. In a normal domain configuration, the WSMAN SPNs are associated with the server's…
Read More
How to Update ESXi 4.1 to ESXi 4.1 Update 1 Without Update Manager

How to Update ESXi 4.1 to ESXi 4.1 Update 1 Without Update Manager

Archive / Legacy Topics, VMware, vSphere
Applies to: VMware ESXi 4.1 → 4.1 Update 1 Historical: This article covers the legacy VMware vSphere CLI vihostupdate.pl workflow for updating ESXi 4.1 to ESXi 4.1 Update 1 without VMware Update Manager. This method does not apply to current ESXi releases. ESXi 4.1 Update 1 was released on February 10, 2011. The original procedure used VMware vSphere CLI (vCLI) from a Windows management workstation and an offline update bundle. In This Article 1. Before You Start 2. Place the Host in Maintenance Mode 3. Install the Offline Update Bundle 4. Reboot and Verify 5. Key Takeaways 1. Before You Start Download the correct ESXi 4.1 Update 1 offline bundle for the host. Install VMware vSphere CLI (vCLI) on the management workstation. Verify network connectivity from the management workstation to…
Read More

How to Block Automatic Database Activation on an Exchange DAG Member

Exchange, Exchange Server SE / 2019 / 2016, High Availability
Applies to: Exchange Server SE / 2019 / 2016 / 2013 / 2010 In an Exchange Database Availability Group (DAG), you can prevent a Mailbox server from being selected for automatic database activation. This is useful when a DAG member should keep passive database copies but should not automatically host an active copy after a failure. The original version of this article described this as “manual failover.” A more accurate description is blocking automatic database activation on a DAG member. In This Article 1. Block Automatic Database Activation 2. What Blocked Does and Does Not Do 3. Allow Automatic Activation Again 4. Maintenance Mode Is Different 5. Key Takeaways 1. Block Automatic Database Activation To prevent database copies on a specific DAG member from being automatically activated, set the server-level…
Read More