My remoting series on the Scripting Guy blog has finished. The full set of posts is:
PowerShell v4 contains a help file
get-help about_Windows_RT –showwindow
That explains the differences between PowerShell on a full Windows device and on a Windows RT device such as a Surface 2
If you use Get-Process in PowerShell v3
£> Get-Process powershell
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
——- —— —– —– —– —— — ———–
516 17 49436 59220 233 8.86 7100 powershell
PowerShell v4 enables you to see the user account associated with the process
£> Get-Process powershell -IncludeUserName
Handles WS(K) VM(M) CPU(s) Id UserName ProcessName
——- —– —– —— — ——– ———–
593 214888 823 17.27 2148 MANTICORE\richard powershell
Now we have an easy way to discover who started a process
My capacity planning series on the Scripting Guy blog finished last week. Didn’t get chance to post about it as I was at Microsoft in Seattle.
Full series and associated powertip postings:
The detailed agenda for the PowerShell Summit can be linked from here.
Members of the PowerShell team will be speaking at the Summit. They are looking for input on the topics you want them to cover. Please view the list of possible topics and leave your comments at
My capacity planning mini series on the Scripting Guy blog continues with the second part – dealing with storing data in SQL Server – available today
I’ll repeat the URL for the first part for reference
The final agenda for the 2014 PowerShell summit has been released.
I’ve got three sessions:
Cmdletize the registry
There are some interesting sessions on that list.
Nows the time to get those tickets booked.
Having seen the comments regarding the removal of the RT upgrade to Windows 8.1 from the Windows app store I was surprised to see it had re-appeared last night.
Late this morning I started the upgrade. Its a 2GB+ download so make sure your Surface is plugged into the mains!
The download wasn’t a speedy affair but it progressed and immediately cut into the upgrade. Everything seemed to go well – usual questions regarding accepting T&Cs and configuration. Express seems to work OK.
The usual Windows.old is left behind (2GB+) so used Disk Cleanup to delete that through the Clean up System Files button and selecting to remove previous windows installations – see http://windows.microsoft.com/en-GB/windows-8/how-remove-windows-old-folder
The apps that I had installed appear to be preserved and at the moment everything looks good. A painless upgrade for me. Hopefully the earlier reported issues are all resolved.
I reported in this post http://richardspowershellblog.wordpress.com/2013/11/06/get-aduser-issue/ an issue with Get-ADUser under PowerShell 4.0 on Windows 8.1/2012 R2 where using –Properties * caused a failure.
I had a comment that this is schema related and a schema upgrade fixes the problem.
My starting point is a Windows 20012 domain
£> Get-ADDomain | ft DomainMode -a
And I have schema version 56
On a Windows 2012 R2 member server I try get-aduser
£> Get-ADUser -Identity richard -Properties *
Get-ADUser : One or more properties are invalid.
Parameter name: msDS-AssignedAuthNPolicy
At line:1 char:1
+ Get-ADUser -Identity richard -Properties *
+ CategoryInfo : InvalidArgument: (richard:ADUser) [Get-ADUser], ArgumentException
+ FullyQualifiedErrorId : ActiveDirectoryCmdlet:System.ArgumentException,Microsoft.ActiveDirectory.Management.Comm
Now lets try the schema upgrade – looks like it goes to version 69 – that’s quite a big upgrade. Once the upgrade has been performed – let the schema replication occur & reboot the Windows 2012 R2 member server just to make sure nothing is cached that could affect the result.
Now to re-try Get-AdUser
Get-ADUser -Identity richard -Properties *
Get-ADUser -Identity richard -Property *
Both work – we have a winner. If you are seeing this problem the answer is to upgrade your schema. You don’t need to upgrade the Domain Controllers just the schema.
Its a bit naught that this happens – I don’t remember similar problems putting a Windows 8/2012 machine with PowerShell 3.0 into a Windows 2008 r2 domain
One of the useful things about Amazon’s Kindle ecosystem is that you can buy ebooks formatted for Kindle from other vendors and email them into your personal documents library. They can then be sent to your Kindle device or app.
Well they can be sent to a Kindle device or they can be sent to a Kindle app on an iPad. They can’t be sent to a Kindle app on a Windows device – that’s the desktop app downloaded from Amazon or the app from the Windows store for Windows 8.
Come on Amazon – lets have some equality here