If you want to hear an interesting inteview regarding PowerShell v3, what got fixed, what didn't and some of the why certain things are different then here's the discussion with Jeffrey Snover. I heard interviews with him before and he's pretty funny as well as fairly straight forward about what got fixed and why certain descians were made.
http://powerscripting.wordpress.com/2012/05/21/episode-186-the-scripting-games-winners-with-jeffrey-snover-and-ed-wilson/ Also, for those on this list starting out with PowerShell, bookmark this link: http://social.technet.microsoft.com/wiki/contents/articles/183.windows-powershell-survival-guide-en-us.aspx It's well maintained. Steven Peck http://www.blkmtn.org On Wed, Jun 6, 2012 at 5:23 PM, Damien Solodow <damien.solo...@harrison.edu>wrote: > That’s what I was afraid of. I hope that Exchange won’t require a new > version or SP to support 3.0 as I’d hate to have my management tools broken. > **** > > ** ** > > DAMIEN SOLODOW**** > > Systems Engineer**** > > 317.447.6033 (office)**** > > 317.447.6014 (fax)**** > > HARRISON COLLEGE**** > > ** ** > > *From:* Michael B. Smith [mailto:mich...@smithcons.com] > *Sent:* Wednesday, June 06, 2012 8:17 PM > > *To:* NT System Admin Issues > *Subject:* RE: Powershell and dos batch**** > > ** ** > > Pretty much everything will require updates.**** > > ** ** > > *From:* Damien Solodow [mailto:damien.solo...@harrison.edu] > *Sent:* Wednesday, June 06, 2012 7:45 PM > *To:* NT System Admin Issues > *Subject:* RE: Powershell and dos batch**** > > ** ** > > Who reads those? ;)**** > > And yeah, I did read through the ones for the most recent 3.0 RC. I did > like the number of “this will now throw an error because it should have > before”**** > > ** ** > > On a related note, any idea how existing modules like Exchange 2010 and > the MS AD module will work with 3.0? I’ll wager the Citrix and VMware ones > will need updates, and I know there is a workaround required with > SharePoint 2010…**** > > ** ** > > DAMIEN SOLODOW**** > > Systems Engineer**** > > 317.447.6033 (office)**** > > 317.447.6014 (fax)**** > > HARRISON COLLEGE**** > > ** ** > > *From:* Michael B. Smith [mailto:mich...@smithcons.com] > *Sent:* Wednesday, June 06, 2012 6:44 PM > *To:* NT System Admin Issues > *Subject:* RE: Powershell and dos batch**** > > ** ** > > OH NO THEY AREN’T fully backward compatible. Read your release notes.**** > > ** ** > > *From:* Damien Solodow [mailto:damien.solo...@harrison.edu] > *Sent:* Wednesday, June 06, 2012 5:41 PM > *To:* NT System Admin Issues > *Subject:* RE: Powershell and dos batch**** > > ** ** > > I blame MBS. ;)**** > > ** ** > > I think it’s because the newer versions are fully backward compatible so > there is no reason for parallel installs. So by putting it in the same > directory scripts and the like invoking powershell aren’t broken by new > versions.**** > > ** ** > > DAMIEN SOLODOW**** > > Systems Engineer**** > > 317.447.6033 (office)**** > > 317.447.6014 (fax)**** > > HARRISON COLLEGE**** > > ** ** > > *From:* Miller Bonnie L. [mailto:mille...@mukilteo.wednet.edu] > *Sent:* Wednesday, June 06, 2012 4:49 PM > *To:* NT System Admin Issues > *Subject:* RE: Powershell and dos batch**** > > ** ** > > Ah, did not know that! I wonder who thought up that gem? =)**** > > ** ** > > *From:* Damien Solodow [mailto:damien.solo...@harrison.edu] > *Sent:* Wednesday, June 06, 2012 12:47 PM > *To:* NT System Admin Issues > *Subject:* Re: Powershell and dos batch**** > > ** ** > > Actually all current powershell versions (including the forthcoming 3.0) > install in that path. > -------------------------- > Sent using BlackBerry > > **** > > *From*: Miller Bonnie L. > [mailto:mille...@mukilteo.wednet.edu<mille...@mukilteo.wednet.edu>] > > *Sent*: Wednesday, June 06, 2012 02:47 PM > *To*: NT System Admin Issues <ntsysadmin@lyris.sunbelt-software.com> > *Subject*: RE: Powershell and dos batch > **** > > Do they require Powershell v2? I see you are using v1.0.**** > > ** ** > > *From:* itli...@imcu.com [mailto:itli...@imcu.com <itli...@imcu.com>] > *Sent:* Wednesday, June 06, 2012 10:36 AM > *To:* NT System Admin Issues > *Subject:* RE: Powershell and dos batch**** > > ** ** > > I did what you said.**** > > Here is my error so far.**** > > The term 'GET-BEJob' is not recognized as the name of a cmdlet, function, > scri**** > > t file, or operable program. Check the spelling of the name, or if a path > was**** > > ncluded, verify that the path is correct and try again.**** > > At C:\WINDOWS\system32\WindowsPowerShell\v1.0\BackupJob.ps1:1 char:33**** > > + Import-module BEMCLI | GET-BEJob <<<< "Test-Full" | START-BEJob**** > > + CategoryInfo : ObjectNotFound: (GET-BEJob:String) [], > CommandNo**** > > tFoundException**** > > + FullyQualifiedErrorId : CommandNotFoundException**** > > ** ** > > *From:* Damien Solodow > [mailto:damien.solo...@harrison.edu<damien.solo...@harrison.edu>] > > *Posted At:* Wednesday, June 06, 2012 1:18 PM > *Posted To:* itli...@imcu.com > *Conversation:* Powershell and dos batch > *Subject:* RE: Powershell and dos batch**** > > ** ** > > Did you run the set-executionpolicy like I mentioned? **** > > If so, what is the exact error you are receiving when running the batch?** > ** > ------------------------------ > > *From:* itli...@imcu.com [itli...@imcu.com] > *Sent:* Wednesday, June 06, 2012 1:00 PM > *To:* NT System Admin Issues > *Subject:* RE: Powershell and dos batch**** > > Not helping…**** > > **** > > *From:* Joseph L. Casale [mailto:jcas...@activenetwerx.com] > *Posted At:* Wednesday, June 06, 2012 12:49 PM > *Posted To:* itli...@imcu.com > *Conversation:* Powershell and dos batch > *Subject:* RE: Powershell and dos batch**** > > **** > > From a DOS shell, type `powershell.exe -?` and you'll see how to invoke a > session with a script and all the other options which may need to apply. * > *** > > **** > > jlc**** > ------------------------------ > > *From:* itli...@imcu.com [itli...@imcu.com] > *Sent:* Wednesday, June 06, 2012 10:07 AM > *To:* NT System Admin Issues > *Subject:* Powershell and dos batch**** > > I have need to running a powershell script for Backup Exec 2012 through a > DOS batch file.**** > > Here is what I have so far:**** > > **** > > ::Batch File**** > > ::powershell**** > > **** > > C:\windows\system32\WindowsPowerShell\v1.0\powershell.exe > "'e:\in01\oper\task\BackupJob.ps1'"**** > > exit**** > > _______________________**** > > BackupJob.ps1**** > > Import-Module BEMCLI | Get-BEJob -Name "BackupJob-Full" | Start-BEJob | > exit**** > > **** > > **** > > Where the BackupJob is already set up in the GUI library on the server.*** > * > > I get nothing.**** > > The batch file just finishes.**** > > I put a pause after it and I see no errors?**** > > So what am I doing wrong and how do I make it work?**** > > Thanks**** > > **** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin**** > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
