(edit @ 4:14 PM EDT: last minute guest change!)
Live show happens tonight! Please join us as we talk with Adam Driscoll, PowerShell MVP, and Andrew Sayre, SDE at Microsoft’s Visual Studio Cloud Tooling team. The topic is a big one: PowerShell Tools for Visual Studio, aka PoshTools!
As always, showtime is at 9:30 PM EDT, and you can watch the live stream at live.powerscripting.net. See ya there!
Join us on Wednesday Dec 18 ( not our usual Thursday) as we talk with Adam Driscoll and Chris Ashley from Dell about PowerGUI and more.
Recently Adam Driscoll of PowerGUI VSX fame was a guest on the .NET Rocks! podcast show, chatting with Carl and Richard about his TFS plugin for Android, PowerShell, PowerGUI, and PowerGUI VSX. Today that show was made available for download, so head on over to the .NET Rocks! page listen to Adam, Carl and Richard in Episode 647 of .NET Rocks!
A Podcast about Windows PowerShell.
In This Episode
Tonight on the PowerScripting Podcast we talk to Adam Driscoll about PowerGUI Visual Studio Extensions
Execute commands and scripts from anywhere including the office and remote locations, as well as from a Web browser or smart phone with PowerGUI Pro from Quest Software. With the MobileShell feature, administrators can quickly run commands to troubleshoot problems or make changes, even when away from your desk! This gives teams more flexibility to work remotely while traveling, and to leverage admins from other offices in case of an emergency.
Â· Execute queries remotely to determine if services or processes are running
Â· Restart services, processes, or entire servers
Â· Check mailbox settings
Â· Unlock user accounts
Â· Reset passwords
Â· Run custom scripts
Visit quest.com/powerguipro and see why PowerShell and Quest PowerGUI are the ultimate Windows management tools.
This segment is brought to you by SAPIEN Technologies.
This segment is brought to you by Serverfault.com!
PowerCLI 4.1 has introduced a big change to the namespace of its .NET types. Listen to the show as we elaborate on the impact of this change to your scripts. You can also read more about this on Poshoholic
and the VI PowerShell blog