Sun Management Center Change Manager 1.0.1 Administration Guide

- Previous: Appendix A Change Manager Browser Interface Navigation (Reference)
- Next: Stale Custom JumpStart Data Not Removed When Change Manager 1.0 Server Software Is Uninstalled

## Sun Management Center Agent Cannot Communicate With the Change Manager Server After Installing a Managed Host

Description:

  When you upgrade your Change Manager 1.0 server to be a Change Manager 1.0.1 server (see How to Upgrade a Change Manager 1.0 Server to Run Sun Management Center 3.5 Server Software), you might experience a problem when installing managed hosts. After you install a Solaris Flash archive on a managed host, the managed host fails to communicate with the Change Manager server.

Cause:

  The custom JumpStart files that were created for the Change Manager 1.0 server are retained. So, if you install a managed host by using these old custom JumpStart files, then the Sun Management Center agent might not communicate with the Change Manager server.

  This problem will occur if you change the value of the “Sun Management Center server seed” during the upgrade of the Change Manager server.

Solution:

  Run Set Up for Install or `changemgr setup` for each managed host that you want to install. This step re-creates the custom JumpStart files for each managed host you specify.

- Previous: Appendix A Change Manager Browser Interface Navigation (Reference)
- Next: Stale Custom JumpStart Data Not Removed When Change Manager 1.0 Server Software Is Uninstalled

- © 2010, Oracle Corporation and/or its affiliates