Deployment Solution

 View Only

  • 1.  Purpose of the Deployment Automation Folder

    Posted Jan 07, 2012 10:03 PM

     

    What exact functionality does the installation of the "Deployment Automation Folder' to clients provide?

    If I am booting the automation environment from PXE,  do I still need to deploy the Automation folder to all clients?

    As it is right now,  I do NOT have the Deployment Automation Folder deployed to clients,  however using PXE, I am still able to perform any tasks that I need (Image capture and deployment).

    Thanks



  • 2.  RE: Purpose of the Deployment Automation Folder

    Broadcom Employee
    Posted Jan 08, 2012 04:04 AM

    This is provided if you dint have PXE setup and will be easy to boot the client machine to WinPE environment for task execution.

    Automation folder has the same winpe image which is used by PXE setup [default] , so you execute all the tasks using PXE setup , just make sure you boot the machine to PXE every time you execute any task required WinPE environment.



  • 3.  RE: Purpose of the Deployment Automation Folder

    Posted Jan 09, 2012 04:27 AM

    In addition to Yogesh:

    Pros of Automation (which are cons of PXE):

    1. Ease of use: Automation env boot is very fast as compare to PXE with not much extra knowledge required

    2. No effect of firewall restriction: Firewall restriction will not affect Automation boot/working

    3. Static IP handling: Static IP address can also be handled by Automation

    Pros of PXE (which are cons of Automation):

    1. Centralize: PXE has centralized management

    2. Preboot Driver management : Driver addition and PXE Preboot image recreate is much easy

    3. Upgrade: PXE image upgrades (for WinPE2.1) are not required for product after product upgrade

    Thanks