Accessing Local Machine
I am new to virtualisation and need some help here.
I am sequening an application which should accesses physical folder "C:\Program Files\<AppName>". The sequenced package should just create the "C:\Program Files\<AppName>" folder and permission it. Users will copy the files to it.
Please let me know what changes to be done to sequencer to make this happen. Below are the option that I have tried, but no luck.
1. "Security Descriptot" checked
2. Allow local interaction set to TRUE
3. Merge with local directory
4. Changed sequencer attribute to UserData from ApplicationData.
I am sequening an application which should accesses physical folder "C:\Program Files\<AppName>". The sequenced package should just create the "C:\Program Files\<AppName>" folder and permission it. Users will copy the files to it.
Please let me know what changes to be done to sequencer to make this happen. Below are the option that I have tried, but no luck.
1. "Security Descriptot" checked
2. Allow local interaction set to TRUE
3. Merge with local directory
4. Changed sequencer attribute to UserData from ApplicationData.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
rock_star
13 years ago
You can write a script to do this , Script will run before running the sequenced app.
Make sure you making it this way that it will only run once.
Make sure you making it this way that it will only run once.
Posted by:
VikingLoki
13 years ago
I'm going to take a step backwards and ask why are you trying to do this? It defeats many of the benefits of virtualizing software and you will have problems if the sequenced app needs to write something there. Users should never be copying files into Program Files. Windows does not support user data there and if asked MS will declare any app that does that puts user data under Program Files to be incompatible with Windows.
The sequenced app will be able to read a file in Program Files if it doesn't exist in the virtual layer. However if the app attempts to write something to that Program Files directory, it won't be written there. It will be captured within the virtual layer. The app will see it (in the virtual layer) but if users open Explorer and look for it, they won't find it (Explorer is not running in the virtual layer).
Can you change this location to a network share? Virtual apps always write to network shares directly and read/writes will always end up in the share as expeted. Program Files is completely different. What one virtual app writes there will not be visible to the OS or other virtual apps.
The sequenced app will be able to read a file in Program Files if it doesn't exist in the virtual layer. However if the app attempts to write something to that Program Files directory, it won't be written there. It will be captured within the virtual layer. The app will see it (in the virtual layer) but if users open Explorer and look for it, they won't find it (Explorer is not running in the virtual layer).
Can you change this location to a network share? Virtual apps always write to network shares directly and read/writes will always end up in the share as expeted. Program Files is completely different. What one virtual app writes there will not be visible to the OS or other virtual apps.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
