Tchater maintenant avec le support
Tchattez avec un ingénieur du support

KACE Systems Deployment Appliance 9.0 Common Documents - Administrator Guide

About the KACE Systems Deployment Appliance Getting started Using the Dashboard Configuring the appliance Setting up user accounts and user authentication Configuring security settings Preparing for deployment Managing device inventory Using labels Creating a Windows or Linux Boot Environment Managing drivers Capturing images Capturing user states Creating scripted installations Creating a task sequence Automating deployments Performing manual deployments Managing custom deployments Managing offline deployments Imaging Mac devices About the Remote Site Appliance Importing and exporting appliance components Managing disk space Troubleshooting appliance issues Updating appliance software Glossary About us Legal notices

Edit the default multicast settings

Edit the default multicast settings

The changes that you make to the default multicast settings apply to all new multicast deployments.

You can change the multicast settings on a per deployment basis. Navigate to the Deployments page, and select the boot action to display the Automated Deployment Detail page, then click Show advanced settings.

1.
On the left navigation pane, click Settings > Control Panel to display the Control Panel, then click Default Multicast Settings to display the Default Multicast Settings page.
2.
Change the Timeout to wait for connection 'Ready to receive' state for the duration that the appliance waits for all target devices to connect. The default is 10 minutes.
* 
NOTE: Consider the connection time that it might take for a task to run or for a device to boot. If you set the timeout to 10 minutes and only one device connects after 5 minutes, the appliance resets to 10 minutes to wait for the remaining devices to connect.
3.
Select the Multicast Protocol, as required by your environment:
◦
Pragmatic General Multicast (PGM)
◦
NACK-Oriented Reliable Multicast (NORM)
▪
The Internet Group Management Protocol (IGMP) is a sub-set of the NORM, and is also supported.
While PGM appears to provide faster data transfer, NORM can typically handle higher transmission rates and is in general more reliable. Choose the protocol that best suits your needs.
4.
Set a different IPv4 Multicast address if a different service is using the default address.
5.
If another device on your network is using port 2112, specify another port number in the Control channel port field.
6.
In the Multicast hops field, type the number of multicast hops over subnets. The default value is 1, but you can change it to suit your needs.
7.
Lower the Transmission Rate, if required.
The transmission rate determines the success or failure of the deployment. The default is 8MB.
8.
If you want to revert to the settings included with the default installation, click Reapply factory settings.
9.
Adjust the Log level, as needed by selecting one of the following options:
◦
Fatal errors only
◦
Fatal errors and warnings
◦
Trace logging
◦
Detailed logging
◦
Verbose logging
10.
Click Save.

View automated deployments in progress

View automated deployments in progress

You can view the progress of automated deployments that are currently running, the status of assigned tasks, and which image was deployed to which device.

1.
On the left navigation pane, click Progress, click Automated Deployments to display the Automated Deployment Progress page.
2.
Under Name, select the boot action to display the Automated Deployment Detail page.
3.
Under the Devices menu bar, click Details to view the status of the assigned tasks.
On the left navigation pane, click Audit Log to view the success or failure of completed automated deployments.

View completed automated deployments

View completed automated deployments

You can view the success or failure of completed automated deployments, the status of assigned tasks, and which image was deployed to which device.

1.
On the left navigation pane, click Audit Log.
2.
Under Name, select the boot action to display the Boot Action Log Detail page.
3.
Under the Devices menu bar, click Details to view the status of the assigned tasks.
The image must be re-deployed separately to the devices where the deployment failed.

Edit failed tasks

Edit failed tasks

If a task fails, you can edit the task from the device where it failed.

Use a VNC or Remote Desktop connection to connect to the target device.
* 
NOTE: The Client Task Error screen displays only on target devices with the Windows operating system.
1.
Select one of the following options:
◦
Open a Command Prompt to run commands on the device.
◦
Open Notepad to modify any file.
◦
Open Edit Tasks.xml file with Notepad to change the Tasks.xml file.
◦
Edit the Registry to change the OS configuration information.
◦
Retry failed task to run the task again.
◦
Resume task execution to continue the deployment with the failed task.
◦
Reboot machine to restart the deployment.
◦
Shut down machine to power off the device.
* 
NOTE: You can view failed tasks on the appliance Audit Log page.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation