Tag Archives: upgrade

Upgrade to Windows 10 20H1 (2004) BSOD

Today when I tried to upgrade my windows 10 1909 to windows 10 20H1, I got multiple BSOD.
Based on the information on the BSOD screen, the BSOD were caused by some drivers (aksdf.sys, hardlock.sys, aksfridge.sys)

bsod 1

bsod 2)

After investigation, looks like all these drivers were Sentinel Data Filter Device Driver/Aladdin HASP Data Filter Device Driver, Which provided by Safenet.
I have no idea how these driver got installed into my computer, and I can’t remove them from control panel.

The fix is to download the Sentinel HASP/LDK Windows GUI Run-time Sentinel HASP/LDK Windows GUI Run-time from thalesgroup website

Install, then uninstall it, reboot.

After reboot, I can upgrade to windows 10 20H1 successfully.

upgrade VCSA6.7 to VCSA6.7u1

It seems there is a bug in vCenter 6.7 which caused the update check of VCSA is not working.
So to upgrade VCSA from 6.7 to 6.7u1, you need to

1. In the vCenter Server Appliance Management Interface, go to Update > Settings and configure the custom URL to https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/
2.Re-try the upgrade.

Then you should be able to see all the patches.

Upgrade ESXi from 6.5 to 6.7 via command line

Run this command to see the VMware online depot and list all profiles

[root@m900:~] esxcli software sources profile list -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | grep -i ESXi-6.7
ESXi-6.7.0-8169922-no-tools       VMware, Inc.  PartnerSupported
ESXi-6.7.0-8169922-standard       VMware, Inc.  PartnerSupporte

Run the upgrade with this command:

esxcli software profile update -p ESXi-6.7.0-8169922-standard  -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

Then reboot server

Upgrade vCenter Server Appliance (VCSA) and ESXi

Upgrade vCenter


Best practices is always to upgrade vCenter before your ESXi hosts. Download the ISO and upload to your Datastore.

Attach the ISO to the vCenter VM.

Mount ISO

Mount ISO

Use Putty to connect to your VCSA and run the following command:

software-packages install --iso --acceptEulas

step 3


reboot -r updates


Update ESXi – Fast Method

This is the fastest way, but requires a decent internet connection.

Shut down all your running VM’s and enter Maintenance Mode.

Use Putty to connect to your ESXi host and run the following command:

esxcli network firewall ruleset set -e true -r httpClient
esxcli software sources profile list -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
esxcli software profile update -p ESXi-6.0.0-20160104001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

updaet esxi


Update ESXi from version 3.5 to 4.0

This page documents the process to update ESXi from version 3.5 to 4.0 if you have a standalone host or do not use vCenter Update Manager. After you have completed the firmware upgrade, you should also upgrade the virtual hardware version of your VMs as shown at the bottom of the page and also upgrade VMware Tools. Upgrading the virtual hardware version will allow you to take advantage of new VM features like 10 virtual NICs per VM, IDE virtual hard drives and VMDirectPath.

This procedure to upgrade an ESXi host from version 3.5 to 4.0 requires version 4.0 of the VMware vSphere client. Typically the vSphere client is installed after your ESXi host is installed. if you don’t have an existing install of the vSphere client v 4.0 you can extract it from the ESXi 4.0 upgrade ZIP package (VMware-viclient.vibdata.tar.gzdata.tar.4.0.0clientVMware-viclient.exe) as shown in the below image.


Continue reading

从Win 2000域升级到Win 2003域的详细步骤

从Windows 2000域升级到Windows 2003域的详细步骤

从Windows 2000域升级到Windows 2003域的问题,建议您参考以下步骤:
1.确认当前的Windows 2000域控制器工作正常,并且都打了Service Pack 4和最新的安全补丁。
2.确认Windows 2000活动目录中的5个FSMO角色都在第一台Windows 2000域控制器上(默认情况就是这样的),关于Windows 2000活动目录中FSMO角色的概念及查看方法,请参考下面两篇文档:
《Windows 2000 Active Directory FSMO 角色》:

《在图形用户介面中查看和转移 FSMO 角色》

3.在Windows 2000域控制器的光驱中插入Windows Server 2003安装光盘。在命令行方式下进入光盘上的I386目录,运行以下命令:adprep /forestprep。该命令成功完成之后,再运行以下命令:adprep /domainprep。

4.完成这一步之后,我们便扩展了当前的Windows 2000活动目录林的架构,这样就可以将Windows Server 2003加入到活动目录林中作为其中的域控制器,或者将现有的Windows 2000域控制器升级为Windows Server 2003。

关于将Windows 2000域控制器升级到Windows Server 2003以及将Windows Server 2003域控制器加入到Windows 2000域的更多详细信息,请您参考下面这篇文档:
《如何将 Windows 2000 域控制器升级到 Windows Server 2003》:http://support.microsoft.com/?id=325379

5.在新购买的计算机上安装Windows Server 2003,并打上最新的安全补丁。
6.确认这台Windows Server 2003网络连接正常,可以访问域控制器和DNS服务器。将其配置为使用固定IP地址,并指定DNS服务器地址。
7.在Windows Server 2003上运行dcpromo命令将其升级为域控制器,并在升级时选择使其成为现有Windows 2000域的额外的域控制器。
8.在Windows Server 2003上安装DNS服务,确认它已经和原来的Windows 2000 DNS服务器上的数据复制同步后,将它的DNS服务器地址指向自己。
9.将这台Windows Server 2003域控制器设为全局编录(Glocal Catalog)服务器,具体方法请参考下面这篇文档:
《How to promote a domain controller to a global catalog server》:

10.将原来的Windows 2000域控制器上的5个FSMO角色转移到这台Windows Server 2003域控制器上,具体方法请参考下面这篇文档:
《如何查看和转移 Windows Server 2003 中的 FSMO 角色》:

当最后一步转移结构主机角色时可能会提示“当前域控制器是全局编录服务器,不要将结构主机角色转移到该域控制器上”,由于是在单域环境中,直接确认忽略该提示即可。关于在Windows 2000/2003域控制器上放置FSMO的更多信息,请参考下面这篇文档:
《在 Windows 2000 域控制器上放置和优化 FSMO》:

11.完成以上操作之后,新的Windows Server 2003域控制器便替代了原来的第一台Windows 2000域控制器的角色,但我们需要等待一段时间使原来的Windows 2000域控制器上的和全局编录及FSMO角色相关的活动目录信息完全复制到Windows Server 2003域控制器上。建议您观察一两天时间,并确认新的Windows Server 2003域控制器/DNS服务器一切工作正常后,再将原来的Windows 2000域控制器降级。

12.当所有的Windows 2000域控制器都成功降级,当前域中只剩下Windows Server 2003域控制器后,我们便可以提升当前域/活动目录林的功能级别,以便应用Windows 2003活动目录中的一些新特性,具体方法和注意事项请参考下面这篇文档:
《如何在 Windows Server 2003 中提升域和目录林功能级别》:

Technorati Tags: ,,,,,