No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionAccess V100R006C20 on FusionCloud V100R006C10 Software Installation Guide 11 (Microsoft AD)

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Creating a User VM Image

Creating a User VM Image

Creating a VM Template

Scenarios

Creating a bare VM is the first step for creating a VM template. You need to set basic VM parameters, such as the OS type and version, hardware specifications (CPU quantity, memory capacity, number of disks, and number of NICs), port group to which the NICs belong, disk data store type, configuration mode, and capacity. After setting the basic parameters, create the bare VM on FusionCompute and prepare for the OS installation on the VM.

This section describes how to create a bare VM, install an OS on the VM, configure the OS, create a user VM image, install an OS and patches, and set the DST for the OS on FusionCompute.

For details about supported user VM OSs, see Supported OSs.

NOTE:

This section uses the Windows 7 Professional 32-bit OS as an example.

Prerequisites
  • You have obtained the image file to be installed.
    NOTE:

    Obtain the Windows ISO file from official channels. Do not use an OS Ghost image that is manually simplified.

  • You have obtained the latest FusionSphere SIA Vx.x.xx.xxx_GuestOSDriver for FusionSphere V100R00xCxx.zip software package if Windows Server 2016 needs to be installed for FusionAccess.
  • You have logged in to FusionCompute.
  • You have obtained the FusionAccess_Windows_Installer_V100R006C20SPC102.iso file.
Procedure

Creating a bare VM

  1. On FusionCompute, click VM and Template.
  2. Click Create VM.

    The Create VM page is displayed.

  3. Select Create VM, click Next, and set the parameters, as shown in Table 4-13.

    NOTE:
    • You can click before a parameter to view detailed configuration items of this parameter.
    • Possible values of Configuration mode:
      • Common: The space configured for the virtual disk is allocated and the data remaining on the physical device is zeroed out when the disk is created. It takes longer to create disks in this mode than to create disks in other modes.
      • Thin provisioning: The system allocates part of the configured disk capacity for the first time, and allocates the rest disk capacity based on the storage usage of the disk until all the configured disk capacity is allocated.
      • Thick provisioning lazy zeroed: The space configured for the virtual disk is allocated during the creation of the disk. The data remaining on the physical device is zeroed out only on the first data write from the VM. It takes less time to create disks in this mode than to create disks in Common mode. The I/O performance is higher than the disks in Thin provisioning mode but lower than the disks in Common mode.
    Table 4-13 VM parameter settings

    Category

    Description

    Data Store resources

    Select a datastore based on the FusionCompute data plan.

    NOTE:

    If you select FusionStorage, you cannot change the storage type to Local disk when you use the template to provision VMs.

    Hardware

    • CPUs:
      • 2 or more for Windows 7 (32-bit or 64-bit)
      • 4 or more for Windows 10 (32-bit or 64-bit)
      • 2 or more for Windows Server 2008 R2
      • 4 or more for Windows Server 2016
    • Memory size:
      • 4 GB or more for Windows 7 (32-bit or 64-bit)
      • 8 GB or more for Windows 10 (32-bit or 64-bit)
      • 4 GB or more for Windows Server 2008 R2
      • 8 GB or more for Windows Server 2016
    • Disk 1:
      • 60 GB or more for Windows 7 (32-bit or 64-bit)
      • 80 GB or more for Windows 10 (32-bit or 64-bit)
      • 60 GB or more for Windows Server 2008 R2
      • 80 GB or more for Windows Server 2016
      • Configuration mode: Common.
    • NIC 1: Select a service plane distributed virtual switch (DVS) and port group for the user VM.

    The quantities of Disks and NICs are 1 by default. You can increase the quantities as required.

    Others

    Retain the default values for other parameters.

  4. Retain the default values for other parameters, confirm information about the VM to be created, and create the bare VM as prompted.

    To start a VM immediately after it is created, select Start the VM after creation.

Mounting the OS ISO file

  1. Choose VM and Template from the main menu of FusionCompute.
  2. In the navigation tree of the page that is displayed, click VM and Template.
  3. In the Name column, click the name of the newly created bare VM.
  1. Choose Hardware > CD/DVD-ROM drive > Mount Local CD/DVD-ROM Drive, and click OK.
  2. Mount the ISO file to a VM. Select Restart the VM now to install the OS, and click Confirm.
  3. In the VM and Template list, locate the row where the newly created bare VM is located, and click Log In Using VNC.

Installing the OS

  1. On the VM, install and configure the OS as required.

    For details about the installation procedure, see Installing a Windows OS.

    NOTE:

    The temporary account must be set to LocalAccount when you install the OS. Otherwise, the template tool cannot delete the temporary account automatically, which poses a security risk.

    If you need to manually delete local users, refer to Deleting Local Users of Windows System.

  2. Uninstall the CD/DVD-ROM drive from the VM.

