14.4 CP2 Directory Install Questions

Products

• CA Identity Manager

Issue/Introduction

This ticket is for IDM 14.4 CP2 standalone.

I upgraded one of our dev servers to 14.4 CP2 and have a couple of questions about the Symantec Directory install portion of the CP2 upgrade.

1. Is it possible to prevent dxsetup.exe from rebooting the server? In previous version installs I have received a prompt asking me if I want to reboot. But with the 14.4 CP2 upgrade to Directory 14.1.03 the server rebooted without any warning. How can I prevent this for future upgrades?

2. How should I handle the directory install on our provisioning servers? We're configured for HA with the provisioning server and connector server on one pair of hosts, and the provisioning directory with Symantec Directory on another pair of hosts. My old notes say to run the directory install on the provisioning servers but to not upgrade the provisioning directory. Is this correct?

Environment

Release : 14.4

Resolution

The logs have the details, but here are a couple of log entries that show the restart during the vc_redist install.

 

At the beginning of the log:

Command Line: '-burn.clean.room=C:\temp\dxserver\windows\vc_redist.x64.exe -burn.filehandle.attached=548 -burn.filehandle.self=560 /q'

 

At the end of the log:

[1148:1BDC][2023-03-11T11:31:08]w005: Restarting computer...

 

I’m pretty sure the “/q” on the vc_redist command line means do an unattended installation. So even though I didn’t perform an unattended install for dxserver, it looks like it calls the vc_redist installer which did do an unattended install and that’s probably why I never saw any warning that the reboot was happening.

 

My guess is that the Windows server may have had a pending reboot and that caused the vc_redist installer to call for a  reboot. I’m not sure. I have more servers to upgrade in a couple of weeks and I’ll check the pending reboot status before the dxserver install. If there is a pending reboot I’ll reboot the server first, then run the dxserver install and verify that it doesn’t cause another reboot.