Yes, it happens to every system administrator from time to time. The account lockout. Usually Microsoft Account Lockout Status tool or Netwrix Account Lockout Examiner (my favorite) work well. Not this time…
Some DFS-related errors, such as “Cannot enumerate namespace“, “Element not found” or “RPC server is not available” are related to the configuration issues in namespace. All DFS components in registry, Active Directory and file system should be in sync. If they are not, the mentioned above errors happen. Pretty often it is easier and faster to remove DFS namespace completely and recreate it rather than to fix it. This article is about removing a DFS namespace and cleaning up all its components.
If you have Western Digital WD Sentinel (DX4000, DX4200, DS5100, DS6100) NAS device, you may have trouble replacing the failed drive. Even if the drive is from the compatibility list, the device does not see it as compatible. Fortunately, WD Support has a solution
Cannot log into remote system due to time discrepancy?
Yes, it happened to me too: I forgot my vCenter SSO master password, the one that used for the admin@System-Domain account. VMware KB 2034608 clearly says that “The master password is stored in the database and can only be changed by re-installing vCenter Single Sign-On 5.1 with a fresh back-end database”. It did not give me extra optimism in resolving the issue, but Ingmar Verheij gave me a hope. His article, which you can find here, describes in full details how to reset the SSO master password. My text is just an instruction, so I strongly recommend to read Ingmar’s page first.
Even though I have already published the article about the sa password recovery, this Part 2 adds some interesting stuff. This time everything is done via command line interface
Here’s another issue I have faced today. I needed to log into one of our vSphere farms, but the only thing I got using any accounts was this: