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 Windows Infrastructure VM Image

Creating a Windows Infrastructure VM Image

Creating a Windows 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).

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.
    Method:
    • Region Type I scenario
      1. Log in to the cascaded FusionSphere OpenStack web client, choose Configuration > OpenStack > Nova, and set VM Watchdog to OFF.
      2. Log in to the cascaded FusionSphere OpenStack web client, choose Configuration > VM Diversification and select the Nova area of the corresponding host group. Ensure that VM Watchdog is set to OFF.
    • Region Type II scenario
      1. Log in to the FusionSphere OpenStack web client, choose Configuration > OpenStack > Nova, and set VM Watchdog to OFF.
      2. Log in to the FusionSphere OpenStack web client, choose Configuration > VM Diversification and select the Nova area of the corresponding host group. Ensure that VM Watchdog is set to OFF.
      NOTE:

      If there are multiple cascaded environments, perform this operation in all of them.

  • You have obtained the ISO files of Windows Server 2012 R2.
Procedure

Registering an image

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

    Table 4-6 Image parameters

    Parameter

    Description

    Provided As Service

    Supported

    Type

    KVM

    Name

    FusionAccess_Windows2012_Image

    Applicable OS

    Windows

    OS Version

    Windows Server 2012 R2 Standard 64-bit

    Min Disk (GB)

    60

    Min Memory (MB)

    4096

    Disk Device Type

    ide

    Image Server Type

    Glance

    Upload Mode

    HTTPS

    Image File

    ISO files of Windows Server 2012 R2

  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 availability zone (AZ) of the interconnected back-end storage, 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.
  5. Select the DMZ_Service network, as shown in Figure 4-4.

    Figure 4-4 Selecting a network

  6. Click Next.
  1. In the window that is displayed, set the VM name to FusionAccess_Windows2012_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.

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

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

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

Configuring a Windows VM

Scenarios

This section describes how to create and configure a Windows VM template.

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

    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.

Procedure

Installing the OS

  1. Log in to the VM by using VNC.
  2. In the VNC window, install the Windows OS as prompted.

    NOTE:
    • During the installation, select Windows Server 2012 R2 Standard (Server with a GUI), as shown in Figure 4-5.
    • Select Custom: Install Windows only (advanced).
    Figure 4-5 OS

Installing UVP VMTools

  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 to go to the vmtools folder.
  6. Locate and double-click the vmtools-WIN2012R2-x64 installation package.
  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, right-click and choose Run. In the Run edit box, 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, as shown in Figure 4-6.

    Figure 4-6 Enabling remote desktop connection

  3. In the Remote Desktop Connection dialog box that is displayed, click OK.
  4. Click OK.

    Remote desktop connection is enabled.

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 the VM and click OK.
  4. Copy the files and folders in Table 4-7 to the C:\ directory of the VM.

Changing the group policy

NOTE:
  • If you change the group policy, no confirmation dialog box is displayed after you disable the Windows VM created using the image.
  • If you do not change the group policy, you can perform this task on a Windows VM that is created using the image.
  1. On the VM, right-click in the lower left corner, enter gpedit.msc in the Run text box, and press Enter.

    The Local Group Policy Editor window is displayed.

  2. In the navigation tree of the Local Group Policy Editor window, choose Computer Configuration > Administrative Templates > System.
  3. Disable Activate Shutdown Event Tracker System State Data feature and Display Shutdown Event Tracker, as shown in Figure 4-7.

    Figure 4-7 Changing the group policy

Configuring the DST

NOTE:

Perform this step only for scenarios 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 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.

Disabling the firewall

  1. On the VM, right-click in the lower left corner, enter gpedit.msc, and press Enter.

The Local Group Policy Editor window is displayed.

  1. In the navigation tree on the left of the Local Group Policy Editor window, choose Computer Configuration > Administrative Templates > Network > Network Connections > Windows Firewall. Click Domain Profile and disable Windows Firewall: Protect all network connections. Click Standard Profile and disable Windows Firewall: Protect all network connections, as shown in Figure 4-8.

    Figure 4-8 Disabling the firewall

  2. Close the Local Group Policy Editor window.
  3. Enter services.msc in the Windows PowerShell text box, and press Enter.
  4. Disable Application Layer Gateway Service, as shown in Figure 4-9.

    Figure 4-9 Application Layer Gateway Service Properties (Local Computer)

  5. Disable the Windows Firewall service. For details, see Step 27.
  6. Close the Services window.

Installing .NET framework 3.5.1

  1. On the taskbar, click .

    The Server Manager window is displayed, as shown in Figure 4-10.

    Figure 4-10 Server Manager

  2. In the middle of the page, click Add Roles and Features.

    The Add Roles and Features Wizard dialog box is displayed.

  3. Click Next for four times.
  4. In the displayed dialog box, select .NET Framework 3.5 Features and click Next, as shown in Figure 4-11.

    Figure 4-11 Installing .NET framework 3.5

  5. Click Specify an alternate source path, as shown in Figure 4-12.

    Figure 4-12 Specifying an alternate source path

  6. In the displayed dialog box, set Path to Windows Server 2012 R2 ISO drive:\Sources\SxS.

    For example, if the Windows Server 2012 R2 ISO file is saved in drive D, set Path to D:\Sources\SxS.

  7. Click OK.
  8. Click Install.

    The installation progress bar is displayed. When Installation succeeded is displayed, the installation is successful, as shown in Figure 4-13.

    Figure 4-13 Installation progress

  9. Click Close.

    The Add Roles and Features Wizard dialog box is closed.

  10. Close the Server Manager window.

Installing the Cloudbase-Init software

  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-14.

    Figure 4-14 Configuration options

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

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

Installing the monitoring agent

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

    The Figure 4-16 window is displayed.

    Figure 4-16 FusionAccess Windows Installer

  3. Click Scale-out Deployment.

    The Deployment page is displayed.

  4. Select Monitoring agent and click Install.

    Install the monitoring agent as prompted.

  5. Close the FusionAccess Windows Installer window.

Encapsulating the VM template

  1. Delete all the files or folders copied in Step 18.
  1. Go to C:\Windows\System32\Sysprep and double-click sysprep.exe.
  2. Set the following parameters as prompted, as shown in Figure 4-17.

    Parameters for encapsulating VM templates:

    • System Cleanup Action: Select Enter System Out-of-Box Experience (OOBE).
    • Select Generalize.
    • Shutdown Options: Select Shutdown.
    Figure 4-17 Parameters for encapsulating VM templates

  3. Click OK.

    The system displays Sysprep is working... After the template encapsulation is complete, the VM automatically shuts down.

Creating a Windows VM Image

Scenarios

This section describes how to create a Windows infrastructure VM 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 Windows 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_Windows2012_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_Windows2012_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: 46365

Downloads: 100

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