Sage on Windows Server 2003?

[Crashless]

Has anyone tried to use sage on a windows server 2003 or 2000 system?

I'm trying to plan out a home automation server, and I'd like to use the box I made for sage. I'm mainly after the terminal services to setup a thin webtablet as the front end, and allow the expansion to other rooms using the same server and additional wifi tablets.

I know I could do this with XP pro, but then I would be limited to one remote connection. I believe that server 2003 has the same basic architecture of XP (and the 2000 server, is the same as the 2000pro.) But has anyone tried this? If so, I'm also looking for a good (cheap) webtablet to use.

I'm looking for an 800x600 screen, used is okay. I really like the epods but it only has a 640x480 screen and that won't fit the sage ui.

Thanks,

[salsbst]

I was ultimately unable to get 2x250s installed on win2k server.

2x250s installed and running with 2.0.13 on win2k3 server. No problems. It runs my websites in the background.

[Crashless]

very cool. thanks. silly question: where'd you buy the os? everywhere I go it's almost $1k, and there are 50 different versions with CALs and COAs. I can't figure out where to go.

thanks

[OPTIMO]

Originally posted by Crashless
Has anyone tried to use sage on a windows server 2003 or 2000 system?

I'm trying to plan out a home automation server, and I'd like to use the box I made for sage. I'm mainly after the terminal services to setup a thin webtablet as the front end, and allow the expansion to other rooms using the same server and additional wifi tablets.

I know I could do this with XP pro, but then I would be limited to one remote connection. I believe that server 2003 has the same basic architecture of XP (and the 2000 server, is the same as the 2000pro.) But has anyone tried this? If so, I'm also looking for a good (cheap) webtablet to use.

I'm looking for an 800x600 screen, used is okay. I really like the epods but it only has a 640x480 screen and that won't fit the sage ui.

Thanks,

You're still going to be limited with a 2003 Server regarding connections unless you have Terminal Services Licensing.

Although a Metaframe solution might be sweet....

[mikejaner]

Yeah, you have to purchase separate licenses for each computer connecting via Terminal Services. It does not matter how many client licenses come with Server. AFAIK, it's not cheap per computer either.
You would be able to pull off 3 simultaneous sessions via Remote Desktop Administration, but you will not be able to use the server at the console at the same time as the third session.

mikejaner

[OPTIMO]

Yeah just go all out and implement this:

[OPTIMO]

Originally posted by Crashless
very cool. thanks. silly question: where'd you buy the os? everywhere I go it's almost $1k, and there are 50 different versions with CALs and COAs. I can't figure out where to go.

thanks

I work for a Microsoft Platinum partner so I find them.

2003 Enterprise server in French, Spanish, English, German.....

I chose not to run it on a 2K3 server because:

- I don't want the overhead associated with a server OS considering that some of the video encoding/decoding can be processor intensive (even though I have the pvr-350).
- I already have (2) 2003 Ent Servers, one is my Domain Controller/File Server/DDNS/DHCP and the other is a backup AD box.

- (XP) I also have a game machine (2500 Barton oc'd with 1gb ddr dual channel, ati 9500 np unlocked)

- (2KPro)Audio recording station hooked up to my turn tables (with an Audiophile 2496 card, Cubase, Acid Pro and Sound Forge).

- ..and two XP laptops with wireless G.

[/bragging].

I also have my wireless running on a separate subnet just in case someone gets through the measley WEP.

Back to your scenario - what's wrong with using a central server with a bunch of Sage clients? That's what I'm using now without any major complaints.

You might want to see if Proxy or PCAnywhere could be a better solution for you.

Good luck finding cheap tablet PCs. I've tested a couple at a previous job and they are pretty fun to use, but I'd still rather have a laptop.

[OPTIMO]

One more run on post...

The reason I was originally interested in KnoppMyth is because it has a web-based mangement tool. You basically point your browser to an internal web paged served by an Apache Server w/JSP Tomcat.

My plan is to be able to remotely admin my box, in case I forgot to record something while I'm at work or on the road.

1) Remote connection into 2003 Server NOT running IIS
2) Launch a local instance of IE
3) Browse to an internal web address
3a) Web server only hosts internal addresses on the specified subnets)
3b) Requires a web based manager which I don't think Sage has yet
4) Set my shows to record then log out of my session

The end.

[Crashless]

Originally posted by mikejaner
Yeah, you have to purchase separate licenses for each computer connecting via Terminal Services. It does not matter how many client licenses come with Server. AFAIK, it's not cheap per computer either.
You would be able to pull off 3 simultaneous sessions via Remote Desktop Administration, but you will not be able to use the server at the console at the same time as the third session.

mikejaner

I figured it wouldn't be cheap to implement. But how cool would it be?

