Post Configuration Blues

I only recently created this BLOG because the majority of the 'findings' that I 'find' only benefit people within the organisation. The last post and this one could benefit some other poor soul out there in internet land so here goes...

After running PSCONFIG or the Post Configuration Wizard you may notice that Central Admin doesn't work.
For reasons unknown the binding in IIS gets altered/removed and needs the HTTPS port and SSL cert re applying for the Central Admin site.

If this saves you a few minutes then my work here is done.

Project Server 2010 setup

I've been trying to recreate our Project Server 2010 environment in a new development farm and while the majority of the installation is straightforward I had a real head-scratcher when the Project Application Service instance wasn't available in my SharePoint Central Admin 'Services on Server' page. I guess the phrase "familiarity breeds contempt" could be used to describe my failing. I've been doing a lot of patching of late and the PowerShell cmdlet that you run to upgrade the databases after all server have been patched is always close at hand (PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures) so I ran that instead of using the 'Post Configuration Wizard' once the Project Server bits had been installed to all farm servers. It seems like this cmdlet doesn't actually enable the newly installed features that are necessary for the next steps in the Project Server configuration process. Once I repeated the Post Config step using the UI rather than PowerShell the Project Application Service was visible in the 'Services on Server' page and after enabling that on each server I was able to create a new 'Project Service Application' and provision the PWA site. I hope this helps someone else who assumes that PSCONFIG.EXE is the same as the Post Configuration Wizard.