By default, Predefined computers are assigned a default 'PXE Boot Image' on the 'NBS General Settings' page that they boot to when turned on. This behavior allows a predefined computer to have a PXE preboot without having to assign a separate 'boot to' task to the system.
When a 'boot to' task is assigned to the prefedined computer, the Notification Server first boots the client to the PXE image specified in the 'PXE Boot Image' setting. Once in PXE automation, the 'boot to' task is processed and the computer reboots to the new PXE environment.
E.g Default is set to 'WinPE5, 'Boot to' task assigned to computer is 'WinPE10'. Client will boot to WinPE5, receive the task and reboot to WinPE10
It should be possible to boot directly to the PXE preboot specified in the 'boot to' task.
DS 8.0 HF2 or higher
In ITMS 8.0 HF2 - in order to improve performance, Task server was changed to no longer receive tasks for clients that are Managed but not registered.
The installation of 8.0 HF6 V1 adds a new Registry Key to the Notification Server that allows predefined computers to be imported as 'Managed' or 'Unmanaged'. The key is listed below:
'HKLM\SOFTWARE\Altiris\Deployment\ImportAsManaged' with Default Value of ‘1’
The two possible values for the key are ‘1’ or ‘0’. The results of setting the key to each value are given below.
If ImportAsManaged - is enabled(1) - client will follow default PXE configuration and will not be able to pick-up assigned Boot To PXE task.
The example below explains how a setting of ‘1’ will affect your environment.
This is the default setting
If ImportAsManaged is disabled(0) - client will be imported as an unmanaged resource. It will be able to execute an individual Boot To PXE task independent of the setting specified on the ‘NBS General Settings’ page.
Note: since Unmanaged computers are not a member of the "All Computers" filter, tasks which require the computer to be a part of this filter will not execute with the value set to ‘0’. (For example: Software Quick Delivery or Package Delivery tasks)
The example below explains how a setting of ‘0’ will affect your environment.
It's recommended to keep the registry key set to ‘1’ (enabled) unless there is a specific need to set it to ‘0’. For example, setting the value to ‘0’ is useful when performing Scripted Install tasks for different Windows Architecture, or performing RedHat installs.