Vmware in kullandığı Vmdk için kısaca sanal bir makineye ait hard disk formatı diyebiliriz.Vmdk dosyası normal şartlarda 2 adet dosyadan oluşur.(Datastore browser dan baktığımızda sadece bir adet vmdk görebiliriz)

Bunlar “vmismi.vmdk ve vmismi-flat.vmdk” dir

Normal şartlarda datastore tarafından browse ettiğimizde sadece vmismi.vmdk dosyasını görebiliyoruz.

Putty ile bağlanarak kontrol ettiğimizde ise 2 dosyayı da ayrı ayrı görebiliriz.

TESTVM-flat.vmdk boyutundan da anlaşılacağı gibi dataların yer aldığı bölümdür.TESTVM.vmdk ise bu flat disk e ait bilgileri veren ve onu tanımlayan vmdk dosyasıdır.Diske ait  cid,parent cid,flat dosyasının yeri ve diskle ilgili diğer bilgileri barındırır.

Vmdk dosyası bir şekilde silindiğinde veya zarar gördüğünde elinizdeki vmismi-flat.vmdk dosyasını direkt olarak esx ekleme şansız bulunmamaktadır.Bu diski flat dosyasını tanımlayacak bir vmdk dosyasına ihtiyaç bulunmaktadır.

Vmdk dosyası bolzulduktan sonra datastore üzerinden browse ettiğinide vmdk dosyasının simgesinin alışmış olduğunuz vmdk simgesi gibi olmadığını görebilirsiniz

Görüldüğü gibi TESTVM.vmdk dosyası yok ve artık flat dosyasını görebiliyoruz. Flat dosyası bir descripter vmdk dosyasına sahip olmadığı için görülebilmektedir.

Sanal makineyi power on yapmaya çalıştığımızda ise aşağıdaki hata ile karşılaşacağız.

“Cannot open the disk ‘TESTVM.vmdk’ or one of the snapshot disks it depends on.

The system cannot find the file specified

VMware ESX cannot find the virtual disk “TESTVM.vmdk”. Verify the path is valid and try again.”

Bu aşamada yapılması gereken  işlem;

Yenibir sanal disk oluşturmak (sanal disk oluştuğunda 2 adet dosya oluşacak yenidisk.vmdk ve yenidisk-flat.vmdk)

Yeni disk i oluşturduktan sonra yeni disk in vmdk dosyasını (flat olanı değil) yenidisk.vmk dosyasını TESTVM-flat.vmdk dosyamızı tanımlayacak şekilde tekrar düzenlemek.

Putty ile server a bağandıktan sonra ilgili vm in olduğu directory e gidin

Ls –l komutu ile gerçekten vmdk dosyasının olmadığını ve  flat dosyasının yani datayı barındıran diskin olduğunu doğrulayın

Bu işlem için kullanılacak yeni diski oluştururken dikkat edilmesi gereken nokta ilgili vm in config dosyası yani vmx dosyasının içerisine bakılarak. Description dosyası bozuk olan diskin tam boyutu ve sanal makinede kullanılan SCSI Controler adapter ın aynı olmasıdır

Öncelikle flat dosyasının size ını kontrol edelim

Komut: ls -l

Görüldüğü gibi flat disk in size ı 10737418240

Şimdi sanal makinenin kullandığı controller type ına bakalım

Komut: vi sanalmakineismi.vmx  veya less *.vmx | grep virtualDev yazarak gelen satırlardaki  yazıyı görebilirsiniz

scsi0.virtualDev = “lsilogic”

ihtiyacımız olan bilgileri aldıktan sonra aynı özelliklerde sanal disk oluşturacağız. Oluşturacağımız disk in boyutu flat disk ile aynı olacak fakat thin disk oluşturduğumuz içn boyutu çok daha küçük olacak.

Yeni diski aşağıdaki komut ile oluşturabiliriz

Komut :vmkfstools -c 10737418240 -a lsilogic -d thin yenidisk.vmdk

-c create etmek için

Sonraki rakam sizin disk size ınız

-a adepter type

Lsilogic olan kısım sizin adepter type ınız

-d disk in yapısını belirtmek için (thin disk oluşturacağız)

Yenidisk.vmdk  vermek istediğiniz isim

Yeni disk oluştuktan sonra yeni disk in vmdk dosyasını kaypveya bozuk olan vmdk dosyamın adı ile değiştiriyorum

