While most applications can be successfully virtualized for use with
SoftGrid, some applications may have certain characteristics that would
prevent them from being completely virtualized using the current
version of Microsoft SoftGrid. This includes:
1. Applications that install and rely on a system-level driver, i.e. an application that installs a print driver or a USB device driver. Some applications may allow for the drivers to be installed independent of the other components of the application. As a work around for this scenario, the driver portion of this application could be installed locally on the client system, allowing the other components of the application to be virtualized.
2. Applications that install boot-time services (like RES PowerFuse)
3. Applications that use COM+.
4. MAPI virtualization. For information on SoftGrid and Microsoft Office, see the following article:939796 Prescriptive guidance for sequencing 2007 Office programs in Microsoft SoftGrid http://support.microsoft.com/default.aspx?scid=kb;EN-US;939796.
5. COM DLL surrogate virtualization, i.e. DLL’s that run in Dllhost.exe.
6. Applications with licensing enforcement tied to machine, e.g. the license is tied to the system’s MAC address. (Due to sequencing issues; this just wouldn't make any sense)Some of the applications that fall into these categories can possibly still be run in Microsoft SoftGrid as long as the component that cannot be virtualized is installed locally on the same machine as the SoftGrid client. This solution may solve the issue but is not a guarantee the applications will properly function. We recommend you test the applications thoroughly to ensure they meet the expected level of functionality.
7. Anti-Virus!
No comments:
Post a Comment