Blog posts tagged with 'sepago'

Not too long ago, I posted an article introducing the availability of ClearType on Citrix XenApp.

Helge Klein - one of my favorite bloggers, has taken it to the next level, he wrote a technical article explaining in great details how to configure ClearType on both XenApp 4.5 and XenApp 5.0, along with their respective requirements. Here's a snippet of his post.

With the release of the hotfixes KB946633 and PSE450R02W2K3037 ClearType font smoothing is finally available on both the current and the upcoming Citrix flagship products Presentation Server 4.5 and XenApp 5.0. Remains the question of how to configure it.

Windows has a GUI for configuring font smoothing (well hidden in the display properties). XenApp does not.

Each user of a published desktop can use the Windows GUI for configuring font smoothing. But what about the majority of XenApp users who only use published applications and do not have access to a published desktop? I do not know. Of course, the admin could set the font smoothing type in the registry for them. But even then users have no means of changing their setting.

Enter XenApp 5.0 and ICA client 11. If and when those two are at the server respectively client end of an ICA connection, the whole thing works the other way round: The ICA client reads the font smoothing type of the Windows client and transmits it to the server who then activates the client's setting for the current session. This even works across reconnects: During a reconnect from a different machine the new client's setting is read and transmitted. If it is different from the previous client's setting the font smoothing type of the session is changed on the fly.

This approach clearly has its advantages: No problems with published applications. Additionally, remote applications always have the same look as local programs.

But wait: What if the client is not a Windows client? Then we are back to the pre-XenApp days: Configuration on the server.

Configuration Overview

Just in case you got confused: The following table lists all requirements and configuration options:

Continue reading Helge's blog post here.

During Citrix Synergy, Sepago announced that the sepagoPROFILE software was sold to Citrix.

The agreement includes the complete takeover of the product, which will form the future core technology for profile management within the Citrix Delivery Center (Citrix XenDesktop, Citrix XenApp and Citrix Provisioning Server). In addition, the development division of sepago will continue development of the product for the virtualization of application provisioning in cooperation with Citrix over the next 18 months.

For more info:

Visit: Citrix.com/UPM

Download: UPM Whitepaper

Download: UPM Technology Preview

Helge pointed me out to his blog just recently, and you know what - he has really userful content there. He just recently blogged about a neat little app that allows you to manipulate REG_LINKs. Very useful for your XenApp environments when configuring your remote apps and streaming profiles.

Here's a snippet of hos post:

---

Recently I got into a very interesting discussion with my colleague Nicholas Dille on various aspects of Windows x64. One question he brought up was especially intriguing: Knowing about registry redirection, it is not astonishing to find that the 32-bit version of the registry key HKLM\Software\Classes (aka HKCR) gets to be HKLM\Software\Classes\Wow6432Node. But there is also HKLM\Software\Wow6432Node\Classes!? How can there be two different Wow6432Node 32-bit keys for one 64-bit key?

It soon dawned on us that one of those two Wow6432Node keys must be a registry link to the other, meaning that the 32-bit data is actually stored in only one place as common sense dictates. But which is the original and which is the link? And what is a registry link anyway?

What Are REG_LINKs?

Registry links (internal type name: REG_LINK) seem to be one of the last great mysteries of Windows NT-based operating systems although they have been around since NT4 at least. Microsoft uses them to point the CurrentControlSet registry key to one of the actual ControlSets (typically 001 or 002). A registry link essentially is a symbolic link in the registry - one registry key pointing to another. The nice thing is that this whole pointing stuff happens completely opaquely to applications: if key A points to key B, and an application tries to access key A, it will actually see the contents of key B. The concept is simple, easy and powerful.

How to Manipulate REG_LINKs

There is only one problem: There is no officially documented way to list, create or delete REG_LINKs. The registry API simply does not have any functions for manipulating them. This makes things more difficult, but not impossible. Searching the net, I quickly found the excellent tool regln which comes with full source code and compiled both as 32-bit and 64-bit binaries. The source code of regln gave me the hints I needed: the internal NT API (not too well documented and hidden in ntdll.dll) contains the functions required for REG_LINK manipulation. With that information and some further research I put together a small command line program that scans the registry for REG_LINKs and lists those found along with their target: ListRegistryLinks.exe. The tool is available both in 32-bit and 64-bit versions.

—

Continue at source: Helge's Blog

Download: ListRegistryLinks.exe 1.0 for Windows x86 (32-bit)
Download: ListRegistryLinks.exe 1.0 for Windows x64 (64-bit)