Jon Griffey

Change Request 433317 Implement New Recast Management Server [MECM-1P-RCST-W1.auth.tamu.edu].

Description: Details of maintenance: This change consists of the implementation of a new Recast Management Server [MECM-1P-RCST-W1.auth.tamu.edu] and upgrade of existing Recast Console Extension agents on MECM Jump Servers and Recast Agents on workstations.

Degraded Recast Management Servers: mecm-1p-rcst-c1.auth.tamu.edu cm2-recast.as.tamu.edu

MECM Jump Servers: mgmt-3p-cst.auth.tamu.edu batcave.it.tamu.edu mgmt-2p-cst.ads.tamu.edu cm2.as.tamu.edu

Benefit of change: This change addresses issues with both former Recast Management Servers that were both in different states of degradation and could not be reverted to a functional state since no backup snapshot existed.

By implementing a new sever, its database is now on the primary sql.it.tamu.edu SQL server and the old servers may now be decommissioned.  The new server is on the latest Recast version 5.11.2511.1804, and agents and Recast Console Extensions will be upgraded on each MECM Jump Server. This brings alignment of each application version in accordance with the vendors specification for a properly configured environment.

The latest version includes several bug fixes and Right-Click Tools features outlined in the following release notes: https://docs.recastsoftware.com/help/recast-software-version-5-11-releases#recast-version-51125111804.

Impact to customers: There is no impact on campus faculty, staff, or students as it is a tool used by MECM admins. Recast Agents for OAL workstations will be upgraded and Unit Admins may deploy the new Recast Agent at their earliest convenience.

Change Request 265098 Intune/SCCM Co-Management settings no longer assigned.

Description: Change Description: An emergency change was implemented to reassign the Intune Enrollment Co-management settings after it was discovered that they were no longer assigned to any device group. This reassignment was necessary to resolve an issue reported by Jon, where SCCM agents were failing to install on OAL Self-Driven Autopilot enrolled devices.

Root Cause and Initial Fix

Root Cause: The Intune Co-management settings had lost their assignments, which prevented proper SCCM agent deployment during Autopilot.

Initial Emergency Action: The Co-management settings were assigned to the device scope group for all Autopilot enrolled devices.

Immediate Outcome: This resolved the issue for OAL Self-Driven devices, as confirmed by Jon.