Remote Configuration Framework Registry Settings (Windows CE 5.0)
The registry stores information necessary to configure the system for applications and hardware devices. The registry also contains information that the operating system continually references during operation. The protected registry contains named values for configuration.
The Remote Configuration Framework settings are located under the HKLM\Comm\HTTPD\VROOTS\ registry key. At least one virtual path must be created before the Web server starts. HKEY_LOCAL_MACHINE\Comm\HTTPD\VROOTS is the virtual path protected registry key. This registry key contains one or more subkeys, one for each virtual path. Each subkey is named for the virtual path that it specifies. For more information, see Virtual Path Settings.
The following table shows the named values for the HKEY_LOCAL_MACHINE\Comm\HTTPD\VROOTS\/RemoteAdmin key.
| Value : type | Description |
|---|---|
| DefaultPage : REG_SZ | Default not set in the registry. Specifies the default .htm file to be served by the ISAPI extension if no specific data has been requested by the browser. For more information, see Base Registry Settings. |
| BackupFileName : REG_SZ | Default setting is gateway_settings.dat. Specifies the name of the file to be created during a backup. |
| RebootTimeClient :REG_DWORD | Default setting is 60. Specifies the number of seconds the client will wait during reboot. |
| HTTPDRestartTimeClient :REG_DWORD | Default setting is 30. Specifies the number of seconds the client will wait during a Web server restart. |
| NDISRestartTimeClient : REG_DWORD | Default setting is 30. Specifies the number of seconds the client will wait during an NDIS rebind. |
| RebootTime :REG_DWORD | Default setting is 15. Specifies the number of seconds the server will wait before rebooting. |
| HTTPDRestartTime : REG_DWORD | Default setting is 15. Specifies the number of seconds the server will wait before a Web server restart. |
| NDISRestartTime : REG_DWORD | Default setting is 15. Specifies the number of seconds the client will wait before an NDIS restart. |
To securely store the .htm files, you can use the HKLM\Comm\HTTPD\VROOTS\/RemoteAdmin\redirectedPages registry key and specify an alternative directory for the ISAPI extension .
The following table shows the named values for the HKLM\Comm\HTTPD\VROOTS\/RemoteAdmin\redirectedPages key.
| Value : type | Description |
|---|---|
| FileName : REG_SZ | Specifies the path of the file to be stored in the alternative directory.
|
The GUID for each Remote Configuration Framework module is stored in the registry. When adding a new module, you must register its GUID under the HKLM\Comm\HTTPD\VROOTS\/RemoteAdmin\Modules*\<module to be created>* registry key.
The following table shows the named values for the HKLM\Comm\HTTPD\VROOTS\/RemoteAdmin\Modules\<module to be created> registry key.
| Value : type | Description |
|---|---|
| GUID : REG_SZ | Specifies the GUID for the CLSID of the Component Object Model (COM) object to be loaded. For more information, see CoCreateGuid. |
You can use the HKLM\Comm\HTTPD\VROOTS\/RemoteAdmin\ToolBar registry key to customize toolbar settings.
The following table shows the named values for the HKLM\Comm\HTTPD\VROOTS\/RemoteAdmin\ToolBar registry key.
| Value : type | Description |
|---|---|
| Index : REG_SZ | Specifies the name of the function or file for the toolbar utility. The JavaScript toolbar will load a file with this value and a .js extension appended to it. This file should contain a function with the same name as the value that will be executed on page load. Setting this value allows you to componentize toolbar entries. |
You can add use the HKLM\Comm\HTTPD\VROOTS\/RemoteAdmin\UserSpecified registry key to add user-specific values to the Remote Configuration Framework.
The following table shows the named values for the HKLM\Comm\HTTPD\VROOTS\/RemoteAdmin\UserSpecified registry key.
| Value : type | Description |
|---|---|
| <User-specified Name> : REG_SZ | Specifies a user-specific value. All values that are specified under this key will be sent to the Web server through the REMOTEUTILS module. |
See Also
Remote Configuration Framework
Send Feedback on this topic to the authors