Service Account Not recognised During MP Instal

Hi Julian,

 

 

I have managed to get past the error message that pops-up whenever I enter the credentials for the F5 monitoring Service Account in the installer wizard by asking one of my Domain Admins to attempt to launch the installer with a Domain Admin level user account.

 

 

This time, the installer wizard did not complain and we were able to see the summary screen that indicates "The F5 Networks management Pack is ready to Install" so it seems that the issue is not the service accounts that I had specified were incorrect but that the installer needs to run using a Domain Admin level account.

 

 

This seems to be borne-out by the Installation Tutorial video that I watched in which the demonstrator right-clicks the F5 MP Installer icon and selects Run As and then enters a Domain Admin user account for his test lab.

 

 

In my own test-lab where the installer worked the account I was logged-in with when I ran the installer was also a Domain Admin though I was not aware of this at the time. I was under the impression that it was just the Builtin Local Administrator account but now I am told it was in fact a Domain Admin account.

 

 

In the Documentation for the F5 Networks Management Pack there does not appear to be any explicit reference to the installer needing to be run using a Domain Admin level account.

 

 

To quote the Installing the F5 management Pack document:

 

 

User Accounts

 

You will want to make sure you have access to the following two accounts.

 

 

•Installation Account -

 

This is the account you will use to install the F5 Management Pack with. This account should have local system administrator privileges, SQL administrator privileges, and Operations Manager Administrator privileges.

 

 

•Service Account -

 

This is the account you will specify to run the F5 Monitoring Service as. This account must be in a group that is specified in the Operations Manager Administrators in the Operations Manager Console under Administration->Security->User Roles->Operations Manager Administrators. It is recommended that you create a separate Active Directory group for this purpose if you have not done so already. This user is also required to be a local system administrator and a SQL administrator.

 

 

So, my next question to this forum is if anyone can provide me with the reason why this installer needs to use a Domain Admin level account in order to run?

 

 

It is one thing if the installer could run using a local Administrator account that only modifies one server but as the installer seems to need a Domain Admin account one would assume that the installer is attempting to write to the Domain which is not something that you allow without knowing exactly what it is that the installer is doing.

 

 

From a Change Management perspective knowing what exactly the installer does that requires it to be run with a Domain Admin account is extremely important in my environment so if anyone in the product team is able to respond I would be grateful as it would assist me in getting approval to run the installer with such an account.

 

 

With thanks for all replies,

 

 

flipa