OSIM installation of Windows 11 24H2 in error

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

OSIM installation of a Windows 11 24H2 image is failing with error : "Windows 11 installation has failed" and

ERROR: Setup of <image_name> did not run correctly.

or Installation hangs during Client Automation Agent installation.

Environment

Client Automation 14.5 CU7

Cause

Windows Setup has changed in Windows 11 24H2 and some modifications should be made in OSIM script files.

Resolution

1. Install the patch 99112377 on Domain Manager and/or server with OSIM IPS installed : 99112377
   
   
2. Create a new Boot Image WINPE10x64. This new boot image will have the new version of osimrun.cmd needed for installation of Windows 11 24H2
   
   
3. Create a new OS Image for Windows 11 24H2 using the new Image Type WINDOWS1124H2X64

 

See : Supportability Matrix - OS Installation Management Support

Additional Information

Previous Solution/workaround before publication of patch 99112377 was : 

1- Edit the file C:\Program Files (x86)\CA\DSM\osimips\os-template\updates\winpe10x64\amd64\ca-osim\osimrun.cmd on Domain Manager and add this line :
 
format u: /FS:FAT32 /X /Q /Y
 
in this part :

:normalOS
rem ++++ normal OS setup job
rem ++++ format the complete partition 
if "%$BootServerNFS$%"=="no" (set FILESYSTEM=NTFS) else (set FILESYSTEM=FAT32)
format c: /FS:%FILESYSTEM% /X /Q /V:OSIM_VOL /Y
if %ERRORLEVEL% NEQ 0 (
    echo Failed to format C: volume. Is disk marked read-only or path not available?
    goto end
)
format u: /FS:FAT32 /X /Q /Y

rem ++++ copies CA tools to c: ++++
mkdir c:\ca-osim
xcopy x:\amd64\ca-osim\* c:\ca-osim /Y /E

 

2- Then update the Boot Image to include the updated file osimrun.cmd in the Boot Image :

3- With this new Boot Image, Windows 11 24H2 could be installed but installation hangs during SD Agent installation (this problem should be resolved when certification of Windows 11 24H2 will be completed).

Set InstallAgent = No in OSIM job

SD Agent could be installed later using deployment Wizard