How to delegate SetSPN in Active Directory

Hi there!  I work as a domain admin for a software development shop.  The product is web and SQL-based, and we use SPN's for authentication.  Our Dev and QA teams are constantly spinning up and destroying VM's as part of our development process, and for each new VM I currently run SetSPN -S HTTP/{server name} {user name} to set authentication with a service account.

What I'd like to do is delegate the running of SetSPN to an AD security group.  We're a 24 hour shop and the overseas folks are getting frustrated having to wait for my working hours to start.  This would make everyone's lives much easier :)

My DC's are a mixture of Server 2008 R2 and Sever 2012 R2, running at a Server 2008 SP2 functional level.  I've followed the steps here under the Delegating Authority To Modify SPN's section, but my test user gets this error: Failed to assign SPN on account '{CN of service account and DN of domain}', error 0x2098/8344 -> Insufficient access rights to perform the operation.

Things I've also tried include:

Running the SetSPN command from an elevated command prompt
Allowed these properties for Computer Objects to the security group: Validated write to service principal name, Validated write to MS DS additional host name, read/write msDS Allowed To Delegate To
Allowed these properties for User Objects to the security group: Read/Write msDS Principal Name,  read/write msDS Allowed To Delegate To
Added the security group to "Enable computer and user accounts to be trusted for delegation" to a custom GPO
Added the service account itself to the security group I've delegated these rights to
Added these same permissions to SELF on the service account user object

What the heck am I missing here?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Amit KumarCommented:
are you planning to provide permission on whole domain or for particular OU?

whatever it is please open DSA.msc then right click on either root domain or choose any OU where computers are stored then open properties --- security --- then click on Advance -- then find a group or user whom you have delegated --- or add an user----- for existing click on Edit ---- then there will be two tabs object and properties click on Properties then see the user/group name to whom you are giving access and change Apply to (Descendent user objects) --- in ACE try to find Read ServicePrincipalName and Write ServicePrincipalName --- mark both of them and run replication then check.
kukhuvudAuthor Commented:
Sadly, this didn't work.  I guess I need to open a ticket with Microsoft!
kukhuvudAuthor Commented:
Microsoft had a solution:  "I did some research on the issue that we were facing yesterday and was able to find the cause why we were not able to set permission on Read ServicePrincipalName and Write ServicePrincipalName for user accounts. These are the filtered properties of user objects and not visible by default. In order to make them visible, you need to perform following steps:

1.      Edit c:\windows\system32\dssec.dat file in notepad.
2.      Search for [user]
3.      Underneath [user], look for ServicePrincipalName=7
4.      Change the value from 7 to 0.
5.      Save the file and reopen Active Directory Users and Computers console.

You will now be able to see Read ServicePrincipalName and Write ServicePrincipalName for User Objects as well."

A friend of mine also has a possible solution, but since I had already applied MS's solution, I haven't tested it yet:  "We have been able to grant a group the ability to run setspn against a user without giving them full control of the AD object. You actually only need to grant “Write Public Information” to the user or group that you wish to be able to run setspn on the object’s security."

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
kukhuvudAuthor Commented:
Microsoft's answer was perfect for delegating setspn to a user object.
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
Microsoft IIS Web Server

From novice to tech pro — start learning today.