Citrix PVS Logon Process - Easily Understandable!

[Music] hello guys hope you are having a fabulous day and welcome back to dran tricks and in this video we are gonna talk about citrix previous food process let's get started so the complete citrix previous logon process and the streaming contains 5 stages first one is ip acquisition and getting and downloading the bootstrap file and previous logon process single read mode and finally bna stack and multiple i o mode so the first thing the ip acquisition so the first thing is the target device ip acquisition from thcp so initially when the target device boots up the first thing it will do is to acquire an ip address from dhcp using the door process which is discover offer request and acknowledgement so the first thing the target device broadcasts the tcp discover packets the dhcp server will send a dhcp offer packet to the target device with the the following information such as ip address subnet mask default gateway dns server name and lease time and the target device will send a message to the dhcp server requesting the offered ip address along with the other information mentioned below and then the target device will send a broadcast message to other dcp servers telling them that the offer from the another dhcp server was accepted and as an acknowledgement ticket cpu server will send a dhcp act to the target device so that's where the ip acquisition from dhcp gets over and when it comes to the second stage uh i have put it in the two parts one is getting the bootstrap file and the second stage will be downloading the bootstrap file so before we go into that further let's talk about what is bootstrap file in the first place so the target device needs certain information to start the communication with the pbs server in order to stream the vdisk and that information is provided by the bootstrap file and the bootstrap file name is ardbp32.pin which will be downloaded using the tftp server hope you guys understand what bootstrap file is gonna do and why it is important and here comes the network booting in pbs so there are different types of network booting and let's see how getting that bootstrap file is diverse from each one of these methods so the first one network booting with the dhcp options so just like the door process the target device broadcasts the dhcp discover packets but in the second stage where the dk cpu server will send the dhcp offer packet to the target device with the usual information but along with those usual information the tftp server name and the bootstrap file name also be provided to the target device so as you can see the dstp server name will be mentioned in the dhcp scope option 66 and the bootstrap file name which is airbp32.bin will be mentioned in the dhcp scope option 67. so the third thing as usual the target device will send a message to the dhcp server requesting the offered ip address along with those information and then target device will send a notification to all the other dhcp servers that telling them it already got the ip address so target device gets the dhcp act back from the dhcp server so that's where it gets over and the next one is pixy method of getting the bootstrap file so in this method target device sends tkcp discover packets along with the pc broadcast by adding the dhcp scope option which is 60 and that is for a pixy client identifier and in the second stage digget cpu server will send a dhcp offer packet to the target device with the usual informations just like we talked before and in the third stage pixi server replies with the tftp server address and the bootstrap file name and the fourth the target device sends the request to the tftp server for the bootstrap file and in return the tftp server replies with the bootstrap file name and the next will be with boot device management and that too with staticap so in this method a custom citrix boot iso is configured with the static ip address and when the target device needs to download the bootstrap file it will just directly get the ip information from the iso itself and the next stage obviously it will proceed with the bootstrap file downloading stage in this method we also have advantage at the same time this advantage too the advantage is the booting time will be decreased because unlike the traditional booting method like you know using dhcp or pxe or tftp servers in this method none of them are going to be you know used and it will just directly get all the information from the iso so that results in lesser booting time and the downside is we need to create a lot of custom isos for each target devices though the next method with boot device management with the dynamic ip so in this method pdm is configured for the target device to follow the door process to accurate the ip address from the dhcp and once all the communication is done then it will proceed with the bootstrap file downloading stage so we are done with getting the bootstrap file and now let's move on to downloading the bootstrap file so downloading the bootstrap file using dhcp so the target device downloads the bootstrap file from the tftp server which is mentioned in the dhcp option 66 and the file name air dbp 32 bin mentioned in the 67 and the next one is downloading the booster file using pdm so unlike pc or dhcp method when bdm is used a tsp bdm.bin file will be downloaded instead of ardbp32 so prior to pbs version 7.x bdm used to have two stage of put process the one is you know the previous server location will be hard coded into the bootstrap file generated by the bdm and the rest of the required boot information such as the low-level previous device drivers will be downloaded from the pbs server using the dftp that uses the udp port 6969 and since the starting of seven dot tx with the help of zendesktop setup wizard a bdm hard disk partition can be assigned to a vm during the initial deployment stage so this wouldn't use a two-stage boot process because it already has all the information including the low level pvs drivers as well so that means everything and i'm sure guys you all know how respected i love him anyway out of trouble let's move on so the next stage is previous logon process so first one the target device contacts the pvs server mentioned in the bootstrap file using the default udp port which is 69.10 or 6910 you call it any hub you want and the pva server responds with the ip address and the port number to continue the logon process and next one is login start and here with the mac address the target device identifies itself and will specify the type of logon being requested and the next will be the pbs server moves the target device from login thread to io thread and pv server replies with all the disk information client and policy information needed and sent to the target device and the target device requires the ip address and port number used for the single read mode and also the target device requests the pva server to start the i o thread and request information on which vdisk to use so the login complete stage is here and the previous server grants the access for io operation to the target device and the additional configuration is also sent specifying the boot device and the target device as request which v disk will be streamed and the previous server replies with the vrx vdisk information including write cache location if the target device is in standard mode single read mode so after the target device has logged into pbs and directed to a pbs server for streaming the bootstrap file will then intercept any request so here the target device and the previous server will continue to communicate exchanging vdisk data until the windows operating system starts loading the drivers and bna stack is successfully loaded and bna stack and multiple i o is the final stage of the pbs boot process so during the final phase the pna stack driver is loaded and multiple i o begins so in bna stack the target device initiates the handshake with the pvs server stating the bni stack driver is up and vna stack is loaded into memory and takes over for the bootstrap managing multiple io communication so at this point uh the following information is exchanged such as vdisk name image mode ad password managing management option and write cache type and size client name and licensing so during the multiple io stage the target device's operation and rewrite requests occur as follows so in the typical read request a single read request packet will be sent from the target device to pbs server and in response multiple re-reply packets will be sent by the pva server to the target device and in the typical write requests the multiple write request packets will be sent to pva server by the target device and in response the pva server will give a single write reply confirmation packet and that's all for today guys hope you have liked the video and hope you have understand all these tips that we've gone through so far and if you have any queries or comments just let me know in the comment section below and if you really like the video do like it and if you really want to watch some more citrix related videos you can subscribe for my channel and have a good day be safe bye

Channel: DranTrix

Views: 1,570

Keywords: Citrix, Citrix Lab, Citrix Lab Setup, Step by step, XenApp, XenDesktop, citrix home lab, citrix logon process, citrix tutorial for beginners, citrix tutorials, Virtual Delivery Agent installation, Citrix PVS Logon process, Citrix PVS boot process, Citrix Provisioning Services, Citrix Provisioning Services boot process, Citrix Interview questions, PVS, Boot method, Logon process, Boot Device Management, BDM, Citrix PVS tutorial, Citrix PVS videos, PVS boot process

Id: XE2_7nnTBac

Length: 12min 8sec (728 seconds)

Published: Sun Jun 20 2021