Learn the workflow.
Prove every result.

Outcome: Select one named cloud device, verify it in Pre-flight, and exit without running an operation.

1. Activate the pilot organization.

   Use the upper-right organization switcher. If it is missing, select Deployment → Organizations and add it.

   Checkpoint: the expected organization name is visible.
2. Prepare a read-only request.

   Select Deployment → xAPI → GET Config. Turn on Download Device Configurations. Leave xConfig Filter empty.

   Checkpoint: the page heading is “Download Device Configuration.”
3. Select by familiar name.

   Select Next: Select Devices. Set Deployment Target to Device ID, select Browse, choose the pilot by name, then select Select.

   Checkpoint: the display name beneath Device ID is your pilot.
4. Resolve and exit.

   Select Pre-flight. Confirm exactly one intended device, then select Cancel and close Deployment Options.

   Completed when: you can state the active organization, targeting method, device name, and resolved count.

Outcome: Set a pilot device to a known volume, capture the response, and restore the original volume.

1. Add the controlled training command.

   Select Add Command, then Search commands. Find Audio Volume Set and set Level to 50. Commands can change state; they are not read-only status queries.

   Checkpoint: the card shows the intended command and no red validation indicator.
2. Choose one pilot and request output.

   Select Next: Select Devices, browse to the pilot by Device ID, and turn on Collect Command Outputs. Run Pre-flight.

   Stop if the preview differs or more than one device resolves.
3. Run and read the report.

   Continue from Pre-flight. In the deployment summary, open Command Output Report. Confirm Device, Command, Status Code, Status, and Result fields.

4. Verify the visible result.

   The device controller should show volume 50. If it does not, stop and compare the output report with device availability.

5. Restore and prove the original value.

   Repeat the operation with the recorded starting volume, keep Collect Command Outputs enabled, and open the second report. Confirm success and verify the controller shows the original value.

   Completed when: both reports exist and the pilot is visibly restored.

Outcome: Export identifiers, prepare a two-device CSV, identify a delimiter fault, and verify row-to-target mapping.

CSV columns

Device ID,,,Command 1
REPLACE_WITH_DEVICE_ID,,,xCommand Audio Volume Set Level: 50

1. Export current identifiers.

   Select Tools → Export, choose Device IDs, and use the narrowest filter. Preserve the export unchanged.

2. Stage A: build one pilot row.

   Replace only the first sample ID and remove the second data row. Column A is Device ID, B and C remain empty, and commands occupy D–M. Do not execute the file in Stage A.

3. Inspect as plain text.

   Confirm comma delimiters, UTF-8, one device per row, and two empty fields between Device ID and command. Compare with the broken semicolon file.

   Checkpoint: each row looks like device-id,,,xCommand….
4. Stage A: upload, Pre-flight, and cancel.

   Select xAPI → CSV, enable Enable CSV-based commands, upload the file, select Next: Select Devices, and run Pre-flight. Confirm one device and the intended command, then cancel.

   Required completion: you repaired the delimiter problem and proved one correct row without executing it.
5. Stage B: optional instructor-approved execution.

   Only with approval, add a second pilot row, record both live volumes, Pre-flight again, execute, and use the restoration template to return both devices to their original values.

   Stop if either resolved count, command, or original value is uncertain.

Outcome: Identify the proxy mode, add the correct trust certificate, and prove Webex connectivity without disabling verification.

Obtain these answers first

• Proxy type: OS-managed, explicit, or PAC
• Proxy host and port
• Whether authentication is required
• The required root or issuing CA
• Whether mutual TLS is required

1. Record current settings.

   Record enabled sliders, proxy address, port, and certificate filenames. Do not record passwords or private keys.

2. Configure one proxy method.

   Enable Auto Web Proxy Detection or Custom Web Proxy. Custom overrides auto detection.

3. Keep validation enabled and add trust.

   Enable Verify TLS Certificates. Under Certificate-Based Proxy (optional), browse for CA Certificate (.pem, .crt). The picker also accepts .cer.

   Checkpoint: client certificate and key remain empty unless mutual TLS is required.
4. Save and test.

   Select Save Web Proxy. Then run Deployment → Tools → Tests → Webex Diagnostics → Run Diagnostics. Under Organizations, open the active organization menu and select Test Connection.

   Completed when: both tests pass without a certificate error.

Symptom map

Outcome: Deploy a harmless logging macro to one pilot, verify its runtime output, then remove it.

1. Upload and review.

   Under Macro JavaScript File, upload the training macro. Open Code Preview and review Issues.

   Checkpoint: it only logs a start message and reads active-call count.
2. Configure the pilot.

   Name it CE-Deploy Training, enable Activate on deployment, and leave Skip Transpilation off.

3. Pre-flight and deploy.

   Select Next: Select Devices, browse to one pilot, and run Pre-flight. Continue only when file, name, activation state, and device are correct.

4. Confirm the runtime is available.

   Select Deployment → Apps → Macro Factory. Select the pilot device card to open its detail panel. Under engine status, confirm the runtime is running. If it is not, stop and enable Macros Mode through the device’s approved administration workflow.

5. Verify runtime behavior.

   In the device detail panel, inspect Engine Logs for CE-Deploy training macro started and CE-Deploy training: active calls = 0. Zero is a valid successful result when the room has no active call.

6. Deactivate, remove, and refresh.

   In Deployment → Apps → Macro Factory, expand the pilot device, find CE-Deploy Training, use the pause control titled Deactivate, then the trash control titled Remove. Confirm Remove Macros, refresh the inventory, and confirm the macro is absent.

   Completed when: the expected logs were observed and a refreshed inventory no longer lists the macro.