Windows has evolved over the years with various tools to diagnose and repair issues. Everyone probably remembers the in-box tools to repair wireless connections in Windows XP. They started getting better in Windows Vista, then Windows 7 comes along with PowerShell in-box and an engine to diagnose, repair, and validate fixes automatically. If you open “Control Panel\All Control Panel Items\Troubleshooting” on a Windows 7 machine, you will see all of the in-box Troubleshooters to diagnose and repair things like network connections, Aero desktop effects, and audio playback. What you may not know is that you can build your own Troubleshooters, so they look and feel just like the in-box items and troubleshoot issues specific to your environment. You might have been doing this for a while with custom scripts, but now you can convert those so they look like the ones natively in Windows-in this article, I will tell you how. More »
Following the advent of Windows 7 and PowerShell 2.0, Microsoft has backported the command-line shell and scripting language on older releases of Windows, including Windows Vista SP2 and Windows XP SP3. However, admins looking to take advantage of the evolution in terms of automation for Windows tasks are not able to grab PowerShell 2.0 as a standalone download. Instead, they have access to Windows Management Framework. According to the Redmond company, the Windows Management Framework Core package brings to the table the following components: Windows PowerShell 2.0 and Windows Remote Management (WinRM) 2.0.
Xin Li, Windows PowerShell Team, revealed that some customers had been reporting installation issues related to Windows Management Framework and down-level operating systems. Li indicates that the vast majority of deployment features are reported to produce the following error message “The update does not apply to your system.”
“It is a blocking issue for some customers since they cannot get WMF successfully installed and the error message does not help much with a fix,” Li stated. However, not even Microsoft is offering a fix. Apparently, the installation failures and associated error message is caused by actions taken from the end users, rather than an actual bug in the package. More »
In 2009 Microsoft kicked PowerShell up a notch to the next level, a move which coincided with the release of the latest iteration of the Windows client, Windows 7. In this context, July 22nd marked the release to manufacturing of PowerShell 2.0, while October 22nd was synonymous with the general availability, as the new Windows command-line shell ships included by default into Windows Vista’s successor. Now developers can also access the Windows PowerShell 2.0 software development kit (SDK) which is designed to bring to the table not only sample code, but also reference assemblies that enable the creation of applications with Windows PowerShell at the core.
“This SDK contains reference assemblies and samples that demonstrates how to use the Windows PowerShell 2.0 APIs to build a rich set of applications. In this package, you will find sample code which shows how to use the new PowerShell class, how to write cmdlets that supports eventing, transactions and jobs. In addition, there are examples of host applications that connect to remote computers using individual runspaces and runspace pools. This SDK also includes modified Windows PowerShell 1.0 samples using the modified and improved Windows PowerShell 2.0 APIs,” Microsoft revealed. More »