>>I am a little confused (my middle name is "confused" :) You wrote above "service" but you are Jeff suggest to have an EXE run from the Windows Scheduler. So, you just call this .exe "service". Is this correct?
>>
>>And if this is correct, I will have to learn how to crate a Windows user account (on the VM) without having this account being logged in at all times.
>
>My first name is Confused, I just go by my middle name ;)
>
>The user account is just a username and login and a set of permissions.
>
>Windows Services and any exe you call from Task Scheduler use a Windows user account.
>They impersonate that user and run outside the desktop.
>They run silently in the background if a user is logged in.
>They run silently in the background if no user is signed in.
>
>I had a scheduled task running under my account and it would grab focus away from the program I was using.
>That was annoying.
>It is best to have this kind of program run invisibly in the background.
>
>Attached is an picture of the setup of a scheduled console app I have had running for years.
>I outlined the relevant details in red.
>I created a user account called TaskRunner for it so I could set permissions to only the folders it needs.
Thank you!
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
