Search
Page 70 of 99. Showing 987 results (0.025 seconds)
Command line usage and the kickstart file
for installation. The filename is in the format qube-component_group-install_version-kickstart.qks, e.g qube-upgrade-6.4-4-kickstart.qks or qube-worker-6.4-4-kickstart.qks…Using the kickstart file
Synopsis Each time you run the installer, a kickstart file is generated. This file will be saved next to the manifest file that was used for installation. The filename…Using the kickstart file
Synopsis Each time you run the installer, a kickstart file is generated. This file will be saved next to the manifest file that was used for installation. The filename…Using the kickstart file
Synopsis Each time you run the installer, a kickstart file is generated. This file will be saved next to the manifest file that was used for installation. The filename…Using the kickstart file
Synopsis Each time you run the installer, a kickstart file is generated. This file will be saved next to the manifest file that was used for installation. The filename…Using the kickstart file
Synopsis Each time you run the installer, a kickstart file is generated. This file will be saved next to the manifest file that was used for installation. The filename…Using the kickstart file
Synopsis Each time you run the installer, a kickstart file is generated. This file will be saved next to the manifest file that was used for installation. The filename…Using the kickstart file
Synopsis Each time you run the installer, a kickstart file is generated. This file will be saved next to the manifest file that was used for installation. The filename…4. Component Selection
on your system will get tri-state check boxes, with the third state signifying that you want to uninstall that component. There are two "special" installation groups - "Upgrade…Development Options
of the QubeGUI and requires no additional Worker installation. Custom jobtypes (backend) – Instead of using the commandline on the backend, one can write jobtype scripts…