I'm interested to learn about the limitations though. I thought that server 2003 could have unlimited RDP sessions and only XP pro was disabled at the console when an RDP session was started. I've seens CAL packs of 5 for around $650 though. Pretty steep.

I've been looking for other solutions, but have only come up with this. I might end up using XP Pro and a smart display until I can afford a proper setup. But this has to have been done already. I've seen home entertainment companies advertising it, but haven't seen any home-brew how-tos.

Anyone have some links to share? or is there no such thing as a cheap solution for what I want to do?

Thanks

[Crashless]

Now that I'm not looking at this thread on my treo, I can type better. I _could_ run a bunch of sage clients (and eventually will) but I'm trying to future-proof my system, as I'm planing on setting up a home automation server with the system that is currently my sage server at the core. So, right now I'm looking at the progear tablet pc (yes, the old one) as a possible front end using netmeeting's remote desktop.

This would allow me to connect and directly control my main TV as I would w/ a remote. Using some yet undetermined home automation software, I'll be able to setup the tablet as a remote for the house.

As things expand, I hope to find a way to add additional tablets in different rooms as standalone monitors using sage client (but that's much later). But mainly what I'm after is a wireless montior for my sage box that won't be a completely dumb terminal (i've given up on the terminal services idea, it's too limiting).

Anyone have cheap tablets to reccomend? Hopefully in the sub $400 range. Used is cool.

Thanks for the help.

And cool setup OPTIMO, BTW.

[KJake]

Terminal Services and RD are two separate things in Server 2003. You only need CALs for Terminal Services AFAIK.

Remember how 2000 Server let you choose Application Server or Remote Administration? Now, in 2003 Server, RD is the Remote Administration and Terminal Services is only used for Application serving.

My Standard Edition only allows 2 connections with RD. Are you saying that there are RD CALs to up that limit?

[mikejaner]

KJake, your server will allow three session, you probably just don't know it.

You can have up to two Remote Administration sessions by logging on machines using the Remote Desktop Client.

You can also log on to the console using the /console flag (mstsc /console), it's just that you can't use your console locally, when logged into the console remotely.

mikejaner

[Crashless]

Originally posted by mikejaner
You can also log on to the console using the /console flag (mstsc /console), it's just that you can't use your console locally, when logged into the console remotely.

mikejaner

Ah ha! Perfect. This is exactly what I want to do. One tablet that takes control of the console, and up to two others that are served apps separately from the console. This way, when the MVP client is released, I can run one instance under the two extra users, and with local rendering of the GUI, use the tablets as remotes for the TVs!

Oh so excited. Now I just need to find the perfect tablet.

[chako]

Hey, I've been using Windows Server 2003 for months now and Sage is working perfectly. I actually am using the three logins (2 Terminals and 1 Console) from an office far away from my house. I can login to the console, open sage tv and set it to record whatever I want, resolve conflicts, etc. You get the idea. I LOVE it!
Feel free to contact me for more details on it. There are quite a few things you need to know before makeing the change.

Ken

[jmossman]

Originally posted by chako
Hey, I've been using Windows Server 2003 for months now and Sage is working perfectly. I actually am using the three logins (2 Terminals and 1 Console) from an office far away from my house. I can login to the console, open sage tv and set it to record whatever I want, resolve conflicts, etc. You get the idea. I LOVE it!
Feel free to contact me for more details on it. There are quite a few things you need to know before makeing the change.

Ken

I would like to hear about those details you speak of....

[chako]

I wish I could remember exactly what I was thinking when I wrote that. I think it had something to do with enabling all the hardware acceleration, directx, etc. Also, you will need to know how to get to the console. Just click on your start button (windows xp computer) and go to Run. Then type in mstsc /console and you're set. It will open up the remote desktop login window where you can type in the address of the server. Please feel free to ask any questions about this as you're implementing it. I've run into almost every error you can so I should be able to help.

chako

[insomniac]

To elaborate...

You have to enable the audio service, and then go into directx config (dxdiag) and enable all acceleration. To connect to the console of a machine, you run the command:
mstsc -v:COMPUTERNAME /F -console

use xp drivers to get all your stuff working...that should be it!

I.

Originally posted by chako
I wish I could remember exactly what I was thinking when I wrote that. I think it had something to do with enabling all the hardware acceleration, directx, etc. Also, you will need to know how to get to the console. Just click on your start button (windows xp computer) and go to Run. Then type in mstsc /console and you're set. It will open up the remote desktop login window where you can type in the address of the server. Please feel free to ask any questions about this as you're implementing it. I've run into almost every error you can so I should be able to help.

chako

[chako]

Yeah, that's it! Stuff like that. Thanks for the info.