Re: Com server setup

From: Brian Nielsen (BrianNielsen_at_discussions.microsoft.com)
Date: 09/01/05 

Date: Thu, 1 Sep 2005 03:00:27 -0700

Hi Adi

I found out that DCOMPerm do actually work in Windows 2003 Server so it is
still possible to set launch and access permissions using this tool.

If you have installed Service Pack 1 on your server, you must be aware of
the extra security check that has been added when accessing COM applications.
If you right-click on My Computer in Component Services and choose
Properties. Then go to COM Security tab and there is a limit button which
controls the additional check. The default (in SP1) is that it is not
possible for others than Administrator to launch com components on the server
from remote.

There is a catch in changing the limits which you can read about on
Microsofts site. Limits are a machine wide check and therefore changes made
here will affect all COM components.

Hope it helps

Brian

"Adi" wrote:

> Hi Brian,
>
> I'm facing the same problem now. Did you find an answer to your
> question?
>
> Bets Regards,
> Adi
>
> Brian Nielsen wrote:
> > Hi People
> >
> > We have just upgraded to Windows 2003 and now we need to make a com server
> > application run on this new platform.
> >
> > I can register the application (and see it show up in dcomcnfg).
> >
> > The problem is that I need to set the identity the compoenent is run as, and
> > I need to set who has launch permissions to the compoent.
> >
> > This I have to do using etiher a command-line tool or programmatic (It is to
> > be used in a unattended installation).
> >
> > In Windows 2000 I used the utility called DCOMPerm library, but it doesn't
> > seem to work under Windows 2003.
> >
> > I hope someone has an idea of how I can do it.
> >
> > Best Regards
> > Brian
>
>