Quantcast
Channel: Symantec Connect: Deployment and Imaging
Viewing all articles
Browse latest Browse all 622

Intelligent handling of "Default Automation Environment"

$
0
0

So for most folks this will not be an issue, but I would like to see some logic added to the Default Automation Environment selection which can be set from within the PXE Manager.  By default, you only get a single choice... Let's say for the purposes of this example, your default automation environment is set to WinPE 10.  I think it would be helpful to incorporate an opportunity for logic based selection.

For example:

if system x, is running a Linux operating system... then you could specify these linux systems boot to a Linux based automation environment - automatically.

Another example of this is legacy systems that don't have driver support in a particular WinPE environment, or drivers for a particular processor architecture.  It could be criteria such as a MANUFACTURER, MODEL NUMBER, PRODUCTION OPERATING SYSTEM, BIOS VERSION, ETC... that would trigger that system to boot to a different WinPE than the one selected as default.  This would be especially helpful to prevent systems from booting into automation environments that they are not compatible with.

I am aware that you can accomplish similar behavior to this by specifying conditions on a job that would target a specific automation environment, but that would not be as seamless as the system being able to detect this and react on its own.


Viewing all articles
Browse latest Browse all 622

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>