Ravikanth CNote: This tip requires PowerShell 2.0 or above. When I start writing a script, I generally start at the shell and make sure the logic I am working on holds good.
Read More
Jaap BrasserWhen working with different PowerShell providers (PSProviders), the use of UNC paths can lead to error messages. This tip will show the pitfalls of using UNC paths when working with PowerShell providers other than the file system.
Read More
David MoravecAs I am still running PowerShell 2.0 on my work computer, I can’t use the Invoke-WebRequest cmdlet. This cmdlet is introduced in Windows PowerShell 3.
Read More
David MoravecAs I mentioned in my previous post, I like to have access to (almost) all my scripts on all machines. That’s why I have Scripts folder inside my Dropbox:\PowerShell\Profile.
Read More
David MoravecAs PowerShell drives are really useful concept, many people use it a lot. I also created some PSDrives for parts of my system I am accessing frequently.
Read More
David MoravecI frequently use different credentials to connect to some of my servers. Oh man, I wish I have just one account J As Configuration Manager is based on WMI, my most frequently used cmdlet is Get-WmiObject.
Read More