Citrix Provisioning Server for OS to remote machines

I followed this link which goes to 3 parts:

What I got from the 3 parts I have read so far, is how to configure PVS,vdisk,create Target Device on PVS an type the MAC address of the Target device  (the Master image),install Target device software on the Master image, download/and run the Xconverter from Master image in order to format the vDisk located on the PVS.
But I have not seen the scenario where the disk/diskless computers that will be rebooted and will grab the OS they are supposed to grab from PVS and become fully functional computers.

I am trying to understand how PVS is similar in deploying OS to remote physical or virtual Machines, a process similar to Windows Deployment Services (ex RIS) that deploys an OS to a computer as a clean install or overwriting the existing OS .

Any help on that?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Have you set up your DHCP server with options 66 and 67 so that the target devices know how to point to the TFTP service on the PVS server?

Once your devices PXE boot, they'll grab their IP address from DHCP and then boot to the PVS server and should grab the VHD.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
You also need to make sure that your VHD is not in Private mode and that your Devices in PVS are set to boot to the VHD, and NOT local disk.
Ayman BakrSenior ConsultantCommented:
In addition to what all the experts have said you need to point your other target devices to that image you have created (called assigning the image to the target devices)
To summarize:
1. Configure DHCP with options 66 and 67 to point to TFTP server which is your PVS
2. Change your image to standard mode
3. Configure your other target devices to:
    A. Boot from VHD
    B. Have the same class as the image that it will boot from
    C. Point to the correct image (if all your intended targets/VMs are in the same device collection then dragging your image and dropping it on the device collection will automatically assign the image to all these devices).
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

jskfanAuthor Commented:
The terminology is a bit confusing:
Target master image= The PC which we want to use as the Golden image
Target Device= is the logical name of the PC that will be created on the PVS

When you create a master image. you manually create the target device and type manually its MAC address on the PVS. This way when you run the Target Device software and Xconvert from the Target master image, it will point to the Target Device which is associated to a vDisk and will format and copy the image of the Target master image to the vDisk

Now, for the other PCs [Not the Master Image], when they boot through PXE and connect to a PVS , how do they know which vDisk to point to ? seeing that the their MAC address is not prestaged [not manually entered on the PVS]
Ayman BakrSenior ConsultantCommented:
The other PCs (not the master image) will be created the same way as you did with the target device used to create the golden image. However the difference is that on the general tab the 'Boot From' field for the device to create the master image is set to boot from Hard Disk until you format and create your image then use XenConvert. While the 'Boot From' field on the other devices will be set to vDisk. Then on the vDisks tab you will select the vDisk you have created. Therefore, to summarize after creating the vDisk ( golden image ) using the target device and XenConvert you do the following:
1. Change the vDisk to Standard mode
2. Assuming you did not create your devices yet then you do so and manually set their MAC addresses as you did for the original master target device (you get the MACs from the VMs created previously) and join them to the Specific OU in Active Directory.
3. Now here is where the difference happen. On the General tab of the properties of each target device you set the 'Boot From' to vDisk.
4. And now on the vDisks tab you click the Add button and select your vDisk. Alternatively you can do it in bulk by dragging the vDisk from the vDisks list and dropping it unto YHWH the device collection where your target devices reside.

This way your VMs when booting from PXE and are able to locate the TFTP server through DHCP they contact the PVS where the latter will understand from the MAC address and the config you had which vDIsk to stream.
jskfanAuthor Commented:
So, we still have to manually type every computer MAC Address and maybe install the Target Device software and run  Xconverter  ??
Ayman BakrSenior ConsultantCommented:
You still need to manually type every computer MAC address - YES.
However, you don't need to install the Target device software and run Xconverter! ANYMORE!

You see what you did at the beginning is the following:
You used the target device (Master target device) with the Target device software to create the vDisk (OS, applications, settings). Then you used Xconverter to have it 'Copied' to the provisioning.

NOW, you are sealing the vDisk by changing it to Standard Mode and you are doing the opposite:
That is, now you are using the 'sealed' vDisk to be streamed to the 'dumb' target devices. In other words, every target device now you have will have a copy of the disk in Read Only mode.
jskfanAuthor Commented:
<<<You still need to manually type every computer MAC address - YES.>>>
There is an "Auti-add" option in PVS config.
I thought this option will avoid us from manually typing the MAC  address of each computer
Ayman BakrSenior ConsultantCommented:
I had a wrong assumption that you are on an older version of PVS where the feature was not available.

But, yes you are right; if you have the 'Enable Auto-Add' configured on PVS, then you will not need to create MAC addresses manually. Once the VMs boot they will be populated automatically into PVS - if say you have previously created the VMs manually on the XenServers. Alternatively you can use the Auto-Add wizard to add your VMs (target devices) in PVS.
jskfanAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.