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 Common User VM Image

Creating a Common User VM Image

Creating a VM

Scenarios

A VM image is a disk partition with an OS installed. You can create a VM image by installing a VM on this disk partition. The process for making a VM image is to create and install a VM.

This section describes how to create a VM on the cascading FusionSphere OpenStack management console (Region Type I scenario) or FusionSphere OpenStack management console (Region Type II scenario). For details about supported user VM OSs, see Supported OSs.

Prerequisites
  • You have logged in to the cascading FusionSphere OpenStack management console (Region Type I scenario) or FusionSphere OpenStack management console (Region Type II scenario).
  • You have set the value of VM Watchdog to OFF. If the value is ON before image creation, set the value to ON after image creation.
  • You have obtained the ISO file of the required Windows OS version.
Procedure

Registering an image

  1. On the FusionSphere OpenStack management console page, choose Resources > Computing > Images, and click Register.
  2. Set the parameters listed in Table 4-8, retain the default values of the other parameters, and click OK.

    Table 4-8 Image parameters

    Parameter

    Description

    Provided As Service

    Supported

    Type

    KVM

    Name

    FusionAccess_WindowsXXX_Image

    Applicable OS

    Windows

    OS Version

    Select the required OS version.

    Min Disk (GB)

    60

    Min Memory (MB)

    4096

    Disk Device Type

    ide

    Image Server Type

    Glance

    Upload Mode

    HTTPS

    Image File

    Select the required image file.

  3. After the registration, refresh the image list.

    If the newly registered image is displayed, the registration is successful.

Creating a VM

  1. Choose Resources > Computing > Compute Instances and click Create.
  2. Set Availability Zones to the AZ where backend storage is interconnected and the VDI specifications are the local disk, for example, manage-az, and click Next.
  3. Select the image registered in Step 2 and click Next.
  4. Select the vdi-windows-image flavor created in Defining Computing Instance Flavors (KVM) and click Next.
  1. Select the DMZ_Service network, as shown in Figure 4-18.

    Figure 4-18 Selecting a network

  2. Click Next.
  3. In the window that is displayed, set the VM name to FusionAccess_WindowsXXX_VM and click Next.

    NOTE:
    • If you do not add the VMTools role to all hosts in the AZ in Obtaining UVP VMTools, select the hosts where the VMTools role is deployed.
    • If the VMTools role has been added to all hosts in the AZ, this option is not selected by default.

  4. Confirm the VM information and click Complete to start VM creation.
  5. Choose System > Tasks and Logs > Task Center to check the VM creation progress.

    When the status becomes Succeeded, the VM is successfully created.

  6. After the VM is created, choose Resources > Computing > Compute Instances to record the VM IP address.

Configuring a VM

Scenarios

This section describes how to install and configure an OS on the bare VM.

Prerequisites
  • You have logged in to the cascading FusionSphere OpenStack management console (Region Type I scenario) or FusionSphere OpenStack management console (Region Type II scenario).
  • You have obtained the required tools listed in Table 4-9.
    Table 4-9 Files to be prepared

    Folder/File

    Description

    How to Obtain

    FusionAccess_Windows_Installer_V100R006C20SPC102

    Decompressed Windows template tool file that is used to create a user VM template

    Decompress the FusionAccess_Windows_Installer_V100R006C20SPC102.iso package obtained in Software Packages.

    OS patch

    To the document release date, the following patches need to be obtained:

    • Windows 7: Install the KB4012212 ransomware patch and patch KB976932 in sequence.
    • Windows Server 2008 R2: Install the KB4012212 ransomware patch.
    • Windows 10: Install the KB3201845 and KB4013429 patch or the latest patch released by Microsoft.
      NOTE:
      • The patch is applicable to Windows 10 version 1607 (Build 14393) only.
      • Before installing the patch, ensure that patch files are copied to the directories except the root directory and Windows directory on the system disk.
      • For Windows 10 VMs, only LTSB and CBB 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.
    • Windows Server 2016:

      Install the KB3201845 and KB4013429 patch or the latest patch released by Microsoft

      NOTE:
      • The KB3201845 patch is applicable to Windows Server 2016 (Build 14393) only.
      • Before installing the patch, ensure that patch files are copied to the directories except the root directory and Windows directory on the system disk.

    For details, see Software Packages.

    CloudbaseInitSetup_xxx.msi

    A VM initialization tool used to set usernames, passwords, and the hostname and hosts files for VMs to be created using images

    For details, see Software Packages.

    TZEDIT.exe

    (Optional) DST modification tool that is used to modify DST rules of Windows OSs

    For details, see Software Packages.

    Peripheral driver

    Set this parameter as required.

    Self-provided