Benim kayıp olan diskmi TESTVM.vmdk bu nedenle yeni disk in vmdk dosyasını bu isimle değiştiriyorum

Artık elimizde TESTVM.vmdk adında bir dosyamız var fakat bu dosyanın içerisinde tanımı olan diski bizim TESVM-flat.vmdk  i işaret edecek şekilde değiştirmeliyiz.Bunun için Vi komutu ile TESTVM.vmdk dosyasının içerisine giriyoruz ve

# Extent description

RW 20971520 VMFS “TESTVM-flat.vmdk”

Kısmındaki vmdk in ihtiyacımız olan flat disk i gösterecek şekilde değiştiriyoruz

Son olarak;

Eğer problem yaşayan disk thin provision olarak yapılandırılmadı ise aşağıdaki satırı silebilriz

Değişiklikleri yapıp kaydettikten sonra vm i poweron yapabilriz.
Aşağıda diskin düzeldikten sonraki halini görebiliriz

Biraz sakat bir konu olduğu için elimden geldiğince detaylı yazmak istedim. Gerçi bu blog a benden başka giren varmı emin değilim J

Eğer snapshot almışşsanız yapılması gerken işlemler biraz daha değişik olacaktır bunu da ayrı bir yazıda belirteceğim

Windows Defender Credential Guard does not allow using saved credentials

Yukarıda yazan ”Windows Defender Credential Guard Kaydedilmiş Kimlik Bilgilerini Kullanmaya İzin Vermiyor” hatasını aldığınızda istemci bilgisayarınızda yapmanız gerekenler sırası ile;

çalıştır’a regedit.exe yazıp açılan pencerede,

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard alanına gidin ve 2 adet dword değer oluşturun

1) EnableVirtualizationBasedSecurity isminde değeri 0 olacak

2) RequirePlatformSecurityFeatures isminde değeri 0 olacak

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa alanına gidin ve 1 adet dword değer oluşturun

1) LsaCfgFlags isminde değeri 0 olacak.

Sonrasında istemci bilgisayarınızı yeniden başlatın artık şifrelerinizi kaydedebileceksiniz.

As with any vSphere release, you should always carefully review the release notes when they are made available and verify that all of your hardware and the underlying components are officially listed on the VMware HCL, which will be updated when vSphere 8 and vSAN 8 GA’s. This is the only way to ensure that you will have the best possible experience and a supported configuration from VMware.

Disclaimer: The following considerations are based on early observations using pre-GA builds of vSphere 8 and it does not reflect any official guidance or support from VMware.

CPU Support

The following CPU generations listed below for both Intel and AMD will not be supported with vSphere 8.

• Intel
  • SandyBridge-DT, SandyBridge-EP/EN
  • IvyBridge-DT, IvyBridge-EP/EN, IvyBridge-EX
  • Haswell-DT, Haswell-EP, Haswell-EX
  • Broadwell-DT/H
  • Avoton
• AMD
  • Bulldozer – Interlagos, Valencia, Zurich
  • PileDriver – Abu Dhabi, Seoul, Delhi
  • Steamroller – Berlin
  • Kyoto

If you boot the ESXi 8.0 installer and it detects that you have an unsupported CPU, you will see the following error message.

The default behavior of the ESXi 8.0 installer is to prevent users from installing ESXi on a system that has a CPU that is not officially supported.

ProTip: With that said, there is a workaround for those that wish to forgo official support from VMware or for homelab and testing purposes, you can add the following ESXi kernel option (SHIFT+O):

allowLegacyCPU=true

which will turn the error message into a warning message and enable the option to install ESXi, knowing that the CPU is not officially supported and accept any risks in doing so.

I/O Device Support

Similarly for I/O devices such as networking, storage, etc. that are not be supported with vSphere 8, the ESXi 8.0 installer will also list out the type of device and its respective Vendor & Device ID (see screenshot above for an example).

To view the complete list of unsupported I/O devices for vSphere 8, please refer to the following VMware KB 88172 article for more information. I know many in the VMware Homelab community makes use of the Mellanox ConnectX-3 for networking, so I just wanted to call this out as that is no longer supported and folks should look to using either the ConnectX-4 or ConnectX-5 as an alternative.

