Episode 108 – SharePoint 2010 with Gary LaPointe

A Podcast about Windows PowerShell.
Listen:

News

Version 2.1 of PowerWF Studio has just been released. PowerWF is a Visual PowerShell development tool allowing users to build PowerShell scripts as workflows, which are similar to a flowchart or Visio diagram.  Once created, workflows can be deployed as applications, run as a scheduled task, or back to PowerShell as a script.  You can even push data to System Center with the click of a button. To get your free 30 day trial go to PowerWF.com.

• @marcoshaw: #PowerShell v3 will be released at this year's TechEd North America in the Big Easy! Complete overwrite for .NET 4!
• The 2010 Scripting Games are ON! Check out the announcement on the Scirpting Guys blog, and you can help spread the news by putting a badge on your blog.
• User Group News
  • Arizona PowerShell User Group meets April 7th
• It's MVP day! Two new MVPs have joined the ranks
  • Sean Kearney
  • Jonathan Medd
  • Doug Finke and Richard Siddaway were renewed
• PowerGUI turns 3!

 

•  

Interview

Before you acquire power, you must acquire knowledge – and Quest Software has what you need! In Jeffery Hicks’ e-book, “Managing Active Directory with Windows PowerShell,” learn how PowerShell helps you master local accounts and groups, password management, security and permissions and much, much more. You’ll also learn about the PowerShell extras and out-of-the-box features that will help you control Active Directory. Don’t wait – visit quest.com/powershellbook to register for your free copy or quest.com/powerguipro and see why PowerShell and Quest PowerGUI are the ultimate Windows management tools.

Links

• Company: http://www.sharesquared.com
• Blog: http://stsadm.blogspot.com/

Questions

• AndrewTearle: ## How large would an enterprise need to be to consider using SharePoint ?
• CodyGros: ## Can he explain the disposal of SharePoint objects in PowerShell? and why it is important?
• TobyM: ## Does think the MSFT will continue to develope PowerShell cmdlets for SharePoint 2010 to fill in the holes he mentioned earlier?

Hero/Power - Sylar

Resources

This segment is brought to you by SAPIEN Technologies.

• Doug Finke wrote a Netflix catalog browser using PowerShell with OData
• Ravikanth Chaganti wrote a Layman's guide to PowerShell 2.0 remoting
• Al Renouf has released v5 of his popular vCheck script (VMware PowerCLI)
• MVP Jonathan Medd posted on Enabling PowerShell 2.0 Remoting in an Enterprise
• MVP Tibor Soós wrote a cool post on the Scirpting Guys blog about old-school text-mode graphics

 

 

• PowerShell quick start for Server Core R2
• Working with the [console] class
• Getting objects into Start-Job
  • start-job -ArgumentList $list {$arg | start-process}

 

Listener John sent this one in:

I got one! (he yelled through tears while pounding his fist on the floor)  After being so good to me and so reasonable about its idiosyncracies, PowerShell has hung it to me good on this one.


Here's what I was after.  I wanted to format my IP addresses I was iterating through so that I could later sort the collection and have it sort correctly.  I used string formating to take the pieces of the address and concatenate it with periods and wound up with this:
010.001.001.001
Before doing the wmi query I had in mind, I wanted to make sure the system was up and not have to wait on the wmi timeout so I had something like this:
if (test-connection prettyip($_) -count 1 -quiet) {go do other stuff}


The prettyip thing came late in the day just so I could further analyze the data and when I put it in, everything stopped.  The test-connection test sat and sat before finally giving up and then my script went on with its fail routine even though I knew these machines were up.


I'm going to let you go try test-connection or ping (that's all I've tested so far) and you're going to find that it tries to ping 8.1.1.1  It's converting the ip to octal.  It has something to do with the leading 0 (and the number being otherwise acceptable in base 8).  060.001.001.001 will ping 48.1.1.1
It isn't hard to work around, but WHO, honestly, expects this behavior?!  If you have (as I did) a mix of 10.x.x.x and 198.216.24.x (our public range) IP's, it will make you think you've lost it.
test-connection 198.216.24.104 works and 198.216.024.104 doesn't.
I can see how it's happening (or think I can) just as 0x0e is hex, 010 CAN be interpreted as octal but should it be?  Really?


It took me lots longer to figure this out than I'd like.  I had about 4 red herrings flopping around on the editor and though I didn't cry, it's only because I'm just too manly and pirate-like.  Otherwise...  I'da been sobbing.


So...  There you go, fellers.  It got me.  Don't let it get you.