Procedure

Installing the OS

  1. Log in to the VM by using VNC.
  2. On the VM, install and configure the OS as required.

    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.

    For details, see Installing a Windows OS.

    NOTE:

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

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. Right-click Administrator and choose Set Password.

    • Set the password for the Administrator account and ensure that the password is not blank. Otherwise, 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.

  6. Click Proceed. The Set Password for Administrator dialog box is displayed.
  7. Set the password of the Administrator account as required, confirm the password, and click OK.

    The password is set.

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

Installing UVP VMTools

NOTE:

For a VM installed using a Windows image, the NIC driver becomes available only after UVP VMTools is installed.

  1. On the FusionSphere OpenStack management console, choose Resources > Computing > Compute Instances.
  2. Locate the row that contains the VM, and choose More > Stop.
  3. After the VM is stopped, choose More > Attach uvptools. After the mounting is successful, click Start.
  4. Log in to the VM by using VNC.
  5. On the VM, start the file resource manager and double-click CD drive E:\ to go to the drive folder.
  6. Double-click Setup.exe.
  7. Install UVP VMTools as instructed.

    If a Windows security dialog box is displayed during the installation, click Install. Otherwise, the installation fails.

  8. On the FusionSphere OpenStack management console page, locate the row that contains the VM, and choose More > Detach uvptools.

Enabling remote desktop connection

NOTE:

After the remote service connection is enabled, each Windows VM created using this image can be accessed in remote connection mode. If this feature is not required, disable the remote service connection after Copying files.

  1. On the VM, click , enter the sysdm.cpl command, and press Enter.

    The System Properties window is displayed.

  2. On the Remote tab page, select Allow remote connections to this computer.
  3. In the Remote Desktop Connection dialog box that is displayed, click OK.
  4. Click OK.

    Remote desktop connection is enabled.

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.

Copying files

  1. Run mstsc on a local PC.
  2. Enter the IP address of the target VM and click Connect.
  3. Enter the username and password for logging in to the VM and click OK.
  4. Copy the files and folders in Table 4-9 to the C:\ directory of the VM.

Configuring the DST

NOTE:

Perform this step only for scenarios that use DST.

  1. Configure the DST on the VM.

    • 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 but needs to use the DST, perform the following steps:
      1. Double-click TZEDIT.exe to start it in the C:\ directory of the VM.
      2. Modify DST rules of Windows OSs as prompted.

Installing OS patches

  1. Double-click the corresponding patch file in the C:\ directory of the VM. For details, see Table 4-10.

    Table 4-10 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.

    Windows Server 2016

    Install the KB3201845 and KB4013429 patch or the latest patch released by Microsoft

    NOTE:
    • The KB3201845 patch is applicable to Windows Server 2016 (Build 14393) only.
    • Before installing the patch, ensure that patch files are copied to the directories except the root directory and Windows directory on the system disk.

Creating a temporary admin user

Cloudbase-Init randomizes the password of user Administrator. To prevent login failure after randomization, create a temporary account and reset the password of user Administrator.

  1. Create a local user admin and add the user to the Administrators group by referring to Creating Local Users of Windows System.

