TS External Connector License?

[DMcCoy]

While digging into this TS asside someone has just insisted that you need an Office CAL for each student not for each device. This is madness surely no one else does this do they?

 

The MS license partners handbook clearly states that Office license are per device only! I wonder if suppliers read stuff from MS

[cookie_monster]

I wonder if suppliers read stuff from MS

 

Exactly i decided to have a read through the Office EULA and is specifies device all over the place with not a mention on per user.

 

Have you read the bible, i mean MS license partners handbook

[DMcCoy]

Exactly i decided to have a read through the Office EULA and is specifies device all over the place with not a mention on per user.

 

Have you read the bible, i mean MS license partners handbook

 

Bits of it although it's huge and still not very clear

 

https://partner.microsoft.com/40017359

[DMcCoy]

From the handbook

 

"Office functionality through Terminal Services — When accessing Office through a Windows Server 2003

(or 2003 R2) Terminal Server, a separate Office license must be acquired for each device."

 

Also see this http://download.microsoft.com/download/1/7/7/17745e4a-5d31-4de4-a416-07c646336d94/desktop_application_with_windows_server_terminal_services.doc

 

Full of lots of horrendous line like "Most retail (full packaged product) and original equipment manufacturer (OEM) licenses for products released in the 2007 release timeframe do not permit network use."

Edited May 9, 2008 by DMcCoy

[cookie_monster]

Nice one cheers i'll do some worshipping

 

For anyone else reading this, page 70 and 71 seem to contain the relevant info.

Edited May 9, 2008 by cookie_monster

[linescanner]

"Office functionality through Terminal Services — When accessing Office through a Windows Server 2003

(or 2003 R2) Terminal Server, a separate Office license must be acquired for each device."

 

Does the mean if using remote access technology, the only way to guarantee being legal is buy a license for ever computer on the planet

 

Bring on OpenOffice

[cookie_monster]

Not quite apparently but one for the server and one for the device (so only twice as many as should be required :-)). or do you not need to bother with a licence for the TS as long as the device has a licence. Ow ow ow

 

 

right it's friday and beer o'clock is approaching i think i'll leave this untill monday

Edited May 9, 2008 by cookie_monster

[DMcCoy]

Not quite apparently but one for the server and one for the device (so only twice as many as should be required :-)). or do you not need to bother with a licence for the TS as long as the device has a licence.

 

For office on TS, if you don't run it on the server console it doesn't actually need a license, no. Just every client that runs office on the TS. Now if you had multiple TS, each client would still only need the one office license.

 

So yes, you would need an office license for every machine ever if you wanted to be fully covered, although this would also allow those machines to use office locally, or on any other TS server

[cookie_monster]

I mentioned this earlier and wanted to provide the answer to where i read about it

 

even embracing Linux in this scenario and supplying a Linux version of RDP (they already have one trust me).

 

WUDSS has a Java based RDP client in case you want to manage it from a "non Windows" sytem.

 

http://windowsitpro.com/article/articleid/94794/windows-unified-data-storage-server-2003.html

[Geoff]

Yeah, but Storage Server is poo.

[cookie_monster]

Storage Server is but WUDSS is supposed to be much better.

 

Anyway i was more talking about the existence of a Linux compatible RDP client written by MS.

[Geoff]

rdesktop works just fine with 2k8 terminal server here.

[cookie_monster]

I'm really not talking on a tecnical level i'm more talking about the fact that MS are slowley bringing in foss compatibility into their products, some of this work is being done behind closed doors (in a just in case sort of way) but you can see evidence of it going on.

[Geoff]

Yes I know, it's called Embrace, extend and extinguish. A tried and tested Microsoft battleplan when faced with opponents they cannot buy out (previous victims: various Web Standards, Kerberos, LDAP, IM, TCP/IP, Java, Web Browser Plugins, ODF, SPF).

[cookie_monster]

Yes i'm well aware of it. Stop being so argumentative it's really not necessary I was merely pointing out this hidden technology, I just find it interesting trying to predict where MS will go next and as I said I think MS see TS as being a key product.

 

But i will ask when did they try to get rid of TCP/IP, i thought it was a well established standard that they embraced. It was hardly as if they had anywhere near a competing product with NetBEUI :-)

[Geoff]

I just find it interesting trying to predict where MS will go next and as I said I think MS see TS as being a key product.

 

MS are hardly a new entrant in the Terminal Services space, it's been in there since NT4 IIRC. Also be aware that TS is wrapped up with Virtualisation, something else MS ignored. Watching them scramble about in the face of VMwares market dominance is rather amusing though. The main issue MS have is the dent in their OS revenue by the 3/4/5 year upgrade cycle disappearing as everyone replaces their desktop PCs with thin clients running an embedded OS/Linux/etc.

 

While we're on the subject, another area where they are currently floundering around is in the ultra light laptop space (Ause eeePC, RM One, OLPC, etc.) where it looks like Linux is going to eat them for lunch unless they hack XP to bits so it runs on these devices and carry on supporting it for ages.

 

But i will ask when did they try to get rid of TCP/IP, i thought it was a well established standard that they embraced. It was hardly as if they had anywhere near a competing product with NetBEUI :-)

 

They never tried to 'get rid' of it, however they are forever tinkering with it and breaking it under the guise of security or performance. An infamous example would be the removal of raw sockets in XP SP2.

 

IanG on Tap: Raw Sockets Gone in XP SP2

[cookie_monster]

Yes i remember the sudden dissapearence of RAW sockets in SP2 :-)

 

I also remember the NT4 Terminal Server edition which was pretty poor but at least they embraced that early. IBM told the OS2 team to get lost when they suggested the idea so the team left and approached MS who gave them access to the OS2 - i mean NT3.1 source code. Of course that became Citrix and MS realised it was a good idea and released NT4 TS edition.

 

On the ultra light laptop space, that's exactly why XP suddenly has a new lease of life i suspect.

 

They tinker with Kerberos as well but it's still essentially Kerberos just it's a smidge undocumented as per usual.

Edited May 12, 2008 by cookie_monster