Re: Privileges needed to instantiate COM objects

"nano2k" <adrian.rotaru@xxxxxxxxxxx> wrote in message
news:306fa8d3-37ec-4173-87db-173766c9afad@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi

I develop a webservice that, from time to time, needs to instantiate a
Word application and to create a document locally.
The webservice is running under the default credentials (ASPNET /
NETWORK SERVICES) but this doesn't provide enough rights to manipulate
Word.
The solution is to impersonate the default user with anothe, more
powerful, user.
What is the minimum access rights that a user should have to work as
described above? I don't want to grant administrative privileges to
this user. Except only if this is mandatory.

Note: I don't want to change the default accounts that dotnet runs by
default.

First of all, are you aware that Microsoft doesn't support the instantiation
of Office applications from a server? It's not just a licensing thing - it
doesn't work reliably. They weren't designed to be run that way.

Secondly, you'll need to look in the COM configuration with the Component
Services applet (Start->Administrative Tools->Component Services). Expand
the "Component Services", and "Computers" nodes. Right-click "My Computer"
and choose Properties. Click on the "COM Security" tab and click the "Edit
Default" button under "Launch and Activation Permissions". Configure it to
allow launch by the users you need. You may want to create a Windows
security group to place those users in, then grant launch permissions to
that group.
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer


.

Loading