In the past, I have blogged that when a developer deploys the a WSP package through PowerShell, it’s nice to see if the deployment job succeeds before moving on to the next step.
In the past, this is the command I have used:
Get-SPSolution -Identity SomeSolution.wsp | Select Last* | fl
And waited until all servers in the farm are reporting that deployment is successful. However, at times the job is still running. A more robust approach I use now is to look for JobExists property and ensure that it’s false. Therefore updated command I use now:
Get-SPSolution -Identity SomeSolution.wsp | Select Last*, JobExists | fl
At my current client, I run a sandbox SharePoint 2010 single server environment on top of Windows 7 with my corporate credential as my service account.
I get a wonderful message saying that my account password is about to expire, so obviously, my heart goes thumping. Here we go again. It’s time to lose more hours on running around and switching around password within SharePoint 2010 that powers all the web apps, service apps, etc…
However, as per my colleague suggestion, it turned out to be pretty easy:
- Change your corporate account password using Ctrl+Alt+Delete -> Change Password
- Run the following command in PS to quickly update everything else.
$cred=get-credential;Set-SPManagedAccount -Identity $cred.Username -ExistingPassword $cred.Password -UseExistingPassword
Restart the IIS via “iisreset /noforce” and you’re all set.
There are many instances where our team would deploy the SharePoint solutions through management shell and then opens the Central Administration in the browser to see the deployment progress.
It’s much easier to just write a one liner to see the status instead.
1: get-SPSolution SampleSolution | Select Last* | format-list