r5000 doesn't start until login on whs?

[btrcp2000]

Not getting myu hopes up, but things seem to be stable enough that it's timeto run down something I've noticed since I installed everything on whs. Microsoft is basically sending out nightly security updates and each %$# one requires a reboot. My r5000 app doesn't start until i login to whs. I figured I could solve this with autologin, but am not comfortable with security. Is this a job for anyservice installer, or is there another solution?

Interestingly, with all the system messages that are available now, sage never seems to notice that the r5000 tuners are not there.

[gplasky]

Originally Posted by btrcp2000

Not getting myu hopes up, but things seem to be stable enough that it's timeto run down something I've noticed since I installed everything on whs. Microsoft is basically sending out nightly security updates and each %$# one requires a reboot. My r5000 app doesn't start until i login to whs. I figured I could solve this with autologin, but am not comfortable with security. Is this a job for anyservice installer, or is there another solution?

Interestingly, with all the system messages that are available now, sage never seems to notice that the r5000 tuners are not there.

If you're not comfortable using autologin then your only other option would be anyservice installer.

Gerry

[btrcp2000]

I have no real reason to be uncomfortable with it, just things I have read. Is there any advantage/disadvantage to anyservice vs autologin? Is it more difficult to get to the gui if needed?

[gplasky]

Originally Posted by btrcp2000

I have no real reason to be uncomfortable with it, just things I have read. Is there any advantage/disadvantage to anyservice vs autologin? Is it more difficult to get to the gui if needed?

Not sure. I suppose you have another executable to start the gui. The advantage is anyservice runs it as a service (just like SageTV on WHS) so you don't have another session running with a user logged in. You're WHS could run with no other users logged in-a more secure way to run. If you're looking from a security level you're better off running as a service than a user in a session.

Gerry

[btrcp2000]

okay, for the benefit of anyone who searches and finds this thread looking for useful info, don't bother with anyservice if you have been having trouble with the r5000 app. It worked fine creating the service, but sage didn't seem to have the tuner. Although "functioning: true" was listed in the status page, it wouldn't tune any channels. Logging into the server as admin put me back into the same frustrating loop of r5000 demanding the license key, only connecting one of the tuners, "SN does not match" etc etc.

To hell with security, I just disabled the service and setup autologin, all seems to be well after reboot. I swear r5000 went from my most stable tuners to a hot mess ever since I set everything up on whs.

[gplasky]

Besides just setting up to run as a service you may have needed to check the box "Allow service to interact with desktop". I don't have the r5000 and not exactly sure of all the requirements but knowing that autologin works fine for you checking that box may have solved the issue of running as a service.

Gerry