PowerScripting Podcast – Episode 5

8 06 2007

A Podcast about Windows PowerShell.

 

  • Introduction
    • Shout-out to Mark Allen for answering the challenge
  • News
    • New AD cmdlets – the one step account creation works great
    • From the ScriptingNewswire, May 2007
      • Windows PowerShell guide for beginners
      • Downloadable and cmdlet-accessible graphical help for Windows PowerShell

 

 

  • Gotchas
    • New-QADUser
    •  Make sure you set the samAccountName and the UPN

Actions

Information

9 responses

8 06 2007
New episode of PowerScripting podcast « Dmitry’s PowerBlog

[...] June 8th, 2007 AD cmdlets , provisioning , PowerShell , podcast Jonathan has just published episode 5 of his PowerScripting podcast. Among other things he is sharing his experience using AD cmdlets and creating new user accounts [...]

12 06 2007
Kevin Kidder

Re: QAD functios.

I was just at techEd in Orlando, where I got to talk with some of the smarties at Quest regarding their efforts about the QAD stuff. It seems that they are pledging that PowerGUI and the QAD cmdlets will be FREE FOR LIFE, and will continue to be developed until we see something better out there (version 2 perhaps? only Jeffrey Snover knows that secret tidbit).

Also, according to te guys at Quest, in the next update, new-QADUser will require -samAccountname, much like how they required -ParentDirectory today. Only time will tell.

Great job on Episode 5. Keep it coming.

Yours in Powershell,

K^2

12 06 2007
Jonathan Walz

Thanks for the kind words. I’m really glad to hear that information about Quest’s plans for the cmdlets and PowerGUI, especially today after reading what Jeffery Snover posted on the PowerShell Team Blog. Thanks for sharing your information.
Jonathan

13 06 2007
Jonathan Walz

Thank you Dmitry for clearing this up for us. Please check out his post.

19 06 2007
Kevin Kidder

Also, I stumbled across a new PowerShell gadget for Vista. Andrew Peters from Mindscape (www.mindscape.co.nz) has coded a powershell gadget for the Vista Sidebar. Version 1.3 seems pretty stable, but there are still some bug to work out that cause the entire sidebar to crash and require all gadgets to restart.

All in all it is pretty cool, allowing the Fly-Out feature to have a memory resident version of the PowerShell running. It can be downloaded from his personal blog site @: http://andrewpeters.net/powershell-gadget/

All Hail PowerShell!

K^2

23 06 2007
Mike Kline

I’m really enjoying your podcasts. This is going to be something I listen to regularly now. Thanks for doing this for the community.

I like during the first episode you said “I’m a beginner too”. If you are considered a beginner with powershell then I’m a -10 :)

23 06 2007
Andy

Hi Jonathan,

I’ve really been enjoying your podcasts. I have found the “resources” section quite useful. Keep up the good work!

Andy

18 10 2007
Darrin

Hello,

First off let me say I love the Podcast. I stumbled onto it two days ago, and already am finishing off episode 6.

My background is in VB Scripting, I’ve created dozens upon dozens of scripts to automate tasks at my company. I’m actually running into a problem with the one-liner from this podcast. My situation is that I’m trying to set permissions on a directory tree, for some reason I attempted to push down the permissions I wanted using explorer but it’s not working. So using the one-liner I thought to do it via Powershell.

However, the one-liner I have works fine for anything in the same directory as I am, it seems to break when going through subdirectories though. The command is similar to Marks, but modified slightly:

get-childitem -recurse | get-acl | where-object {$_.AccessToString -notlike “MHJMBDA\HR Folder Access Allow FullCon*”} | set-acl -AclObject $HRAcl

The variable $HRAcl is the output of get-acl of a known folder containing the permissions I want. When I run this command, the command seems to work, but about 45 seconds into it I get the following message:

Get-Acl : The specified wildcard pattern is not valid: TRANSPARENCY -CONCLUSION [ ORGANIZATIONAL CULTURE.doc
At line:1 char:33
+ get-childitem -recurse | get-acl <<<< | where-object {$_.AccessToString -notlike “MHJMBDAHR Folder Access Allow Ful
lCon*”} | set-acl -AclObject $HRAcl

Also if I remove the where-object command, and just plaster the acl variable onto everything I get the same message. Any ideas? Thanks.

20 10 2007
Jonathan Walz

Thanks for posting this comment, I had fun playing with it. Darrin also posted this over at http://PowerShellCommunity.org and I answered on that site. Here’s a link to the thread. http://powershellcommunity.org/Forums/tabid/54/forumid/1/postid/35/view/topic/Default.aspx

Leave a comment