Office 2007 MSDN on Server 2003 - Terminal Server error

G

Greg Stewart

Installed Office 2007 over Office 2003 on my Windows Server 2003 R2 Std Ed
test machine using MSDN key.

When I launched any office program, I got this dialog box:

"This copy of <product> cannot be used on Terminal Server. Please contact
your local authorized Microsoft retailer for more information."

Needless to say, nothing would run.

Issues:

1. I presume this is a license key issue and not a product issue. Can MSDN
users get an Office 2007 license key that will allow it to run on Windows
Server 2003 R2 with Terminal Server enabled?

2. When I uninstalled Office 2007 and ran a "detect and repair" on Office
2003 (SP2), Outlook 2003 wouldn't run because MAPI32.DLL was missing or
corrupt. it kept prompting me to reinstall Outlook but no amount of "detect
and repair" or "reinstall" would fix it. To fix this, I had to do an
add/remove components on Office 2003 and specifically install "Outlook
Messaging Components" under "Microsoft Office Outlook".
 
P

Patrick Schmid [MVP]

During the beta, Office 2007 would only install on a terminal server if
you used a volume license key.

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007: http://pschmid.net/office2007/customize
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed
 
P

Patrick Schmid [MVP]

During the beta, Office 2007 would only install on a terminal server if
you used a volume license key.

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007: http://pschmid.net/office2007/customize
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed
 
P

Patrick Schmid [MVP]

During the beta, Office 2007 would only install on a terminal server if
you used a volume license key.

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007: http://pschmid.net/office2007/customize
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed
 
P

Patrick Schmid [MVP]

During the beta, Office 2007 would only install on a terminal server if
you used a volume license key.

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007: http://pschmid.net/office2007/customize
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed
 
B

Bob Buckland ?:-\)

Hi Greg,

For the 2007 Office system, only Enterprise/Volume license key copies will be able to install and run on Windows Terminal
Server/services.
http://support.microsoft.com/kb/924622/en-us?FR=1

============
Installed Office 2007 over Office 2003 on my Windows Server 2003 R2 Std Ed test machine using MSDN key. >>
--

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

When I launched any office program, I got this dialog box:

"This copy of <product> cannot be used on Terminal Server. Please contact
your local authorized Microsoft retailer for more information."

Needless to say, nothing would run.

Issues:

1. I presume this is a license key issue and not a product issue. Can MSDN
users get an Office 2007 license key that will allow it to run on Windows
Server 2003 R2 with Terminal Server enabled?

2. When I uninstalled Office 2007 and ran a "detect and repair" on Office
2003 (SP2), Outlook 2003 wouldn't run because MAPI32.DLL was missing or
corrupt. it kept prompting me to reinstall Outlook but no amount of "detect
and repair" or "reinstall" would fix it. To fix this, I had to do an
add/remove components on Office 2003 and specifically install "Outlook
Messaging Components" under "Microsoft Office Outlook".
 
B

Bob Buckland ?:-\)

Hi Greg,

For the 2007 Office system, only Enterprise/Volume license key copies will be able to install and run on Windows Terminal
Server/services.
http://support.microsoft.com/kb/924622/en-us?FR=1

============
Installed Office 2007 over Office 2003 on my Windows Server 2003 R2 Std Ed test machine using MSDN key. >>
--

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

When I launched any office program, I got this dialog box:

"This copy of <product> cannot be used on Terminal Server. Please contact
your local authorized Microsoft retailer for more information."

Needless to say, nothing would run.

Issues:

1. I presume this is a license key issue and not a product issue. Can MSDN
users get an Office 2007 license key that will allow it to run on Windows
Server 2003 R2 with Terminal Server enabled?

2. When I uninstalled Office 2007 and ran a "detect and repair" on Office
2003 (SP2), Outlook 2003 wouldn't run because MAPI32.DLL was missing or
corrupt. it kept prompting me to reinstall Outlook but no amount of "detect
and repair" or "reinstall" would fix it. To fix this, I had to do an
add/remove components on Office 2003 and specifically install "Outlook
Messaging Components" under "Microsoft Office Outlook".
 
B

Bob Buckland ?:-\)

Hi Greg,

For the 2007 Office system, only Enterprise/Volume license key copies will be able to install and run on Windows Terminal
Server/services.
http://support.microsoft.com/kb/924622/en-us?FR=1

============
Installed Office 2007 over Office 2003 on my Windows Server 2003 R2 Std Ed test machine using MSDN key. >>
--

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

When I launched any office program, I got this dialog box:

"This copy of <product> cannot be used on Terminal Server. Please contact
your local authorized Microsoft retailer for more information."

Needless to say, nothing would run.

Issues:

1. I presume this is a license key issue and not a product issue. Can MSDN
users get an Office 2007 license key that will allow it to run on Windows
Server 2003 R2 with Terminal Server enabled?

2. When I uninstalled Office 2007 and ran a "detect and repair" on Office
2003 (SP2), Outlook 2003 wouldn't run because MAPI32.DLL was missing or
corrupt. it kept prompting me to reinstall Outlook but no amount of "detect
and repair" or "reinstall" would fix it. To fix this, I had to do an
add/remove components on Office 2003 and specifically install "Outlook
Messaging Components" under "Microsoft Office Outlook".
 
B

Bob Buckland ?:-\)

Hi Greg,

For the 2007 Office system, only Enterprise/Volume license key copies will be able to install and run on Windows Terminal
Server/services.
http://support.microsoft.com/kb/924622/en-us?FR=1

============
Installed Office 2007 over Office 2003 on my Windows Server 2003 R2 Std Ed test machine using MSDN key. >>
--

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

When I launched any office program, I got this dialog box:

"This copy of <product> cannot be used on Terminal Server. Please contact
your local authorized Microsoft retailer for more information."

Needless to say, nothing would run.

Issues:

1. I presume this is a license key issue and not a product issue. Can MSDN
users get an Office 2007 license key that will allow it to run on Windows
Server 2003 R2 with Terminal Server enabled?

2. When I uninstalled Office 2007 and ran a "detect and repair" on Office
2003 (SP2), Outlook 2003 wouldn't run because MAPI32.DLL was missing or
corrupt. it kept prompting me to reinstall Outlook but no amount of "detect
and repair" or "reinstall" would fix it. To fix this, I had to do an
add/remove components on Office 2003 and specifically install "Outlook
Messaging Components" under "Microsoft Office Outlook".
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Office 2010 viewers and Terminal Services 2008 R2 1
office 2010 install error. 2
MS Office 2007 on terminal server. 1
Office 2010 Visio Pro or Standard installation problem to terminal 0
can't run office 2000 on terminal server 2003 3
Office 2003/2007 on terminal server 2
Microsoft Office Enterprise 2007 won't install on terminal server 1
Office 2007 on Terminal Server 1

Top