Jump to content
Welcome to our new Citrix community!
  • Creating a Citrix XenApp Test Environment in 5 Minutes on Microsoft Azure


    cugcblogs

    joharderrnd.png by Jo Harder, CTP, Tampa CUGC Leader, CUGC Women in Tech Founding Mentor

    For all of the geeks that want more hands-on time with Citrix technologies but don’t want to spend a lot of money purchasing a server, Microsoft Azure can be your key to “renting” compute time rather than buying it.  The beauty of creating an environment this way is that you can test as much as you’d like (or even blow it up!) for 30 days for only the cost of Azure.  Using the options selected below, your cost will be about $2/hour when turned on.

    The key to saving money with Azure is to turn off your servers when you’re not using them!

    In this article, we’ll walk through the steps to create a Citrix environment based on a pre-defined template in Azure.  For anyone in the Tampa area that will be attending the CUGC meeting on August 18th, I'll be demo'ing this as part of the meeting.  It only takes a few minutes to initiate the Citrix environment and then the provisioning process itself takes about two hours.  After that, voila!

    First, go to https://portal.azure.com.  You’ll need to create an account (called Pay as you Go wherein Azure gives you a $150 initial credit for your first month of service) or use credits from a Visual Studio (MSDN) subscription. 

    After your account is created, access the Azure portal.  Select the +New button and enter XenApp Trial in the search box.  At the bottom of the next screen, select Create.

    harder8101601.png.312437c62496c562547babfe5abf6e3b.png

    The Basics screen will appear, asking you which Subscription, Resource group, and Location you wish to use.  Make your selections here.  In my case, I selected my Visual Studio Professional subscription, a Resource group named RGTest2, and the East US data center.  Then click OK at the bottom of the screen.

    harder8101602.png.ea63b48849142c4dce5eddde1aa1c373.png

    The second step is Deployment settings.  Here, you will select your admin credentials and email address.  The email address is the one where notifications should be sent, such as deployment confirmation.  The Size item is directly related to pricing.  For a lab or test environment, choose the smallest size presented.  Then click OK at the bottom of the screen.

    harder8101603.png.7c176ead5a6bac73cfafc289353b8e2b.png

    The Summary screen will confirm your settings, so just click OK at the bottom of the screen.

    harder8101604.png.5a7867c82909057fe0032590c92f03b3.png

    The last screen, Buy, shows the terms of use, and you should just select Purchase at the bottom of the screen.

    The configuration of your deployment is now complete.  In about two hours, you will receive an email from Azure informing you that your environment is ready, including details regarding access to your specific environment.  Within that email, the Login to StoreFront link enables you to access your specific environment with the admin credentials you entered during setup. 

    harder8101605.png.63aecf0e281443ef861a734dc24a4407.png

    A few notable items:

    • Login.  Be sure to capture that URL of the StoreFront login because that is how you and any other users will access your environment.
    • Domain.  If you attempt to log into the domain controller, know that your domain name is xenapp.local.
    • Eval licenses are allocated. The Citrix license is good for 30 days, and the Remote Desktop license for 120 days.  Some pesky reminders are shown for each.
    • Time zone.  The servers are based on Coordinated Universal Time, which in my case, did not equate to my local time zone, but it didn't matter because this was just a test environment.
    • Wallet drain.  You will be charged for compute time based on when your servers are turned on, which includes during and after deployment.  As soon as you receive the email that your environment is ready, start using it or turn it off. 

    Stopping your servers will take a few minutes because you need to individually turn off each one.  You should verify that each is stopped before you exit the Azure portal to be sure that you don't incur unexpected fees.  To stop your servers, expand the Resource Group and select each invididual VM.  Click Stop and confirm each one.  Then wait a minute or two and verify that Stop is no longer an option for each VM.

    … One last time: don’t forget to turn off your servers when you’re not using them!

    harder8101606.png.5668c77e7eccf8bbd70b276b9d9254c1.png

    User Feedback

    Recommended Comments

    There are no comments to display.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...