1.3 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| reference_screenconnect_custom_property_slots | ACG ScreenConnect custom-property slot -> label mapping (CP1..CP8) for session tagging |
|
ACG's ConnectWise ScreenConnect instance (computerguru.screenconnect.com) custom-property
slot order, reverse-engineered 2026-07-03 from a labeled test session (HOWARD-HOME, values
"howard company / howards site / Howard department / howard type / ... / howard tag"):
- CP1 (index 0) = Company
- CP2 (index 1) = Site
- CP3 (index 2) = Department
- CP4 (index 3) = Device Type
- CP5 (index 4) = unused/other
- CP6 (index 5) = unused/other
- CP7 (index 6) = unused/other
- CP8 (index 7) = Tag
The API does NOT expose the property LABELS (only values), so this mapping is the reference.
UpdateSessionCustomProperties [sessionID, [cp1..cp8]] REPLACES the whole 8-element array — always
read the session's current values first, modify only the slots you intend, write the full array back.
Set via the [[screenconnect]] skill: sc.py set-properties --session <id> --props-json '[...8...]' --confirm.
Read via GetSessionsByName -> .CustomPropertyValues.
Used by the GPS->RMM audit ScreenConnect cleanup (projects/gps-rmm-audit/): normalize Company,
set Site/Department/Device Type/Tag per machine, dedupe sessions.