ProTip: A very easy and non-impactful way to check whether your existing CPU and I/O devices will run ESXi 8.0 is to simply boot an ESXi 8.0 installer using USB and check whether it detects all devices. You do NOT have to perform an installation to check for compatibility and you can also drop into the ESXi Shell (Alt+F1) using root and no password to perform additional validation. If you are unsure whether ESXi 8.0 will run on your platform, this is the eaiest way to validate without touching your existing installation and workloads.

For those that require the use of the Community Networking Driver for ESXi Fling to detect onboard networking like some of the recent Intel NUC platforms, folks should be be happy to learn that this Fling has been officially productized as part of vSphere 8 and custom ESXi ISO image will no longer be needed. For those that require the USB Network Native Driver for ESXi Fling, a new version of the Fling that is compatible with vSphere 8 will be required and folks should wait for that to be available before installing and/or upgrading to vSphere 8.

USB Install/Upgrade Support

Last year, VMware published revised guidance in VMware KB 85685 regarding the installation media for ESXi which includes ESXi 8.0 and specifically when using an SD or USB device. While ESXi 8.0 will continue to support installation and upgrade using an SD/USB device, it is highly recommended that customers consider a more reliable installation media like an SSD, especially for the ESXi OSData partition. Post-ESXi 8.0, USB installation and upgrades using an SD/USB device will no longer be supported and it is best to have a solution now than to wait for that to happen, if you ask me.

If you do decide to install and/or upgrade ESXi 8.0 using SD/USB device, the following warning message will be presented before allowing you to proceed with the install or upgrade.

Hardware Platform Support

While this is not an exhaustive list of hardware platforms that can successfully run ESXi 8.0, I did want to share the list of systems that I have personally tested and hope others may also contribute to this list over time to help others within the community.

The following hardware platforms can successfully run ESXi 8.0:

• Intel NUC 5 (Rock Canyon)
• Intel NUC 6 (Swift Canyon)
• Intel NUC 8 (Dawson Canyon)
• Intel NUC 9 Extreme (Ghost Canyon)
• Intel NUC 9 Pro (Quartz Canyon)
• Intel NUC 10 Performance (Frost Canyon)
• Intel NUC 11 Performance (Panther Canyon)
• Intel NUC 11 Pro (Tiger Canyon)
• Intel NUC 11 Extreme (Beast Canyon)
• Intel NUC 12 (Dragon Canyon)
• Intel NUC 12 Pro (Wall Street Canyon)
• Supermicro E200-8D
• Supermicro E302-12D

VCSA Resource Requirements

With all the new capabilities in vSphere 8, it should come as no surprise that additional resources are required for the vCenter Server Appliance (VCSA). Compared to vSphere 7, the only change is the amount of memory for each of the VCSA deployment sizes, which has increased to an additional 2GB of memory. For example, in vSphere 7, a “Tiny” configuration would required 12GB of memory and in vSphere 8, it now will require 14GB of memory.

ProTip: It is possible to change the memory configurations after the initial deployment and from my limited use, I have been able to configure a Tiny configuration with just 10GB of memory without noticing any impact or issues. Depending on your usage and feature consumption, you may need more memory but so far it has been working fine for a small 3-node vSAN cluster.

Nested ESXi Resource Requirements

Using Nested ESXi is still by the far the easiest and most efficient way to try out all the cool new features that vSphere 8 has to offer. If you plan to kick the tires with the new vSAN 8 Express Storage Architecture (ESA), at least from a workflow standpoint, make sure you can spare at least 16GB of memory (per ESXi VM), which is the minimum required to enable this feature.

Note: If you intend to only use vSAN 8 Original Storage Architecture (OSA), then you can ignore the 16GB minimum as that only applies to enabling vSAN ESA. For basic vSAN OSA enablement, 8GB (per ESXi VM) is sufficient and if you plan to run workloads, you may want to allocate more memory but behavior should be the same as vSphere 7.x.

A bonus capability that I think is worth mentioning is that configuring MAC Learning on a Distributed Virtual Portgroup is now possible through the vSphere UI as part of vSphere 8. The MAC Learning feature was introduced back in vSphere 6.7 but was only available using the vSphere API and I am glad to finally see this available in the vSphere UI for those looking to run Nested Virtualization!

You can still configure RDP settings, but you’ll have to use Group Policy to do so. Just use these steps:

1. Launch “gpedit.msc“.
2. Navigate to “Computer Configuration” > “Administrative Templates” > “Windows Components” > “Remote Desktop Services” > “Remote Desktop Session Host“.

