Cisco Server Provisioner 6.6 User's Guide ("Chuck Berry")

License Keys for Optional Modules

Hide Navigation Pane

License Keys for Optional Modules

Previous topic Next topic No expanding text in this topic  

License Keys for Optional Modules

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function Mail us feedback on this topic!  

Optional modules, such as the WPM Windows Provisioning Module and the EPM ESX Provisioning Module, require that the license key for the base Provisioner PXE Server explicitly authorize the use of individual add-on modules. Unless your Provisioner PXE Server license key enables an optional module, that module will not provision systems.

 

If at one point you were running an optional module but no longer are (e.g., you evaluated a module but elected not to license it), the licensing mechanism will prevent systems from being provisioned. Please refer to the PXE Event Log for details on individual systems that attempted to be provisioned using an unlicensed module.

 

MAC-Independent: if a Provisioning Role based on an optional module exists, and if a client system attempts any MAC-Independent installation, a message appears on the client system screen until the system is rebooted, an entry is made in the PXE Event Log and the Provisioner PXE Server service will be stopped. To remedy the situation, delete all MAC-Independent Roles created using the unlicensed optional module then start the Provisioner PXE Server service.

 

MAC-Specific: if a system attempts to be provisioned using a Role based on the Provisioning Role Template for an unlicensed product or module, a message appears on the client system screen until the system is rebooted and an entry is made in the PXE Event Log. To remedy the situation, change the Template assigned to the client system Role to a template that is not based on an unlicensed optional module. Also, remove all Templates based on unlicensed products to avoid such instances in the future.