Skip to content

Add Eaglesoft Schick IOSS driver stack installer for ES 24.20+ workstations#109

Open
AlrightLad wants to merge 2 commits into
mainfrom
enhancement/eaglesoft-schick-ioss-install
Open

Add Eaglesoft Schick IOSS driver stack installer for ES 24.20+ workstations#109
AlrightLad wants to merge 2 commits into
mainfrom
enhancement/eaglesoft-schick-ioss-install

Conversation

@AlrightLad

Copy link
Copy Markdown

Summary

Automates the Schick sensor driver migration required for Eaglesoft 24.20+ (IOSS replaces the discontinued CDR driver integration per Patterson Answer 44313). Built for an ES 25 upgrade at a 30+ workstation dental office; eliminates the per-machine manual procedure.

Installs, per Patterson's documented sequence: Schick digital integration (registry import, Answer 18352) → MSXML 4.0 (skip-if-present) → CDR Elite 5.16 + Shared Files strip preserving CDRData.dll/OMEGADLL.dll + CDRPatch-2808.msi (produces CDRImageProcess.dll 5.15.1877.10093 for pre-24.20 image filters) → IOSS v3.2 (VC++ 2019 prereq, en-us MSI) → sets Sirona Intraoral Sensor Service to Automatic (Delayed Start) per Patterson guidance.

Design

  • 100% non-interactive — RMM execution only; hard-fails with guidance if $env:RMM is not "1" rather than prompting. Deliberate deviation from the template's dual-mode pattern: an installer that silently strips the Schick driver stack should never run on ad-hoc manual invocation.
  • Per-component B2 URLs (repo/vendors/Patterson-Eaglesoft/), empty URL = phase skipped — composable per workstation profile (full fresh install, IOSS-only top-up, filter-stack repair)
  • Eaglesoft version gate: reads uninstall registry ("Patterson Eaglesoft", highest parseable version across multiple entries), hard-stops below 24.20 — prevents stripping the legacy CDR stack a pre-24.20 install still requires. SkipVersionCheck=1 override.
  • Idempotent: IOSS service presence + CDRImageProcess.dll version + msxml4.dll checks skip completed components; safe to re-run fleet-wide
  • Fail-fast: aborts before any changes if CdrEliteArgs is unset while the legacy stack is needed (CDR Elite Setup.exe is InstallShield; verified silent switches: /S /v/qn /v/norestart)
  • Registry import filtered to Schick_Sensor_Integration.reg (package ships 14 vendors' files; importing all would enable integrations for absent hardware)
  • Disables Core Isolation/HVCI per Patterson Answer 40785 (vendor requirement for sensor function; DisableCoreIsolation=0 opt-out)
  • 64-bit relaunch guard, TLS 1.2, Start/Stop-Transcript with full phase logging

RMM Variables

IossUrl, CdrEliteUrl, DigitalIntegrationUrl, MsxmlUrl, CdrEliteArgs, Description + optional DigitalIntegrationRegFiles, DisableCoreIsolation, SkipVersionCheck, ForceReinstall (defaults in header)

Testing

  • Piloted via NinjaOne on a Win11 Pro workstation (ES 24.20.03, unconverted legacy stack). All phases exit 0. Post-reboot verified: SironaUSBService Running / AUTO_START (DELAYED), CDRImageProcess.dll 5.15.1877.10093, CDRData.dll + OMEGADLL.dll present, IOSS 3.2.4024.52346 registered, HVCI 0.
  • Version gate verified against real registry data (dual uninstall entries 24.00.07 + 24.20.03 → correctly selects 24.20.3).
  • PSScriptAnalyzer clean except PSAvoidUsingWriteHost (repo convention for RMM output).
  • Functional sensor gate (acquisition test, pre-upgrade exam filter rendering) pending on an operatory workstation before fleet rollout.

Known limitations

  • IOSS does not function over RDS/RDP (vendor limitation, Answer 44313) — not applicable to this deployment, noted for reuse
  • Module/sensor firmware updates remain hands-on via the IOSS Configuration Application
  • Default static enhancement is a one-time office-wide GUI step, not scripted

@AlrightLad AlrightLad requested a review from Gumbees as a code owner July 8, 2026 02:19

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Code review skipped — your organization has reached its monthly code review spending cap.

An organization admin can view or raise the cap at claude.ai/admin-settings/claude-code. The cap resets at the start of the next billing period.

Once the cap resets or is raised, push a new commit or reopen this pull request to trigger a review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant