Ceyhun KIRMIZITAS

22Sep 2011 by Ceyhun Kirmizitas 0 Comments

How to Install Intel 82576 / 82580 NIC Drivers on VMware ESX / ESXi 4.x

Archive / Legacy Topics, VMware, vSphere

Applies to: VMware ESX / ESXi 4.x | IBM System x3850 X5 | Intel 82576 / 82580 Gigabit Ethernet Controllers Historical: This article covers a legacy ESX/ESXi 4.x driver installation scenario for Intel 82576 and 82580 Gigabit Ethernet controllers, including the IBM I340-T4 adapter used in IBM System x servers such as the x3850 X5. In this configuration, the network adapter could be supported by VMware but the required igb driver was not included in the ESX/ESXi installation media. The driver therefore had to be installed separately from an offline bundle. In This Article 1. Driver Package 2. Prepare the ESX Host 3. Install the Driver 4. Reboot and Verify 5. Important Version Note 6. Key Takeaways 1. Driver Package The original installation used the Intel igb 2.1.10.2 offline bundle:…

08Sep 2011 by Ceyhun Kirmizitas 0 Comments

How vSphere HA Fault Domain Manager (FDM) Works

VMware, vSphere

Applies to: VMware vSphere 9.x / 8.x / 7.x / 6.7 / 6.5 / 6.0 / 5.5 / 5.1 / 5.0 vSphere High Availability (HA) uses the Fault Domain Manager (FDM) agent on ESXi hosts to monitor host and virtual machine availability and coordinate recovery when a failure occurs. FDM was introduced with vSphere 5 and replaced the older AAM-based HA architecture. The basic design is still used in current vSphere releases: one host takes the Primary role and the remaining hosts run as Secondary nodes. Network heartbeats and datastore heartbeats help vSphere HA determine whether a host has failed, is isolated, or is part of a network partition. In This Article 1. What Is FDM? 2. Primary and Secondary Hosts 3. Network Heartbeats 4. Datastore Heartbeats 5. What Happens…

29Aug 2011 by Ceyhun Kirmizitas 0 Comments

How to Configure the VMware ESXi Firewall

VMware, vSphere

Applies to: VMware ESXi 9.x / 8.x / 7.x / 6.7 / 6.5 / 6.0 / 5.5 / 5.1 / 5.0 VMware introduced a built-in host firewall with ESXi 5.0. The same service-based firewall model continues in current ESXi releases: firewall rules are grouped into rulesets for services such as SSH, DNS, NTP, syslog, and management traffic. The original version of this article focused on what was new in vSphere 5. This updated version keeps that history but focuses on how the ESXi firewall is managed today. In This Article 1. How the ESXi Firewall Works 2. View Firewall Rules in the vSphere Client 3. View Firewall Rules with ESXCLI 4. Enable or Disable a Ruleset 5. Restrict a Ruleset by IP Address 6. System-Owned Rulesets 7. Key Takeaways 1.…

19Jul 2011 by Ceyhun Kirmizitas 0 Comments

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…

16Jun 2011 by Ceyhun Kirmizitas 0 Comments

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…

11Jun 2011 by Ceyhun Kirmizitas 0 Comments

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…

12May 2011 by Ceyhun Kirmizitas 0 Comments

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…

04May 2011 by Ceyhun Kirmizitas 0 Comments

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…

21Apr 2011 by Ceyhun Kirmizitas 0 Comments

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…