To upgrade ESXi to 6.7U2, usually use below command is enough:
esxcli software profile update -p ESXi-6.7.0-20190402001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
But this time I got error “[Error28] No space left on device”.
Someone said to enable the swap on SSD can fix the issue, but I tried, it doesn’t work.
The fix is to manually update a vib first
[root@host:~] cd /tmp
[root@host:/tmp] wget http://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/tools-light/VMware_locker_tools-light_10.3.5.10430147-12986307.vib
[root@host:/tmp] esxcli software vib install -f -v /tmp/VMware_locker_tools-light_10.3.5.10430147-12986307.vib
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: VMware_locker_tools-light_10.3.5.10430147-12986307
VIBs Removed: VMware_locker_tools-light_10.3.2.9925305-10176879
Then run the update again, you should be able to update your ESXi host now.
It seems Microsoft is encourage people to use the app outlook. The app is good, but I still need to sync the contact between my iphone and outlook to get my contacts number.
Spent some time to check this issue, here is the fix:
Login to outlook.live.com
In the browser, click on Settings icon (gear at top right) ; scroll down the Quick Settings panel and click on 'View all Outlook settings'
In the pop-up window, select 'General'; 'Mobile Devices'
Select the iPhone, note if you have more than one iPhone (e.g. an older device), select the 'Edit' icon (pencil) to check the details including the version, 'OK' to exit details
Click on the 'Delete' icon (bin) to remove the device
Power off the iPhone
Power on the iPhone - device should attempt to re-register with Microsoft
Open the iPhone Mail app and look for email with subject: "ACTION REQUIRED TO SYNC EMAIL" (note, this email won't appear in the online version of Outlook, only in the iPhone Mail app)
Scroll down the message and click on: "Continue using this email app".
Even though MS provide the document about how to rename domain controller, the thing is, if you only have one domain controller, the “rename” will break the AD service and you are not able to roll back.
The issue you will get is that after you rename domain controller, the AD DS services are still using the old hostname because you didn’t transfer the FSMO roles from the old name to the new name. And if you want to start any domain management tools you’ll get error said that domain is unavailable. And if you want to change domain controller name back you will get the same error because dc is not available and your renaming will failed too. And this issue won’t happen if your domain get two or more domain controllers.
Ok, how to fix this issue if you have already done so? What we can do now is to update registry and change the computer name back to the old one. Below are the four registry keys you need to update: