Posted: Mon Jul 06, 2009 12:31 pm
Well, I have no clue of the actual application design, so I don't expect to be correct. However, if my words have some truth, then it is better to be heard...
I noticed that application requires elevation of priviledges when UI starts. If fbaSched.exe is a service, then why do I have to elevate to admin just to connect to a local service? I noticed that service runs as under my user id instead of Local System account. I am sure running under my user ID will work fine until I want to backup another user's files.
I personally think that interacting with Operating System scheduler is a better way to go. In fact that's what Vista's native backup does. One simply has to create task with a reference to a job config file and schedule to run it as an appropriate user. It is not that difficult to control scheduler even via .NET API.
I noticed that application requires elevation of priviledges when UI starts. If fbaSched.exe is a service, then why do I have to elevate to admin just to connect to a local service? I noticed that service runs as under my user id instead of Local System account. I am sure running under my user ID will work fine until I want to backup another user's files.
I personally think that interacting with Operating System scheduler is a better way to go. In fact that's what Vista's native backup does. One simply has to create task with a reference to a job config file and schedule to run it as an appropriate user. It is not that difficult to control scheduler even via .NET API.