Windows Executable

[Fuzzy]

Originally Posted by jusjoken

I have not reviewed the servicecontrol code, but its the installer that creates the service set as manual, and the servicecontrol app modifies the settings of the service. Not certain if it would create the service if it did not exist.

Either way, it could be modified to likely adjust the calling commandline.

Yeah, the code to change the commandline should be almost identical to the code that's already in there to change the user.

[jusjoken]

Originally Posted by jusjoken

I will give the manifest solution a shot tomorrow and report back. It mimics what works in v7 so it may be the best short term solution.

I updated the manifest appropriately and this resolved the issue. Sage immediately on next run created the default entry in the right place in the registry under v9.

I did this for the client and server.....question is do I need to do it for the Placeshifter launcher as well... I assume yes as it needs java so likely reads the registry as well.

k

[Fuzzy]

Originally Posted by jusjoken

I updated the manifest appropriately and this resolved the issue. Sage immediately on next run created the default entry in the right place in the registry under v9.

I did this for the client and server.....question is do I need to do it for the Placeshifter launcher as well... I assume yes as it needs java so likely reads the registry as well.

k

I have copied a placeshifter install to a very locked down system at work and it 'just works', so I doubt it 'needs' the registry for anything.

[jusjoken]

Originally Posted by Fuzzy

I have copied a placeshifter install to a very locked down system at work and it 'just works', so I doubt it 'needs' the registry for anything.

Thanks.

[brianrent]

Quick question. Does the version on the server need to match the version on the client? I know they both need to be version 9, I mean the 9.0.3.194 or 9.0.3.220 etc...

[jusjoken]

Originally Posted by brianrent

Quick question. Does the version on the server need to match the version on the client? I know they both need to be version 9, I mean the 9.0.3.194 or 9.0.3.220 etc...

Both need to be any version of 9.

[jusjoken]

One key point though....only the latest 9.0.4.224 exe's will force to run as admin and therefore have needed access to the registry. Older versions you should run as administrator.

k

[brianrent]

One thing that I noticed about the running as administrator in the latest installer is that when restarting the computer (client), even though in the settings it is set to start up in full screen mode it does not start. Even when put in the startup folder it does not start. So I guess its a run as administrator thing in general and not SageTV specific.

[EnterNoEscape]

Anything that needs to run with elevated permissions will not run if it is placed in Startup or even if you place it in a similar purposed registry key (Ex. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run).

[jusjoken]

Originally Posted by brianrent

One thing that I noticed about the running as administrator in the latest installer is that when restarting the computer (client), even though in the settings it is set to start up in full screen mode it does not start. Even when put in the startup folder it does not start. So I guess its a run as administrator thing in general and not SageTV specific.

I found and tested a solution. Use Task Scheduler. Create a simple task to run the Client on Logon. At the end of creating the task go into the properties and check the box Run with highest privileges.

So after that, as long as the user that is logging on is an Admin then the client will launch properly.... it did in my test at least.

k

[brianrent]

Thanks. I will give that a try.

[nyplayer]

Originally Posted by jusjoken

I found and tested a solution. Use Task Scheduler. Create a simple task to run the Client on Logon. At the end of creating the task go into the properties and check the box Run with highest privileges.

So after that, as long as the user that is logging on is an Admin then the client will launch properly.... it did in my test at least.

k

One thing to remember is that windows scheduler defaults to “below normal”, when running tasks which is a priority of 7... you have to export the task change the priority and re-import.

[wayner]

If I reinstall over an existing V9 system will it update the permissions properly?

[jusjoken]

Originally Posted by wayner

If I reinstall over an existing V9 system will it update the permissions properly?

Yes it should.

[wayner]

Originally Posted by jusjoken

Yes it should.

Great. The good thing is that I have been using my new V9 server for some of my extenders and everyone seems happy with it. The bad thing is that means that I can't play around with the server and do something like a reinstall during normal hours.