Here you can find group policy settings to set Licensing, Security, Connections, etc. You’ll notice these are the same settings you would find in the old Remote Desktop Host Configuration tool like “Limit number of connections”, “Set time limit for disconnected sessions” , and setting the licensing mode.

You don’t need to utilize Active Directory in your environment to use these settings on the server either.

Use dig command to find which version is running on your name servers:

$ dig +short @ns1.example.com version.bind txt chaos
"9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1"

Bind

To hide version in when using Bind, open named.conf configuration file using your favorite editor, go to options section and set a custom version string using version option.

Example:

// /etc/named.conf
options {
  // Hide bind version
  version "unknown";
};

Restart the server (use bind9 instead of named on systems based on Debian):

$ sudo service named restart
Stopping named: .                                          [  OK  ]
Starting named:                                            [  OK  ]

Verify that server is returning new version string:

$ dig +short @ns1.example.com version.bind txt chaos
"unknown"

Knot

Edit knot.conf and set version parameter in system section to off:

system {
  # Used for answer to CH TXT 'version.server' or 'version.bind'
  version off;
}

Restart the server to apply changes:

$ sudo service knot restart
Stopping knot: .                                          [  OK  ]
Starting knot:                                            [  OK  ]

MyDNS

TODO

NSD

Edit nsd.conf configuration file and set hide-version parameter to yes in server section.

server:
  # /etc/nsd/nsd.conf
  # Don't answer VERSION.BIND and VERSION.SERVER CHAOS class queries
  hide-version: yes

Restart NSD server:

$ sudo service nsd restart
Stopping nsd:                                              [  OK  ]
Starting nsd:                                              [  OK  ]

PowerDNS

Edit /etc/pdns/pdns.conf and set version-string to anonymous then restart PowerDNS server.

version-string=anonymous

TinyDNS

TinyDNS doesn’t expose version.

Microsoft DNS

To control how the server responds to version query, use dnscmd command with EnableVersionQuery parameter. Possible values:

• 0x00000000 (DNS_VERSION_QUERY_OFF) No version information will be returned.
• 0x00000001 (DNS_VERSION_QUERY_FULL) The server responds with major operating system version, minor operating system version, and operating system revision.
• 0x00000002 (DNS_VERSION_QUERY_MINIMAL) The server responds with major operating system version and minor operating system version.

Example:

dnscmd /config /EnableVersionQuery 0

On Windows Server 2008 and Windows Server 2008 R2, the default value is 0x00000001. On Windows Server 2012 and Windows Server 2012 R2, the default value is 0x00000000.

YADIFA

Yadifa version can be hidden setting version in main section:

<main>
  version "not disclosed"
</main>

Çözüm (A)

Öncelikle bilmeniz gerekirki bu problem mysql sürümleri arasında oluşan farklılıklardan kaynaklanmaktadır. Sunucunuz sizin elinizde ise yani hosting değilde vps – vds vs. kullanıyorsanız mysql sürümünüzü güncelleyerek bu problemi doğrudan aşabilirsiniz. utf8mb4_unicode_ci yeni bir kodlama türüdür bu sebeple en güncel mysql sürümünü kullanmanız gerekmektedir.

Çözüm (B)

Eğer sunucu elinizde değil ise databesenizde bazı değişiklikler yaparak bu sorunu çözebilirsiniz.
İlk olarak bilgisayarınızda notepad++ editörü bulunmalıdır.

.sql dosyanızı notepad++ aracılığı ile açın.
ctrl + f kombinasyonunu kullanarak arama penceresine ulaşın, açılan arama penceresinde bul sekmesinden değiştir sekmesine geçin ve sırası ile aşağıdaki kodları tümünü değiştir butonunu kullanarak değiştirin.

1 – Aranan :  utf8mb4_unicode_ci  Değiştir : utf8_general_ci  (TÜMÜNÜ DEĞİŞTİR)

2 – Aranan : utf8mb4_unicode_520_ci Değiştir : utf8_general_ci (TÜMÜNÜ DEĞİŞTİR)

3 – Aranan : utf8mb4  Değiştir : utf8 (TÜMÜNÜ DEĞİŞTİR)

Bu işlemleri yaptıktan sonra değişiklikleri kayıt edin. sql’nizin yeni sunucuya hatasız olarak yüklendiğini göreceksiniz.

