Windows PowerShell is an extensible automation engine from Microsoft, consisting of a command-line shell and associated scripting language. Windows PowerShell is built on top of, and is integrated with, the Microsoft .NET Framework. Additionally PowerShell enabled easy access to COM and WMI to provide an environment in which administrators perform administrative tasks on both local and remote Windows systems. Recently we had the release of the version 2.0. PowerShell 2.0 is backward-compatible with its earlier one 1.0. This article explains the changes which are undergone from PowerShell 1.0 to PowerShell 2.0.
Download this collection of tools designed to help IT professionals manage a mixed environment of Windows 7, Windows Vista, and Windows XP PCs. The framework includes Windows PowerShell 2.0, Windows Remote Management 2.0, and Background Intelligent Transfer Service (BITS 4.0).
Remember that Microsoft .NET Framework Assistant add-on that Microsoft sneaked into Firefox without explicit permission from end users? […]
This error message is displayed by the Microsoft Windows Installer Engine (Wondering whats this? Read here) and is […]
Well, The Run and RunOnce registry entries help programs to be run automatically. In device driver installations, A […]
Today, The Windows Team announced the upcoming release of the Remote Desktop Connection 7.0 (RDC7) client for Windows […]
Version Check is a basic operation which every developer does while building applications. Microsoft says, wrong Conditions may cause […]
Setting ARPSYSTEMCOMPONENT property to 1 does make the application program to be hidden in the Add/remove programs. The […]
“DLL Isolation” is used when our application needs to have a specific version of a shared DLL for […]
This cryptic-looking string, sometimes referred to as a “Darwin Descriptor” is actually an encoded representation of a specific product, component, and feature. If this extra value exists, Windows Installer will decode the data, and use it to perform checks against that product and component. If the component is found to be missing or corrupt, Windows Installer will launch a repair to restore the missing file or data, and finally launch the referenced application as normal, passing the appropriate command-line options to it.