Activating the Administrator account for the VM

NOTE:

Skip this section if Windows Server 2008 R2 or Windows Server 2016 is used.

  1. On the VM, click , enter the compmgmt.msc command, and press Enter.

    The Computer Management window is displayed.

  2. In the navigation pane on the left, choose Computer Management (Local) > System Tools > Local Users and Groups, and select Users.
  3. In the right pane, right-click Administrator and choose Properties from the shortcut menu.

    The Administrator Properties window is displayed.

  4. On the General tab page, deselect Account is disabled, and click OK.

    The Administrator account is activated, and its default password is empty.

  5. NOTE:
    • Set the password for the Administrator account and ensure that the password is not blank. Otherwise, executing the task fails.

      The password must conform to the following rules:

      • Contains at least one uppercase letter (A to Z), one lowercase letter (a to z), one digit (0 to 9), and one space or special character (~!@#¥%...&*(-_=+\|{};:'",<.>/?).
      • Contains 8 to 32 characters.
      • Cannot be the same as the recent three passwords.
      • Cannot contain the username or reversed username.

    Set the password of the Administrator account as required, confirm the password, and click OK.

    The password is set.

  6. Click OK.
  7. Log out of the OS and log in to the VM using the Administrator account.

Configuring the remote desktop service

NOTE:

This operation ensures that the VM provisioned by using the template can be remotely accessed.

  1. On the VM, click , enter the compmgmt.msc command, and press Enter.

    The Computer Management window is displayed.

  2. In the navigation pane on the left, choose Computer Management (Local) > Services and Applications and select Services.
  3. In the list on the right, right-click Remote Desktop Services and choose Properties from the shortcut menu.

    The Remote Desktop Services Properties (Local Computer) window is displayed.

  4. On the General tab page, set Startup type to Automatic and click OK.

Installing the PV driver

  1. Install the PV driver for different OSs. For details, see Table 4-14.

    Table 4-14 Install the PV driver.

    VM OS

    Procedure

    Windows 7 and Windows Server 2008 R2

    1. On the FusionCompute portal, locate the row of the VM to be operated, choose More > Mount Tools, and click OK twice.
    2. Go to the VM CD-ROM directory. Right-click Setup and choose Run as administrator from the shortcut menu. Install the software as prompted. During the installation, retain the default settings.
    3. After the software is installed, restart the VM once or twice as prompted, and then log in to the VM using the Administrator account.
    4. On the FusionCompute portal, locate the row that contains the target VM, and choose More > Unmount Tools.

    Windows 10

    1. On the FusionCompute portal, locate the row of the VM to be operated, choose More > Mount Tools, and click OK twice.
    2. Go to the VM CD-ROM directory. Right-click Setup and choose Run as administrator from the shortcut menu. Install the software as prompted. During the installation, retain the default settings.
    3. After the software is installed, restart the VM once or twice as prompted, and then log in to the VM using the Administrator account.
    4. On the FusionCompute portal, locate the row that contains the target VM, and choose More > Unmount Tools.

    Windows Server 2016

    1. On the FusionCompute portal, locate the row of the VM to be operated, choose More > Mount Tools, and click OK twice.
    2. Go to the VM CD-ROM directory. Right-click Setup and choose Run as administrator from the shortcut menu. Install the software as prompted. During the installation, retain the default settings.
    3. After the software is installed, restart the VM once or twice as prompted, and then log in to the VM using the Administrator account.
    4. On the FusionCompute portal, locate the row that contains the target VM, and choose More > Unmount Tools.

Copying non-ISO files

  1. Copy non-ISO files, such as OS patches and installation programs of peripheral drivers, application software, and Cloudbase-Init, to the C:\ directory of the VM.

    Select applications based on Huawei FusionAccess Preferred Applications.

(Optional) Configuring the DST

Perform this operation only for regions that use DST.

  1. Configure the DST.

    • If your OS supports the DST, perform the following steps:
      1. On the VM, click the Date and Time area on the taskbar. In the dialog box that appears, click Change date and time settings.
      2. Click Change time zone.
      3. On the Time Zone Settings page, select a time zone based on the actual region and click OK twice.
        NOTE:

        If Automatically adjust clock for Daylight Saving Time is displayed on the Time Zone Settings page, select it.

    • If your OS does not support the DST, obtain TZEDIT.exe from http://support.huawei.com/ecommunity/bbs/10301999.html and set the DST as prompted.

Installing OS patches

  1. Install OS patches based on Table 4-15.

    NOTE:

    Obtain OS patches based on Software Packages.

    • If the OS patch is an .iso file, mount the CD-ROM drive and run the installation program.

      After the installation is complete, unmount the CD-ROM drive promptly. Otherwise, the CD-ROM drive cannot be mounted to another VM running on the same host.

    • If the OS patch is not an .iso file, find the patch in C:\ on the VM and run the installation program.
    Table 4-15 Installing OS patches

    OS Type

    Description

    Windows 7 and Windows Server 2008 R2

    • Windows 7: Install the KB4012212 ransomware patch and patch KB976932 in sequence.
    • Windows Server 2008 R2: Install the KB4012212 ransomware patch.

    Windows 10

    For Windows 10 VMs, only LTSB and CBB services are supported. You are advised to update the VM patch using Windows Server Update Services (WSUS). For details about patch version mapping, see Huawei FusionCloud Compatibility Check Assistant.

    Other supported OSs

    Install OS patches as required.

(Optional) Installing peripheral drivers

  1. Install peripheral drivers as required.

    Search for the peripheral driver installation programs in the C:\ directory on the VM and install them.

    NOTE:

    If a driver can be installed only when the peripheral is connected to a TC, copy the driver installation program to the VM and ask the user to install the driver when the peripheral is connected.

(Optional) Initializing the data disk

You must perform this operation when adding a data disk to a VM.

  1. On the taskbar of the VM OS, choose Start, and enter compmgmt.msc in Search programs and files to go to the Computer Management window.
  2. In the navigation pane on the left, unfold Storage, and choose Disk Management.

    The Initialize Disk window is displayed.

  1. Click OK.

    NOTE:

    If the disk to be initialized is in the Offline state, right-click the disk and choose Online from the shortcut menu, and then right-click the disk again and choose Initialize Disk.

  2. In the right area similar to Figure 4-43, right-click the disk on which no partition is created, and choose New Simple Volume from the shortcut menu.

    The New Simple Volume Wizard window is displayed.

    Figure 4-43 Creating a simple disk

  3. Create simple volumes as required.

    NOTE:

    After volumes are created, you must manually change the drive letters. In the Disk Management window, right-click each volume, choose Change Drive Letter and Paths, and change the drive letters of data disks and CD-ROM. You are advised to change the drive letters in alphabetical order of D and E because they will be rearranged in alphabetical order after template encapsulation.

(Optional) Deleting local users

NOTE:

A local user of the Windows system can log in to each Windows VM created by the image. For security reasons, you are advised to delete unnecessary local users in the Windows system as needed.

  1. Delete unnecessary local users in the Windows system as needed. For details, see Deleting Local Users of Windows System.

Using the template tool to configure the VM OS

  1. Mount FusionAccess_Windows_Installer_V100R006C20SPC102.iso to the VM.
  2. On the VM, double-click the CD/DVD-ROM.

    NOTE:

    The FusionAccess Windows Installer window is displayed after the CD-ROMs of some VMs are double-clicked.

  3. Double-click run.bat.

    The Figure 4-44 window is displayed.

    NOTE:
    • On Windows 7 or Windows Server 2008 R2, the system asks you to enable the .NET Framework 3.5 function. Then the tool window is displayed automatically and you do not need to restart the OS.
    • On other OSs, the tool window is displayed directly.
    Figure 4-44 FusionAccess Windows Installer

  4. Click Create Template.

    The window for creating a template is displayed.

  5. Set the virtualization environment to FusionSphere(OpenStack), as shown in Figure 4-45.

    Figure 4-45 Environment

  6. Select the desktop type, as shown in Figure 4-46.

    Figure 4-46 Core components

  7. Set the HDC addresses to hdc01.desktop.com and hdc02.desktop.com, as shown in Figure 4-47.

    Figure 4-47 HDC
    NOTE:

    During the configuration of HDC, if a message is displayed indicating that the HDC address is unreachable and asking you whether to continue, ignore the error and proceed with the subsequent operations.

  8. Perform other operations as prompted.

Installing software

  1. Install applications on the VM.

    • Some security software (antivirus software, safeguards, and firewalls) may conflict with the Microsoft encapsulation tool and cause a VM creation failure, the blue screen of death (BSOD), or blank screen for created VMs. Therefore, install security software only after VMs are provisioned successfully.
    • It is recommended that Kingsoft V8+ terminal security system software be installed on VMs to perform operations such as clearing viruses, optimizing OSs, clearing junk files, repairing vulnerabilities, and managing software.

    Select one of the following installation methods based on the formats of application software:

    • If the OS patch is an .iso file, mount the CD-ROM drive and run the installation program.
    • If the OS patch is not an .iso file, search for application software in C:\ on the VM, and run the installation programs.
    NOTE:
    • After the installation by mounting the CD-ROM drive is complete, unmount the CD-ROM drive promptly. Otherwise, the CD-ROM drive cannot be mounted to another VM running on the host to which the VM belongs.
    • If the antivirus software contains firewalls, disable the firewalls or enable the ports required by the HDP in the firewalls before you install the application software. Otherwise, VM connections will be affected. For details about ports required by HDP, see Communication Ports.
    • After the application software is installed, you are advised to clone the VM:
      1. In the row that contains the VM to be cloned, choose Operation > More > Clone VM and click Next as prompted. Then click Finish to perform the clone VM operation.
      2. In the row that contains the cloned VM, choose Operation > Power off, and power off the VM as prompted.

    If this operation is not performed, you need to create a bare VM again and install and configure the VM OS when image encapsulation fails. To reduce repeated operations, you are advised to clone the VM.

    Cloning a VM takes about 20 minutes. You are advised to perform this operation during off-peak hours.

Installing the Cloudbase-Init software

NOTE:
  • If the Cloudbase-Init mode is enabled for FusionSphere, install Cloudbase-Init. For details, see Step 44 to Step 47.
  • If Cloudbase-Init is not enabled for FusionSphere (that is, the default FusionCompute file injection mode), do not install Cloudbase-Init. Go to Step 48.
  1. Copy the Cloudbase-Init software to the C:\ directory on the VM. Run the Cloudbase-Init software and install it as prompted.
  2. On the Configuration options page, configure the software according to Figure 4-48.

    Figure 4-48 Configuration options

  3. After the configuration, deselect the selected options and click Finish, as shown in Figure 4-49.

    Figure 4-49 Finish

  4. Add configuration item netbios_host_name_compatibility=false to the last row in the C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf configuration file of the Cloudbase-Init software so that the host name can contain a maximum of 63 characters.

    NOTE:

    NetBIOS is limited by Windows and can contain at most 15 characters.

Stopping the VM

  1. Stop the VM.

Registering a VM Image

Scenarios

This section describes how to upload the created image file to the target storage directory and register the image for creating compute instances.

Prerequisites

You have logged in to FusionCompute.

Procedure

Exporting the VM

  1. On FusionCompute, choose VM and Template and go to the VM page.
  2. In the Name column, click the name of the created VM.
  3. On the Options tab page, click NIC Advanced Settings. In the right area, set NIC type to HW_V_NET, as shown in Figure 4-50.

    Figure 4-50 NIC Advanced Settings

  1. Click VM and Template and go to the VM page. Locate the row of the VM and click More.
  2. Select Export VM from the prompted drop-down list.
  3. Set Select Export Source to Local PC and click Next.
  4. Set the following parameters and click Finish.

    NOTE:

    A Java plug-in is required if you want to export the VM to the local PC.

    • Name
    • Directory
    • Format (Retain default value ovf.)

    The export process takes about 10 minutes. Then, an .ovf file and a .vhd file are obtained.

Registering an image

  1. Select the image upload mode.

    • If the image file is smaller than 6 GB, select the HTTPS or NFS upload mode, or register the image on FusionSphere OpenStack.
    • If the image file is larger than and equal to 6 GB and smaller than and equal to 200 GB, select the NFS upload mode, or register the image on FusionSphere OpenStack.
    • If the image file is larger than 200 GB, register the image on FusionSphere OpenStack.

    Perform the operations according to the upload mode:

  2. Upload the image file to the NFS server (for example, NAS).

    The NFS server is prepared by customers and must meet the following requirements:

    • If you register a FusionCompute image, the IP address of the NFS server can communicate with the management plane of the CNA node.
    • If you register a KVM or Ironic image, the NFS server can communicate with the API network plane of the VM on FusionSphere OpenStack Management Console.

  3. Log in to the FusionSphere OpenStack management console, choose Resources > Computing > Images, and click Register.

    In the image registration dialog box that is displayed, set the parameters.

    The key parameters are as follows:
    • Provided As Service: Set it to Supported.
    • Type: Set it to FusionCompute.
    • Cloud-Init: Select it.

    Set other parameters as required.

  4. Select the image file. Set the image parameters and click Register.

    • If Upload Mode is set to HTTPS, the image is uploaded and registered on the local PC.
    • If Upload Mode is set to NFS, the image is uploaded and registered on the NFS server.

    View the Status column to check whether the image is successfully registered.

  5. In the KVM and FusionCompute scenarios, if the image cannot be displayed in the image list on the ServiceCenter tenant portal, update the image attributes. For details, see Updating an Image.
Translation
Download
Updated: 2019-07-01

Document ID: EDOC1100021785

Views: 48315

Downloads: 104

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next