Access 2007 and Terminal Server users

[Dirtbike]

So I see where Office 07 won't fly TS. If I have Access 2007 with all the
developer extensions and I create a package for deployment, can I then allow
TS users run my apps on my 2003 Server? Thanks for the help.
Are the Access 2007 Developer Extensions available now? Where?

 

[Douglas J. Steele]

I don't know the answer to your first question, I'm afraid, but the Access
2007 Developer Extensions aren't available quite yet.

The good news, though, is that they'll be free once they're released. Check
http://blogs.msdn.com/clintcovingto...me-and-developer-extensions-will-be-free.aspx
for details.

 

[Arvin Meyer [MVP]]

So I see where Office 07 won't fly TS. If I have Access 2007 with all the
developer extensions and I create a package for deployment, can I then
allow
TS users run my apps on my 2003 Server? Thanks for the help.
Are the Access 2007 Developer Extensions available now? Where?

As Douglas stated, the Developer extensions aren't available yet. I asked
the same question as you of the Access programming team just last week, and
I haven't received an answer yet.

I'll go out on a limb and say that I doubt it unless you create the package
using an MDB on an Access 2003 or earlier machine. I hope I'm wrong though
because I have been using Terminal Servers fairly extensively as of late.

 

[Albert D. Kallal]

So I see where Office 07 won't fly TS.

Is this true? Do you have a link, or article that says so? I find it hard to
believe that office will not work with TS....

 

[Larry Linson]

Is this true? Do you have a link, or article that
says so? I find it hard to believe that office will
not work with TS....

Nothing that comes from the mysterious minds in the world of computing
should come as a _surprise_, Albert. <SMILE>

Larry

 

[Tony Toews [MVP]]

So I see where Office 07 won't fly TS.

Apparently you need some kind of volume licensing version of Office or
something like that. I misremember the details though.

As far as the A2007 and runtime I suspect it would still work but no
guarantees until it's out and we can test it.

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

 

[Arvin Meyer [MVP]]

It only runs with the Enterprise Edition and with a volume license key (IOW,
forget about small business using it)

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

 

[aaron.kempf]

in other words; if you've listened to MDB _FAGS_ like these idiots
around here-- you're going to get stuck paying 50 grand

much easier to use VPN and Access Data Projects

I mean diz-uhhhhhh!

-Aaron

 

[David W. Fenton]

I'll go out on a limb and say that I doubt it unless you create
the package using an MDB on an Access 2003 or earlier machine. I
hope I'm wrong though because I have been using Terminal Servers
fairly extensively as of late.

Let me get this straight: A2K7 doesn't run on WTS? Or it won't run
with an ACCDB? Or both?

What are they thinking? They've invested all this effort in
developing WTS and now they are making it not work for their
flagship applications? Access more than any other Office app greatly
benefits from being run on WTS because of the data sharing issues.

Is this perhaps just a tactic to force people to use Sharepoint
instead?

If so, I say good riddance to Office 2007!

 

[David W. Fenton]

It only runs with the Enterprise Edition and with a volume license
key (IOW, forget about small business using it)

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

That article doesn't say it's limited to Enterprise Edition of
Windows Server, but that it's limited to the volume licensing
editions of Office. I don't know about the pricing for O2K7 on that,
but the prices were not bad even for small batches of licenses for
O2K3 just a couple of years ago. So, I don't really see that as a
terrible issue.

If it's limited to the top-end version of Windows Server, though,
that's a major problem. Small Business Edition has never run WTS
(beyond the built-in two admin licenses), but Standard always has.

Can you confirm that volume licensing O2K7 won't run on Win2K3
Server Standard Edition?

 

[David W. Fenton]

It only runs with the Enterprise Edition and with a volume license
key (IOW, forget about small business using it)

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

BTW, what happens with Office licensing when running Winconnect
instead of WTS?

 

[aaron.kempf]

microsoft is on mother fucking crack and I've been saying this for a
few years now.

I urge all you script kids to move to Dreamweaver, PHP and mySQL.

-Aaron

 

[aaron.kempf]

listen dipshit

I am SO SORRY that you're crippled and retarded and you've been
listening to these diseased dipshits for the past few years.

RELYING ON TERMINAL SERVICES INSTEAD OF USING ADP WAS A SHORT-SIGHTED
BANDAID

LOSE THE MOTHER FUCKING TRAINING WHEELS AND LEARN HOW TO WRITE
DATABASES THAT WORK ACROSS _ANY_ NETWORK

 

[Albert D. Kallal]

I don't know about the pricing for O2K7 on that,

but the prices were not bad even for small batches of licenses for
O2K3 just a couple of years ago. So, I don't really see that as a
terrible issue.

yes, not too bad, but you can see how users of TS were getting around
licensing issues.

I always thought that if you are using cals, that the licensing server would
not allow users to unlimited run office anyway..I just not 100% sure on
this.

Can you confirm that volume licensing O2K7 won't run on Win2K3
Server Standard Edition?

My impression from the article that is anything with volume licensing WILL
work...but, don't quote me on this...

I was never really aware how the licensing server for TS worked with office
installed anyway..but, the use of volume licensing makes sense here (I was
not aware of this new change...and not been following this issue that close
of late).

 

[Rick Brandt]

yes, not too bad, but you can see how users of TS were getting around
licensing issues.

I always thought that if you are using cals, that the licensing
server would not allow users to unlimited run office anyway..I just
not 100% sure on this.

Just as with Windows activation, proper licensing of apps run on TS was on the
honor system and MS has concluded that too many people were not being honorable
about it. Makes perfect sense to me.

 

[Arvin Meyer [MVP]]

Terminal Server doesn't run on SBS, 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 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. 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.

 

[Arvin Meyer [MVP]]

BTW, what happens with Office licensing when running Winconnect
instead of WTS?

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.

 

[Arvin Meyer [MVP]]

I was never really aware how the licensing server for TS worked with
office installed anyway..but, the use of volume licensing makes sense here
(I was not aware of this new change...and not been following this issue
that close of late).

I never paid much attention to it either since all of our users had full
local copies of Office Pro, and therefore had a license for each machine. We
never used WTS to save licenses, rather it was only used to make remote
connections to our databases.

 

[David W. Fenton]

yes, not too bad, but you can see how users of TS were getting
around licensing issues.

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

I always thought that if you are using cals, that the licensing
server would not allow users to unlimited run office anyway..I
just not 100% sure on this.

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).

My impression from the article that is anything with volume
licensing WILL work...but, don't quote me on this...

I was never really aware how the licensing server for TS worked
with office installed anyway..but, the use of volume licensing
makes sense here (I was not aware of this new change...and not
been following this issue that close of late).

As long as it still runs on Windows Server Standard I think it's not
really a major change.

 

[David W. Fenton]

I never paid much attention to it either since all of our users
had full local copies of Office Pro, and therefore had a license
for each machine. We never used WTS to save licenses, rather it
was only used to make remote connections to our databases.

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.