In previous posts I, have already provided instructions and building blocks to automate the deployment of Citrix StoreFront and the XenDesktop Delivery Controller. While the automation of the deployment of Citrix Director is still in the planning stages, someone requested a building block for the deployment of the Citrix Virtual Delivery Agent. I started looking around other Ivanti/RES ONE Automation resources and I noticed that there isn’t much available. Sure, the unattended deployment is described very well in the Citrix Product Documentation. But ROA/IA building blocks for VDA deployment aren’t too common. Reason enough for me to create them.
I will give a small walkthrough of the automation steps and why I made certain decisions and of course instructions on how to import and use them. You can find the download link for the Ivanti/RES ONE Automation building block at the bottom of this blog post.
These modules have been tested on Windows Server 2016 and Windows 10 Enterprise (version 1703) and you can use the same module for the Desktop OS installation of the VDA and the Server OS installation.
Edit March 1st 2018:
The module has been tested with the Virtual Delivery Agent of Citrix XenDesktop 7.17 and Ivanti Automation 10.2.100.0 and works accordingly. The /enable_hdx_3d_pro switch is deprecated since 7.16 and is no longer a selected option by default in the module. However, I have kept it in to keep the module compatible with older 7.x versions (like the 7.15 LTSR version for example).
Edit January 30th 2019:
I have created a new version with the new switches/features of the Citrix Virtual Apps and Desktops version 1811 Virtual Delivery Agent as described in the docs page: Link
Building block is available for download below along with the old version.
A while back I needed to automate the deployment of Citrix StoreFront 3.x for a customer I was working for at the time. However it wasn’t perfect. It only did the installation of the software and didn’t do anything with stores, server groups and certificates. Since time was scarce these items were put on hold. However, I put them on my own ToDo-list with the goal to automate an (almost) complete deployment of StoreFront with Ivanti Automation and share it with anyone who would like to use it.
I will give a small walkthrough of the automation steps and why I made certain decisions and of course instructions on how to import and use them.
You can find the download link for the Ivanti Automation building blocks here and also at the bottom of this blog post.
These modules have been tested on Windows Server 2012 R2 and 2016 (with User Experience enabled) and up to StoreFront version 1912.
While the current RES ONE Workspace management console is very feature rich, there is always room for improvement. There is often a task that you might want to automate or at the very least make it a bit easier. Now my fellow RES aficionado Chris Twiest (@TwiestChris) did exactly that. He had a solid business case for a couple of RES ONE Workspace related tasks, automated them and bundled them into a neat and easy to understand toolkit. Read on for all the tasks that are included in this toolkit (and for the download link of course).
The Self-Service Password Reset has got to be one of the most used features of RES ONE Identity Director (previously RES ONE Service Store/RES IT Store). It allows a user to reset his/her Active Directory user account password without assistance from the IT organization. This is possible on a 24/7 basis, so even in the evening or the weekends the user can use this service.
While this is very useful service, you should think about the security implications. Since the user apparently cannot login the RES ONE Identity Director site he/she should be to open the site from an untrusted network like the internet. But this would imply that everyone with internet-access can change the password of a user account as long as the username is known. So how to verify that the user requesting the service is actually the user in question?
Picture the following setting: A rainy Sunday afternoon. You need to prepare some presentation slides for a sales pitch the following day. You are working from home and are logged in on the company’s virtual desktop (running Citrix XenDesktop). Everything is fine and you are almost done. Suddenly the screen freezes, everything is locked and you are unable to continue your preparation. You disconnect your session and try a reconnect, which is not successful.
Sadly the support desk is only available during business hours.
What should you do? A. Cry B. Scream C. Start all over again on your local machine D. All of the above
Now this is a pretty specific setting, but a customer sometimes had similar issues. Users are working in the weekend and need to contact an administrator just to logoff their session. How can you solve this with RES ONE Service Store?
For a while now RES has supported the management of published applications from Citrix XenApp. This was quite easy to do. Before the release of XenDesktop 7 there wasn’t really a difference between a Data Collector and a Session Host. Both had the same XenApp installation and if was just a matter of configuration as to which role the server had. You would need the RES Workspace Manager Console on one of the XenApp servers and you could simply select Enable Citrix XenApp Application Publishing, define your preferred options and servers and you were good to go.
In XenApp/XenDesktop 7.x this is a bit different. Since the session hosts only contain the Virtual Delivery Agent the requirements are a bit different. You need a machine with the full installation of RES ONE Workspace (Agent + Console) and the Citrix Studio. I will try to define and explain each step from the publishing to the application shortcuts.
I am working on the automation of a Citrix XenDesktop 7.9 deployment for a large customer with RES ONE Automation. Since the created modules work pretty good I would like to share them with the rest of the community.
Larger customers, like the one I created these modules for, usually have dedicated database administrators. Normally only they have SQL dbcreator and security admin rights on the SQL environment. This means that you can’t create the database directly from your automation. So you need to create the XenDesktop database scripts and send them to the DBA’s.
I have created building blocks of the modules for which you can download here. I will give a small walkthrough of the automation steps and why I made certain decisions and of course instructions on how to import and use them.
Since the release of Microsoft Internet Explorer 10, Microsoft has changed the way they handle cookies. In older versions your user profile just had a folder named Cookies that contained them all. When using RES ONE Workspace, you just needed to make sure that the folder was included in the user settings.
Capturing the history was also easy. The only difference was that it was located in the local part of the profile and not the roaming part.
However, when IE 10 was released, everything changed. They started using a webcache database that’s located in the local part of the user profile. It gets locked after logon and simply adding it to the user settings in ROW apparently isn’t enough.
When implementing software, an organization usually wants to go for the DTAP approach (Development, Testing, Acceptance and Production). An application gets developed for the specific organization in the Development environment. The version is then tested in the Testing environment. After that de customer/(key-)users can approve of it in the Acceptance environment and when successful it can be deployed in de Production environment.
This method defines specific steps in the development of a new application or an update of a current one. It also reduces the risk of downtime when developing or testing the new application.
Everyone is familiar with the single sign on (SSO) principle (assumption, yes, I know). You log in to your machine and are authenticated. Now when you log in to a subsequent application (regular or web-based) single sign on functionality (if the application in question supports it) provides the credentials of your desktop session automatically to the application. This ensures a smooth experience for the user and a higher level of productivity.