I’ve been using PowerShell for quite a while now, as you may have gathered from some of my previous posts. However, I have yet to really dig into PowerShell Web Access (PSWA) with Windows Server 2012. That is, until today.
I have been slowly getting my VM environment up to par on my new Focal Point Solutions laptop, and the last piece that I was hoping to try was PSWA with SP2013. I assumed this would work, but in a few Google searches I had yet to find anyone who had shown any screenshots of this working – so I decided to be that guy.
In the screenshots below, I am running PSWA from Google Chrome on my host (Windows 8) – connecting to a VM running on my local Hyper-V instance. The VM is SP2013 connected to another VM for a domain controller. I’ve got Hyper-V networking set up so that all of my VMs have 10.x.x.x IP addresses and I can access them from my host without issues. For PSWA, I went with the “test” setup by following the instructions here. That is, i am using a test certificate and I am not using the kind of security i would certainly use for a Production environment. It’s my Virtual environment, sue me…
In any case, i literally followed the Technet instructions to get PSWA installed and configured – and then I opened up my browser and entered the URL of http://servername/PSWA and voila – I get a login prompt:
Okay that’s cool, so I entered my domain\spfarm account and password and the server name and then i was able to sign in…
Now for the fun I started typing a few things and as you can see, I’m able to access not only the $Host itself (which interestingly enough is v1, not v3) but by adding the Microsoft.SharePoint.PowerShell snapin I can then run my SharePoint Cmdlets like Get-SPFarm and Get-SPSite.
How sweet is that?
This article was originally posted here.