Configuration files

For OS Sequence-based provisioning, depending on the operating system being provisioned, the following configuration file must be specified in an OS Installation Profile:

• Oracle Solaris/Sun SPARC 10

  JumpStart profile

• Oracle Solaris/Sun SPARC 11

  Automated Installation

• Red Hat Linux

  Anaconda (Kickstart configuration file)

• VMware ESX

  ESX 3.5: Anaconda (Kickstart configuration file)

  ESX 4: Weasel (Kickstart configuration file)

• SUSE Linux

  YaST2 configuration file

• Windows

  unattend.xml

If your configuration file enables a firewall, you must ensure that all necessary ports and protocols for communication between the SA core and the OS Build Agent and the SA Agent are allowed. Refer to the SA 10.50 Install Guide for details. To help isolate firewall related issues, you should leave firewalls disabled while configuring OS Provisioning for the first time and reenable them once the system is correctly configured. For Red Hat Enterprise Linux 5 and 6, the following line in your ks.cfg profile enables the firewall and allows the SA Agent to function correctly:

firewall --enabled --port 1002:tcp,1002:udp

For VMware ESX prior to 4.1 provisioning, the SA Agent installer may temporarily bypass any OS-based firewall configured in the ks.cfg.