In the blog previous post, we covered the steps to prepare a main picture XenApp server for supply. We installed the software needed to communicate with PVS, made a PXE boot and prepared a virgin vDisk to store the image of the server. We are now ready to continue and capture XenApp Master Image in a PVS vDisk.
From the launch of XenApp Master Image XenConvert server. XenConvert options we use will " This machine " and " Provisioning Services vDisk ."
Be sure to take the following steps, the next step : ..
- Remove the disk write cache from the list of players Source
- Click the Autofit button to automatically adjust the free space of vDisk
After editing, the screen should look like this: (numerical values will be different)
On the next screen, click the Optimize button for Provisioning services . Make sure that all options are selected
Click the Convert button to start conversion button. You may be prompted to format the disk, you should do. Once the conversion process is finished, stop the XenApp server image master, and return to the PVS service console. The PVS console, change the mode from the vDisk access Private to Standard . Also change the type of cover Cache on the hard drive of the unit
We are now ready to begin deploying new XenApp servers from the vDisk created. From the service console PVS launch the setup wizard Streamed VM . Start the wizard by selecting the hypervisor you use, and enter the credentials used to access the hypervisor
Next select the VM template created earlier from the XenApp backup. Specify the PVS collection where XenApp VMs are created, and select XenApp vDisk to assign.
Next, specify the number of virtual machines to create (I recommend one or two for initial testing), how many vCPUs to allocate, and the amount of memory to allocate
Next specify the OU where the accounts will be created in Active Directory, and to define a naming scheme account. After reviewing the summary of settings, tap Finish to begin the process of building virtual machines. If everything is successful, you should now see new XenApp VMs in your hypervisor.
Power on the new XenApp virtual machines. If the VM model used to create the machine was configured with a static IP address, you must assign a new IP address at this point to avoid IP conflicts.
Log in to the new XenApp server and launch the Citrix Application Centre. Run Discovery and specify a XenApp server controller in the server farm to manage.
Expand the Farm node and select the Servers folder. New provisioned XenApp servers should be listed
If you have published applications Groups worker, then you want to add new servers to workers groups so they can start serving applications. Other measures recommended to perform are:
- Provide redirection to write caching works properly for the Pagefile and event logs
- Configure the antivirus software as described in CTX127030 and CTX124185 .. antivirus signature files must be placed on the write cache drive.
- Hide write cache drive using a GPO.
- From the service console PVS follow the process to configure the vDisk using Microsoft KMS or MAK Volume Licensing. To configure KMS see CTX128276, follow scenario 2 procedures. To configure MAK see Configuring Microsoft MAK Volume Licensing in eDocs.
That's about all. I hope you found this informative blog
Ed Duncan -. Senior Consultant
Worldwide Consulting
Desktop Team & Applications
Manual Virtual Desktop
Accelerator Project
Follow @CTXConsulting
0 Komentar