Since Android Enterprise is the way forward, I decided to write up a complete walk-through how-to implement this in a Citrix Endpoint Management (XenMobile) environment. You can enable and use this in the On-Premises and Read more…
When using Microsoft User Profile Disks you also know the tool Sidder: https://gallery.technet.microsoft.com/Sidder-Quickly-see-which-fa6360b3 This tool will show the username who belongs the the User Profile Disk. I’ve found this not so conveniant as you must run Read more…
A couple months ago I made a post about customizing the cloud gateway.The real name for that product is Citrix Receiver for Web and is part of the StoreFront Express. Digging deeper in the Receiver for Web I found that it is really easy to modify the appearance of that site. You don’t have to change all the original files. Only just one.
Terry Duchastel has made a very clean and easy how-to about branding the site. I’ve borrowed some elements from that post and put it in this simple CSS He has made a couple of links in the logon page for helpdesk purpose. That part is skipped (because I don’t want to change the default html structure). The only thing with that type of branding, is that it will be gone when an upgrade is performed.
Welcome back, in the previous post, we have configured the CAG and the StoreFront server to enable access to the internal XenApp/XenDesktop environment with a web browser. Now we are going to enable the environment to support internal and external access with the Self Service Plugin (Dazzle). First upgrade all receivers to the latest versions. Citrix Receiver 3.2 is necessary to get this working.
Logon to the admin panel on the CAG. Edit the logonpoint that we made in part3. Make changes so that the logonpoint looks like this:
(Click title to read more..) (more…)
When installing the Citrix Receiver you can give the following setup switch: ALLOWADDSTORE=A|N|S
- A = Always, allow adding and removing stores;
- N = Never, allow adding and removing stores;
- S = Secure (https) stores allowed.
When the client is already deployed the following registry key can be changed to change this behavior: