Running as a client

[Panzer]

So, other than making the changes to the startsage script as detailed in the FAQ, are there any other changes that need to be made when trying to connect to a windows server?

[AboveUnrefined]

Nope, I don't think so... maybe you could add where the server is but I think it'd pick it right up.

[Panzer]

Hmm, whenever I try either as a client or a 2nd slave server to my windows servers, I receive the message Bad License in sageout and in the debug log "Client License Piracy". I went through the activation without any problems and looking at the activkey file afterwards it's exactly as from the confirmation email.

Also this is using the latest iso burned yesterday afternoon and the last windows beta.

[skeltonl]

I have similar issues after editing the startsage script to make it a client - while the splash screen screen comes up as a SageTV client and automatically finds my windows server it then craps out because of licensing issues. I am wondering if the startsage script needs to be edited before the install so the activation is for a client and not a server?

[LostInSpace]

How did you edit the startsage script?
I did not find any sagetv Sage.properties in that file...
Thanks for your help

Ferdinand

[laurenglenn]

Originally Posted by LostInSpace

How did you edit the startsage script?
I did not find any sagetv Sage.properties in that file...
Thanks for your help

Ferdinand

"nano startsage"

Sage.properties is located in /opt/sagetv/usr/

Lauren