<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SPN on Vibhu Bhatnagar — PowerShell &amp; Infrastructure Engineer</title><link>https://pwsh.in/tags/spn/</link><description>Recent content in SPN on Vibhu Bhatnagar — PowerShell &amp; Infrastructure Engineer</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 20 Jul 2026 07:30:24 +0530</lastBuildDate><atom:link href="https://pwsh.in/tags/spn/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrate a Kerberos SPN to a New Service Account</title><link>https://pwsh.in/posts/migrate-spn-new-account/</link><pubDate>Mon, 20 Jul 2026 07:30:24 +0530</pubDate><guid>https://pwsh.in/posts/migrate-spn-new-account/</guid><description>&lt;h2 id="what-this-covers">What This Covers&lt;/h2>
&lt;p>How to move a Kerberos Service Principal Name (SPN) from one account to another — the manual step migrations, server renames, and account swaps don&amp;rsquo;t do for you.&lt;/p>
&lt;h2 id="before-you-start">Before You Start&lt;/h2>
&lt;ul>
&lt;li>Domain Admin or delegated &lt;code>Validated write to servicePrincipalName&lt;/code> rights on both the old and new accounts&lt;/li>
&lt;li>&lt;code>setspn.exe&lt;/code> (built into Windows Server, RSAT-AD-Tools on clients)&lt;/li>
&lt;li>The exact SPN string you&amp;rsquo;re moving — run &lt;code>setspn -Q &amp;lt;SPN&amp;gt;&lt;/code> if you&amp;rsquo;re not sure who currently holds it&lt;/li>
&lt;li>A maintenance window: clients holding cached Kerberos tickets against the old SPN mapping will keep failing until tickets expire or are purged&lt;/li>
&lt;/ul>
&lt;h2 id="steps">Steps&lt;/h2>
&lt;h3 id="step-1-inventory-all-spns-on-an-account">Step 1: Inventory all SPNs on an account&lt;/h3>
&lt;p>Before touching anything, see the full picture — every SPN a given service or machine account currently holds:&lt;/p></description></item></channel></rss>