VMware Enable SSH (vSphere ESX)
VMware Enable SSH KB ID 0000299 Problem Should you wish to get SSH (remote secure console) access to your ESX hosts, you need to do the following. ESX Version 8 and Newer ESX Version 6.5 and Newer ESX version 5 and Newer ESX version 4.1.0 ESX version 4.0.0 and earlier ESX version 4.0.0 and earlier Solution VMware Enable SSH ESX 8.0 Directly on an ESX Host: If you have a stand-alone ESX Server running version 8.x, Log in via the...
Restore AD Objects
Restore AD Objects KB ID 0000096 Problem Ever since we had Server 2008 R2 we have had the AD recycle bin (which is not enabled by default). Even if you have not enabled the AD Recycle bin, when objects are deleted from AD they are not completely ‘deleted’ they are simply tombstoned, and they can be restored (for 180 days). Note: Those object’s when restored WILL lose some of their attributes though! CAN I RESTORE AD...
MAC OSX – Add ‘Open Terminal Window Here’ to ‘Right Click’
KB ID 0001060 Problem One of the things I used to like about using Windows was if I needed to drop to command line, I could (from any given location), by simply right clicking (while pressing CTRL) and selecting ‘Open Command Window Here. On a MAC I have Terminal but thats not an option. Solution As with most things on the MAC it is there, you just need to enable it. 1. Apple Logo > System Preferences. 2. Keyboard. 3....
Windows – Certificate Enrollment Fails
KB ID 0000921 Problem I first saw this problem a few years ago trying to get some Windows clients to auto enrol with server 2008, then this week my colleagues could not get new 2019 Domain Controller to enrol for a Kerberos certificate, and the this was caused by the same problem. Symtoms (RPC Error) 1. Test to make sure the client can see the CA, and is able to communicate with it, issue the following command; certutil -pulse As...
Outlook OAB download fails with 0x80004005 and/or 0x8004010F
KB ID 0000035 Problem 0x8004010F is caused by client not being able to see the Offline Address Book. 0x8004010F Error With Exchange 2013/2016/2019 Firstly make sure your autodiscover is correct, on the Exchange server open the Exchange management shell, and issue the following command. Get-clientAccessServer | fl Name,AutoDiscoverServiceInternalUri If you need to fix/change it, use the following syntax. Set-ClientAccessServer...