AGPM Install on Windows Server 2016

Trying to install AGPM 4 sp3 on Windows Server 2016, this is a member server joined to the domain and I am attempting to use a Domain Account to install. When running the AGPM Server setup the AGPM Service fails to start with the error that "service startup was aborted because no matching SPN was found registered for the service account". I have used the setspn command to bind what I believe is the correct spn to the account however I continue to receive these errors. Again I am using a Domain User Account not a gMSA Account, the format for the spn I am using is AGPMServer/myserver.mydomain.com mydomain\serviceaccount. Any help would be greatly appreciated.
bhagsupportAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LearnctxEngineerCommented:
A few years ago I came across the SPN problem in an earlier version and raised a call with Microsoft Premier Support about what seemed to be a bug in the installers logic. Though back then the installer didn't give you an SPN error it would just fail and you had to go through the installer logs to find the SPN issue. Microsoft's advice was to run the installer as a Domain Admin or temporarily elevate the installing account to a Domain Admin for the purpose of registering the relevant SPN records. I've always found the AGPM installer less than ideal, sometimes even if you have manually performed the necessary steps the installer will still fail unless you run it with the required rights to perform the action even if it does not need to.

That said the SPN for the service account should be...

AgpmServer/myserver.mydomain.com/mydomain.com

Open in new window

0
bhagsupportAuthor Commented:
Should the SPN Syntax be AgpmServer/myserver.mydomain.com/mydomain.com mydomain\servicename ?
0
LearnctxEngineerCommented:
If you're talking about running the setspn command, you would run:

setspn -A AgpmServer/myserver.mydomain.com/mydomain.com mydomain\servicename

Open in new window


or

setspn -A AgpmServer/myserver.mydomain.com/mydomain.com servicename

Open in new window

0
bhagsupportAuthor Commented:
Thank you for the advice, that is how I had been constructing the the setspn commands. The issue turned out to be related to also registering the NETBIOS name of the server in the setspn command, I used setspn -S AgpmServer/NETBIOSNAME/mydomain.com mydomain\servicename. Once I created this SPN entry then the installer went through was no issue.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bhagsupportAuthor Commented:
I was able to use the setspn command with the NETBIOS Name of the server in combination with the setspn command using the FQDN and complete the install.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.