Hi

I'm not sure if there's a Dcom ng so forgive the cross-post maybe someone
will be able to help with this.

Have an executable component (actually a Desaware-built NT Service for those
who are familiar with that) that I need to deploy across approx 30
workstations. I want to deploy this component using the same InstallShield
project that deploys my standard (VB6) application.

This particular component requires to me to configure Dcom security before
it will work properly. Once I have run the Installshield installation
program on each workstation, I have to go around to each workstation and
configure the DCOM Launch, Access etc. permissions using DCOMCNFG32.exe.
This is all on Win2k Professional, btw.

Having done some research on MSDN a while back, I have come to understand
that DCOMCNFG32 merely writes a sequence of Registry keys to a certain
location to specify the permissions I want to set up. And that therefore, it
should be possible for me to write these keys myself (using the
Installshield package) instead of having to go and do it manually with
dcomcnfg32.

Can someone help me understand, how I can write these registry keys myself?
And where I need to put them? In other words, can someone point to me a
resource, or give me some basic answers, as to how to configure DCOM
security on components, at install time? Preferably in the context of using
an Installshield package?? I know it seems a rather oblique question, but it
must be possible, someone else must have faced this before!!

TIA

Robert Ellis Software Developer (MCSD) t-07984034050
(E-Mail Removed)

There are two articles on MSDN that might point you in the right direction
Robert:

Setting Processwide Security Through the Registry
Setting Processwide Security Through the DCOMCNFG

It's certainly possible because we do it ourselves

For instance, have a look at the key:

HKEY_LOCAL_MACHINE\Software\Classes\AppID\{GUID}

and the associated 'value':

AuthenticationLevel

Tony Proctor

"Robert E." <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi
>
> I'm not sure if there's a Dcom ng so forgive the cross-post maybe someone
> will be able to help with this.
>
> Have an executable component (actually a Desaware-built NT Service for
those
> who are familiar with that) that I need to deploy across approx 30
> workstations. I want to deploy this component using the same InstallShield
> project that deploys my standard (VB6) application.
>
> This particular component requires to me to configure Dcom security before
> it will work properly. Once I have run the Installshield installation
> program on each workstation, I have to go around to each workstation and
> configure the DCOM Launch, Access etc. permissions using DCOMCNFG32.exe.
> This is all on Win2k Professional, btw.
>
> Having done some research on MSDN a while back, I have come to understand
> that DCOMCNFG32 merely writes a sequence of Registry keys to a certain
> location to specify the permissions I want to set up. And that therefore,
it
> should be possible for me to write these keys myself (using the
> Installshield package) instead of having to go and do it manually with
> dcomcnfg32.
>
> Can someone help me understand, how I can write these registry keys
myself?
> And where I need to put them? In other words, can someone point to me a
> resource, or give me some basic answers, as to how to configure DCOM
> security on components, at install time? Preferably in the context of
using
> an Installshield package?? I know it seems a rather oblique question, but
it
> must be possible, someone else must have faced this before!!
>
> TIA
>
> Robert Ellis Software Developer (MCSD) t-07984034050
> (E-Mail Removed)
>
>

Thank you, Tony!
Will check them out....

Robert Ellis Software Developer (MCSD) t-07984034050
(E-Mail Removed)
"Tony Proctor" <tony_proctor@aimtechnology_NOSPAM.com> wrote in message
news:#Q#(E-Mail Removed)...
> There are two articles on MSDN that might point you in the right
direction
> Robert:
>
> Setting Processwide Security Through the Registry
> Setting Processwide Security Through the DCOMCNFG
>
> It's certainly possible because we do it ourselves
>
> For instance, have a look at the key:
>
> HKEY_LOCAL_MACHINE\Software\Classes\AppID\{GUID}
>
> and the associated 'value':
>
> AuthenticationLevel
>
> Tony Proctor
>
> "Robert E." <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi
> >
> > I'm not sure if there's a Dcom ng so forgive the cross-post maybe
someone
> > will be able to help with this.
> >
> > Have an executable component (actually a Desaware-built NT Service for
> those
> > who are familiar with that) that I need to deploy across approx 30
> > workstations. I want to deploy this component using the same
InstallShield
> > project that deploys my standard (VB6) application.
> >
> > This particular component requires to me to configure Dcom security
before
> > it will work properly. Once I have run the Installshield installation
> > program on each workstation, I have to go around to each workstation and
> > configure the DCOM Launch, Access etc. permissions using DCOMCNFG32.exe.
> > This is all on Win2k Professional, btw.
> >
> > Having done some research on MSDN a while back, I have come to
understand
> > that DCOMCNFG32 merely writes a sequence of Registry keys to a certain
> > location to specify the permissions I want to set up. And that
therefore,
> it
> > should be possible for me to write these keys myself (using the
> > Installshield package) instead of having to go and do it manually with
> > dcomcnfg32.
> >
> > Can someone help me understand, how I can write these registry keys
> myself?
> > And where I need to put them? In other words, can someone point to me a
> > resource, or give me some basic answers, as to how to configure DCOM
> > security on components, at install time? Preferably in the context of
> using
> > an Installshield package?? I know it seems a rather oblique question,
but
> it
> > must be possible, someone else must have faced this before!!
> >
> > TIA
> >
> > Robert Ellis Software Developer (MCSD) t-07984034050
> > (E-Mail Removed)
> >
> >
>
>