Can anybody tell me the limitations or drawback of using the method Application isolation.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Principally, it's that the app might not work! Some poorly-written apps whine if they can't find their support files EXACTLY where the developer deems they belong. Other than that, nothing, really. This article http://www.symantec.com/community/article/2609/application-isolation-basics-and-how-isolate-application mentions patching but, if you've re-packaged the app to isolate components, you're surely going to have to re-package the patch (if you catch my drift).
Answered 02/17/2009 by: VBScab
Red Belt

Please log in to comment
It should also be noted that my research from websites seems to indicate that the isolation is dynamic in that it checks to see if a file is already in the shared location and if it is then it isolates and if it isnt then it installs to that shared locations. Thus you can end up in a situation when you dont actually know if a file has been isolated during installation and so having to build checker scripts to locate the file before patching it!

If you want to do proper conflict analysis then use GUID syncing and merge modules and not isolation. If unable to do either GUID syncs or MM's then isolate but only as a last resort in my book.

Answered 02/17/2009 by: Inabus
Second Degree Green Belt

Please log in to comment