2k8 or 2k3 server standard - just need the ts and vpn areas

[bob4432]

is one of these better than the other? i need it because of ts and vpn or else xp would be fine. prices are pretty close between the 2, so just wondering a reason go either way?

i like that 2k3 has been around for some time and figured it was mature, so how is ms doing w/ 2k8 and any issues it may have? also, how is hardware support for 2k8 vs 2k3?

 

[yinan]

Terminal Server 2008 is a great version of the server OS. If I had a choice I would use 2008 over 2003. Terminal services 2008 is nice as well and really easy to set up. If you want to test it out get a technet direct subscription and download it.

 

[RebateMonger]

Well, you don't really even need a Technet Subscription to test it, since trial versions of Server 2008 are good for about six months.

If this is for a business with a lot of users, licensing issues might come into effect. Depending on your licensing situation, you could add probably another Server 2003 without additional licenses (except for TS licenses).

 

[loup garou]

Depends on what you need TS for, but TS in 2008 is really awesome. RemoteApps are great and easy to set up.

 

[bob4432]

low amount of users - but they are remote and the software we are looking at using needs ts for remote access which is all this will be. to be honest, server software is overkill for what we need, but it is the only way to get 3-4 simultaneous connections in via either ts or vpn.

also, no current server software, so it will be a new setup.

i d/l 2008 standard trial and was getting ready to install it.

i haven't messed w/ server stuff since server2k and that was up to ~2004, then it was all in-house for the needs - i need to do some serious reading w/ the remote access stuff but i am sure i can get it all squared away 🙂

usage will be 100% for remote use of 1 app....i wish these companies would make their software have a ssl encrypted web interface and go that route, but no such luck..., so her i am w/ this.

 

[loup garou]

If you're just providing terminal session for a single app, 2008 is the way to go IMO. Install your app as a remote app and you won't have to worry about teaching users about remote desktops, etc. You can just send them the rdp file and when they click it, it looks like another app on their desktop. However, you will have to teach them about the remote open/save/etc windows and how to navigate to their local drives/folders if necessary. Oh and another huge advantage of 2008 is the Easy Print driver...makes using local printers from remote apps SO much easier.

 

[RebateMonger]

Yeah, if Remote Apps in 2008 work for you, they are great. It allows the User to make use of multiple monitors, which the older Terminal Services client didn't do.

 

[bob4432]

Originally posted by: loup garou
If you're just providing terminal session for a single app, 2008 is the way to go IMO. Install your app as a remote app and you won't have to worry about teaching users about remote desktops, etc. You can just send them the rdp file and when they click it, it looks like another app on their desktop. However, you will have to teach them about the remote open/save/etc windows and how to navigate to their local drives/folders if necessary. Oh and another huge advantage of 2008 is the Easy Print driver...makes using local printers from remote apps SO much easier.

sounds good. basically everything they will need will be in the software, so i am assuming it would be save within the software on the server machine correct? the easier it is the less headaches i have w/ them 🙂

 

[bob4432]

Originally posted by: RebateMonger
Yeah, if Remote Apps in 2008 work for you, they are great. It allows the User to make use of multiple monitros, which the older Terminal Services client didn't do.

thanks for the info. users will be on laptops connected via either att 3g cards or spring ev-do cards. there may be 1 or 2 machines at the location connected via lan, so i need to verify that the softwares can handle both ts and regular lan connections at the same time.

thing that is a pita is that the software people don't have a demo.....personally not too happy about that, they just say it needs ts for remote use....

 

[loup garou]

Originally posted by: bob4432

Originally posted by: loup garou
If you're just providing terminal session for a single app, 2008 is the way to go IMO. Install your app as a remote app and you won't have to worry about teaching users about remote desktops, etc. You can just send them the rdp file and when they click it, it looks like another app on their desktop. However, you will have to teach them about the remote open/save/etc windows and how to navigate to their local drives/folders if necessary. Oh and another huge advantage of 2008 is the Easy Print driver...makes using local printers from remote apps SO much easier.

sounds good. basically everything they will need will be in the software, so i am assuming it would be save within the software on the server machine correct? the easier it is the less headaches i have w/ them 🙂

I can't really say without using the software, but say it's something like a database where input is committed just by entering (or even form submission). Obviously, where that data is going would be transparent to the user -- it was just being "saved." However, say it's something like Word. The user types up a document and goes to File>Save. As a remote app, first of all, they'll be presented with a Vista/Server08 save dialog which may be foreign to them....something you'll have to go over with them. Secondly, if they want to save the document on the machine they are working on and not the TS server (or wherever you have set the default save location), you'll have to teach them about connected drives and how to get to their Documents, etc folders from the connected drives (ie, navigating through the file system). I'm pretty sure you can set default save locations to connected drives through scripting/policy, but I've never done it as we always have stuff default to fileshares at the home office where the TSes are. It sounds like your app is more like my former example, though, so hopefully less user training will need to be done on your part.

 

[bob4432]

Originally posted by: loup garou

Originally posted by: bob4432

Originally posted by: loup garou
If you're just providing terminal session for a single app, 2008 is the way to go IMO. Install your app as a remote app and you won't have to worry about teaching users about remote desktops, etc. You can just send them the rdp file and when they click it, it looks like another app on their desktop. However, you will have to teach them about the remote open/save/etc windows and how to navigate to their local drives/folders if necessary. Oh and another huge advantage of 2008 is the Easy Print driver...makes using local printers from remote apps SO much easier.

sounds good. basically everything they will need will be in the software, so i am assuming it would be save within the software on the server machine correct? the easier it is the less headaches i have w/ them 🙂

I can't really say without using the software, but say it's something like a database where input is committed just by entering (or even form submission). Obviously, where that data is going would be transparent to the user -- it was just being "saved." However, say it's something like Word. The user types up a document and goes to File>Save. As a remote app, first of all, they'll be presented with a Vista/Server08 save dialog which may be foreign to them....something you'll have to go over with them. Secondly, if they want to save the document on the machine they are working on and not the TS server (or wherever you have set the default save location), you'll have to teach them about connected drives and how to get to their Documents, etc folders from the connected drives (ie, navigating through the file system). I'm pretty sure you can set default save locations to connected drives through scripting/policy, but I've never done it as we always have stuff default to fileshares at the home office where the TSes are. It sounds like your app is more like my former example, though, so hopefully less user training will need to be done on your part.

thanks for the info again 🙂. i just went over their requirements list, and they recommend 2003 sbs (must have not had my glasses on when i first read it), but i have contacted them to see if there are any issues w/ 2k8.

another question - this software recommends for a server on a lan - basic c2d setup, but if you use ts it recommends dual xeon single cores @ 3+GHz (the 2MB cache ones). is there that much difference between a xeon and c2d, hell a 8400 has more cache than that? is there some architecture within the chip that i am not understanding or was this "requirement" page written by a marketing person? hell, wouldn't one of the last gen 45nm quads be faster?

last, is it abnormal for me to want a running demo so i can compare different types of the software? there are a few major players in the arena but nobody offers a demo, to me this seems a bit weird as this software is in the upper thousands to lower ten thousands of $$. i have such a hard time recommending something when they won't let me use it and really get in and test it. basically all i get is to test it on a sales persons laptop.... hell, i have never known of software costing this much that doesn't have a demo.