Provisioning Services 7.8 Introductory Tutorial One deployment learning environment introduction

When I first approached provisioning services, I was reminded of the past. I do not know is Yichi years, the author has not been clear. At that time, personal computers were still expensive. In order to save costs, a lot of LAN to take diskless workstations. I remember the use of the Novell 3.12 NetWare, then used DOS. At the time, the deployment process for diskless workstations was complex. Provisioning Services deployment is now much easier than before.

Most companies are now struggling to cope with the growing number of computers in the environment and the complexity of managing their work. Each computer must be managed as a separate entity, whether it is a desktop PC, a data center server, or a self-service device. To gain the benefits of distributed processing, you must invest more in distributed management. Setting up, updating, supporting, and eventually deactivating each computer can be time-consuming and financial. In the face of high operating costs, the cost of acquiring computers is often insignificant.

Provisioning Services employs a radically different approach to traditional imaging solutions, fundamentally altering the relationship between hardware and software that relies on hardware. Provisioning Services pushes a single shared disk image (virtual disk) through streaming technology, rather than copying the image to each computer, enabling the organization to reduce the number of disk images managed, even if the number of computers continues to increase. This approach combines the efficiency of centralized management with the benefits of distributed processing.

In addition, because computers dynamically and in real-time push disk data from a single shared image through streaming technology, the computer image is guaranteed to be consistent, while a large computer pool can completely change its configuration, applications, and even operating systems when the machine reboots.

With provisioning Services, any virtual disk can be configured as a standard image mode. virtual disks in standard image mode allow multiple computers to boot through the virtual disk at the same time, which greatly reduces the number of images that must be maintained and the storage space required. The virtual disk is in read-only format and the target device cannot change its image.

At present, the latest version of Provisioning Services is 7.8, in order to be familiar with Provisioning services, I deploy the installation in the virtualized environment. The following is the author's deployment environment:

Physical machine: Lenovo Notebook, 4-core I5, Memory 8g,windows 10 Professional Edition.

Virtualization platform: Windows 10 comes with Hyper-V. When I started to learn, I tried to use the VMware Workstation V12, but after the image capture, starting the client, the following error always occurs:

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/7F/A0/wKiom1cltT2SwjTEAABMEbkHBy0932.png "title=" Win7pvs01-2016-04-19-15-27-46.png "alt=" wkiom1cltt2swjteaabmebkhby0932.png "/> Through analysis, I think there is a problem with the boot file (BCD) of the captured image disk. (This author's point of view, hope that the vast number of it enthusiasts can analyze its reasons, find solutions). Therefore, the author has abandoned the use of VMware Workstation.

requirements for Provisioning Services v7.8:

1, the Active Directory domain environment is required. The author uses Windows Server R2 to install AD.

2. Requires a DHCP server. Implemented on a domain controller DC.

3, need database server. Use SQL Server R2 to install on the DC. In a production environment, it is recommended that the database be deployed on a separate computer.

4. Citrix License Server. Install the implementation on the DC.

5. At the same time, in order to achieve high availability of storage, the author installs the iSCSI target server on the DC and installs the Provisioning Services management Console.

6. Provisioning Services Server needs to be installed . Implemented through two domain-joined Windows Server R2 virtual machines.

In order to be familiar with the high availability of Provisioning services, the author uses two servers. In a learning deployment, if you don't need to know about its high availability, we can install Provisioning services on a DC to conserve resources.

7, target device installation. Two virtual machines, one installation of Windows 2008R2, one installation of Windows Server R2, and DHCP enabled. Familiarize yourself with the relevant features by capturing different operating system images.

Given the author's limited computer memory, dynamic memory is enabled for all virtual machines, where the DC is assigned 2G and the other computers are allocated 1G of memory, just enough.

Precautions :

1, the same operating system of the computer as far as possible to use a differencing disk, dynamic disk to deploy the associated virtual machine. The goal is to conserve hard disk space. However, after the differencing disk starts the computer, the SID of the computer is the same, so you need to re-Sysprep the program. Otherwise, there will be a failure to join the domain.

In the case of dynamic disks, although disk space can be saved, but the speed of deployment is affected, it is recommended to use a fixed-size disk in a real production environment.

2, temporarily shut down the firewall. A good multi-port is required for the entire environment and it is recommended to turn off the firewall to ensure smooth deployment. Not recommended in a production environment.

3. To prepare the virtual machine for image capture and testing, before generating the virtual machine, installing the system or using it, you need to remove the original network adapter and add the older network adapter because only the legacy network adapter in Hyper-V supports PXE boot.

4. Establish a virtual private network to connect all virtual machines to the private network. This goal prevents the impact of other DHCP servers.

5. Create a dedicated service account for the SQL Sever Database engine service, stream service, and SOAP service, and do not use the default network Service account. If you use the default network Service account, there may be some errors during deployment, which can be unsuccessful. Because it is a learning environment, I use the Administrator account to act as a (production environment is not recommended, so there is a security risk)

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

Provisioning Services 7.8 Introductory Tutorial One deployment learning environment introduction