Customized Version of NetMeeting Is Applied Applied Only to Logged-On User (242787)


The information in this article applies to:

  • Microsoft NetMeeting 3.01 for Windows NT 4.0
This article was previously published under Q242787
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

Installing customized versions of NetMeeting installs only the settings in the user profile for the user who was logged on when the program was installed. Other users do not retain all of the customized settings.

CAUSE

Several customized settings are saved under the HKEY_CURRENT_USER key in the registry, and are only available to the user who was logged on when the customized version was installed.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To deploy customized versions of NetMeeting in Microsoft Windows NT for multiple users, use any of the following methods:
  • Push the installation of NetMeeting across the network during user logon. This ensures that the program is run for each user.
  • Deploy NetMeeting using the Auto-Configuration option. To set each user to be able to use the Auto-Configuration option:
    1. Create a custom build that uses the Auto-Configuration option from Web servers.
    2. Install the custom build on a computer.
    3. Export the following registry key:

      [HKEY_CURRENT_USER\Software\Microsoft\Conferencing\AutoConf]
      "Use AutoConfig"=hex:01,00,00,00
      "ConfigFile" "http://[network URL path]/nm3conf.inf"

    4. Import this key for each user either by pushing it during user logon, or by sending it to the users in e-mail (or another delivery system) and having the users double-click the registry file to import it.

STATUS

This issue has been resolved in NetMeeting 3.01 Service Pack 1.

MORE INFORMATION

You can also create customized versions of NetMeeting by using the Microsoft NetMeeting Resource Kit.
Modification Type:MajorLast Reviewed:10/2/2002
Keywords:kbenv kbprb KB242787
©2002 Microsoft Corporation. All rights reserved.