Office Automation on a remote computer from a Windows 2003 Server

L

LAURENTVVW

Hi,

Concerning the article Q257757 - INFO: "Considerations for Server-Side
Automation of Office", I've got a small question.

I alreday have the following (legacy) architecture working fine : a Windows
2003 Server building Word document and Excel documents through DCOM +
Automation on a remote Windows XP PRO computer where Office is installed. My
ASP application displays then in a new browser the new built documents.

The key point of this architecture is : OFFICE IS NOT INSTALLED on the W2003
Server, only Type Libaries for DCOM are known on this server (installation
previoulsy describeb int the no more existing Q244264 article) wich is fine.
The identity problems are also resolved through the identity set in the DCOM
application.

My question is the following : is this architecture allowed or proscribed by
Microsoft regarding the Q257757 article and knowing that :

- I met all the principal requirements and MS Office is not installed ont
the server and after 2 years in production I can say that this architecture
is absolutely stable (automation run Office Applications in "Quite Mode")

- this solution is no more mentioned in the Q257757 article and the Q244264
article no more exists ...


Thanks for your answer
 

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

Outlook Desktop (latest) stopped syncing IMAP accpounts from selfowned Mail server. 0
Office automation run on Terminal Server = Server-Side Automation? 0
Automating an Office app (Word, Excel, etc) from webpage 0
automating office on a server? 0
Word Automation on IIS 0
0x800A03EC error when call open or saveas in service on server 200 7
Server side automation, what a stupid idea of not supporting it :-( 0
MS word Automation error - server-side 1

Top