kkohl
asked on
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
ASKER
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\C
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...
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\C
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...
HKEY_LOCAL_MACHINE\SOFTWAR
Communicator REG_SZ "C:\Program Files\Microsoft Office Communicator\communicator.
Communicator REG_SZ "C:\Program Files\Microsoft Office Communicator\communicator.
You could just run PSExec command to launch communicator against a list of all your computers. =]
ASKER
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 :-)
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 :-)
ASKER
I didn't need to create a custom ADM file as my desired app was already listed.
The "fromrunkey" never really worked.
The "fromrunkey" never really worked.
ASKER
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.