Automating the world one-liner at a time…
MMS is going well. Yesterday Dan and Bruce presented an Introduction To PowerShell talk and then we all presented a What's Coming In PowerShell V2 talk. The slides are attached.
Jeffrey Snover [MSFT] Windows Management Partner Architect Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
It's a shame that #PowerShell on irc.FreeNode.net can't make it onto the community resources slide...
Would it kill you to provide the slides in widely-compatible form like, say, HTML or PDF? The company I work for is running Office 03 and has no plans to upgrade before Vista migration, and that could take a few years...
> Would it kill you to provide the slides in widely-compatible form like, say, HTML or PDF?
Actually I spent a bunch of time on this. I exported it to a previous PowerPoint format and it was so large that the uploads to the website failed. I got a lousy error message so I'm not sure why it failed but after 3 failed attempts, I uploaded this version and it worked so I guessed that it was size.
Anyway I'm working the show so I don't have a lot of time to mess with this and if you look it up, there are plugins that you can install on your existing office to read Office 2007 files.
Sorry for the inconvience.
Jeffrey Snover [MSFT]
Windows Management Partner Architect
Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
You can use the free PowerPoint viewer to view the presentation. Here's the link:
Would it kill you to ask nicely?
Great stuff!!! I'm really looking forward to digging in to 2.0.
One question I have though is about using PowerShell for monitoring. When I worked for Exchange we built a service specifically for running monitoring cmdlets. This allowed us to run many cmdlets on short schedules without incurring the overhead of starting PowerShell every time.
I'm still working on monitoring, but no longer work for Exchange and don't have such a cool service to do my bidding. I have to open PowerShell every time I want to execute a script or cmdlet and therefore have to limit my usage of powershell for monitoring.
Are there any features in 2.0 that will let me use PowerShell to it's fullest extent without writing my own host service?
all the best
"Would it kill you to provide the slides in widely-compatible form like, say, HTML or PDF? The company I work for is running Office 03 and has no plans to upgrade before Vista migration, and that could take a few years..."
<RANT>Instead of being critical of the content given, I believe thanks should be given to Jeffrey providing this info. With comments like the one above, you take away the enjoyment of providing information like this to customers. Keep in mind, he is not required to do this.</RANT>
> Are there any features in 2.0 that will let me use PowerShell to it's fullest extent without writing my own host service?
I'm very interested in your scenario but I didn't understand the details. In particular, what is the model you are now using and why can't you host PowerShell? Also - what would a nirvana solution look like for you?
Exciting presentation filled with good stuff. I'm looking forward to PS 2.0. I realize that you're working on a whole native remoting concept, but one request I'd like to lay on you is to fix compatibility with PTYs under Interix (SUA).
The problem is that if you have a terminal that is anything but posix.exe, then Powershell hangs during startup. For example, it doesn't work with XTerm, Interix Telnet Daemon or (the biggy for us) OpenSSH. I'm a big fan of OpenSSH and we're still going to be using it even if there is native PowerShell remoting that we're also using.
It seems like the Prompt function is the trigger of the hang, maybe the $host.UI.RawUI API? The unsatisfactory workaround is to alias (under TCSH/KSH/BASH on my Vista x64 box) PowerShell to
"/dev/fs/C/Windows/System32/WindowsPowerShell/v1.0/powershell.exe -command -". Then you can invoke a sort of crippled PowerShell session inside your SSH shell session. One of the real frustrations is that you can't use ^C or it kills your session.
We spend a lot of time on servers using OpenSSH and bouncing between Solaris, Linux and Windows. We also use OpenSSH port forwarding heavily. It seems like PowerShell remoting as you're envisioning it is going to be more of a web service thing. It just doesn't sound like it's going to address these use scenarios.
I don't know who needs to patch what and whether it's an Interix problem or a PowerShell problem, but I'd really like to see seamless compatibility. I know you guys have ties to the Interix team through Bruce Payette. Please, please can you resolve this?
PowerShell is one of the 3 most exciting things I've seen come out of MSFT in the last 10 years. The other two were SQL 7 and C#. Good on ya!
I'm assuming you're familiar with the model for the MSExchangeMonitoring service in Exchange 2007. If not, talk to An on the Exchange team. He'll give you the full scoop.
In a nutshell, MOM runs a bunch of the Test-* Exchange cmdlets on a schedule to monitor availablility. These test mailbox connectivity, mailflow between servers, etc.
Rather than incurring the penalty of starting PowerShell (really - it's .NET's fault) multiple times per minute in some cases, the monitoring service hosts PowerShell and a VBScript in the Exchange management pack passes requests to the service to run the Test-* cmdlets.
That works great for Exchange, but the service was designed very carefully to prevent it from executing other cmdlets or scripts in order to prevent possible security issues and to minimize the testing required.
In my present role I'd like to be able to use PowerShell for at least most of my monitoring, but since I don't have a service hosting PowerShell I have to start it every time I run a cmdlet or script.
Ideally, in the short term I'd like to see something similar to the Exchange monitoring service , except open for running all cmdlets and scripts passed to it from both 32-bit and 64-bit processes.
In the longer term, I'd like native support for running cmdlets and PowerShell scripts in OpsMgr where I can essentially build my monitoring pipeline by telling OpsMgr which cmdlet/script to run to collect data and then specify an additional cmdlet/script to process the data and generate alerts or store the data in the reporting database.
Have a great weekend!
Actually, I tried opening the slide presentation in PPT Viewer 2007 (with SP1 installed) and it was unable to open it.
The slides content was such a great teaser I want to see the demo's too. It looks like there will be a lot of value for the casual script writer (me) and even more for the hard core development types.
I'd like to see the slides but get
'PowerPoint Viewer cannot open the file "SE02_Snover_v08.pptx" '
from a freshly downloaded PPT 2007 viewer
Are the slides for the other talk "PowerShell Scripting for Wizards" available anywhere, I can't find them on the site.