When you examine this issue, you notice that, if a set of three-part SPNs includes both a NetBIOS name that has a port and an otherwise identical NetBIOS name that does not have a port, the non-port entry is not re-created by using the new computer name.
For example, you notice the following examples that have identical NetBIOS names:
- customspn/DC1:200/app1 - This three-part SPN has a port (:200) that is specified. In this scenario, the SPN is re-created by using the new fully qualified computer name. The SPN is not recreated by using the new computer NetBIOS name.
- customspn/DC1/app1- This three-part SPN does not have a port that is specified. In this scenario, the SPN is not re-created by using the new computer name
However, SPNs that do not have three parts are all re-created, and fully qualified names are re-created, regardless of whether ports are specified. For example, you notice that in all the following scenarios, SPNs are re-created:
For more information about how to configure and troubleshoot VDC together with details and step-by-step guidance, go to the following Microsoft websites:
Article ID: 2742874 - Last Review: 21 Sep 2012 - Revision: 1