OSIM: When deploying Windows 10 with the parameter set to install the ITCM agent, the CAF service is missing in services.msc, and CAF does not start.

Document ID : KB000009034
Last Modified Date : 05/03/2018
Show Technical Document Details
Issue:

When deploying Windows 10 to a target PC, with the OSIM InstallAgent=yes parameter, the ITCM agent gets installed, however the CAF service is missing/not installed inside of services.msc.  As a result, the ITCM agent is not functional...

2017-12-22_14-58-08.png

Environment:
Client Automation (ITCM) -- r14 SP1 & SP2
Cause:

The ITCM agent installation occurs inside the custom.cmd file, which executes while still inside the Windows setup environment.  Reviewing the MSI trace, for some unclear reason, the CAF service install returns an error code.

Resolution:

This issue has been reported to CA Development for remediation in a future release of ITCM.  For now, we can edit the oobecustom.cmd file, to include commands to ensure the CAF service is installed and started after the OSIM process is completed.  Unlike the custom.cmd file which is executed during the Windows Setup environment, the oobecustom.cmd file is executed by Windows itself, after reboot from the setup environment.

On the ITCM Domain Manager, you can find the oobecustom.cmd file here:

C:\Program Files (x86)\CA\DSM\Server\SDBS\var\managedpc\images\win10_1703\win10_1703\oeminst

2017-12-22_15-10-07.png

Add the following lines to the bottom of the oobecustom.cmd file:

------------------------------- 
if "$InstallAgent$" == "yes" ( 

rem -- install caf service 
echo Install CAF Service (in case it was missed) >> c:\calogfile.txt 
caf install >> c:\calogfile.txt 

rem -- start caf service 
echo Start CAF Service (in case it was missed) >> c:\calogfile.txt 
caf start >> c:\calogfile.txt 

-------------------------------

It should look like this:

2017-12-22_15-23-53.png

Note: After updating the script on the Domain Manager, you will need to remove the OS image from any remote Scalability Servers/Boot Servers, and then redeploy the updated OS image back out.