dism /online /add-package /packagepath:”C:\Windows\Servicing\Packages\Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum”
sc config wuauserv type= own
Today when I installed mysql5.7 on my new freebsd server, I got below problem:
Error adding new user - pw: user 'anne' disappeared during update
This issue is not common. And it’s caused by atabases are out of sync.
To fix this issue, just Run
/usr/sbin/pwd_mkdb -p /etc/master.passwd
Put the host into maintenance mode, ssh to the host, and then run below command:
esxcli network firewall ruleset set -e true -r httpClient
esxcli software profile install -p ESXi-6.5.0-20170404001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
Then reboot the host after installation finished:)
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:
We are using VMware NSX in our production environment for a long time.
And recently we got some problem with NSX, the symptoms is
Some VMs will lose network connection after migrated to another VM;
New firewall rules are not able to apply on some of the VMs.
After engaged VMware, VMware confirmed that it’s a bug in NSX.
VMware assigned about 1.6G heap memory for NSX firewall on each of the ESX hosts. If you applied too much rules or you have too many VMs and you’ll reach the memory limit. Then you’ll get this issue…
Current fix is to upgrade to 6.2.3…