{"id":56,"date":"2026-08-19T18:09:03","date_gmt":"2026-08-19T15:09:03","guid":{"rendered":"https:\/\/licensepow.com\/blog\/?p=56"},"modified":"2026-08-19T18:17:43","modified_gmt":"2026-08-19T15:17:43","slug":"vmware-esxi-8-0-u3k-offline-patch-25595708","status":"publish","type":"post","link":"https:\/\/licensepow.com\/blog\/vmware-esxi-8-0-u3k-offline-patch-25595708","title":{"rendered":"VMware ESXi 8.0 U3k Offline Patch G\u00fcncellemesi Nas\u0131l Yap\u0131l\u0131r? – Build 25595708"},"content":{"rendered":"
\r\n

Platform:<\/strong> VMware ESXi 8.0 Update 3
Hedef s\u00fcr\u00fcm:<\/strong> ESXi 8.0 Update 3k
Hedef Build:<\/strong> 25595708
G\u00fcncelleme y\u00f6ntemi:<\/strong> Offline Bundle \/ ESXi Shell \/ SSH
G\u00fcncelleme Konusu:<\/strong> VMXNET3 G\u00fcvenlik A\u00e7\u0131\u011f\u0131 ve Kabuk Eri\u015fiminin Atlat\u0131lmas\u0131

<\/p>\r\n<\/blockquote>\r\n

\u26a0\ufe0f \u00d6nemli G\u00fcvenlik Uyar\u0131s\u0131<\/strong> VMware ESXi altyap\u0131lar\u0131 son d\u00f6nemde fidye yaz\u0131l\u0131m\u0131 sald\u0131r\u0131lar\u0131n\u0131n \u00f6nemli hedeflerinden biri haline gelmi\u015ftir.
\u00d6zellikle ESXi \u00fczerinde \u00e7al\u0131\u015fan sanal makinelerin disk dosyalar\u0131n\u0131n (.vmdk<\/code>) ve di\u011fer sanalla\u015ft\u0131rma bile\u015fenlerinin hedef al\u0131nmas\u0131, tek bir ESXi hostunun ele ge\u00e7irilmesi halinde \u00e7ok say\u0131da sanal makinenin ayn\u0131 anda etkilenmesine neden olabilir.
Bu nedenle ESXi hostlar\u0131n\u0131n yaln\u0131zca i\u015fletim sistemi g\u00fcncellemeleri a\u00e7\u0131s\u0131ndan de\u011fil, g\u00fcvenlik yamalar\u0131 a\u00e7\u0131s\u0131ndan da g\u00fcncel tutulmas\u0131 kritik \u00f6neme sahiptir.<\/strong>
Bu rehberde VMware ESXi 8.0 Update 3 kullanan bir hostun, internet ba\u011flant\u0131s\u0131 olmadan offline depot ZIP paketi kullan\u0131larak ESXi 8.0 U3k Build 25595708 s\u00fcr\u00fcm\u00fcne nas\u0131l g\u00fcncellenece\u011fini<\/strong> ad\u0131m ad\u0131m anlataca\u011f\u0131m.

Ayr\u0131ca e\u011fer bu g\u00fcncellemeye sahip olam\u0131yorsan\u0131z, VMXNET3 a\u011f kart\u0131n\u0131z\u0131 t\u00fcm sunucular\u0131n\u0131zda E1000 veya muadili ile de\u011fi\u015ftirmeniz \u015fiddetle tavsiye edilir.<\/strong><\/span><\/blockquote>\r\n
\r\n

\u0130\u00e7indekiler<\/h2>\r\n
    \r\n
  1. ESXi U3k nedir?<\/li>\r\n
  2. Neden bu g\u00fcncelleme \u00f6nemli?<\/li>\r\n
  3. G\u00fcncelleme \u00f6ncesinde dikkat edilmesi gerekenler<\/li>\r\n
  4. Mevcut ESXi s\u00fcr\u00fcm\u00fcn\u00fc kontrol etme<\/li>\r\n
  5. Offline Bundle dosyas\u0131n\u0131 datastore’a y\u00fckleme<\/li>\r\n
  6. Offline Bundle i\u00e7erisindeki image profile’lar\u0131 listeleme<\/li>\r\n
  7. ESXi hostunu Maintenance Mode’a alma<\/li>\r\n
  8. Dry-run ile g\u00fcncellemeyi \u00f6nceden test etme<\/li>\r\n
  9. Ger\u00e7ek patch i\u015flemini ger\u00e7ekle\u015ftirme<\/li>\r\n
  10. ESXi hostunu yeniden ba\u015flatma<\/li>\r\n
  11. G\u00fcncelleme sonras\u0131nda s\u00fcr\u00fcm kontrol\u00fc<\/li>\r\n
  12. Maintenance Mode’dan \u00e7\u0131kma<\/li>\r\n
  13. G\u00fcncellemenin ba\u015far\u0131l\u0131 oldu\u011funu nas\u0131l do\u011frular\u0131z?<\/li>\r\n
  14. S\u0131k kar\u015f\u0131la\u015f\u0131lan hatalar<\/li>\r\n
  15. G\u00fcvenlik a\u00e7\u0131s\u0131ndan patch sonras\u0131nda yap\u0131lmas\u0131 gerekenler<\/li>\r\n
  16. Sonu\u00e7<\/li>\r\n<\/ol>\r\n
    \r\n

    1. ESXi 8.0 U3k nedir?<\/h1>\r\n

    VMware ESXi 8.0 Update 3k, VMware’in ESXi 8.0 Update 3 ailesi i\u00e7in yay\u0131nlad\u0131\u011f\u0131 bir g\u00fcvenlik g\u00fcncellemesidir. Broadcom’un resmi release notes sayfas\u0131nda:<\/p>\r\n

      \r\n
    • Version:<\/strong> ESXi 8.0 Update 3k<\/li>\r\n
    • Build:<\/strong> 25595708<\/li>\r\n
    • Release Date:<\/strong> 29 July 2026<\/li>\r\n
    • Category:<\/strong> Security<\/li>\r\n<\/ul>\r\n

      olarak belirtilmektedir. Bu nedenle ESXi 8.0 Update 3 kullanan sistemlerde g\u00fcvenlik a\u00e7\u0131s\u0131ndan \u00f6nemli bir g\u00fcncellemedir. Bu rehberde kullan\u0131lan hedef build:<\/p>\r\n

      ESXi 8.0.3 Build 25595708\r\n<\/code><\/pre>\r\n
      \r\n
      2. Neden bu g\u00fcncelleme \u00f6nemli?<\/h1>\r\n
      ESXi, fiziksel sunucu \u00fczerinde \u00e7al\u0131\u015fan sanalla\u015ft\u0131rma katman\u0131d\u0131r. 
      \u00d6rne\u011fin fiziksel bir sunucuda:<\/p>\r\n
      Physical Server\r\n      \u2502\r\n      \u25bc\r\nVMware ESXi\r\n      \u2502\r\n      \u251c\u2500\u2500 VM01 - Windows Server\r\n      \u251c\u2500\u2500 VM02 - Linux\r\n      \u251c\u2500\u2500 VM03 - Windows\r\n      \u251c\u2500\u2500 VM04 - Database\r\n      \u2514\u2500\u2500 VM05 - Web Server\r\n<\/code><\/pre>\r\n
      \u015feklinde onlarca sanal makine \u00e7al\u0131\u015fabilir. ESXi hostunun g\u00fcvenli\u011finin ihlal edilmesi durumunda sald\u0131rgan\u0131n eri\u015febilece\u011fi alan, tek bir sanal makineyle s\u0131n\u0131rl\u0131 olmayabilir. \u00d6zellikle ransomware sald\u0131r\u0131lar\u0131nda ESXi hostlar\u0131n\u0131n hedef al\u0131nmas\u0131n\u0131n \u00f6nemli sebeplerinden biri de budur. Fidye yaz\u0131l\u0131m\u0131 gruplar\u0131 ESXi ortamlar\u0131n\u0131 hedefleyerek sanal makinelerin disk dosyalar\u0131n\u0131 ve sanalla\u015ft\u0131rma altyap\u0131s\u0131n\u0131 etkisiz hale getirmeye \u00e7al\u0131\u015fabilir. Bu nedenle:<\/p>\r\n
      ESXi hostunun g\u00fcncel olmas\u0131, \u00fczerinde \u00e7al\u0131\u015fan sanal makinelerin g\u00fcvenli\u011fi a\u00e7\u0131s\u0131ndan da kritik bir katmand\u0131r.<\/strong><\/blockquote>\r\n
      Ancak \u00f6nemli bir noktay\u0131 \u00f6zellikle belirtmek gerekir: Bir ESXi patch’inin uygulanmas\u0131 ransomware sald\u0131r\u0131lar\u0131na kar\u015f\u0131 tek ba\u015f\u0131na tam koruma sa\u011flamaz.<\/strong> Patch i\u015flemi ilgili yaz\u0131l\u0131m g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 kapat\u0131r. Bunun yan\u0131nda ESXi y\u00f6netim aray\u00fczlerinin internete a\u00e7\u0131k olmamas\u0131, g\u00fc\u00e7l\u00fc kimlik do\u011frulama, firewall kurallar\u0131, yedekleme ve eri\u015fim kontrolleri de uygulanmal\u0131d\u0131r.<\/p>\r\n
      \r\n
      3. G\u00fcncelleme \u00f6ncesinde dikkat edilmesi gerekenler<\/h1>\r\n
      ESXi patch i\u015flemine ba\u015flamadan \u00f6nce a\u015fa\u011f\u0131daki maddeler kontrol edilmelidir.<\/p>\r\n
      3.1. Sanal makinelerin durumunu kontrol edin<\/h3>\r\n
      Host \u00fczerinde \u00e7al\u0131\u015fan sanal makineleri kontrol edin. Tek hostlu bir sistem kullan\u0131yorsan\u0131z sanal makineleri kapatman\u0131z gerekebilir. Cluster ve vCenter kullan\u0131lan ortamlarda ise sanal makineler ba\u015fka hostlara ta\u015f\u0131nabilir. DRS kullan\u0131lan cluster ortamlar\u0131nda Maintenance Mode i\u015flemi s\u0131ras\u0131nda sanal makinelerin otomatik olarak ba\u015fka hostlara ta\u015f\u0131nmas\u0131 m\u00fcmk\u00fcnd\u00fcr. Broadcom’un g\u00fcncel patch prosed\u00fcr\u00fcnde de bu davran\u0131\u015f a\u00e7\u0131klanmaktad\u0131r.<\/p>\r\n
      \r\n
      3.2. ESXi configuration backup al\u0131n<\/h3>\r\n
      Patch i\u015fleminden \u00f6nce ESXi host configuration backup al\u0131nmas\u0131 tavsiye edilir. \u00d6zellikle production sistemlerde yaln\u0131zca sanal makine backup’lar\u0131n\u0131n olmas\u0131 yeterli de\u011fildir. ESXi host konfig\u00fcrasyonunun da yedeklenmesi \u00f6nemlidir.<\/p>\r\n
      \r\n
      3.3. Donan\u0131m \u00fcreticisinin compatibility durumunu kontrol edin<\/h3>\r\n
      Dell, HPE, Lenovo vb. \u00fcretici taraf\u0131ndan sa\u011flanan \u00f6zel ESXi image’lar\u0131 kullan\u0131yorsan\u0131z, ilgili donan\u0131m \u00fcreticisinin VMware ESXi 8.0 U3k deste\u011fini kontrol edin. \u00d6zellikle:<\/p>\r\n
        \r\n
      • RAID\/HBA controller<\/li>\r\n
      • Network adapter<\/li>\r\n
      • Fibre Channel HBA<\/li>\r\n
      • NVMe controller<\/li>\r\n
      • Storage controller<\/li>\r\n
      • \u00d6zel OEM driver’lar\u0131<\/li>\r\n<\/ul>\r\n
        kontrol edilmelidir.<\/p>\r\n
        \r\n
        4. Mevcut ESXi s\u00fcr\u00fcm\u00fcn\u00fc kontrol etme<\/h1>\r\n
        \u0130lk olarak ESXi hostuna SSH ile ba\u011flan\u0131yoruz. A\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\r\n
        vmware -vl\r\n<\/code><\/pre>\r\n
        \u00d6rne\u011fin:<\/p>\r\n
        VMware ESXi 8.0.3 build-25429389\r\nVMware ESXi 8.0 Update 3\r\n<\/code><\/pre>\r\n
        Alternatif olarak:<\/p>\r\n
        vmware -v\r\n<\/code><\/pre>\r\n
        komutu kullan\u0131labilir. Daha ayr\u0131nt\u0131l\u0131 bilgi i\u00e7in:<\/p>\r\n
        esxcli system version get\r\n<\/code><\/pre>\r\n
        \u00d6rne\u011fin:<\/p>\r\n
        Product: VMware ESXi\r\nVersion: 8.0.3\r\nBuild: Releasebuild-25429389\r\nUpdate: 3\r\nPatch: 100\r\n<\/code><\/pre>\r\n
        Bu durumda host:<\/p>\r\n
        ESXi 8.0 Update 3\r\nBuild 25429389\r\n<\/code><\/pre>\r\n
        kullan\u0131yor demektir.<\/p>\r\n
        \r\n
        5. Offline Bundle dosyas\u0131n\u0131 datastore’a y\u00fckleme<\/h1>\r\n
        Offline patch y\u00f6ntemi i\u00e7in VMware taraf\u0131ndan sa\u011flanan Offline Bundle ZIP dosyas\u0131na ihtiyac\u0131m\u0131z vard\u0131r. 
        \u00d6rne\u011fin:<\/p>\r\n
        VMware-ESXi-8.0U3k-25595708-depot.zip\r\n<\/code><\/pre>\r\n
        dosyas\u0131. Bu dosyay\u0131 ESXi hostunun eri\u015febildi\u011fi bir datastore’a y\u00fckleyebilirsiniz. 
        \u00d6rne\u011fin:<\/p>\r\n
        datastore1\r\n<\/code><\/pre>\r\n
        i\u00e7erisine y\u00fcklenmi\u015fse dosyan\u0131n tam yolu:<\/p>\r\n
        \/vmfs\/volumes\/datastore1\/VMware-ESXi-8.0U3k-25595708-depot.zip\r\n<\/code><\/pre>\r\n
        olabilir. Dosyan\u0131n ger\u00e7ekten mevcut oldu\u011funu kontrol etmek i\u00e7in:<\/p>\r\n
        ls -lh \/vmfs\/volumes\/datastore1\/VMware-ESXi-8.0U3k-25595708-depot.zip\r\n<\/code><\/pre>\r\n
        komutunu kullanabilirsiniz.<\/p>\r\n
        \r\n
        6. Offline Bundle i\u00e7erisindeki image profile’lar\u0131 listeleme<\/h1>\r\n
        ESXi 8.0 Update 2 ve sonraki s\u00fcr\u00fcmlerde patch i\u015flemi i\u00e7in eski:<\/p>\r\n
        esxcli software vib update\r\n<\/code><\/pre>\r\n
        y\u00f6ntemi yerine image profile tabanl\u0131 g\u00fcncelleme<\/strong> kullan\u0131lmal\u0131d\u0131r. Broadcom bunu ESXi 8.0 U2 ve sonraki s\u00fcr\u00fcmler i\u00e7in \u00f6zellikle belirtmektedir. Offline Bundle i\u00e7erisindeki profile’lar\u0131 g\u00f6rmek i\u00e7in:<\/p>\r\n
        esxcli software sources profile list \\\r\n-d \/vmfs\/volumes\/datastore1\/VMware-ESXi-8.0U3k-25595708-depot.zip\r\n<\/code><\/pre>\r\n
        \u00d6rne\u011fin sonu\u00e7:<\/p>\r\n
        Name                           Vendor        Acceptance Level\r\n----------------------------------------------------------------\r\nESXi-8.0U3k-25595708-no-tools  VMware, Inc.  PartnerSupported\r\nESXi-8.0U3k-25595708-standard   VMware, Inc.  PartnerSupported\r\n<\/code><\/pre>\r\n
        \u015feklinde olabilir. Burada iki profile bulunmaktad\u0131r:<\/p>\r\n
        ESXi-8.0U3k-25595708-no-tools\r\n<\/code><\/pre>\r\n
        ve:<\/p>\r\n
        ESXi-8.0U3k-25595708-standard\r\n<\/code><\/pre>\r\n
        Genel olarak standard<\/code> profile, VMware Tools image g\u00fcncellemelerini de i\u00e7eren standart g\u00fcvenlik ve bug-fix image’\u0131d\u0131r. Broadcom’un dok\u00fcmantasyonunda no-tools<\/code> ve standard<\/code> profile farklar\u0131 ayr\u0131ca a\u00e7\u0131klanmaktad\u0131r. Bu nedenle standart bir VMware offline bundle i\u00e7in:<\/p>\r\n
        ESXi-8.0U3k-25595708-standard\r\n<\/code><\/pre>\r\n
        profile’\u0131 kullan\u0131labilir.<\/p>\r\n
        \r\n
        7. ESXi hostunu Maintenance Mode’a alma<\/h1>\r\n
        Patch i\u015fleminden \u00f6nce ESXi hostunu Maintenance Mode’a almak gerekir. ESXi Shell veya SSH \u00fczerinden:<\/p>\r\n
        vim-cmd \/hostsvc\/maintenance_mode_enter\r\n<\/code><\/pre>\r\n
        komutunu \u00e7al\u0131\u015ft\u0131r\u0131n. Ard\u0131ndan kontrol edin:<\/p>\r\n
        vim-cmd \/hostsvc\/hostsummary | grep inMaintenanceMode\r\n<\/code><\/pre>\r\n
        \u015eu sonucu g\u00f6rmeniz gerekir:<\/p>\r\n
        inMaintenanceMode = true\r\n<\/code><\/pre>\r\n
        Bu durumda host Maintenance Mode’dad\u0131r.<\/p>\r\n
        \u26a0\ufe0f D\u0130KKAT:<\/strong> Production ortam\u0131nda \u00e7al\u0131\u015fan sanal makineler varsa Maintenance Mode’a ge\u00e7meden \u00f6nce VM’lerin durumunu mutlaka kontrol edin.<\/blockquote>\r\n
        \r\n
        8. Dry-run ile g\u00fcncellemeyi \u00f6nceden test etme<\/h1>\r\n
        Ger\u00e7ek patch i\u015fleminden \u00f6nce en \u00f6nemli ad\u0131mlardan biri dry-run<\/strong> i\u015flemidir. Dry-run ger\u00e7ek g\u00fcncelleme yapmaz. Sadece ESXi’nin g\u00fcncelleme s\u0131ras\u0131nda hangi bile\u015fenleri y\u00fckleyip kald\u0131raca\u011f\u0131n\u0131 g\u00f6sterir. 
        \u00d6rne\u011fin:<\/p>\r\n
        esxcli software profile update \\\r\n-d \/vmfs\/volumes\/datastore1\/VMware-ESXi-8.0U3k-25595708-depot.zip \\\r\n-p ESXi-8.0U3k-25595708-standard \\\r\n--dry-run\r\n<\/code><\/pre>\r\n
        Baz\u0131 sistemlerde hardware warning nedeniyle i\u015flem engelleniyorsa \u015fu se\u00e7enek kullan\u0131labilir:<\/p>\r\n
        --no-hardware-warning\r\n<\/code><\/pre>\r\n
        \u00d6rne\u011fin:<\/p>\r\n
        esxcli software profile update \\\r\n-d \/vmfs\/volumes\/datastore1\/VMware-ESXi-8.0U3k-25595708-depot.zip \\\r\n-p ESXi-8.0U3k-25595708-standard \\\r\n--dry-run \\\r\n--no-hardware-warning\r\n<\/code><\/pre>\r\n
        Broadcom’un resmi prosed\u00fcr\u00fcnde de patch \u00f6ncesinde dry-run kullan\u0131larak de\u011fi\u015fikliklerin do\u011frulanmas\u0131 \u00f6nerilmektedir.<\/p>\r\n
        \r\n
        9. Dry-run \u00e7\u0131kt\u0131s\u0131 nas\u0131l yorumlan\u0131r?<\/h1>\r\n
        \u00d6rne\u011fin:<\/p>\r\n
        Update Result\r\nMessage: Dryrun only, host not changed.\r\n\r\nVIBs Installed:\r\nVMware_bootbank_esx-base_8.0.3-0.102.25595708\r\nVMware_bootbank_esxio-base_8.0.3-0.102.25595708\r\n\r\nVIBs Removed:\r\nVMware_bootbank_esx-base_8.0.3-0.100.25429389\r\nVMware_bootbank_esxio-base_8.0.3-0.100.25429389\r\n\r\nReboot Required: true\r\n<\/code><\/pre>\r\n
        g\u00f6r\u00fcyorsan\u0131z i\u015flem planland\u0131\u011f\u0131 \u015fekilde ilerliyor demektir. Burada:<\/p>\r\n
        25429389\r\n<\/code><\/pre>\r\n
        eski build,<\/p>\r\n
        25595708\r\n<\/code><\/pre>\r\n
        ise yeni build’dir. Ayr\u0131ca:<\/p>\r\n
        Reboot Required: true\r\n<\/code><\/pre>\r\n
        g\u00f6r\u00fclmesi normaldir. \u00c7\u00fcnk\u00fc ESXi kernel\/core bile\u015fenlerinin g\u00fcncellenebilmesi i\u00e7in hostun yeniden ba\u015flat\u0131lmas\u0131 gerekir.<\/p>\r\n
        \r\n
        10. Ger\u00e7ek ESXi patch i\u015flemi<\/h1>\r\n
        Dry-run sonucunda herhangi bir hata veya beklenmeyen dependency problemi yoksa ger\u00e7ek g\u00fcncelleme ger\u00e7ekle\u015ftirilebilir. Komut:<\/p>\r\n
        esxcli software profile update \\\r\n-d \/vmfs\/volumes\/datastore1\/VMware-ESXi-8.0U3k-25595708-depot.zip \\\r\n-p ESXi-8.0U3k-25595708-standard\r\n<\/code><\/pre>\r\n
        E\u011fer dry-run s\u0131ras\u0131nda --no-hardware-warning<\/code> kullanman\u0131z gerekti\u011fi do\u011frulanm\u0131\u015fsa:<\/p>\r\n
        esxcli software profile update \\\r\n-d \/vmfs\/volumes\/datastore1\/VMware-ESXi-8.0U3k-25595708-depot.zip \\\r\n-p ESXi-8.0U3k-25595708-standard \\\r\n--no-hardware-warning\r\n<\/code><\/pre>\r\n
        kullan\u0131labilir.<\/p>\r\n
        \u26a0\ufe0f \u00d6nemli:<\/strong> --force<\/code> veya --no-sig-check<\/code> gibi se\u00e7enekleri gereksiz yere kullanmay\u0131n. Normal ve resmi VMware\/Broadcom Offline Bundle kullan\u0131l\u0131yorsa standart profile update y\u00f6ntemi tercih edilmelidir.<\/blockquote>\r\n
        Broadcom’un resmi offline bundle prosed\u00fcr\u00fc de esxcli software profile update<\/code> komutunu kullanmaktad\u0131r.<\/p>\r\n
        \r\n
        11. G\u00fcncelleme tamamland\u0131ktan sonra reboot<\/h1>\r\n
        Patch i\u015flemi ba\u015far\u0131l\u0131 \u015fekilde tamamland\u0131ktan sonra:<\/p>\r\n
        esxcli system shutdown reboot -r 'apply patch'\r\n<\/code><\/pre>\r\n
        komutunu kullanabilirsiniz. Alternatif:<\/p>\r\n
        reboot\r\n<\/code><\/pre>\r\n
        komutu da kullan\u0131labilir. Broadcom’a g\u00f6re ESXi patch i\u015flemi reboot tamamlanmadan bitmi\u015f say\u0131lmaz. Hostun tamamen boot olmas\u0131n\u0131 beklemek gerekir.<\/p>\r\n
        \u26a0\ufe0f D\u0130KKAT:<\/strong> Reboot s\u0131ras\u0131nda fiziksel sunucunun enerjisini kesmeyin.<\/blockquote>\r\n
        \r\n
        12. G\u00fcncelleme sonras\u0131nda s\u00fcr\u00fcm kontrol\u00fc<\/h1>\r\n
        ESXi tekrar a\u00e7\u0131ld\u0131ktan sonra SSH ile ba\u011flan\u0131n. \u0130lk olarak:<\/p>\r\n
        vmware -v\r\n<\/code><\/pre>\r\n
        \u00e7al\u0131\u015ft\u0131r\u0131n. Ba\u015far\u0131l\u0131 bir g\u00fcncelleme sonras\u0131nda:<\/p>\r\n
        VMware ESXi 8.0.3 build-25595708\r\n<\/code><\/pre>\r\n
        g\u00f6rmelisiniz. Daha ayr\u0131nt\u0131l\u0131 kontrol:<\/p>\r\n
        esxcli system version get\r\n<\/code><\/pre>\r\n
        Beklenen sonu\u00e7:<\/p>\r\n
        Product: VMware ESXi\r\nVersion: 8.0.3\r\nBuild: Releasebuild-25595708\r\nUpdate: 3\r\n<\/code><\/pre>\r\n
        Buradaki en \u00f6nemli de\u011fer:<\/p>\r\n
        Build: 25595708\r\n<\/code><\/pre>\r\n
        olmas\u0131d\u0131r.<\/p>\r\n
        \r\n
        13. Maintenance Mode’dan \u00e7\u0131kma<\/h1>\r\n
        Patch i\u015flemi tamamland\u0131ktan ve hostun d\u00fczg\u00fcn \u015fekilde boot etti\u011finden emin olduktan sonra Maintenance Mode’dan \u00e7\u0131kabilirsiniz. SSH \u00fczerinden:<\/p>\r\n
        vim-cmd \/hostsvc\/maintenance_mode_exit\r\n<\/code><\/pre>\r\n
        Ard\u0131ndan:<\/p>\r\n
        vim-cmd \/hostsvc\/hostsummary | grep inMaintenanceMode\r\n<\/code><\/pre>\r\n
        kontrol\u00fc yap\u0131labilir. Beklenen:<\/p>\r\n
        inMaintenanceMode = false\r\n<\/code><\/pre>\r\n
        \r\n
        14. G\u00fcncellemenin ba\u015far\u0131l\u0131 oldu\u011funu nas\u0131l do\u011frular\u0131z?<\/h1>\r\n
        Patch sonras\u0131nda a\u015fa\u011f\u0131daki kontrolleri yapman\u0131z\u0131 \u00f6neriyorum.<\/p>\r\n
        ESXi version<\/h3>\r\n
        vmware -v\r\n<\/code><\/pre>\r\n
        ESXi build<\/h3>\r\n
        esxcli system version get\r\n<\/code><\/pre>\r\n
        VMXNET3 driver<\/h3>\r\n
        esxcli software vib list | grep -i vmxnet\r\n<\/code><\/pre>\r\n
        ESXi image profile<\/h3>\r\n
        esxcli software profile get\r\n<\/code><\/pre>\r\n
        Bu kontroller \u00f6zellikle g\u00fcvenlik g\u00fcncellemesinin ger\u00e7ekten host \u00fczerinde aktif oldu\u011funu do\u011frulamak i\u00e7in kullan\u0131labilir.<\/p>\r\n
        \r\n
        15. ESXi g\u00fcvenli\u011fi yaln\u0131zca patch i\u015fleminden ibaret de\u011fildir<\/h1>\r\n
        ESXi’nin g\u00fcncellenmesi \u00e7ok \u00f6nemli olmakla birlikte tek ba\u015f\u0131na yeterli de\u011fildir. A\u015fa\u011f\u0131daki g\u00fcvenlik \u00f6nlemleri de uygulanmal\u0131d\u0131r.<\/p>\r\n
        15.1. ESXi y\u00f6netim aray\u00fcz\u00fcn\u00fc internete a\u00e7may\u0131n<\/h2>\r\n
        ESXi y\u00f6netim IP adresi olan:<\/p>\r\n
        443\r\n<\/code><\/pre>\r\n
        ve SSH:<\/p>\r\n
        22\r\n<\/code><\/pre>\r\n
        portlar\u0131n\u0131n do\u011frudan Internet \u00fczerinden eri\u015filebilir olmas\u0131 ciddi bir g\u00fcvenlik riskidir. M\u00fcmk\u00fcnse ESXi y\u00f6netim a\u011f\u0131:<\/p>\r\n
        Internet\r\n   \u2502\r\n   X\r\n   \u2502\r\nFirewall\r\n   \u2502\r\n   \u2514\u2500\u2500 Management VLAN\r\n          \u2502\r\n          \u2514\u2500\u2500 ESXi\r\n<\/code><\/pre>\r\n
        \u015feklinde izole edilmelidir.<\/p>\r\n
        \r\n
        15.2. SSH’\u0131 gereksiz yere a\u00e7\u0131k b\u0131rakmay\u0131n<\/h2>\r\n
        Patch i\u015flemi bittikten sonra SSH’a ihtiyac\u0131n\u0131z yoksa SSH servisini kapat\u0131n. ESXi \u00fczerinde SSH yaln\u0131zca gerekti\u011finde a\u00e7\u0131lmal\u0131 ve m\u00fcmk\u00fcnse yaln\u0131zca y\u00f6netim IP’lerinden eri\u015filebilir olmal\u0131d\u0131r.<\/p>\r\n
        \r\n
        15.3. ESXi root hesab\u0131n\u0131 do\u011frudan Internet’e a\u00e7may\u0131n<\/h2>\r\n
        root<\/code> hesab\u0131 ESXi \u00fczerinde \u00e7ok y\u00fcksek yetkilere sahiptir. Bu nedenle ESXi y\u00f6netim eri\u015fiminin:<\/p>\r\n