Application Isolation Environments - Compatibility Issues
Application Isolation Environments - Compatibility Issues Application Isolation Environments - Compatibility Issues
Citrix states in their article: CTX109254
Document ID: CTX109254, Created on: Apr 27, 2006, Updated: Apr 27, 2006
Products: Citrix Presentation Server 4.0 for Microsoft Windows 2000, Citrix Presentation Server 4.0 for Microsoft Windows 2003, Citrix Presentation Server 4.0 x64 Edition
Compatibility Issues That Isolation Environments Do Not Resolve
When attempting to resolve application compatibility problems using isolation environments, it is important to understand the type of problems that application isolation does not address. Isolation environments may not completely resolve application compatibility issues that are caused by one of the following:
Device or Kernel Drivers. Isolation environments do not isolate device or kernel drivers. For example, if the application installs and depends on a driver to function, it will not work in an isolation environment.
Windows Services. Some applications install and rely on a Windows service (except MSI) to function correctly. Compatibility issues resulting from such applications may not be resolved using application isolation.
Investigate further to see if the application functions correctly without the service. To establish whether an application attempted to install a service, examine the CtxSbxAppMsg section in the Windows Event Log
Windows Class Names or Window Names. If the incompatibility is the result of Windows messages being used as an Inter process communication (IPC) mechanism, application isolation is not the solution. Isolation environments do not isolate Windows class names or window names.
Registry or Application Objects that Do not Link to USER32.DLL. An isolation environment will not resolve compatibility issues caused by applications that do not link to User32.dll. Typically, such applications do not have a Windows interface and use only the console.
DCOM. An isolation environment will not resolve compatibility issues caused by applications that rely on Distributed Component Object Model (DCOM) to function correctly.
IP Addresses. Application isolation cannot resolve compatibility issues that occur because all instances of an application running on Presentation Server share a common IP address. Investigate further to see if the using Virtual IP (VIP), a new feature in Presentation Server 4.0, resolves the issue.
Installers that Require a Reboot During Installation. If an application installer requires a reboot during installation, it may not install correctly into an isolation environment. Removing or renaming files during reboot after an install or repair operation is also not supported.
Application Isolation Is Not a Security Feature. Do not rely on isolation environments to provide secure access to an application. Application isolation does not provide any form of security; Citrix administrators should comply with existing Windows security best practices to ensure that users are allowed access only to resources that they are authorized to access.
User login
Who's new
- Rullydery
- eagenorce
- rittaarier
- swasseZex
- gaterfoko