Provisioning Services 7.8 Getting Started tutorial ten automatic updating of virtual disks by class

Continuing provisioning Services 7.8 Introductory Series nine manual update of virtual disks

The Update method for the automatic updating of virtual disks described in this article, as in the manual update of virtual disks described earlier, also requires the creation of updated virtual disks by replicating copies of virtual disks.

This article focuses on how the update disk is generated and how it is applied to the device.

In the actual production environment, some users of the PVS application environment can be large scale, there are many sites, each site has a lot of device collections. At the same time, it is difficult to have all the computers shut down at one time, so it is very difficult for the application to update the disk generation.

Furthermore, the administrator in the actual update, may be such a need for some devices need to be updated, others do not need to update, even if they originally used the same virtual disk (the operating system is the same).

For the above requirements, through manual update is very complicated.

Provisioning Services 7.8 Introductory Series Tutorial eight manual update virtual disk continue Introduction

There are now win2008,win2008v1 two virtual disks in the system store. WIN2008V1 is the virtual disk after the update is installed. (production process slightly)

Suppose there are thousands of devices under the Device collection, to automatically upgrade some of these devices to WIN2008V1, the others do not upgrade, how to do?

PVs can be automatically updated by "class" matching in this way. class, which allows you to match a new vdisk image to a target device by matching the new virtual disk with the target device when using an automatic disk image update. If a class is set, only devices with the same class properties are automatically updated.

That is, the class that satisfies the device virtual disk and the class of the new virtual disk are upgraded only by the device. At the same time, this approach also provides an advantage, that is, the device does not need to shut down. If the device meets the update criteria, the device will automatically be upgraded after the next reboot, even if it is powered on.

In the operating environment of 5 devices, the administrator only wants to CLT02AD,CLT04AD,CLT06AD, these three devices are updated. The following procedures are described:

1. Set the target device "class" that needs to be updated

because the actual production environment requires more than one device to update, the user can manually set up a class for a device and then complete it by copying or pasting device properties.

Or, when planning, plan a device of the same property to a Device collection, set the same class.

650) this.width=650; "title=" DC037 "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" DC037 "src=" http:// S3.51cto.com/wyfs02/m02/7f/e3/wkiom1cwvrfdg8pwaahder9vp5m399.jpg "width=" 842 "height=" 539 "/>

2. Enable automatic updating of virtual disks

start Win2008 Automatic Updates for this virtual disk

Enter the class, type.

     650) this.width=650; "title=" DC040 "style=" Border-right-width:0px;background-image: none;border-bottom-width:0px;padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "Border=" 0 "alt=" DC040 "src=" http://s3.51cto.com/wyfs02/M02/7F/E0/wKioL1cwv6LSL03gAAFgWvVWqVE171.jpg "width=" 1004 "height=" 480 "/>

• Enable Automatic Updates for this virtual disk

• Enable the automatic disk update process for the virtual disk file. Select one of the following update procedures:

  Updates are applied immediately when a virtual disk update is detected by the server: Apply the update immediately when an update is detected.

  Schedule the next vdisk update: Select Update disks on a schedule, and then select the date to run the update process. The update process will attempt to find a match for the selected Vdisk file on an existing target device, and then test to verify that it is automatically updated.

• Class

• Enter the class associated with the virtual disk file. This field is used in conjunction with automatic disk update and managed disk functionality to match the new Vdisk file with the appropriate target device. You can enter a maximum of 40 characters.

• Type

• Enter the type associated with the virtual disk file. This field is used in the Automatic disk Update feature to match the new Vdisk file to the old file. You can enter a maximum of 40 characters.

• Major version number, minor version number, build number

• If the version of the new vdisk is higher than the version of the old image, the virtual disk image is replaced to match the class and type image. The priority is from highest to lowest: Major version, minor version, build number.

  Note: During the update process, if multiple virtual disks have the same version number because the version number is not incremented, Provisioning Services uses the first updated virtual disk in the list.

• Serial number

• The globally unique identifier (GUID) that was initially set to random. The user can set the serial number as needed. The serial number is used to ensure that the delta files are applied to the correct vdisk image file.

Enable automatic update of virtual disk WIN2008V1 after update

Enter the same class, type value as the Win2008 vdisk, and modify the version number to ensure that the version number is larger than the virtual disk Win2008

650) this.width=650; "title=" DC041 "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" DC041 "src=" http:// S3.51cto.com/wyfs02/m00/7f/e0/wkiol1cwv6jjdyctaadv6bz0ium010.jpg "width=" 679 "height=" 425 "/>

3. Check for Automatic Updates

Right-click the virtual Disk pool and select check for Automatic Updates.

650) this.width=650; "title=" DC042 "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" DC042 "src=" http:// S3.51cto.com/wyfs02/m00/7f/e0/wkiol1cwv66tgxvhaadl-emnbuq164.jpg "width=" 656 "height=" 342 "/>

4. View Operation results

Restart the device, you can view the effect of the update, that is, the system installed thunder this application

650) this.width=650; "title=" DC043 "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" DC043 "src=" http:// S3.51cto.com/wyfs02/m01/7f/e0/wkiol1cwv7vxxwaxaaelcz6aamk026.jpg "width=" 986 "height=" 422 "/>

With the introduction above, the user can simply understand the automatic update process in this way:

Whether you apply an update immediately, or if you plan to apply an update, the system looks for a virtual disk in the store that matches the underlying disk class and type. If there is, the system compares the version number of both. If the version number is higher than the underlying disk, the system will use the found disk as the update disk. The system then looks for the same device in the device collection as the virtual disk class and updates it. (Modify disk allocation properties)

This article is from the "Start from the Heart" blog, please be sure to keep this source http://ycrsjxy.blog.51cto.com/618627/1771646

Provisioning Services 7.8 Getting Started tutorial ten automatic updating of virtual disks by class