File: rsControllingInstallation.htm

package info (click to toggle)
office2003-schemas 1.0%2Bds-1
  • links: PTS, VCS
  • area: non-free
  • in suites: bookworm, forky, sid, trixie
  • size: 42,304 kB
  • sloc: javascript: 2,429; makefile: 29
file content (9 lines) | stat: -rw-r--r-- 7,934 bytes parent folder | download
1
2
3
4
5
6
7
8
9
<html dir="ltr"><head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<META HTTP-EQUIV="assetid" CONTENT="HV01082283"><META NAME="lcid" CONTENT="1033"><title>Controlling Service Installation Options</title><link rel="stylesheet" type="text/css" href="office10.css"><script type="text/javascript" language="Javascript" src="ExpCollapse.js"></script><script type="text/javascript" language="JavaScript" src="inline.js"></script></head><body><p id="ExpandAllLine" class="ExpFav"><a href="#" onclick="ExpandAll()" onkeypress="ExpandAll()" class="DropDown"><img id="picHeader" border="0" src="expandtri.gif" alt="Show All"><span id="ExpandAll">Show All</span></a></p><h1>Controlling Service Installation Options</h1><p>You can use optional Microsoft® Windows® registry settings to control which services are installed by default, whether users can add services manually, and whether users automatically connect to arbitrary discovery servers.</p><p>If you intend to let users have full control over the research services that they want to install, you do not need to use these optional settings.</p><p><b>Important</b>  Although we talk about registering a research service, the normal registration process registers a research service <i>provider</i>, along with the research <i>service or services</i> that the provider chooses to register on the user's computer. While the provider (through logic in the <b class="bterm">Registration</b> method) can programmatically select which services to install, the user does not have an equivalent option in the <b class="bterm">Research</b> task pane user interface to select or exclude individual services at the time of registration. In some cases, the provider may choose to install services, but not to activate them, by setting their <b class="bterm">Display</b> setting to "Off." The user can activate or deactivate services at any time, from the <b class="bterm">Research Options</b> dialog box.</p><p><a href="#" class="DropDown" onclick="Outline2()" onkeypress="Outline2()"><img border="0" src="blueup.gif" alt="Show">How to control the installation of default services</a></p><div id="ExpCol" class="collapsed" border="0"><p>Research services are made available through a provider, which can host multiple services. Microsoft Office 2003 applications connect to a provider through its URL and receive a list of available services from the provider. By default, all Office 2003 installations are configured to check Microsoft's provider for new Microsoft services and for third-party services that Microsoft lists, and to install specific services by default. Organizations can also create their own providers, exposing whichever services they want.</p><p>The normal registration process registers research services  for the current user only, under the <b class="bterm">HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\Research\Sources</b> registry subkey. To specify which services are installed by default, you can create a set of subkeys under <b class="bterm">HKEY_LOCAL_MACHINE</b> that define those services. By default, no subkeys exist at <b class="bterm">HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\Common\Research\Sources</b>. Creating a list of provider and service subkeys in this location causes Office to modify its normal procedure for the initial installation of  services. Before contacting Microsoft's discovery servers and any registered discovery servers, and installing default services from those sources, Office finds these subkeys located at <b class="bterm">HKEY_LOCAL_MACHINE</b> and copies them to <b class="bterm">HKEY_CURRENT_USER</b>. Copying the subkeys results in the services that you specified being installed for the user. This process is called "propagation."</p><p><b>Note</b>  The values of the <b class="bterm">NoAdd</b>, <b class="bterm">NoDiscovery</b>, and <b class="bterm">DiscoveryNeedOptIn</b> registry entries do not prevent propagation. For more information about these entries, see <a href="rsregAdministrativeOptions.htm" id="HV01083009" lcid=" ">Administrative Option Settings</a>.</p><p>The subkeys and entries created by the administrator under <b class="bterm">HKEY_LOCAL_MACHINE</b> should have the same names and format as those normally installed under <b class="bterm">HKEY_CURRENT_USER</b>. For more information, see <a href="rsregRegistryOverview.htm" id="HV01083005" lcid=" ">Registry Settings Overview</a>.</p></div><p><a href="#" class="DropDown" onclick="Outline2()" onkeypress="Outline2()"><img border="0" src="blueup.gif" alt="Show">How to control the manual installation of services</a></p><div id="ExpCol" class="collapsed" border="0"><p>You can create the optional <b class="bterm">NoAdd</b> entry under <b class="bterm">HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\Common\Research\Options</b> to control the manual installation of services by users. This entry is a DWORD value that behaves as a Boolean. When this entry has a value of 0 (false), users can add services. When it has a value of 1 (true), the  <b class="bterm">NoAdd</b> entry blocks all methods of adding services except:<ul><li>Propagation from <b class="bterm">HKEY_LOCAL_MACHINE</b> to <b class="bterm">HKEY_CURRENT_USER</b>, as described earlier.</li><li>Manual addition of service settings under <b class="bterm">HKEY_CURRENT_USER</b> by using the Registry Editor.</li></ul></p><p><b>Note</b>  The <b class="bterm">Options</b> subkey under <b class="bterm">HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\Common\Research</b> does not exist by default.</p><p>For more information, see <a href="rsregAdministrativeOptions.htm" id="HV01083009" lcid=" ">Administrative Option Settings</a>.</p></div><p><a href="#" class="DropDown" onclick="Outline2()" onkeypress="Outline2()"><img border="0" src="blueup.gif" alt="Show">How to control the use of a discovery server</a></p><div id="ExpCol" class="collapsed" border="0"><p>You can create the optional <b class="bterm">Discovery</b> entry under <b class="bterm">HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\Common\Research</b> to specify up to five arbitrary discovery servers that Office queries for available services. The values used to specify the discovery servers have the following format:<ul><li>DiscoveryPath1 = http://server1/service.asmx</li><li>DiscoveryPath2 = http://server2/service.asmx</li><li>...</li></ul></p><p>You can also create the optional <b class="bterm">NoDiscovery</b> entry under <b class="bterm">HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\Common\Research\Options</b> to control whether Office applications contact discovery servers for available services. When this entry has a value of 0 (false), Office 2003 contacts discovery servers (as discussed in <a href="rsAddingSetupRegistry.htm" id="HV01082280" lcid=" ">Deploying Services to Office Users</a>; when it has a value of 1 (true), the <b class="bterm">NoDiscovery</b> setting prevents Office 2003 applications from contacting either Microsoft's discovery servers or any arbitrary discovery server.</p><p><b>Note</b>  The <b class="bterm">Options</b> subkey under <b class="bterm">HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\Common\Research</b> does not exist by default.</p><p>For more information, see <a href="rsDiscovery.htm" id="HV01083307" lcid=" ">Configuring Service Discovery</a> and <a href="rsregAdministrativeOptions.htm" id="HV01083009" lcid=" ">Administrative Option Settings</a>.</p></div><center><a href="XMLSchemaCopyright_HV01147162.htm">&copy;2003-2004 Microsoft Corporation. All rights reserved.</a>  

Permission to copy, display and distribute this document is available at: <a 

href="http://r.office.microsoft.com/r/rlidAWSContentRedir?AssetID=XT010988631033&amp;CTT=11&amp;Origin=HV011232471033" 

target="_new">http://msdn.microsoft.com/library/en-us/odcXMLRef/html/odcXMLRefLegalNotice.asp</a></center></body></html>