Service Account Not recognised During MP Instal

Michael,

 

 

I think we've been poking in the wrong direction. On a second thought, looking back to your initial post and the error about the logon failure and related security exception context, I think it all comes down to the security profile associated with the account that you're passing into the setup wizard, for the F5 Monitoring service account. You said you get the error, regardless if you're using the designated service account for the F5 Monitoring Service or the 'SCOM admin account'.

 

 

Let's just focus on the designated service account to run the F5 Monitoring Service. There's no other magic going around in the F5 MP setup about the error you get, other than trying to create a WindowsIdentity instance with the service name you're providing. To take the F5 MP setup wizard completely out of the picture, please open up a PowerShell command window on the management server where you try to run the F5 MP setup on, and type the following code into it:

 

 

$wi = New-Object 'System.Security.Principal.WindowsIdentity' 'account_name'; Write-Host $wi.Name;

 

 

This code basically attempts to create a new windows identitiy for the account in question (replace account_name with your service account designated for the F5 Monitoring Service). The output should either give you the domain name of the account or give you the same error you're getting while running the F5 MP setup.

 

 

If you still get the error, you'll have to somehow figure out why the account you're passing in may not have a valid name. If the script above returns a valid name, please pass the exact name as you got from the output, into the F5 MP wizard.

 

 

Julian