Phone Provisioning75Configuring a Provisioning ServerThe provisioning server can be set up on the local LAN or anywhere on the Internet. Use the following procedure as arecommendation if this is your first provisioning server setup.To set up the provisioning server:1. Install a provisioning server application or locate a suitable existing server, such as 3CDaemon.2. Create an account and home directory.3. Set security permissions for the account.4. Create boot files and configuration files, and then edit them as desired.5. Copy the boot files, configuration files and resource files to the provisioning server.6. If performing static provisioning, obtain the provisioning server address.TipTypically, all phones are configured with the same server account, but the server account provides a means of convenientlypartitioning the configuration. Give each account a unique home directory on the server and change the configuration on aper-line basis.Keeping User’s Personalized Settings after Auto ProvisioningGenerally, you deploy phones in batch and timely maintain company phones via auto provisioning, yet some userswould like to keep the personalized settings (for example, ring tones, wallpaper or DSS keys) after auto provisioning.TopicsKeeping User’s Personalized Settings ConfigurationAuto Provisioning Flowchart for Keep User’s Personalized Configuration SettingsExample: Keeping User’s Personalized SettingsClearing User's Personalized Configuration SettingsKeeping User’s Personalized Settings ConfigurationThe following table lists the parameters you can use to keep user's personalized settings.Parameter static.auto_provision.custom.protect .cfgDescriptionIt enables or disables the phone to keep user’s personalized settings after auto provisioning.Note: The provisioning priority mechanism (phone/web user interface >central provisioning >factorydefaults) takes effect only if the value of this parameter is set to 1 (Enabled). If “overwrite_mode” is set to1 in the boot file, the value of this parameter will be set to 1 (Enabled).PermittedValues0-Disabled1-Enabled, -local.cfg file generates and personalized non-static settings configured via the webor phone user interface will be kept after auto provisioning.Default 0Parameter static.auto_provision.custom.sync .cfgDescriptionIt enables or disables the phone to upload the -local.cfg file to the server each time the fileupdates, and to download the -local.cfg file from the server during auto provisioning.Note: It works only if “static.auto_provision.custom.protect” is set to 1 (Enabled). The upload/downloadpath is configured by the parameter “static.auto_provision.custom.sync.path”.Permitted 0-Disabled
