For Windows
==========
1- From Windows services stop fglam or from command line %FGLAM_HOME\bin\fglam --stop
2- Remove Agent_Manager Service: from command line: %FGLAM_HOME\bin\fglam -r
3- Copy %FGLAM_HOME to any external storage device.
4- Proceed with the re-image.
5- Copy %FGLAM_HOME to the newly imaged server.
6- Create new Windows Service from command Line: %FGLAM_HOME\bin\fglam -i
7- Start FglAM Service from Windows Services or command line %FGLAM_HOME\bin\fglam --start
8- Log into the FMS Web Console and confirm the Agent Manager is listed and working.
Is best practice to generate a FglAM support bundle before any major change in order to save also last configuration files.
For Linux
========
1- Stop fglam service or daemon with the following options:
Service = %FGLAM_HOME/bin#./fglam --stop
daemon = %FGLAM_HOME/bin#./fglam -q
init.d Script: /etc/init.d/dell-fglam stop
2- Copy %FGLAM_HOME to any external storage device
3- Proceed with the re-image
4- Copy %FGLAM_HOME to the newly imaged server
5- Start fglam service or daemon with the following options:
Service = %FGLAM_HOME/bin#./fglam --start
daemon = %FGLAM_HOME/bin#./fglam -d
init.d Script = /etc/init.d/dell-fglam start
7- Log into the FMS Web Console and confirm the Agent Manager is listed and working
Locating the init.d Script
~~~~~~~~~~~~~~~~~~~~~
Depending on the operating system you are running, the init.d-style script quest-fglam is installed to a different location either by the Agent Manager installer or after you run the script fglam-init-script-installer.sh.
The locations of the installed init.d script (listed by operating system) are as follows:
• AIX: /etc/rc.d/init.d
• All Linux operating systems: /etc/init.d
• HP-UX: /sbin/init.d
• Solaris: /etc/init.d