Forum Discussion
David_23288
Nimbostratus
NimbostratusInstall on second management server removes management pack from RMS
We have installed the management pack on the RMS and it works well. We install on a secondary management server and the first time we get an error that the file Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Console.psc1 is missing. I copy that file from the RMS server to the management server and now when I run the install it throws an error as follows: "FATALERROR: The F5 Networks Management Pack could not be located on this Management Group." I log into the console on the RMS and sure enough the entire management pack appears to be gone. The service is still there and running but the management pack does not exist.
I have attached my systeminformation. I need to know why the management pack is deleting from the RMS and how to get it installed to the secondary management server.
- Hey David,
The first thing you might want to try is re-importing the management pack file. If the service is still installed, you shouldn't have any problems.
To import the mp, open up the Operations Manager Operations Console, navigate to the Administration area, the right-click on Management Packs and choose "Import Management Packs..." You will find the F5 Management Pack here: "C:\Program Files\F5 Networks\Management Pack\F5_ManagementPack.mp"
After the import completes successfully, retry installation on the secondary management server.
From what you've told us, there may be a bug in the installer, which is inadvertently removing the mp upon installation failure on the secondary management server. I will look into this potential issue.
Good Luck!
-Dave 
David_23288I had already repaired the install of the management pack on the RMS. That seemed to have fixed the disappearing management pack.
As you indicated I re-ran the installer on the secondary management server and this time around it managed to install the service.
One thing I did notice is that neither the RMS or the secondary management server were able to start the service themselves. On both I had to manually start the service before the installer timed out and then it worked fine.
Thanks for the help it seems to be working.- Great to hear you are up and running.
It's interesting that you had to manually start the service. Was it set to automatic when you looked at it in the service control manager?
Also, it would be of great help to us if you could post the event log messages for "F5 Monitoring Log" from around that time on the secondary management server, as well as the trace.log file located in C:\Program Files\F5 Networks\Management Pack\logs\.
Thank you! - David_23288On the RMS the service was set to Manual when I started it and changed it to Automatic. On the secondary the service was set to Automatic just not started. I save the F5 Monitor Log as a tab delimited and zipped it in with the trace.log and attached.
- Perfect!
Thank you. I'll let you know what we find.
-Dave
