Browse by Tags
All Tags »
Module (
RSS)
var addthis_config = {"data_track_clickback":true}; One of the new improvements in the .NET Framework version 4 is the Microsoft.Win32.RegistryView enumeration. On the 64-bit version of Windows, portions of the registry are stored separately for 32-bit and 64-bit applications. There is a 32-bit view for 32-bit applications and a 64-bit view for 64-bit applications. Many of the 32-bit keys have the same names as their 64-bit counterparts, and vice versa. In the 64-bit version of Registry...
Windows Server 2008 R2 includes a PowerShell module, ServerManager , for managing server roles, role services, and features via PowerShell cmdlets. In Windows 7, there is no such module and we need to use the GUI (OptionalFeatures.exe) or the ‘Deployment Image Servicing and Management’ tool (DISM, see list of resources below). The problem with DISM, from a PowerShell perspective (objects, objects…), is that DISM is a legacy application that emits text and is not written with automation in mind ....
PSTerminalServices is a PowerShell module that helps you manage Terminal Services (including Remote Desktop connections) sessions and processes. No more legacy applications text parsing! The module is based on an open source project named Cassia (version 2.0.0.60), a .NET library for accessing the native Windows Terminal Services API. What you can do with it The following operations are supported on local and remote computers: Enumerating terminal sessions and reporting session information including...
Module authors can use a manifest file for their modules (although this is not required). A manifest file is a .psd1 file that contains a hash table. The keys and values in the hash table describe the contents and attributes of the module, define the prerequisites, and determine how the components are processed. How do you know all the hash table keys? You don’t have to. PowerShell can create the file for you with the New-ModuleManifest cmdlet. New-ModuleManifest creates a new module manifest (.psd1...
About two years ago I wrote a Stand alone registry functions library to help managing Windows Registry on local or remote computers. Now that PowerShell 2.0 has released, I’ve taken the time to convert the library to Advanced Functions and now they are part of a PowerShell module . The big improvement in the functions, beside the richness of PowerShell 2.0 features used in the module ( support for Common Parameters , Comment Based Help and declaring a function that acts similar to a compiled cmdlet...