Yukarıdaki adımları dikkatli bir şekilde yaptıysanız problem ile karşılaşmazsınız. Sorun yaşarsanız yorum kısmından yazın sorununuza çözüm bulunmaya çalışılacaktır.

#1273 – Unknown collation: ‘utf8mb4_unicode_ci’ çözümü

#1273 – Unknown collation: ‘utf8mb4_unicode_520_ci’ çözümü

utf8mb4_unicode_ci to  utf8_general_ci

utf8mb4_unicode_520_ci to utf8_general_ci

My IP address is blacklisted by some sender reputation RBL and emails are not delivered.
How can I remove it form the blacklists?

RBLs

Our dedicated IP are only assigned to one account at a time, so we expect those users to take responsibility for all of the mail that is sent through their account. 

Please note: in the event that a sending domain (and not the IP address) is blacklisted, that domain’s controller will be responsible for handling the delisting request.

RBLs are blacklists of IP addresses. One IP address enters into a blacklist for spamming activity.
Here you can find instructions on what to do once the IP address entered into one or more blacklists.

Why did you get into the blacklist in the first place?

First of all, make sure you identified the reason for the blacklisting.
If you didn’t identify and resolve it, you will just make things worse by asking for delisting. The IP will be quickly re-blacklisted and it will be harder to delist it.
So, check why the IP has been blacklisted and fix the source of the problem before going ahead.
Once you resolved all the problems (if it is a new IP address there is no problem to resolve, of course), you can go ahead with the delisting with the following instructions.

First time cleanup

If you just acquired this IP address, make sure that the dns reverse lookup is set before requesting removal from blacklists.
When asked for a reason for requesting delisting, tell that you just acquired the IP address.

Delisting

First of all, let Valli check a bunch of RBLs for you: http://multirbl.valli.org/lookup
For each RBL where the IP is listed, follow the link and read the instructions on how to delist.
Each RBL has it’s own rules, some of them require an email verification in order to delist, some of them require that you explain the reasons of the listing (if it’s a new ip address just tell them that this ip address has just been assigned to you), some of them don’t allow delisting at all (it’s automatic after some time).

In the Valli list of RBLs, some are more important than others.
Some important blacklists are Spamhaus, Barracuda, SORBS, V4BL.
Start requesting the delisting from the important ones and then proceed until you requested delisting from all of the blacklists that allow it. The ones that don’t accept delisting requests will delist automatically after some time (like rbldns.ru).

There are some important blacklists that are not checked by Valli, make sure you remove the IP address also from those:

Outlook (Microsoft): https://support.microsoft.com/en-us/getsupport?oaspworkflow=start_1.0.0.0&wfname=capsub&productkey=edfsmsbl3&locale=en-us&ccsid=636014233369251686
This list doesn’t provide a test to check if the IP is blacklisted, you can easily test by sending an email from the ESVA IP address to a hotmail email address. If the email does go through then the IP address is not blacklisted, if the email isn’t delivered you can read in the SMTP response message the reason. You can find the SMTP response message in the maillog. Copy the text because it is needed in the removal request.

Microsoft Office: https://sender.office.com/Delist
This service offers a reputation check. You will be required to enter the ip address and your email address where a confirmation link will be sent.

Trend Micro: https://ers.trendmicro.com/reputations
Reputation check available.

Sophos: https://www.sophos.com/en-us/threat-center/ip-lookup.aspx
Reputation check available.

Symantec: http://ipremoval.sms.symantec.com/
Reputation check available.

Yahoo: http://help.yahoo.com/l/us/yahoo/mail/postmaster/bulkv2.html
This service is not just for bulk mailers, it is also used for delisting requests. Just like the Outlook service above, it does not offer a reputation lookup service so you should test for blacklisting trying to send an email to a yahoo email address and checking the result as described above for Outlook. In order to request delisting you must have a yahoo account, which you can create for free.

AT&T: http://rbl.att.net/cgi-bin/rbl/block_admin.cgi
It is not possible to check whether an ip address is listed or not. If your ip address is listed your messages will be bounced with an SMTP clause similar to this:
553 5.3.0 alph155 DNSBL:ATTRBL 521< 199.169.39.199 >_is_blocked.For assistance forward this email to abuse_rbl@abuse-att.net>

Barracuda: https://www.barracudacentral.org/rbl/removal-requestDelist request.

