Group Policy Setting MOC 2007 AutoRun

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?

LVL 3
kkohlAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dfxdeimosCommented:
Here is the registry setting that controls that setting:

[HKEY_CURRENT_USER\Software\Microsoft\Communicator]
"AutoRunWhenLogonToWindows"=dword:00000001

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kkohlAuthor Commented:
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.
0
dfxdeimosCommented:
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:

http://thelazyadmin.com/blogs/thelazyadmin/archive/2005/07/05/Creating-Custom-ADM-Templates.aspx
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

HayesJupeCommented:
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.
0
kkohlAuthor Commented:
Update:

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

[HKCU\Software\Microsoft\Communicator]
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...
0
gaanthonyCommented:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Communicator REG_SZ "C:\Program Files\Microsoft Office Communicator\communicator.exe" /fromrunkey
0
dfxdeimosCommented:
You could just run PSExec command to launch communicator against a list of all your computers. =]
0
kkohlAuthor Commented:
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 :-)

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

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.