Select is a filter
Profile: Richard Siddaway
This is a common scenario:
Get-WmiObject -Class Win32_Logicaldisk | select Name, Size, Freespace
You will see a display with three properties – turning them into a list for ease of display:
Name : C: Size : 248951861248 Freespace : 171627724800
What this means is that you’ve got an object with 3 properties.
£> Get-WmiObject -Class Win32_Logicaldisk | select Name, Size, Freespace | Get-Member
TypeName: Selected.System.Management.ManagementObject
Name MemberType Definition
—- ———- ———-
Equals Method bool Equals(System.Object obj)
GetHashCode Method int GetHashCode()
GetType Method type GetType()
ToString Method string ToString()
Freespace NoteProperty System.UInt64
Freespace=171627569152 Name
NoteProperty System.String Name=C: Size
NoteProperty System.UInt64 Size=248951861248
The object type changes – its now a Selected.System.Management.ManagementObject rather than System.Management.ManagementObject#root\cimv2\Win32_LogicalDisk you get from WMI.
Try this to see the whole list of properties
Get-WmiObject -Class Win32_Logicaldisk | Get-Member
Select-Object is great because you can trim down the size of the objects on your pipeline but you have to remember that once you performed that selection its a one way street you can’t get back to the original.
If you need to perform multiple actions on the objects put them into a variable:
$disks = Get-WmiObject -Class Win32_Logicaldisk
then you can do:
$disks | <pipeline 1>
$disks | <pipeline 2>
or
foreach ($disk in $disks) { <do stuff to the disks>}
Where and when to filter you data using Where-Object or Select-Object is part of your design process and only you know what works in your situation. The rule of thumb is filter early to reduce the data on the pipeline but knowing when to break that rule is what makes or breaks your solution
0 Comments
RSS Feed
Email a friend
Learn Active Directory Management in a MoL on offer
Profile: Richard Siddaway
Learn Active Directory Management in a MoL is 43% off through April 3, 2014 with code pbradm at www.manning.com/siddaway3/
0 Comments
RSS Feed
Email a friend
Module confusion–what’s really in PowerShell 3 and 4
Profile: Richard Siddaway
If I run
Get-Module –ListAvailable
on my Windows 8.1 system (PowerShell 4.0) I find a total of 58 modules installed in $pshome\modules i.e. C:\windows\system32\WindowsPowerShell\v1.0\Modules
These are the modules installed as part of PowerShell. Right?
Wrong?
Compare this with a Windows 7 machine that’s been upgraded to PowerShell 4.0. Repeating the exercise I find a grand total of 15 modules.
So where has the other 75% of my functionality gone.
This is the breakdown down of the modules installed on the Windows 7 machine – terminology is mine (feel free to disagree with the groupings).
Core PowerShell:
Microsoft.PowerShell.Diagnostic
Microsoft.PowerShell.Host
Microsoft.PowerShell.Management
Microsoft.PowerShell.Security
Microsoft.PowerShell.Utility
CimCmdlets
ISE
Microsoft.WSMan.Management
File Transfer module
BitsTransfer
Troubleshooting:
PSDiagnostics
TroubleshootingPack
Other related engines:
PSDesiredStateConfiguration
PSScheduledJob
PSWorkflow
PSWorkflowUtility
and that’s it. Everything else as far as I can determine is CDXML based and therefore can’t be made available on legacy systems. The following modules are included in that category:
AppBackgroundTask
AppLocker
Appx
AssignedAccess
BitLocker
BranchCache
Defender
DirectAccessClientComponents
Dism
DnsClient
International
iSCSI
Kds
MMAgent
MsDtc
NetAdapter
NetConnection
NetEventPacketCapture
NetLbfo
NetNat
NetQos
NetSecurity
NetSwitchTeam
NetTCPIP
NetWNV
NetworkConnectivityStatus
NetworkTransition
PcsvDevice
PKI
PrintManagement
ScheduledTasks
SecureBoot
SmbShare
SmbWitness
StartScreen
Storage
TLS
TrustedPlatformModule
VpnClient
Wdac
WindowsDeveloperLicense
WindowsErrorReporting
WindowsSearch
A CDXML based module is produced by taking a CIM (WMI) class and wrapping it in some simple XML and saving it as a .cdxml file. This can then be published as a PowerShell module. The CIM classes won’t be made available on downlevel systems so you won’t find this functionality on anything earlier than Windows 8/2012.
If you need the functionality supplied by these modules you will either have to use the old command line tools or a WMI class – much of the functionality of the NetAdapter and NETCPIP modules for instance can be duplicated using Win32_NetworkAdapter and Win32_NetworkAdapterConfiguration..
0 Comments
RSS Feed
Email a friend
AD Management in a Month of Lunches in print
Profile: Richard Siddaway
Manning have released the print edition of Learn Active Directory Management in a Month of Lunches – http://www.manning.com/siddaway3/ – joining the pdf version released earlier. ePub & Kindle versions scheduled for 20 March
0 Comments
RSS Feed
Email a friend
Get-ADUser issue fixed
Profile: Richard Siddaway
The issue that I discussed in these posts:
http://richardspowershellblog.wordpress.com/2013/11/08/get-aduser-issue-2/
http://richardspowershellblog.wordpress.com/2013/11/06/get-aduser-issue/
With Get-ADUser and –Properties * in a forest level below 2012 R2 has been resolved in this update:
http://support.microsoft.com/kb/2923122
0 Comments
RSS Feed
Email a friend
End of PowerShell Jobs week
Profile: Richard Siddaway
My series on PowerShell Jobs for the Scripting Guy blog has finished. The set of articles is:
Jobs week 1 : Introduction to PowerShell jobs http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/02/powershell-jobs-week-introduction-to-powershell-jobs.aspx http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/02/powertip-control-job-starts-with-powershell.aspx
Jobs week 2 : WMi and CIM jobs http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/03/powershell-jobs-week-wmi-and-cim-jobs.aspx http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/03/powertip-use-powershell-to-keep-job-data.aspx
Jobs week 3 : Remote Jobs http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/04/powershell-jobs-week-remote-jobs.aspx http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/04/powertip-use-powershell-to-find-job-help.aspx
Jobs week 4 : Scheduled Jobs http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/05/powershell-jobs-week-scheduled-jobs.aspx http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/05/powertip-use-powershell-to-discover-tasks-associated-with-scheduled-jobs.aspx
Jobs week 5 : Workflow Jobs http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/06/powershell-jobs-week-jobs-and-workflows.aspx http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/06/powertip-stop-a-powershell-job.aspx
Jobs week 6 : Job processes http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/07/powershell-jobs-week-job-processes.aspx http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/07/powertip-protect-the-data-produced-by-powershell-jobs.aspx
Jobs week 7 : Jobs in the enterprise http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/08/powershell-jobs-week-jobs-in-the-enterprise.aspx http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/08/powertip-find-more-information-about-windows-powershell-jobs.aspx
Enjoy
0 Comments
RSS Feed
Email a friend
PowerShell Summit 2014 edging closer
Profile: Richard Siddaway
Now we’re in March the Summit is getting closer. Looking forward to see friends old & new and listening to some excellent sessions.
If you haven’t registered there’s still places available.
As a bonus one of the things you’ll take away is a module for working with the registry – filling one of gaps in the PowerShell cmdlets for Windows administrators
0 Comments
RSS Feed
Email a friend
PowerShell Jobs Series
Profile: Richard Siddaway
Today sees the start of my series of articles on PowerShell jobs for the Scripting Guy blog.
First article is here –
With the associated Power Tip here
0 Comments
RSS Feed
Email a friend
do and while
Profile: Richard Siddaway
Do you understand the difference between do loops and while loops? On the surface they appear very similar.
£> do{$i++}while($i -lt 10) £> $i 10
£> $i=0 £> while($i -lt 10){$i++} £> $i 10
BUT there is a difference
£> $i=11 £> do{$i++}while($i -lt 10) £> $i 12
£> $i=11 £> while($i -lt 10){$i++} £> $i
Notice the difference in the final result
A DO loop will ALWAYS execute at least once because the test is at the end.
A while loop has the test at the beginning so may not execute at all.
I’ve seen this cause people real difficulty at times so think about where you need the test to be, if the loop needs to execute at least once and what the final value of any incrementing variables should be
0 Comments
RSS Feed
Email a friend
Automatically create folder for home drive
Profile: Richard Siddaway
In this post http://richardspowershellblog.wordpress.com/2013/10/28/setting-ad-attributes-from-a-csv-file/
I showed how to modify the user’s home folder setting in Active Directory.
A comment was recently left asking about automatically creating the folder on the fileserver and creating the share that is associated with it.
This isn’t a simple exercise – you will need a script to:
You can create the folder using New-Item
New-Item -Path c:\test -Name anyolduser -Type Directory
You can share it
$max = [uint32]5
$type = [uint32]0
Invoke-CimMethod -ClassName Win32_Share -MethodName Create -Arguments @{Name=’anyolduser’; Path=’c:\test\anyolduser’; Type=$type; MaximumAllowed=$max; Description=’anyolduser – homedrive’}
And then you have to set share and NTFS permissions according to your organization’s policies
0 Comments
RSS Feed
Email a friend