Installing the Cloudbase-Init software

NOTE:

Cloudbase-Init is used for automatic initial VM configurations (such as the host name, network adapter, key, and password).

  1. Run the Cloudbase-Init software in C:\ of the VM and install it as prompted.
  2. On the Configuration options page, configure the software according to Figure 4-19.

    Figure 4-19 Configuration options

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

    Figure 4-20 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.

Creating a VM template

  1. Open the C:\FusionAccess_Windows_Installer_V100R006C20SPC102 directory of the VM.
  1. Double-click the run.bat file in the folder.

    The Figure 4-21 window is displayed.

    Figure 4-21 FusionAccess Windows Installer

  2. Click Create Template.

    The window for creating a template is displayed.

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

    Figure 4-22 Virtualization environment

  1. Set the HDA type to Common, as shown in Figure 4-23.

    Figure 4-23 Core components

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

    Figure 4-24 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.

  3. On the Function page, select Optimize function and Configure user login, as shown in Figure 4-25.

    Figure 4-25 Function
    NOTE:

    Do not select Enable Restart Restore. Otherwise, the provisioned VMs may be faulty.

  4. On the Firewall page, retain the default settings and click Next.
  5. On the Summary page, click Install.

    • During the installation, the VM will be restarted. Restart the VM using the Administrator account.
    • If you fail to log in using the default password of user Administrator after the restart, log in to the system as user admin, reset the password of user Administrator, and log in to the system again as user Administrator.

Installing peripheral drivers

  1. Install peripheral drivers as required.

    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.

Installing software

  1. Install application software based on site requirements.

    • 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.
    • 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 the ports required by the HDP, see Communication Ports.

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 the temporary user admin by referring to Deleting Local Users of Windows System.
  2. Delete other unnecessary local users in the Windows system as needed.

Encapsulating the VM template

  1. Open the C:\FusionAccess_Windows_Installer_V100R006C20SPC102 directory of the VM.
  2. Double-click the run.bat file in the folder.
  3. In the FusionAccess Windows Installer window, click Sysprep, as shown in Figure 4-26.

    Before encapsulating a template, ensure that:

    • The IP address and DNS server address are automatically obtained.
    • All software has been installed and configured.
    Figure 4-26 Encapsulating the VM template

  4. After the template is encapsulated, click Finish.

Stopping the VM

  1. Delete all the files or folders copied in Step 31 (except the peripheral drivers that need to be reserved in Step 48).
  2. Stop the VM.

Creating an Image

Scenarios

This section describes how to create a common user image.

Prerequisites

You have logged in to the cascading FusionSphere OpenStack management console (Region Type I scenario) or FusionSphere OpenStack management console (Region Type II scenario).

Procedure
  1. On the FusionSphere OpenStack management console, choose Resources > Computing > Compute Instances.
  2. Locate the row that contains the VM that has been stopped in Configuring a VM, and choose More > Make image.

    Click OK to go to the task center to view the progress. The image creation time depends on the size of the image file, which takes about 15 minutes. When the status of the image creation task changes to Succeeded, the image creation is complete.
    NOTE:
    • If the VM is in the Running state, choose More > Stop and perform this operation after the VM is stopped.
    • Do not perform other operations on the selected VM and its associated resources during image creation.

  3. On the FusionSphere OpenStack management console, choose Resources > Computing > Images.
  4. Locate the row that contains the newly generated image, click Modify.
  5. Modify the image information and click Save.

    • Name: The value can be customized. The recommended value is FusionAccess_WindowsXXX_Template.
    • Cloud-Init: Select it.
    • Retain the default values for other parameters.

  6. 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.
  7. In order to save resource space, if resources such as FusionAccess_WindowsXXX_VM are not needed after the image is created, delete them on the FusionSphere OpenStack management console.
Translation
Download
Updated: 2019-07-01

Document ID: EDOC1100021785

Views: 49586

Downloads: 112

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