The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.

Deploying COM Object in Active Directory [Solved]

bowenbowen Sup?Registered User regular
edited April 2010 in Help / Advice Forum
Does anyone know how I can deploy and register a COM object in AD?

I've got a COM object that I've got to deploy to all of the domain and I'm really not looking forward to having to do it manually.

not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
bowen on

Posts

  • PirateJonPirateJon Registered User regular
    edited April 2010
    You have that in an exported EXE right? That's step one. Step two is push it out via AD's software distribution.

    PirateJon on
    all perfectionists are mediocre in their own eyes
  • bowenbowen Sup? Registered User regular
    edited April 2010
    Hmm, the project was given to us is a DLL. I should be able to get an EXE from it though.

    That's the easy part, the hard part is the actual process of pushing it out. How do I do that, exactly?

    bowen on
    not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
  • PirateJonPirateJon Registered User regular
    edited April 2010
    Typically when I was dealing with COM/DCOM I'd get a package from the dev's off their production servers to install on the clients. Like so. http://technet.microsoft.com/en-us/library/cc750201.aspx

    Once you have that exe package then it's the software distribution time. I have had issues with bighuge apps via AD (office, I'm looking at you) but most stuff works ok.
    http://support.microsoft.com/kb/816102
    Although if you have SMS/SCM or some other software for patches you could use that as well. Or log in scripts.

    PirateJon on
    all perfectionists are mediocre in their own eyes
  • PirateJonPirateJon Registered User regular
    edited April 2010
    Wait, are you just talking about registering a single DLL?

    Add regsvr32 <dllname> to the log on script and call it a day. Might need runas if the dudes aren't local admins.

    PirateJon on
    all perfectionists are mediocre in their own eyes
  • bowenbowen Sup? Registered User regular
    edited April 2010
    Thanks Jon, I'll see if that fixes it. Yeah it's just a single DLL that needs to be accessed via COM from a utility.

    bowen on
    not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
  • PirateJonPirateJon Registered User regular
    edited April 2010
    anytime my admin brother. couple of gotchas in that... I've had to map drives to the spot with the DLL/EXE before. off the tops:

    net use w: \\server\dllpath
    regsvr32 /s DLL.DLL (might need runas here)
    net use w: \\server\dllpath /delete

    PirateJon on
    all perfectionists are mediocre in their own eyes
  • bowenbowen Sup? Registered User regular
    edited April 2010
    This worked Jon, thanks.

    bowen on
    not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
  • RuckusRuckus Registered User regular
    edited April 2010
    PirateJon wrote: »
    anytime my admin brother. couple of gotchas in that... I've had to map drives to the spot with the DLL/EXE before. off the tops:

    net use w: \\server\dllpath
    regsvr32 /s DLL.DLL (might need runas here)
    net use w: \\server\dllpath /delete

    You probably don't need to runas, I think logon scripted actions already run as SYSTEM processes.

    [edit] Nope, I was wrong, logon/logoff script run with User credentials, Startup and Shutdown scripts run with Computer object credentials.

    Ruckus on
Sign In or Register to comment.