Cloudmark: https://csi.cloudmark.com/en/reset/
Delist request.

Comcast: http://postmaster.comcast.net/block-removal-request.html
Delist request.

McAfee: https://www.mcafee.com/enterprise/en-us/threat-center/threat-feedback.html
Delist request.

Mimecast: https://www.mimecast.com/senderfeedback/
Delist request.

ProofPoint: https://ipcheck.proofpoint.com/
Delist request.

SORBS: http://www.sorbs.net/overview.shtml
Delisting and Reputation check available.

SpamCop: https://www.spamcop.net/bl.shtml
Delisting and Reputation check available.

Spam rats: https://www.spamrats.com/removal.php
Delisting service.

Spamhaus: https://www.spamhaus.org/lookup/
Delisting service.

SURBL: http://www.surbl.org/surbl-analysis
Delisting service.

URIBL: https://admin.uribl.com/
Delist service.

Whitelisting

It is a good thing also to enter into white lists:
https://www.dnswl.org/selfservice/

IP Reputation Monitoring

There are some services that allow you to monitor your reputation and check it over time. You can take advantage of this services if you send a few thousand emails on a daily basis to domains like gmail or hotmail. For small amounts of email traffic they don’t provide feedback.

Google: https://postmaster.google.com/
Microsoft: https://postmaster.live.com/snds/JMRP.aspx

1. Check that Printers Are Enabled on Connection

Ensure that you have the Printers option selected in your Remote Desktop settings. You can check this by bringing up the Remote Desktop Connection screen, selecting Local Resources and ensuring the Printers option is selected.

2. Check Server Settings

If you are connecting to a Windows Server box, ensure the settings on the server don’t disable the sharing of Printers. Login to the server, and perform these steps.

Windows 2016 & 2019

In these versions of Windows Server, RDP settings are controlled in Group Policy.

1. Launch “gpedit.msc“.
2. Navigate to “Computer Configuration” > “Administrative Templates” > “Windows Components” > “Remote Desktop Services” > “Remote Desktop Session Host“.
3. Expand “Printer Redirection“.
4. Ensure that “Do not allow client printer redirection” is set to “Not configured” or “Disabled“. Another setting you may want to check is the “Redirect only the default client printer“. This policy should also set to “Not configured” or “Disabled” if you want more than just the default printer to be available to use.

Windows 2012

1. Open “Server Manager“.
2. Select “Remote Desktop” Services.
3. Select “Collections“.
4. Select “Tasks“, then choose “Edit Properties“.
5. Under the “Client Settings” tab, ensure the “Windows Printer” is enabled.

Windows 2008

1. Go to “Start” > “Administrative Tools” > “Remote Desktop Services” > “Remote Desktop Session Host Configuration“.
2. Select “Connections“, right-click the name of the connection > “Properties” > “Client Settings” > “Redirection“. Ensure that “Windows Printer” is not checked.

3. Ensure Drivers Are Installed On Server

Check that the printer drivers for the printer you are attempting to use are installed on the computer you are connecting to. If the drivers haven’t been installed on the computer you are connecting to, the printer won’t appear at all.

Bu yazımda DELL İdrac’inizi bir firewall arkasından internete çıkarmak isterseniz gerekli olan portları paylaşacağım. (Genel olarak uzaktan erişim cihazlarınızı internete çıkarmamanızı tavsiye ederim, ama bazen ihtiyaç olabiliyor.

Umarım faydası olur.

• 22 SSH
• 23 Telnet
• 80 HTTP
• 443 HTTPS
• 161 SNMP
• 3668 Virtual Media server
• 5869 Remote racadm server
• 5900-5901 Console Redirection

Adım 1: Disk Performans Sayaçlarını Etkinleştirme 
 

1. Görev Yöneticisinin kapalı olduğundan emin olun.
    
2. “Yönetici Olarak Çalıştır” seçeneğini kullanarak Komut İstemi’ni (cmd) başlatın. 
    
3. Komut İstemine aşağıdaki komutu girin: 
    
   diskperf -Y
    
4.  Enter tuşuna basın.
    
5. Komut İstemi‘ni kapatın.
    
6. Görev Yöneticisi‘ni tekrar açın.

Diskperf komutunu çalıştırdıktan sonra, performans sekmesinde Disk performans istatistiklerini görüntüleme şimdi görünür olmalıdır.

Umarım faydası olur. İyi çalışmalar.