If you have been doing Citrix for any length of time you are probably very familiar with the “Web Interface” servers of old. That has now changed, Web Interface is on its way out and its replacement is StoreFront. With the release of XenDesktop 7 we also finally got StoreFront 2.0 which addressed a lot of the complaints I had with StoreFront 1.2 (namely, the PITA SQL requirement). Having finally done some SF 2.0 deployments now I can say I am pleased with the progress that has been made..and for users running XenApp 6.5 we finally got pre-launch functionality back with SF2.0.
In this post I would like to walk you through a basic 2 server, highly available StoreFront deployment with remote access via Access Gateway. This will strictly be the server side, and you would want to read my How To series on NetScaler 10.1 config to cover the NS config side. So let’s get started…without requiring all the SQL databases this really lays down smooth now as you will see.
First off, check your prereq’s and make sure you’re inline. They can be found in the eDocs here: http://support.citrix.com/proddocs/topic/dws-storefront-20/dws-system-requirements.html
For the purposes of this How To, I am deploying on 2x 2008 R2 SP1 servers running on Hyper-V R2.
Step 1: Navigate to the properties of your Local Area Connection and disable IPv6. Once complete, click IPv4 and open its Properties.
Step 2: Navigate to the WINS tab and disable NETBIOS of TCP/IP.
Step 3: Navigate to your install media (SF2.0 comes on the XD7 media or as a separate download, whichever) and run the Storefront executable. If you are like me and you want to let the installer do all the requirements for you you will get the following popup. Just click “YES” and let it do its thing.
Step 4: Eventually the install of the prereq will complete and the StoreFront install can proceed. Accept the license and click “Next”.
Step 5: Yep, I’m lazy..it’ll install IIS for me because I didn’t. Click “Next”.
Step 6: Click “Install”. Wow..that is SO much easier than StoreFront 1.2.
Step 7: After a few minutes the install will complete and you can click “Finish”.
Step 8: You are now presented with the StoreFront console. If you are using HTTP internally and will not be placing SSL certificates on the StoreFront servers then proceed to Step 12.
Step 9: Go open up IIS Manager and “Import” your certificate. This will be the same certificate you would have (or will be) loading on your NetScaler to handle the internal load balancing.
Step 10: Select the “Default Web Site” and click “Binding” on the right-hand side.
Step 11: Change the drop down to https, then select your SSL certificate from the drop down. Click “OK”. You can now close out of IIS Manager.
Step 12: Since IIS and .NET have both been laid down by the StoreFront installer its a good bet to go check Windows Updates and bring them current. Reboot if required.
Step 13: Open up (or go back to) the Citrix StoreFront mmc from the Start Menu. Click “Create a new deployment”
Step 14: Enter in the name of your internal load balanced DNS name (this is an internal DNS record that points to the load balancing VIP for SF on your NetScaler. i.e., sf.mydomain.local. Don’t really sweat the name..with SF and Receiver your users are getting away from typing URLs so its unlikely they would need to go to it anyhow.) Be aware, this internal URL should NOT be resolvable externally. Things will NOT work correctly with the beaconing if it is (beaconing is how Receiver figures out if it inside the LAN or outside) Info HERE and HERE.
Step 15: Enter in a name for your store
Step 16: Click “Add”
Step 17: Select your controller type, display name, change the transport type to HTTP (usually, unless you ride XML over HTTPS), and then your XenApp servers XML port. Click add and enter in your controllers FQDN one at a time. Repeat for every controller type in your org. To be clear, don’t mix XD and XA controllers in the same “group” here. You should end up in step 18 with a line for each type..XenApp..XenDesktop..etc. Note, if you have a netscaler load balancing your XML traffic (if you followed my articles you do), that IP should be the first in the list of controllers for each respective type.
Step 18: Click Next
Step 19: Remote Access. Select No VPN Tunnel for the majority of deployment unless you require VPN with Access Gateway Plugin or the like. (NOTE: If you are not allowing external access then leave “None” selected and proceed with clicking “Create” and go to Step 22, otherwise..) Click Add.
Step 20: Enter in the display name for your Access Gateway, your external URL, version, leave SNIP blank, and callback url is also your external URL. Click Next.
Step 21: Add STA’s one by one in format http://XAFQDN.internaldomain.local:XMLPORT. When complete, click “Create”.
Step 22: You should be presented with a summary screen and a success message!
Step 23: Now navigate to the “Authentication” section and click Add/Remove Methods
Step 24: If you did in fact configure for external access, User name and Password and Pass-through for NS Gateway are already checked. Lets add Domain pass-through to make it easier on our users to not have to login to Receiver if on a domain joined laptop. Remember to install Receiver with /IncludeSSON switch for that to work. See CTX133855 for details or my more detailed “How To” article HERE.
Step 25: Missed a screenshot here but navigate back to “Server Group” and select “Add Server”. You will see the following box appear.
Step 26: Now go to your second StoreFront server, on which you have done you IPv6, NETBIOS, Updates, installed StoreFront and its just sitting there waiting….and click “Join existing server group”.
Step 27. You will be prompted for the “Authorizing Server” and “Authorization Code” that you received on the first box..enter it and give it a few minutes. Once done, both servers will be in sync. Don’t forget that any changes you do moving forward you need to propagate by going to the server on which you made the changes and clicking “Propogate Changes” on the Server Group page
Step 28. Lets enable the Receiver for HTML5. With SF 2 its included (Hallelujah!) but we still have to enable it. Navigate to Receiver for Web and click “Deploy Citrix Receiver”
Step 29: Select “User Receiver for HTML5 if local install fails” and click OK.
Step 30. Ok, lets propagate our changes by going to Server Group and clicking “Propogate Changes”.
Congratulations you now have a StoreFront 2.0 server group deployed and in-sync, with Receiver for HTML5 enabled. If you follow my series on the NetScaler you will load balance the SF traffic with a VIP and your Access Gateway is providing for external access when your users are on the go. In addition your XML traffic is all load balanced via the NetScaler and those VIPs are #1 in your list of Controllers on StoreFront!
As always, hope this can help someone out there!