The January meeting of the UK Powershell User Group takes place Wednesday 21st Jan 2009 6.30pm GMT.
Memphis Room
Building 3
Microsoft Campus TVP
Reading UK
We have a Live Meeting with Jeffrey Snover talking about PowerShell v2
Pizza break
Then Jeremy Pack from HP will then be doing a PowerShell demo - exact topic to be confirmed
It should be a great evening. Jeffrey is obviously the man to ask if you have any burning questions about Powershell, particularly V2 for this event.
Recently I’ve been testing out some different disaster recovery scenarios for Exchange 2003, one of which involved a dial-tone method - i.e. create some new mailbox servers with blank databases to get users up and running quickly and then merge the restored data back in later. One of the types of dial tone method we used was to create new server names rather than re-use existing Exchange server names.
So for example to re-create a four node (3 active, 1 passive) cluster with new names, instead of
Recently I blogged about some scripts I left behind in my previous employment for managing AD - really a lot of them were just quick one liners. Not that that is necessarily a bad thing, one of the best things for me about Powershell is the way you can get great information with very little effort. Of course I am using my good friend the Quest AD cmdlets.
I thought I’d share a few of them:
So we got Episode 6 of the Get-Scripting Podcast out last week. You can get it from here:
Download it here, subscribe in iTunes or via a different feed reader
Normally Alan, Matt and I all arrange to be in the same place to record the show. Given we live in completely different places in the UK this is not easy and is probably the main reason we keep it to one show per month.
I was recently invited to record a webcast by the Product Manager at Quest for PowerGUI, Darin Pendergraft, demoing the Exchange 2003 Powerpack I made for PowerGUI.
They came up with the idea to make some videos / webcasts giving some community members the opportunity to show what PowerGUI can do. A lot of people primarily use it only as a script editor, but the management console side of things is brilliant once you get into it - hopefully these examples will help inspire more people to make some powerpacks.
So I was pretty sceptical for a long while about things like Twitter and Facebook, but I finally gave in mostly thanks to my buddy Alan Renouf and to be honest its been brilliant. Its such a useful way to quickly find information and keep up to date with a particular topic, obviously in my case Powershell.
Whilst at Teched it was a great tool to keep up with things which were going on in sessions or what people where up to.
This is a must watch PowerScripting Podcast special - the hint is in the title.
Jeffrey Snover and Bruce Payette are the two guests, it should be an awesome show.
Thursday 18th Dec 9pm EST, which translates to 2am UK time. I think I’m going to have to stay up for it!
During this last year I’ve done quite a few presentations about Powershell and quite often as part of the demo I have included PowerGUI since I find it a great way to reel people in who aren’t quite yet ready to make a jump the whole way to command line scripting.
One of the topics I usually talk about around this is how I (like most people seem to) initially used the PowerGUI script editor for writing my scripts, but didn’t really get what the PowerGUI console was all about.
We had a lot of fun recording the latest episode of the Get-Scripting podcast on Tuesday night. Its been great having Alan join the show, gives the show a much more conversational feel plus I don’t have to come up with all the content. :-)
We had a really interesting interview in this episode with Dmitry Sotnikov talking about the Quest AD cmdlets and PowerGUI - go check it out.
Following on from my last post about WSUS 3.0 and Powershell another thing which bugged me about the WSUS 3.0 GUI is the Cleanup Wizard. This is a really useful tool for keeping your WSUS deployment running efficiently.
It includes the ability to clean out computers which haven’t synched with the WSUS server for over 30 days - unfortunately 30 days is the default value which can’t be changed in the GUI.