locked
C:\Windows\X.ini on Terminal Server with App-v, multiple user conflict RRS feed

  • Question

  • Hi,

    I'm new to sequencing and am unsure about the following so would like some advice.

    I have sequenced an application which installs a .ini file to C:\Windows. The file is installed there during the sequence and is therefore captured inside my AppV bubble.

    When the user then runs the application the C:\Windows\X.ini file is referenced and the application behaves in a certains way after reading some settings from within the .ini file.

    Am I right in assuming that this file, because it's installed to C:\Windows\ and is a system file rather than a user specific file, is stored in the Appv cache file in this location - C:\ProgramData\Microsoft\Application Virtualization Client\SoftGrid Client\AppFS Storage\XXXXXXXX\XXXXX.pkg

    Also, am I right in saying that any change made to the user specific part of the application gets stored in the file in the following location - \AppData\Local\SoftGrid Client\XXXXX\XXX.tmp?

    If my assumptions are correct then I was wondering if there is any way to change this behaviour, the reason I ask is that I need to run this application on a Terminal Server and therefore, multiple users could be running this application at the same time and if one user changes the settings in the INI file to suit them, the following user may need to use different settings and so there is a conflict of interests with this file. Even though it's not installed directly onto the machine but because it's stored in C:\ProgramData\Microsoft\Application Virtualization Client\SoftGrid Client\AppFS Storage and will therefore apply to all users.

    I would like to know if there is a way around this happening so that the file cannot be edited for a start and also if anyone has had to deal with this situation in the past and how they got around it.

    Unfortunately, the application looks for the INI file in C:\windows and so this location can't change.

    Any advice would be greatly appreciated as a this moment in time I am looking at removing this file from the package entirely and installing it via a script outside of appv.

    Rgds,

    Mark

    Friday, March 23, 2012 8:51 AM

Answers

  • Hi,

    use a script to delete this file after application shutdown by using the POST tag.
    Some hints using Scripts in OSD files.

    /vkleinerde

    • Proposed as answer by J.Badia Monday, March 26, 2012 11:00 AM
    • Marked as answer by Aaron.ParkerModerator Friday, November 16, 2012 11:33 PM
    Friday, March 23, 2012 2:43 PM

All replies

  • Hello,

    1. You can check Enforce Security Descriptors (default is checked) under the deployment-tab while in the sequencer. The user would then not have the possibility to edit the file

    2. However, since you are running RDS - it may well be that the .INI-file is not stored in c:\windows\ but redirected to the users home-path. Use process monitor to confirm this.

    3. Default behavior should be that the file should up in a .PKG-file within the users-profile and therefore not effect other users on the platform.

    Have you tested the problem you are describing, or are you simply worried?


    Nicke Källén | The Knack| Twitter: @Znackattack

    Friday, March 23, 2012 10:06 AM
  • Hi,

    OK, I've carried out some more testing. It seems as though the file is being copied to the users home-path, in this instance H:\Windows\X.ini.

    So, once this file is copied there the user then has full access to it, even after I have set it to be read only within the sequencer and I enforced security descriptors.

    Also, it seems as though I was previously mistaken, in that, the X.ini file is not shared between users on the machine.

    Therefore, my question now is how do I ensure that this file is removed from the users home path once the application is closed?

    Thanks for your help,

    Mark

    Friday, March 23, 2012 12:13 PM
  • Hello,

    This is unrelated to App-V and is a feature of RDS - I suggest you post the question in a RDS-forum.

    General topic for installing applications in RDS;

    http://technet.microsoft.com/en-us/library/cc730696(v=ws.10).aspx

    RDS-forum;

    http://social.technet.microsoft.com/forums/en/winserverTS/threads


    Nicke Källén | The Knack| Twitter: @Znackattack

    Friday, March 23, 2012 12:29 PM
  • But why is the file being written outside of the bubble? Even though it's in my VFS?
    Friday, March 23, 2012 1:10 PM
  • Hello,

    Again - a feature of RDS is redirecting the file into the home-path of your user-profile. The home-path is not part of the VFS

    Nicke Källén | The Knack| Twitter: @Znackattack

    Friday, March 23, 2012 1:11 PM
  • Hi,

    use a script to delete this file after application shutdown by using the POST tag.
    Some hints using Scripts in OSD files.

    /vkleinerde

    • Proposed as answer by J.Badia Monday, March 26, 2012 11:00 AM
    • Marked as answer by Aaron.ParkerModerator Friday, November 16, 2012 11:33 PM
    Friday, March 23, 2012 2:43 PM