Access 2007 and Terminal Server users

[David W. Fenton]

Terminal Server doesn't run on SBS,

I know that. And it's yet another reason why I steer clients away
from SBS (which I consider a scam).

but I have successfully used WinConnect
with SBS:

http://www.thinsoftinc.com/index.aspx

For limited installations, it is a great product because it works
well with XP and with SBS.

I can't see using it in any other environment, though.

I haven't tried it with Office 2007 though. I haven't
personally tried running Office 2007 on any Terminal Services, but
the KB articles and some of the MVP private messages suggest that
it will only work with an Enterprise Edition license which uses a
volume license key.

I think you're mixing two different generations of Office licensing
terminology. My understanding is that "Enterprise Edition" was the
old name for it, before the volume licensing program was introduced
4 or 5 years ago. Now, "Enterprise Edition" is used only on the
top-end version of Win2K3 Server, so I think it's confusing to use
the term here.

The
Standard edition of Win2K3 Server should not be a problem. Several
MVPs have asked for a definitive clarification, but as of yet
nothing beyond the KB article quoted has been forthcoming. As soon
as I have an answer, I'll let you know.

I think one should no longer use the term "Enterprise Edition" as a
synonym for "volume licensing."

 

[David W. Fenton]

I don't know, but it stands to reason that the bits which keep it
from running are in Office, not the server or licensing. If it
doesn't detect the proper licenses, it doesn't run.

I thought the bits were in the licensing server which runs as a
client of WTS and of the apps involved. I guess the Office apps
would be clients of the licensing server, too.

As long as this affects only the version of Office I don't see a big
issue. Well, actually, I guess I do -- it depends on where it
matters, on the server Office installation or on the client
installation. If it's the latter (or both), then, yes, it's a major
problem. It would mean I could no longer work remotely unless my
clients provided me with a volume licensing installation.

 

[aaron.kempf]

I personally can't get Office 2007 to launch, not even on the local
desktop

it bitches about how it won't run on a terminal server.
EVEN WHEN I USE MY KVM TO GET TO THE MACHINE.

-Aaron

 

[aaron.kempf]

WHY THE **** DO YOU NEED TERMINAL?

TO RUN MDB?

LOSE THE GODDAMN TRAINING WHEELS, ADP WORKS _FINE_ OVER A VPN

-Aaron

 

[Arvin Meyer [MVP]]

I thought you *couldn't* use WTS to save buying licenses. I thought
that there were special licenses that you had to buy to allow users
who didn't have Office installed on their client PCs to allow them
to run Office on TS.

I can't be too sure because I've always had the proper licenses, so I've
never been challenged. I do believe, however, that WTS never checked for
licenses on the client machine. If that's true, the only way that you could
enforce licensing would be to do so from the client app. It seems to me that
there should be some way that small users who buy their servers preloaded
from the manufacturer, and their copies of Office from a local retail
dealer, or over ther internet need to be able to buy connection licenses
(CALs) for Office as well as the server. That doesn't appear to be the case.

 

[Arvin Meyer [MVP]]

There's validation on both ends. The CALs installed on the Terminal
Server control only the number of people who can connect
simultaneously (and who they are, either by machine or by logon).

CALs are for server connections, not application connections.

 

[Arvin Meyer [MVP]]

I think you're mixing two different generations of Office licensing
terminology. My understanding is that "Enterprise Edition" was the
old name for it, before the volume licensing program was introduced
4 or 5 years ago. Now, "Enterprise Edition" is used only on the
top-end version of Win2K3 Server, so I think it's confusing to use
the term here.

These are the versions of Office 2007:

Microsoft Office Professional Plus 2007
Microsoft Office Enterprise 2007
Microsoft Office Ultimate 2007
Microsoft Office Professional 2007
Microsoft Office Standard 2007
Microsoft Office Home and Student 2007
Microsoft Office Basic 2007

As you can see, there is an Enterprise Edition.

Please read the KB article for the exact language:

http://support.microsoft.com/kb/924622/en-us

 

[Tony Toews [MVP]]

No, actually, I don't. You have to have Office installed on the
client PC to run Office apps on the TS.

A client was running Citrix not TS but their client PCs were 500 Mhz
systems running NT 4.0. Office was not installed on those systems.

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Rick Brandt]

A client was running Citrix not TS but their client PCs were 500 Mhz
systems running NT 4.0. Office was not installed on those systems.

In fact for a few years we used Wyse (dumb) terminals for an entire department
and provided them a desktop on terminal servers. Those terminals contained no
software at all except for a simple OS that would load the TS client. They
could run anything on the TS that we gave them access to. While we were fully
licensed to have them run all the office apps, there was nothing that forced us
to have those licenses just to make it work.

The newer version of Office and Windows might have tighter hooks into each other
to prevent cheating now, but it certainly could be done prior to that.

 

[Tony Toews [MVP]]

In fact for a few years we used Wyse (dumb) terminals for an entire department
and provided them a desktop on terminal servers. Those terminals contained no
software at all except for a simple OS that would load the TS client. They
could run anything on the TS that we gave them access to. While we were fully
licensed to have them run all the office apps, there was nothing that forced us
to have those licenses just to make it work.

Ah, yes, a client is experimenting one of those devices. About the
size of a hard cover book with no fan. One feature he really likes
is that it will work from the motel room or behind a clients firewall
to hit his TS system. Thus consultants his employer hires can't
charge them $X per day for rent on their laptop. <smile>

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[aaron.kempf]

tony

you've got to admit that you didn't forecast; when you reccomended
that idiots kept MDB and used terminals-- that MS woudl screw terminal
users by requiring enterprise edition.

what is it, $699 per seat?

my ADP is a lot cheaper than that; and it works across wireless; it
works across the WAN, across the VPN

you're a flaming fucking pussy for shoving terminal down peoples
throats-- just because MDB sucks balls at networking

 

[Arvin Meyer [MVP]]

Thus consultants his employer hires can't
charge them $X per day for rent on their laptop. <smile>

<sarcasm>

And here I've been showing up on client sites with tools, laptops, a
projector, etc. and haven't been collecting rent. I've missed a revenue
stream <lol>

</sarcasm>

Times have sure changed from when a workman showed up at the jobsite with
the tools of his trade. AAMOF, I don't want to work on a client computer.
They are never better than my own.

Sheesh!