Downloaded 1,527 times
Uploaded byDavid McGeough
Troubleshooting Provisioning Services Target Boot Processes
The document outlines the key findings of a recent study on climate change. It highlights the urgency of addressing rising global temperatures and their impact on weather patterns. Recommendations for policy changes and community actions are also discussed.
More Related Content
![[Unity Forum 2019] Mobile Graphics Optimization Guides](https://cdn.slidesharecdn.com/ss_thumbnails/20191108taipeiunityforum-191204024024-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Troubleshooting Provisioning Services Target Boot Processes
More from David McGeough
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
Troubleshooting Provisioning Services Target Boot Processes
- 1. Citrix Support Secrets WebinarSeries Troubleshooting Provisioning Services Target Boot Processes Konstantin Cvetanov– PVS Escalation Engineer December 5th 2013
- 2. PVS Boot ProcessDemystified! PVS is not magic PVS does not use alien technology PVS is cool technology 2 © 2013 Citrix
- 3. Agenda • PXE Specification •PVS Boot Process ᵒIP Acquisition ᵒBootstrap Download ᵒPVS Logon Process ᵒSingle read Mode ᵒBNISTACK / MIO Read Mode • Resources • Questions 3 © 2013 Citrix
- 4.
- 5. PXE (Pre-boot ExecutionEnvironment) DHCP Server 1 2 3 TFTP Server 4 5 PXE Client 6 5 © 2013 Citrix NFS Server
- 6. Normal PC BootProcess (abridged) Target Device PC starts up BIOS POST Identify boot device Load operating system 6 © 2013 Citrix
- 7. Normal PC Bootvs. PXE Boot Target Device PC starts up PVS Server BIOS POST Identify boot device PXE boot: Load Get IP address operating system Get NBP name / location Local HDD Get NBP vDisk NBP initializes Connect to network resource Load operating system 7 © 2013 Citrix
- 8.
- 9. PVS Boot Process •The following five steps make up the PVS Boot Process: ᵒIP Acquisition ᵒBootstrap Download ᵒPVS Logon Process ᵒSingle Read Mode ᵒBNISTACK / MIO Read Mode 9 © 2013 Citrix
- 10.
- 11. DHCP – UsingScope Options DHCP Server PVS Server DHCP ACK DHCPDISCOVER DHCP REQUEST DHCPOFFER TFTP Server Name Bootfile Name DHCP Client 11 © 2013 Citrix
- 12. DHCP – withPXE Service DHCP Server PVS Server DHCP ACK DHCPDISCOVER SERVICE DHCP REQUEST PVS DHCPOFFERPXE TFTP Server Name Bootfile Name DHCP Client 12 © 2013 Citrix
- 13. Citrix Boot ISOwith Statically Assigned IPs 13 © 2013 Citrix
- 14. IP Acquisition -Troubleshooting Spanning Tree Protocol 14 © 2013 Citrix
- 15.
- 16. Capture Guidelines • Wheneverpossible capture both a server-side and target side trace • Try to capture a good vs. bad trace • Get all of the IP/MAC information pertaining to a trace 16 © 2013 Citrix
- 17. Target Side capturemethods • XenServer ᵒTCP Dump ᵒhttp://support.citrix.com/article/CTX120869 • VMware ᵒSet V-Switch into promiscuous mode ᵒhttp://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1004 099 • Hyper-V ᵒHost OS tracing ᵒOnly works if the traffic leaves the Hyper-V Machine 17 © 2013 Citrix
- 18. Target Side capturemethods – cont. • Physical ᵒPort Mirroring ᵒUsing a Tap 18 © 2013 Citrix
- 19.
- 20. Bootstrap Download ARDBP32.BIN –UDP Port 69 Citrix PVS TFTP Service TSBBDM.BIN – UDP Port 6969 Citrix PVS Two-Stage Boot Service TSBOROM.BIN – UDP Port 6969 20 © 2013 Citrix Citrix PVS Two-Stage Boot Service
- 21. Configuring the BootstrapFile 21 © 2013 Citrix
- 22. Bootstrap Download -Troubleshooting 22 © 2013 Citrix
- 23. Packet Capture PXETFTP download Provisioning Server 10.1.1.1 TFTP DHCP PXE Target 10.1.1.100 23 © 2013 Citrix
- 24. Common Issues DuringDHCP TFTP Download • Target does not receive IP address • Target gets IP but times out to TFTP • PXE Errors No bootstrap found Provisioning Server 10.1.1.1 TFTP DHCP PXE Target 10.1.1.100 24 © 2013 Citrix
- 25.
- 26. PVS Protocol • UDPbased • Layer 7 additions – BNISTACK.SYS ᵒSequencing/ Fragments ᵒAcknowledgements ᵒRetry mechanism ᵒHeartbeat 26 © 2013 Citrix
- 27. PVS Login Sequence TargetDevice What Login IP:Port can I use? Use this Login IP:Port Login Server – Log me in; here’s my MAC address Use this least busy server Least busy server – what IO port should I use? Use this IO port Service my request for this disk on this device All set – begin streaming 27 © 2013 Citrix PVS Farm
- 28. Login Process Traffic ProvisioningServer 10.1.1.1 TFTP Stream Process 28 © 2013 Citrix TFTP - Login Target 10.1.1.100
- 29. PVS Login –Load Balancing 29 © 2013 Citrix
- 30. PVS Login -Troubleshooting • Incorrect bootstrap information • Stream service not started • Target device does not exist in database • UDP port 6910 is blocked 30 © 2013 Citrix
- 31.
- 32. Single Read Mode 32 ©2013 Citrix
- 33. Single Read Modestreaming Stream Process 33 © 2013 Citrix OS Booting UNDI Driver Target 10.1.1.100
- 34. Single Read Mode- troubleshooting 34 © 2013 Citrix
- 35. Slow Boot &Performance troubleshooting • Network or Storage ᵒSeparate the two ᵒMove vdisk local to PVS server • Storage related ᵒTry different LUN or different NAS device ᵒTry using locally attached LUN vs CIFS share • Network related ᵒBidirectional network trace ᵒCheck all network devices for old or faulty connections 35 © 2013 Citrix
- 36. BNISTACK / MIORead Mode
- 37. BNISTACK / MIORead Mode BNISTACK • • • • • 37 © 2013 Citrix Image Mode Active Directory Write Cache Client Name Licensing
- 38. BNISTACK / MIORead Mode 38 © 2013 Citrix
- 39. MIO Read Mode ProvisioningServer 10.1.1.1 Stream Process 39 © 2013 Citrix Target 10.1.1.100
- 40. BNISTACK / MIO- Troubleshooting Provisioning Services Antivirus Best Practices http://support.citrix.com/article/CTX124185 40 © 2013 Citrix
- 41. Retry Mechanism andHA Failover • Target requests data block from vdisk ᵒIf the server does not respond completely within 1 second timeout a retry is attempted • During retry the timeout is doubled to 2 seconds ᵒIf the server does not respond completely within 2 seconds the retry process repeats • Each retry doubles the timeout to a maximum of 10 seconds • After 10 consecutive retries for the same data an HA retry occurs ᵒTarget device refers to the bootstrap for login info 41 © 2013 Citrix
- 42. PVS Login Sequence– HA Reconnect Target Device What Login IP:Port can I use? PVS Farm Use this Login IP:Port HA reconnect begins here Login Server – Log me in; here’s my MAC address Use this least busy server Least busy server – what IO port should I use? Use this IO port Service my request for this disk on this device All set – begin streaming 42 © 2013 Citrix Non-HA reconnect begins here
- 43. PVS Boot ProcessSummary • Here is a summary of the PVS Boot Process: ᵒIP Acquisition – The Target Device acquires an IP address. ᵒBootstrap Download – The bootstrap file is downloaded. ᵒPVS Logon Process – The Target Device logs on to PVS. ᵒSingle Read Mode – Single read mode communication is established between the Target Device and the PVS Server. ᵒBNISTACK / MIO Read Mode – The BNISTACK driver on the Target Device takes over communications with the PVS Server and Multiple I/O occurs. 43 © 2013 Citrix
- 44. PVS Boot ProcessDiagram
- 45. Citrix Provisioning Services(PVS) Boot Process 1 2 IP Acquisition The PVS target device acquires an IP address using the DORA process. The following configurations are supported: 4 Bootstrap Download An IP Address is obtained using the following Discover, Offer, Request and Acknowledge (DORA) process. BNISTACK / MIO During the final phase, the BNISTACK Driver is loaded and multiple I/O (MIO) begins BNISTACK DHCP The TFTP Server Name is obtained from DHCP option 66 and the filename is obtained from DHCP option 67. 1. The Target Device broadcasts DHCP Discover packets. Simple Requests & Replies DHCP Discover Broadcast Target Device 5 After a target device has logged into PVS and has been directed to a PVS Server for streaming, the bootstrap file (ARDBP32.bin, TSBBDM.bin or TSBOROM.bin) will then intercept any requests (i.e. hard disk requests) made to Interrupt 13. The bootstrap file is downloaded from the TFTP Server to the Target Device using the TFTP Server from DHCP option 66 and filename (ARDBP32.bin) from DHCP option 67. TSBBDM.bin is downloaded if Boot Device Manager (BDM) is used and TSBOROM.bin is used if the target devices use option ROM (OROM). DHCP Single Read Mode v1.4 ARDBP32.bin 2. The DHCP Server sends a DHCP Offer packet to the DHCP Target Device with the IP address, Subnet Mask, lease time. Default Gateway and DNS Server Domain Name information Server to the Target Device. 3. The Target Device sends a unicast message to the DHCP Server requesting the offered IP address. A Transaction ID is used to track the accepted offer. The Target Device will send a broadcast message notifying other DHCP Servers that the offer from another DHCP Server was accepted. DHCP Request Target Device PVS Server Target Device DHCP Offer Packet Target Device The Target Device and the PVS Server will continue to communicate exchanging vDisk data until the Microsoft PVS Windows Operating Systems starts loading drivers and Server BNISTACK is successfully loaded. MIO Boot Device Manager (BDM) During the MIO stage, the Target Device is operation and read /write requests occur as follows: Typical Read Requests BDM uses a two-stage boot process where the PVS location is hardcoded into the bootstrap generated by BDM. The rest of the required boot information like the low level PVS device drivers is downloaded from the PVS Server using a proprietary download protocol based on TFTP that uses UDP port 6969. 4. The DHCP Server sends a DHCPACK packet to the Target Device. DHCP Acknowledgement Single Read Request Packet M ul PVS ti Server pl e R Typical Write Requests* e a M d u R l e t pl i PVS Target y p Server Single Write Reply P Confirmation Packet l Device ac e ke W ts r *MIO writes occur when the vDisk is in private mode or the write i cache is configured for server side cache. t e TSBBDM.bin Network Booting – w/DHCP Options (no PXE Service) In this configuration, the DORA process explained above is used in addition to the following: Target Device PVS Server Target Device DHCP Offer Packet Target Device The TFTP Server Name and Bootfile Name (ardbp32.bin) is provided using options 66 & 67 The Target Device initiates a handshake with the PVS Server stating the BNISTACK driver is up. BNISTACK is loaded into memory and takes over for the bootstrap PVS Server managing the MIO communication. At this point , the following information is exchanged: • vDisk name • Image Mode • Active Directory Password Management Option • Write Cache Type and Size • Client Name • Licensing DHCP Server Option ROM (OROM) On Target Devices that use option ROM, the bootstrap file name is configured on the network interface card (NIC) . Network Booting – w/PXE Service (no DHCP Options) TSBOROM.bin In this scenario, the Target Device is configured for network boot. Target Device 1. The firmware of the Target Device adds option 60 to the DHCP Discover packet being broadcast. This option is used with devices from Dell and others that use the Intel Desktop Board. Further information can be found at http://download.intel.com/products/motherb oard/DQ45CB/323251.pdf PVS Server R e q u e s t DHCP Discover Broadcast Target Device 2. DHCP Server responds with IP Address, Gateway and Subnet information. DHCP Server Reply 3. The PXE Server replies with the TFTP Server address and bootstrap file name. PXE & DHCP Servers PXE Server Reply 4. The Target Device sends a request to the TFTP Server for the bootstrap file. 3 PVS Logon Process Bootstrap File Reply When using a Citrix Boot ISO to download the bootstrap the Target Device gets the IP address information directly from the boot ISO and downloads the bootstrap manager. As configured in the Boot Device Management (BDM) configuration. Citrix Boot ISO – DHCP In this scenario, BDM is configured for the Target Device to use the DORA process to get the IP address information. Then the two stage bootstrap download will start. Get IO Port Get Login Port TFTP Server Citrix Boot ISO – Static IP 45 Load Balancing Algorithm After the Target Device gets an IP address and downloads the bootstrap file it proceeds to login to a PVS Server to start streaming the vDisk image. This steps are as follows: Bootstrap File Request 5. The TFTP Server replies with the bootstrap file name. • Target Device • The Target Device contacts the PVS Server specified in the bootstrap file using the default UDP port 6910. PVS Server The server responds with the IP address and port to Continue the login process. The Target Device requests the IP address and port used for the single read mode. PVS Server The Target Device requests the PVS Server start the I/O thread and requests information on which vDisk to use. Target Device Get IO Service Login Start • The Target Device identifies itself by its MAC address and specifies the type of login being requested. Login Complete • • Transferred to IO • The PVS Server moves the Target Device from the login thread to the I/O thread. The PVS Server replies with all disk, client and policy information needed and sent to the Target Device. P a c k e t PVS Boot Process s Summary The PVS Server grants access for the I/O operation to the Target Device. Additional configuration is sent specifying the boot device. Get vDisk Information • • The Target Device requests which vDisk will be streamed. The PVS Server replies with the vDisk information including write cache location if the Target is in standard mode. © 2013 Citrix © 2013 Citrix. Citrix Provisioning Services is either a registered trademark or a trademark of Citrix in the United States and/or other countries. All rights reserved. Other trademarks or trade names mentioned herein are the property of their respective owners. All PVS servers are capable of acting as both a login server and an I/O server. A PVS login server normally attempts to load balance devices between all servers that have access to a given vDisk when the device initially logs in. The login server only bypasses load balancing if the server override property is set for the vDisk locator. The load balancing algorithm provides simple connection count balancing. (i.e. the login server attempts to place the same number of devices on each server that has access to a given vDisk.) The following summarizes the diagram: detailed on the 1. 2. 3. 4. IP Acquisition – The Target Device acquires an IP address. Bootstrap Download – The bootstrap file is downloaded. PVS Logon Process – The Target Device logs on to PVS. Single Read Mode – Single read mode communication is established between the Target Device and the PVS Server. 5. BNISTACK / MIO – The BNISTACK driver on the Target Device takes over communications with the PVS Server and Multiple I/OCitrix Technical Support/Provisioning Services Escalation Authors: occurs. Team Please submit feedback to http://support.citrix.com/article/CTX136378
- 46. Resources • Provisioning ServicesBoot Process Diagram http://support.citrix.com/article/CTX136378 • Provisioning Services Antivirus Best Practices http://support.citrix.com/article/CTX124185 • Dynamic Host Configuration Protocol (DHCP) and Bootstrap Protocol (BOOTP) Parameters - http://www.iana.org/assignments/bootp-dhcp-parameters/bootpdhcp-parameters.xml • Preboot Execution Environment (PXE) Specification Version 2.1 – http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf • Provisioning Services eDocs – http://support.citrix.com/proddocs/topic/technologies/pvs-provisioning.html 46 © 2013 Citrix
- 47. About Citrix Services Citrix Servicesmake sure you succeed with your virtualization programs. Educate | Guide | Support | Succeed How we can help Citrix Education – The fastest, most efficient way to get your team the virtualization skills they need. Online, on-site or in class. citrix.com/training Citrix Consulting – Intensive engagements for complex, critical or just plain massive projects. citrix.com/consulting Citrix Support – Always-on support services that leverage everything we know about best-practice deployment and maintenance. citrix.com/support © 2013 Citrix
- 48. Secrets of theCitrix Support Ninjas • 40 insider troubleshooting tips • Covering XenDesktop, XenServer, XenApp and NetScaler • Citrix Support top engineers • FREE eBook • Citrix Auto Support • Now available! © 2013 Citrix
- 49. Premier Support Calculator Checkit out © 2013 Citrix
- 50. Next Webinar: January2014 Title: 10 Tips Every XenDesktop Admin Should Know Description: As a XenDesktop administrator, it’s your responsibility to make sure your XenDesktop infrastructure is running smoothly and your users are working efficiently. In this webinar our very own XenDesktop master, Michael Glover will guide you in utilizing our award winning solution for virtual desktop delivery, XenDesktop, with some really key tips and time savers to help you make the very most of your investment. Michael has been involved in XenDesktop from day one and has gathered a huge amount of knowledge which he would love to share with you. • When: Jan 30th • Registration Now! © 2013 Citrix
- 51. Work better. Livebetter.
Editor's Notes
- #2 Good Afternoon and welcome to SupportWebinar 2013.My name is Konstantin Cvetanov and I am an Escalation Engineer with the Provisioning Services Escalation Team from our offices Alpharetta, Georgia. The purpose of this presentation is to provide a step-by-step detailed overview of the Provisioning Services (PVS) Boot Process used by Citrix Provisioning Services.
- #4 In today’s session we will discuss the PXE specification and how it relates to the PVS boot process. Next we will discuss the PVS boot process in depth and go over some common troubleshooting steps and scenarios. I will provide you with a list of resources that I used in creating this presentation in the event that you want to do further research. And lastly I will open the floor to any questions you may have.
- #6 The PXE protocol operates as follows. (CLICK) The client initiates the protocol by broadcasting a DHCPDISCOVER containing an extension that identifies the request as coming from a client that implements the PXE protocol. (CLICK) A DHCP server or a proxy DHCP server implementing this extended protocol sends the client a list of appropriate Boot Servers. The client also receives the name of an executable file on the chosen Boot Server. (CLICK) The client uses TFTP to download the executable from the boot server. (CLICK)(CLICK) Finally, the client initiates execution of the downloaded image and then contacts a server on the network to load its operating system (CLICK)
- #7 Now lets talk about what happens during a normal PC Boot Process.1. The machine starts up and 2. the BIOS starts the POST process. 3. The BIOS then identifies a boot device 4. which allows the operating system to load.
- #8 Specifically the way the boot device gets identified is by the PXE (CLICK) Process. Once we have the information on where to download the Network Boot Program or NBP we contact the TFTP server and download the bootstrap which then allows us to login to PVS
- #10 The PVS boot process is broken down into 5 steps.IP AcquisitionBootstrap DownloadPVS Logon ProcessSingle Read ModeBNISTACK / MIO Read ModeThis process is very similar to the PXE boot process, and in fact in order to be able to use a target device with PVS it myst be PXE 2.1 or higher compatible
- #12 Specific to Provisioning Services a PVS PXE client will identify itself with DHCP option 60 signifying that it is a PXE clientThis is used in conjunction with the PXE service running on the PVS server The PXE service, which acts like a DHCP relay will respond to DHCP Discover packets that have option 60 in them and provide the client with the location and filename of the network boot programDHCP Options 66 & 67 can be used to specify the location of the network boot programThe PVS PXE Service acts as a DHCP relay that responds to DHCP Discover packets that have option 60 specified
- #13 Specific to Provisioning Services a PVS PXE client will identify itself with DHCP option 60 signifying that it is a PXE clientThis is used in conjunction with the PXE service running on the PVS server The PXE service, which acts like a DHCP relay will respond to DHCP Discover packets that have option 60 in them and provide the client with the location and filename of the network boot programDHCP Options 66 & 67 can be used to specify the location of the network boot programThe PVS PXE Service acts as a DHCP relay that responds to DHCP Discover packets that have option 60 specified
- #14 In the event that you would like to assign an IP address statically you can use the Citrix BDM or Boot device manager to create either a boot disk or boot iso that will allow you specify the IP address per target. You will be required to create one iso per machine in order to prevent any issues with duplicate IPs
- #15 Network tracing is the best method of troubleshooting DHCP/IP Acquisition issuesSTP (Spanning tree protocol issues)Using spanning tree protocol causes the port to stay in a blocking state for up to 30 seconds while checking for bridge loopsRapid Spanning Tree ProtocolReduced the delay from switching from a blocking to forwarding state from 30 seconds to under 6 seconds
- #21 Once the target device obtains an IP address, it goes through the phase of downloading the bootstrap file.Using the address configured in DHCP option 66, the PVS target device contacts the TFTP server (or boot server) and requests the boot file that is configured in DHCP option 67. This bootstrap file is called ARDBP32.bin. Using BDM a PVS target will download TSBBDM.bin over port 6969Dell devices using an OEM version of BDM built into the BIOS and download TSBOROM.binOnce the target device obtains an IP address it uses TFTP to download a bootstrap filePXE Boot (NIC)ARDBP32.binTFTP – UDP port 69BDM Boot (ISO)TSBBDM.binTFTP – UDP port 6969DELL OEM (BIOS)TSBOROM.binTFTP – UDP port 6969
- #22 Right-click the server that acts as the TFTP server and click Configure Bootstrap.Click Add and type the IP address of the Provisioning Server that will act as a login server.Type the port number that is configured for the Stream Service.Choose to use DHCP or BOOTP supplied netmask and gateway settings or type this information in the appropriate fields and click OK.Click Move Up or Move Down to place the Provisioning Servers in the order in which target devices should contact for login processing.Click the Options tab and select Restore network connection as the network recovery method.(Optional) Make any additional configuration changes.
- #23 Common bootstrap download issuesConfiguration issuesTFTP info not provided with DHCP DORAPacket loss
- #24 First thing we are going to take a look at is the DHCP packets [CLICK]After DHCP packets complete we see the target device ARPs for the TFTP server[CLICK]Lastly we will see the TFTP transfer Start [CLICK]
- #25 If the target does not get a IP address, this portion of the network trace can help you ID the root cause of the issue. Router in network path No Ip-helper address. [CLICK] PXE Service and DHCP options configured.Target gets IP but times out to TFTP TFTP service not on. Issue with network connectivity.
- #28 Login Port RequestPresent MAC addressLoad BalancingTransfer to I/O
- #29 Here you will see the end of the TFTP transfer [CLICK] You will know the transfer has completed correctly by verifying that the last TFTP packet sent by the server is tagged (last)Once the bootstrap downloads you will see a series of packets going through the login process. When the login process is completed the target will send a ARP request for the IP of the Streaming Server.
- #30 All PVS servers are capable of acting as both a login server and an I/O server. A PVS login server normally attempts to load balance devices between all servers that have access to a given vDisk when the device initially logs in. The login server only bypasses load balancing if the server override property is set for the vDisk locator. The load balancing algorithm provides simple connection count balancing. (i.e. the login server attempts to place the same number of devices on each server that has access to a given vDisk.)
- #31 Stream Service must be on.Target not being in the DBThis can be caused by bad bootstrap IP information.Firewall blocking the login port 6910.
- #33 The bootstrap directs any block level requests for data as to the PVS server as single read requests The single read mode procedure will continue until the Microsoft Windows Operating System starts loading drivers and BNISTACK is successfully loaded
- #34 After the login the target will continue to process traffic using the UNDI driver. (Universal Network Driver Interface and will send one to one packets. [CLICK]During this time the target will display the windows logo. Low level drivers are being loaded here. Failures at this level include:
- #35 If the server does not respond to a request within 5 seconds the target device will request the same data again. This will happen a maximum of 3 time before the target will attempt to reconnect and login to the PVS server againThis is generally the longest portion of the boot process due to the amount of data that has to be transferredResponse delays here contribute the most to long boot timesLarge Send OffloadNetwork instabilityConflicts with UNDI DriverStarting with Single Read Mode network traces need to be analyzed by Citrix
- #38 MIO (Multiple Input/Output) mode begins when BNISTACK is loaded by the operating systemBNISTACK is loaded into memory and takes over for the bootstrap, it manages the communication between the target device and the PVS serverAt this point the following information is exchanged:Image Mode Active Directory Password Management Option Write Cache Type and Size Client Name Licensing
- #39 BNISTACK uses multiple threads to communicate with the PVS serverAdmin ThreadUsed for passing additional configuration settings after initialization and for the heartbeat mechanismRead/Write ThreadsTwo Read threadsOne Write threadOnly used when write cache exists on the PVS serverMIO uses a single request -> multiple response structureSingle read request -> Multiple read repliesMultiple write request -> Single write reply
- #40 Once UNDI hands off to BNIStack (PVS Target Device’s Main Filter Driver) the target will begin to request larger amounts of data. This activity will continue up to the windows login screen.
- #41 Filter Driver conflictsFirewall/Antivirus Services kickoffAntivirus Updates being loadedDomain Profile creation
- #48 At Citrix Services - we’re Citrix consultants, teachers and support engineers and we’re all about one thing: making sure you succeed.With our help, you’ll deploy high-performance, robust virtualization and networking projects, faster – with dramatically lower risk and higher return.The best Citrix architects and administrators are the ones who never stop learning – and Citrix Education is here to help you learn those skills.Citrix Consulting gives you direct access to our most experienced virtualization and networking experts.When it’s complex; when it’s mission-critical; when it’s big; That’s when Citrix consultants can really help.On your virtualization journey, you’ll want always-on support from people who really care about your success.There’s no better insurance for your Citrix investment than with Citrix Support.
- #49 Secrets of the Citrix Support Ninjas is a FREE eBook available next week.The eBook contains 40 insider troubleshooting tips for administrators.So the purpose of the eBook is to help administrators like you keep your Citrix deployments on track.We’ve collected some of their best tips and tricks for running robust Citrix environments and packaged them up into a free eBook.In it, you’ll discover some of the little-known tricks that our own support people use every day to tune, tweak, troubleshoot and test Citrix solutions. You may know a few of these tips. But you probably don’t know them all.And – you never know – you might discover just one that will change your life as an administrator.Let me give you a sneak peak now.