Remove all environment-specific data and make the dashboard adoptable anywhere, then add a demo that runs the real PowerShell services. - Strip cached device data, internal knowledge-base articles and screenshots, server/site names and the old project notes; replace the knowledge base with generic sample articles and diagrams - Move every environment value into Config/usmt-dash.psd1 - Route all infrastructure access in the worker and Get-Software.ps1 through a provider (Providers/SCCM.ps1), with a config-driven asset inventory view instead of a hard-coded custom class - Add Providers/Demo.ps1: a deterministic simulated fleet whose migrations progress in real time, and Demo/New-DemoData.ps1 to seed it - Server: -Demo makes the API read-only; add get-config and get-logs; serve static files only from web/, Documentation/ and an allowlist of Data/ files with a path-traversal guard; gzip large responses - Mirror both services' console output to Data/Logs via a Write-Host proxy, and add a terminal panel to the dashboard that streams it - Demo sandbox (web/demo/demo.js): visitor changes to tags, articles and images are kept in the visitor's browser and echoed in the terminals; nothing a visitor does reaches the server - Vendor marked, highlight.js and html2pdf.js instead of loading CDNs - Dockerfile and compose file for hosting the demo (Coolify-ready)
1.0 KiB
1.0 KiB
Salesforce
Salesforce itself is web based. Desktop components are only needed by some Sales and Support users.
| Component | Who needs it |
|---|---|
| Salesforce for Outlook / Outlook integration | Sales reps who log email to Salesforce |
| Salesforce Data Loader | Sales Ops / admins doing bulk imports |
Install
- Install the components that were on the old device (check Missing Software on the All Devices page).
- Installer share: Copy:\fileserver\software\Salesforce
- Data Loader needs a Java runtime. The installer bundles one; accept the defaults.
Outlook Integration
The modern integration is an Outlook add-in deployed from the Microsoft 365 admin center. After migration:
- Open Outlook and look for the Salesforce button on the ribbon.
- If it's missing, wait for add-in sync (up to 24 hours) or ask the M365 admins to confirm the assignment.
Single Sign-On
Users sign in with Use Custom Domain > company > SSO. They shouldn't need a separate password.