Running PowerShell script file from BAT file

I’ve seen a lot of information about how to run a PowerShell script from inside a BAT file, but most seem very outdated, using the “&” (ampersand) character together with a difficult to remember set of single and double quotes.   For me at least, the simple answer is something like the following, where we assume parameters are passed into the BAT file via the usual method, via %1, %2, etc.

PowerShell.exe -file c:\someplace\someScript.ps1 %1 %2

Very easy.  No convoluted &.  No complex double-quote characters surrounding single-quoted values.  I hope this helps others who, for whatever reason, have to call a PowerShell script from inside a BAT or CMD file.

Where is SharePoint 2010 Service Pack 1? The world wonders.

Those of you who know your history will instantly recognize the title above as borrowed from the coded message of October 24, 1944 from Admiral Nimitz to Admiral Halsey, which originally read “Where is Task Force Thirty Four?” plus the padding phase “The world wonders” which was designed to confuse the Japanese.

In today’s world, it means that approximately a year after it first appeared, SharePoint 2010 still lacks an official Service Pack. The world wonders when it will show up.

Yes, there are numerous (at least five) “cumulative updates”, but I do wonder what kind of person has converted or is planning a conversion of any large production SharePoint 2007 installation to a production SharePoint 2010 installation without first waiting for the official Service Pack 1.

Having used Microsoft technology since 1987, I’ve learned (sometimes the hard way) to always wait for Service Pack 1 before committing to a new major version of anything produced by Microsoft. If you don’t believe me, ask anyone who jumped into SQL Server 7 before Service Pack 1.

Update 2011-05-28: Microsoft says that Service Pack 1 should arrive by then end of June 2011.