SharePoint – How do I tell if my the FQDN of my server is different from the NetBios Name?

And why do I need to know?


You need to know to set up the User Profile Service Application correctly. If they are different, there is a setting that will make things magically work. If you don’t fix the setting, then get ready for days or even weeks of dealing with: “Syncronisation starting’, and various other unhelpful messages from a stuffed User Profile Sync.


There are plenty of ways of checking the NetBios Names and FQDNs but these are my favourites. They don’t require Active Directory modules and should work on any server.

FQDN of computer:

 HostName Aliases AddressList
 -------- ------- ----------- {} {}

NetBios Domain of Computer:
(gwmi Win32_NTDomain).DomainName MYCompany

In this case != MYCompany so I would have to use NetBiosDomainNamesEnabled = “1”

Next utility for my SharePoint Toolbox

There are times when I need to verify what I am syncing using the User Profiles Synchronization. The problem is, many sites won’t give SharePoint consultants access to the domain controller. This makes it very difficult to query AD.

Sysinternals have a very useful tool called: ADExplorer.
It doesn’t need installing.
You don’t need to be a member of the domain, just run it and put in the credentials.
You can use your Farm or Profile Sync account as it will have read access to your OU as per your setup.

ADExplorer for Browsing Active Directory at SharePoint sites

Click here to download


Just stumbled across AutoSPInstaller. It’s a community SharePoint Installation script.
It seems to be a good start if you haven’t put together your own scripts. And it covers many things that often get forgotten, or need to be done manually ( iFilter for PDF ). But I am finding it a bit infuriating when it gets to the Web Application level. We shall see …..