Group Policy Setting MOC 2007 AutoRun

Posted on 2008-11-04
Last Modified: 2013-11-29
Microsoft shop running on 2003 AD domain with OCS 2007 and MOC 2007.
I am trying to find a way to get all Office Communicator Clients to autorun and run minimized when users log on to their machines.
I have the Office Communicator Administrative Template loaded in my group policy manager but cannot find the setting to enable AutoRun.

Is there a way for me to do this using Group Policy?
If not, what is the best way to go with a solution that includes new installs AND existing ones?

Question by:kkohl
    LVL 15

    Accepted Solution

    Here is the registry setting that controls that setting:


    You could create a custom ADM file that adds that registry key to all users.
    LVL 3

    Author Comment

    I haven't had any experience creating a custom ADM file.
    Once I figure that out, does it show up in the group policy manager like the other settings?
    This sounds like a pretty easy solution.
    LVL 15

    Assisted Solution

    It will be applied via group policy, but will edit the registry of machines that it is applied to.

    Here is a good guide on writing ADM files:
    LVL 15

    Expert Comment

    agree wtih the above poster that an ADM is the best way to go... however, if your looking to do it in a quick and nasty fashion, you can always roll it out via logon script.

    Because the reg key in question is a HKCU key, the users will have access to that key - hence put it into your vbscript or (yuck) batch file logon script, and you'll update everyone as they logon, ready for thier next logon. Probably quicker if you dont know how to write an ADM, but an ADM is quicker and more managable in the long-term.
    LVL 3

    Author Comment


    I have successfully created a custom ADM file and have implemented the desired hive key.  It is populating correctly in each user's registry.

    AutoRunWhenLogonToWindows REG_DWORD 0x00000001(1)

    Yet, Communicator fails to launch.

    Currently, Communicator is installed and once a user is logged in and manually launches the client, it will automatically launch each time the user logs in.  It behaves in this manner prior to the custom ADM addition.
    I was hoping to gain the effect of removing the need to manually launch the client.

    So far, it looks like the key is added correctly, but I am still having to manually launch...
    LVL 12

    Expert Comment

    Communicator REG_SZ "C:\Program Files\Microsoft Office Communicator\communicator.exe" /fromrunkey
    LVL 15

    Expert Comment

    You could just run PSExec command to launch communicator against a list of all your computers. =]
    LVL 3

    Author Comment

    I found a fix that works.  It works well enough, but still has some 'clunk' to it.

    Group Policy | User Configuration | Administrative Templates | System | Logon | Run These Programs at User Logon

    Enabled this policy and pointed to Communicator.exe.

    Now Communicator properly launches the first time a user logs in.  This is great as it is the initially desired feature.
    The 'clunk' comes from the fact that after Communicator has successfully ran the first time, it automatically logs you in each logon anyway, thereby causing two separate launch commands on future logins... the call to launch from the group policy AND the Communicator internal setting to auto sign in.
    This can sometimes cause an error popup stating communicator is already running.

    This is considered a very minor nuisance and I can live with this, but I may try playing more finding a way to maybe update the Run Once key.... just once :-)

    LVL 3

    Author Closing Comment

    I didn't need to create a custom ADM file as my desired app was already listed.
    The "fromrunkey" never really worked.


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    IT, Stop Being Called Into Every Meeting

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Suggested Solutions

    Title # Comments Views Activity
    UNC paths question 18 58
    Retire Active Directory server 3 19
    ADFS SSL Clarification 4 34
    Virtual Memory using Group Policy 5 28
    I'm sure that every Windows systems administrator has written, or at least used, a batch or VBS login script at some point in their career, whether it is to map network drives, install printers, or set some user preferences.  No more! With Window…
    Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip is around source server preparation. No migration is an easy migration, there is a…
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    10 Experts available now in Live!

    Get 1:1 Help Now