Category Archives: Citrix
First I want to say it’s been awhile since I wrote up an article back on NetScaler 9.3 Code, not much has changed but just enough I figured I would write up one for 10.5 Code.
First login to your NetScaler, Expand Traffic Management, Load Balancing, and Click on Servers. Click Add
In this example we will be using Domain Name, this Requires DNS to be configured prior to this step. Note the Server Name Field is just for Display proposes, and the Domain, is the FQDN of the Backend Server we are wanting to utilize.
Next we Need to Create a Service to Bind to the Backend Server, Click Services, And Click Add
The Service Name is just a Display Name, Select Existing Server, Select the Server you created in the Above Step, Select the Correct Protocol, And port number.
Click Virtual Servers, Click Add
Name is again just a Display Name, Select Protocol, and in this Example we are going to use Non Addressable for the Type
Click Continue, Click on the No LBVserver Binding
Click The Service we created earlier, Click Insert
Click the Plus Sign
Select Cache Policy, Leave Type as Request, Click Continue.
Select the No Cache Reset Policy, Click Insert
Now to change it up, Click On Content Switching, Click on Actions, Click Add
The Name Is just a display name, Select the vServer We created from the Dropdown List, Click Create
Click Policies, Click Add
The Name is yet again, just a display name, Select the Action we just created, now for the Magic, In the Expression field, HTTP.REQ.HOSTNAME.CONTAINS(“NameToFilterAgaist”), Click Create
Select Virtual Servers, Select HTTP, Click Edit
Click Content Switching Policies
Select The Policy we just created and Click Insert
That’s it, Now as long as your Domain Name and IP all match you should get to your Backend Site.
Thanks for reading
So after many hours of Trouble shooting thinking I was battling a VMWare 5.5 Hardware Version 10 issue. Became a super easy Partition layout issue. So here the run down.
I was trying to capture a Golden image, had everything setup and working. I was giving a new Base Build image to capture and started having problems when I tried to run through the Image Wizard… This would run through without issues until the reboot, it would come up attach the vDisk but wouldn’t capture the image. I tried every combo I could think of going to an E1000 instead of the VMXNET3, still got the same results.
Now for the good news, I found that it was a simple Partition issue, the Wizard hard codes the small windows 300mb partitions to the first volume, however I found running the P2PV tool under the Provisioning Services folder, selecting This machine to VHD, and manually moving the 300mb partition to the last part of the Drive and moving the Data Volume to the front resolved the issue. Granted you have to point the saved VHD to the PVS Server, and you will have to manually import the VHD after it is captured.
Anyways thought I would share this, thanks for reading.
I am going to start this off with a bit of a disclaimer. I really am not trying to sell anything! Just want to get the information out there, I highly recommend talking to your trusted advisor(s) before starting a PoC/Pilot just my two cents worth.
So you have most likely heard of a “VDI Assessment”, and may have even pondered the thought of having one done. Well here are a few reasons to take the next step and get that Assessment.
Some of the main things I hear:
1. I want to go VDI but don’t have the resources…
2. I want to go VDI but it’s not “good” or doesn’t work well
3. I want to go VDI but it is to much over head NO ROI
I will just start right in…
1. Most likely you are half right about the resources. You most likely have the infrastrucure to support a VDI Environment, and you may even have the resources you just don’t know it, or you can “Exchange” one type of resource for another… I have seen many cases where we were able to get rid of OLD style VDI (RDP to Desktops) & (RDP one to one Servers) and move to a slimmer Thin Provisioned Style VDI Deployment. For example: Say you have 100 Desktop’s you want to Virtualize. Windows 7 recommends you go no less then 24GB for a disk I recommend 30-50GB Depending on Application(s) needed. 2GB of RAM, and 2 vCPU’s (avg. config for win7). In theory, you would need 30GB x 100 Desktops in disc space alone! This is not the case. You will only need 4GB x 100 Desktops as you will only need to account for the delta files (Cache Disk). Note: If you are running ESX you will also need to account for a SWAP file which is the same size as your machines RAM. In this example you would need 2GB x 100 extra disk space.
2. This is a common misconception, which in fact, is what most people see in self-deployed PoC’s and Pilots. There are a number of tweaks your friendly Partner/VAR should know that will help improve performance and usability. This is because “this is what we do”. We have ALOT of tricks up our sleeves. I have been involved with several Citrix Projects where “Citrix” was considered such a bad word that the Citrix team could hardly walk down the hall without getting mauled. In less then 6 months we had users asking to be moved to XenDesktop. Talk about a culture shift! Remote workers suddenly jumped by a good 15-20% because they could actually function while working remotely. Everything roamed with them. (as advertised) No more working in one environment while at work and a completely different environment while working remotely… Another common issue I see is a lot of people think going VDI also means going with some sort of application streaming, or thin-app. This is not always the best solution, as it doesn’t necessarily save you all that much disk space in the long run. Using the example in Statement 1, the only thing you really need to be concerned about is your Delta (cache disks). So, in some cases, streamed or thin-apps can cause double the overhead.
3. Well this one is a fine line. Really, you can make VDI as simple or as complicated as you want :). Most of the time I hear “My users won’t buy off on VDI.” Again, this is a false statement burnt into you from the Beginning of Statement 2. With the proper configuration there is no reason users would complain and in most cases once the users logon they are hooked. ROI really should be Return On Individual, if we can make our users (which in fact are our customers) happy and more Productive we have succeeded. I have seen the cost estimation on the Individual’s time and that was staggering… We are talking 100’s of thousands of dollars a year in regained work and help desk calls. I saw a customer where their computers would take roughly 10 minutes just to login, this was on top of the 10 minute boot time if you abide corporate policy and shutdown your machine which took 10 minutes… as you can see time was adding up in the NOT working area extremely fast. So for pretty much every HelpDesk call workers and the company where out about a half hour of actual work… Now for the ROI part if you go with thin clients, and high capacity servers you can really start saving money just in power, then looking at the management of a VDI deployment this again saves money as everything is the Same! No guessing if a patch, update, or user screwed up the machine simply have them reboot and back to the Golden Desktop.
With all this being said, NOT every application, or use case is a “Good Fit” for VDI. And this is one of the key discussion in having a VDI Assessment done, we can tell you whether or not going VDI is a good fit.
Thanks for reading.
I am going to start with what I think are going to be some key Partners to be keeping an eye on this year.
Now for the reasoning behind my top 4 mentions VMTurbo is your single pane of glass into your data center, ESX, XenServer, Hyper-V all in one, plus services. No more do you have to monitor and manage each product separately, you simply point it at all the Products you want, it runs a discovery that is it. If you want it to manage the resources you simply to it on otherwise it will just warn you about workload balancing, also Simply give it some domain Credentials and have it monitor Windows Server resources… IIS, SQL, XenApp, XenDesktop. As well as NetScalers.
ExtraHop is a great looking product that is a “One of a Kind” as it is more of a Network Sniffer that can actually completely look into the ICA Stack and tell you everything you wished EdgeSight could!
AppSense, well if you follow me on twitter then you most likely have heard me “pimping” it. It really is an amazing software suite, You can use it to Dynamically apply GPO’s and GPO like controls as well as Lock Down your environment without killing your user experience. If you haven’t seen it I would highly recommend you check it and have them give you the “Dog and Pony” Show!
More to come as I have time to Update the Blog.
Thanks for reading, Lawrence
So after a few hours of beating my head against the desk, and reading a few dozen articles, this is what I have found.
Well First I was going to go on how you had to down grade your Target agent to 5.6 Sp2 to make things work and how you would have to piss off your ESX guys by having to use the E1000 driver, but all that has changed. Earlier this month, Citrix released a “Hot Fix” CPVS61E001 for PVS 6.1 basically it is PVS 6.2 from what I can tell 🙂 anyways it is about 700Mb and you have to completely remove the existing install and re-install the core software, you will be asked to upgrade the Database so make sure you have a good backup. Then install the New target Agent. Now for the wrinkle this is all fine if you are Running ESX5 if you are still on 4.1 like a lot of people, you will need to apply Hot fix CPVS56SP1E011 (Don’t ask) Now you can use ESX4.1 and the VMXNET3 Driver.
Hope this helps, thanks for reading.
Just a few notes about XenApp 6.5:
First if you where a custom to using Load Evaluators for managing Servers Maintenance Windows or taking servers offline you better start getting use to Worker Groups. The Reason is they have moved Load Evaluators to Machine Policies so you can’t change them on the fly, with this being said I highly recommend using Worker Groups based on Farm Servers instead of OU. This is so you can easily add and remove servers this taking them out of the published application.
Second, Licensing is a Must, but again this is done through Machine Policies. You have to select the right Version (Adv, Ent, or Plat) Also a new feature is you have to select your licensing model (XD or XA, Concurrent or Named). Note: if you run the following command qfarm /load and get a load of 20,000 you don’t have licensing set correctly.
That is mostly it for now, just wanted let you all know of the few changes. More to come…
Thanks for reading
First you will need to download the latest VPX Appilance from http://www.citrix.com (a mycitrix is required)
You will also need to download the Web Interface components
You will need a VM with at least 4GB of RAM to support more than 3 Sites
Once you have imported the machine, Open the console to setup, you will prompt for the following:
Once you have configured the IP Address, enter that into a browser. (Java Required)
You will get a login page simply type nsroot and nsroot, username and password
It is highly recommended to change the Default password
Install Citrix License
You will need to find the Interface on the NetScaler with the lowest MAC Address
Under the Network Folder, > Interfaces
Copy the lowest MAC address
Now go back to your mycitrix account and allocate a NetScaler License
Note if you want to use an Express License
Click on NetScaler VPX Express
About half way through the page you should find a link to Get License
It should be right in-between the Appliances and the Builds/Upgrade packages.
Run through the Allocation Wizard and download the new License file.
Expand the System Folder, and then select Licenses
At the Bottom left of the Frame you should see Manage Licenses…
Click Add… Select the license file you just created and Downloaded, Click Select
The device will reboot for the license to take affect
Once it has rebooted, log back in
Expand System and Select Settings
Click on Configure modes
Make sure all the options from the above Screen shot are all checked.
Click Yes to the warning
Click Configure basic features
Make sure all the options from the above Screen shot are all checked.
Click Yes to the warning
Select Web Interface folder
Click On Web Interface
Click Install Web Interface
Click the Dropdown arrow to the right of “Browse (Appliance)” and select Local
Select nswi-1.3.tgz, and click Open
Select diablo-latte-freebsd6-amd64-1.6.0_07-b02.tar.bz2, and Click Open
(Note: if default to 25 sites you will have to have at least 4GB of RAM installed for the VPX otherwise this will error out.)
Web Interface Configuration
Login to the NetScaler and Expand the Web Interface Folder
Click Add.. at the bottom of the Frame
Enter the IP address of the Web Interface Server VIP. Check the Box Enable access through mobile receiver, Click Next
Enter in the XenApp servers here, Just the Data Collectors
Click next, after you have entered all the Data Collectors
Highlight the Web Interface Site you just created
Click on the WebInterface.conf… link at the bottom of the Frame
Remove the # from the beginning of the Line, and add your Domain Name removing everything else… Click Save
You will receive a warning, Click Yes
Click the Add Button at the Bottom of the Frame
Select XenApp Service Site, Click the Dropdown for Virtual Server, and Select the previously Created Server, Note should be listening on port 80, Click Next
Click the Add, and add all Data Collectors, Click Next
Select the PNA Site (XenApp Service Site)
Click the config.xml… Button at the bottom of the Frame
Change the <LogonMethod> from Prompt to Pass-Through, Click Save
Click Yes to the Warning Message
It has been awhile since my last post. And sadly it is going to be a bit longer. I have been slammed and my lab has been down, but here are just a few things to look forward to.
PowerShell samples and examples…
PowerShell XenApp Commands for XenApp 4.5/5 farms!
XenDesktop 5.5 tweaks
Branch Repeater VPX
NetScaler integrated Web Interface
Thanks for reading and hopefully I will be able get some of this out sooner then later.