![]() ![]() This can cause your session to become unresponsive, as there are certain internal dependencies that the application requires (I’ve seen this same odd behaviour when copying executables such as the Registry Editor to other folders or locations as well). Years ago, it used to be common practice to create a copy of Windows Explorer and call it explorer2.exe or something similar, but this shouldn’t be done any more. In a support situation, they possibly may lean back on any oddities around a published version of File Explorer as caveats towards the “we generally wouldn’t recommend this” approach. The same goes for Citrix – they appear reluctant to nail their colours to the mast regarding this issue, and this probably boils down to the fact that they know they have large customers who publish File Explorer as a matter of course, and don’t wish to upset those applecarts. In conversations with Microsoft, they seem reluctant to be drawn on whether they actually recommend this or not. From an administrative perspective, though, it can be a pain – the seamless integration with the local desktop can often cause confusion and if access to virtual channels is restricted, there’s the potential for a lot of frustration.Ĭitrix have a document published that explicitly states “ Microsoft does NOT recommend running Explorer.exe as a published application because the published Explorer.exe application runs as a separate process with restricted access to the desktop“, but this is an old technote and still lists “XenApp” and “XenDesktop” as the products it applies to. ![]() Users in published application environments often like to use it, as it gives them almost a “semi-desktop”, allowing them to navigate around filesystems and invoke applications from within the same session, and often you may even see savvy users invoking it from within other published applications. File Explorer ( explorer.exe) is actually the full Windows shell and has a significant amount of processing and functionality attached to it. It’s difficult to get a steer, either from Microsoft, Citrix or any other vendor, as to whether you even should publish an instance of File Explorer. But is doing this such a good idea? Vendor stance ![]() I know that many customers using virtualized solutions such as Citrix Virtual Apps or Remote Desktop Session Host often publish an instance of Windows Explorer (or File Explorer, as it is now known) to allow users to browse filesystems and network shares. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |