Windows 10 Upgrade Utility

[Oliver Parkes]

GSUpgrade Tool is a Windows-based firmware upgrade utility to help users to flash firmware for the security products such as GDS3710 and Grandstream IP Camera products in LAN environment. Using this tool to upgrade can prevent bricking the device during firmware upgrade process due to Internet interruption or power outage, as well as help users to upgrade firmware at installation sites where Internet access is restricted.

I suspect the flash needs to be formatted MBR and FAT as I show in that image. Possibly neither NTFS nor exFAT will boot from USB flash. i have had problems using CD or DVD in a USB adapter. USB2 does not always provide enough current (0.5 amp) to spin the DVD. Internal DVD drive should be OK but older systems can be full of dust causing reading problems. I do not think the problem is the bios.

The HP Business Desktop system supported by this softpaq provides a BIOS upgrade option through F10 setup using the "Flash System ROM" feature. Reboot the PC and press F10 to enter setup. In the File menu, select the "Flash System ROM" item. This flash utility will present the user with the option to select the media containing the BIOS image file (XXX_MMmm.bin). The binary image file is contained in the DOS Flash directory and is named XXX_MMmm.bin where "XXX" is the abbreviated BIOS family, "MM" is the major version number, and "mm" is the minor version number. F10 ROM based flash can accept the binary file from the root directory of any removable media such as USB or legacy floppy diskette. The user is prompted when the process is completed. The new BIOS code will not take effect until the PC is rebooted.

We recommend that you install the latest PV drivers to improve the stability and performance of your EC2 Windows instances. The directions on this page help you download the driver package and run the install program.

You can use Distributor, a capability of AWS Systems Manager, to install or upgrade the AWS PV driver package. The installation or upgrade can be performed one time, or you can install or update it on a schedule. The In-place update option for Installation Type isn't supported for this Distributor package.

Instead of creating the AMI from the Amazon EC2 console, you can use Systems Manager Automation to create the AMI using the AWS-CreateImage runbook. For more information, see AWS-CreateImage in the AWS Systems Manager Automation runbook reference User Guide.

When you stop an instance, the data on any instance store volumes is erased. Before you stop an instance, verify that you've copied any data that you need from your instance store volumes to persistent storage, such as Amazon EBS or Amazon S3.

We recommend that you take all non-system disks offline and note any drive letter mappings to the secondary disks in Disk Management before you perform this upgrade. This step is not required if you are performing an in-place update of AWS PV drivers. We also recommend setting non-essential services to Manual start-up in the Services console.

Verify that the driver version is the same as the latest version listed in the Driver Version History table. For more information, see AWS PV driver package history Open Disk Management to review any offline secondary volumes and bring them online corresponding to the drive letters noted in Step 3.

If you previously disabled TCP offloading using Netsh for Citrix PV drivers we recommend that you re-enable this feature after upgrading to AWS PV drivers. TCP Offloading issues with Citrix drivers are not present in the AWS PV drivers. As a result, TCP Offloading provides better performance with AWS PV drivers.

Use the following procedure to perform an in-place upgrade of AWS PV drivers, or to upgrade from Citrix PV drivers to AWS PV drivers on Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, or Windows Server 2022. This upgrade is not available for RedHat drivers, or for other versions of Windows Server.

Some older versions of Windows Server can't use the latest drivers. To verify which driver version to use for your operating system, see the driver version table in the Paravirtual drivers for Windows instances page.

If you receive an error when downloading the file, and youare using Windows Server 2016 or earlier, TLS 1.2 might needto be enabled for your PowerShell terminal. You can enableTLS 1.2 for the current PowerShell session with thefollowing command and then try again:

After running the MSI, the instance automatically reboots and then upgrades the driver. The instance will not be available for up to 15 minutes. After the upgrade is complete and the instance passes both health checks in the Amazon EC2 console, you can verify that the new driver was installed by connecting to the instance using Remote Desktop and then running the following PowerShell command:

We recommend that you create a backup of your domain controller in case you need to roll back your changes. Using an AMI as a backup is not supported. For more information, see Backup and Restore Considerations for Virtualized Domain Controllers in the Microsoft documentation.

Before running this command, confirm that you know the DSRM password. You'll need this information so that you can log in to your instance after the upgrade is complete and the instance automatically reboots.

The system must boot into DSRM because the upgrade utility removes Citrix PV storage drivers so it can install AWS PV drivers. Therefore we recommend noting any drive letter and folder mappings to the secondary disks in Disk Management. When Citrix PV storage drivers are not present, secondary drives are not detected. Domain controllers that use an NTDS folder on secondary drives will not boot because the secondary disk is not detected.

After the upgrade is complete and the instance passes both health checks in the Amazon EC2 console, connect to the instance using Remote Desktop. Open Disk Management to review any offline secondary volumes and bring them online corresponding to the drive letters and folder mappings noted earlier.

To complete the upgrade process, verify that the new driver was installed. In Device Manager, under Storage Controllers, locate AWS PV Storage Host Adapter. Verify that the driver version is the same as the latest version listed in the Driver Version History table. For more information, see AWS PV driver package history.

If you previously disabled TCP offloading using Netsh for Citrix PV drivers we recommend that you re-enable this feature after upgrading to AWS PV Drivers. TCP Offloading issues with Citrix drivers are not present in the AWS PV drivers. As a result, TCP Offloading provides better performance with AWS PV drivers.

Windows PowerShell 3.0 is bundled in the Windows Management Framework (WMF) version 3.0 install package. If you need to install Windows PowerShell 3.0, see Windows Management Framework 3.0 in the Microsoft Download Center.

If you are using Citrix PV drivers on Windows Server, you can upgrade the Citrix Xen guest agent service. This Windows service handles tasks such as shutdown and restart events from the API. You can run this upgrade package on any version of Windows Server, as long as the instance is running Citrix PV drivers.

Before you start upgrading your drivers, make sure you back up your important information on the instance, or create an AMI from the instance. For more information about creating an AMI, see Create an Amazon EBS-backed AMI.

Note: The tabcmd command-line utility version 2.0 is available at Tableau tabcmd(Link opens in a new window). This new version allows you to run tabcmd commands on MacOS and Linux, and to authenticate using personal access tokens (PATs). Version 2.0 is built on public endpoints available in the Python-based Tableau Server Client (TSC). This latest version has limited support for Tableau Server.

When Tableau Server or Tableau Cloud is upgraded to a new version, if an updated version of tabcmd is required, you can download it from the Tableau Server Releases page on the Tableau website.

3a8082e126