Properties files, Sagetv service and Vista

[nielm]

I am trying to write an installer for my webserver to automate all the annoying properties file edits...

Works fine on XP, but I think I am going to have some problems on Vista...

According to these posts, Vista stops user-level programs from writing properties files in Program Files, and redirects the write to a user level location...

This is all well and good when running Sage as a real user, but what happens to Sage.properties when you run sage as a service? and is there a difference when running the service as LocalSystem or as a user?

me=confused. Anyone with vista know anything about this, or wants to have a quick play?

This also looks like a recipe for disater if a user switches from using Service (with admin rights) to user (without) and back again...

Anyone from Sage wanting to step in and let me know if Sage will work in a more defined manner with Vista?

[nielm]

Looking NSIS forums there are a whole bunch of problems with installers that need admin rights (for installing into Program Files), but also need to do things to the current user's rights...

[owilsky]

Originally Posted by nielm

Vista stops user-level programs from writing properties files in Program Files, and redirects the write to a user level location...

This is all well and good when running Sage as a real user, but what happens to Sage.properties when you run sage as a service? and is there a difference when running the service as LocalSystem or as a user?

On XP there is a hidden folder "\Documents and Settings\LocalService", so the "service user" should have a user profile as every "normal" user has and somewhere in this profile folder (I do not remember the exact folder) the Sage.properties should be saved on Vista. So I guess this programs folder virtualization should also work when a program is run as service as user "LocalService". But I did not test this.