HOW TO: Change the port number of SharePoint 2010 Central Admin POST-INSTALL…

2010 05 26: You’re doing a SharePoint 2010 medium server farm install, and things are moving swimmingly along. You’re doing everything right settings-wise, and are relaxing as the SharePoint Technologies Configuration Wizard coasts along provisioning the Central Admin web app with the custom manually-selected port 10101 per the client’s completely reasonable naming convention (no that’s NOT the real port number). SharePoint completes the install & configure, and you lean forward expecting to wow everyone attending the install (for their own gratification) the cool new features in the new Central Admin web app…

…but when the browser opens to Central Admin (at your port number), all you see is “^&*%*%^$SK”

WHAT WENT WRONG? SharePoint gave NO signs WHATSOEVER that anything was amiss…


Everyone leaves the room snickering, and you feel like a dullard.

Time to earn your keep.

You open a command window and at the C:> prompt run “netstat – a”:
SURE ENOUGH, there IS a process already USING your port number !!! k


You can:
A) UNINSTALL SharePoint 2010, manually delete the databases, and start ALL OVER FROM SCRATCH, but this time enter an UNused port number; OR
B) LEVERAGE a few amazingly-still-working remnant utilities from SP2007.

Me? I’d go with Plan B, and here it is:

OPEN a command prompt, using right-mouse-click >  “run-as-administrator” option to ensure you’ve FULL ADMIN access…

CD to C:\program files\common files\microsoft shared\web server extensions\14\bin

RUN the beautiful little command “STSADM.EXE -o getadminport”
=> The command executes successfully, and you see “10101” (which you KNOW you need to change);

RUN the even-MORE-beautiful command “STSADM.EXE -o setadminport -port 40101”
=> the command chews a bit, then completes successfully;

RE-RUN the beautiful little command “STSADM.EXE -o getadminport”
=> The command executes successfully, and you see “40101” (now changed EVERYWHERE you need it to, including in all the shortcuts & whatnot!!! );

OPEN IIS Manager
START your Central Admin web application (because it likely NEVER STARTED because of the original port conflict!)

CLICK Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Central Administration
=> this now-updated link successfully opens IE to your now-reachable Central Admin web app…

… and all is right with your world.

Thank God that even with my beloved PowerShell running as the “true” admin technology for SharePoint 2010, the original stsadm utility commands (even if actually PowerShell under-the-hood) STILL WORKED.



This entry was posted in Sharepoint Tips. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s