Showing archive results for January 2013

Jan 21, 2013
Post comments count0
Post likes count0

PowerTip: Find Out From Whence a Command Comes

Doctor Scripto

Summary: Find out information about where a Windows PowerShell command comes from by looking at the module information.  I need to find out who authored a cmdlet. How do I go about finding out this information?  The first thing you need to do is to find the module that supplies the cmdlet. You can use the Get-Command cmdlet...

Scripting Guy!Windows PowerShellPowerTip
Jan 21, 2013
Post comments count0
Post likes count0

Using .NET Framework Assemblies in Windows PowerShell

Doctor Scripto

Summary: Guest bloggers Microsoft PFEs Adam Haynes and Shubert Somer continue their .NET Framework Essentials post by talking about assemblies. Microsoft Scripting Guy, Ed Wilson, is here. Today is part 4 of a 5-part series written by guest blogger Adam Haynes with help from his friend Shubert Somer. You will want to go back and read part 1, part 2...

Scripting Guy!Windows PowerShellguest blogger
Jan 20, 2013
Post comments count0
Post likes count0

PowerTip: Use PowerShell Find all Enabled Group Policy Objects

Doctor Scripto

Summary: Use a Windows PowerShell cmdlet to find all enabled Group Policy objects in an Active Directory domain.  How can I easily find all enabled Group Policy objects in an Active Directory domain?  Use the Get-Gpo cmdlet, specify the domain, and use the –all switch. Pipe the resulting objects to the ...

Scripting Guy!Windows PowerShellPowerTip
Jan 20, 2013
Post comments count0
Post likes count0

Weekend Scripter: Using .NET Framework Enumerations in Windows PowerShell

Doctor Scripto

Summary: Guest bloggers Microsoft PFEs Adam Haynes and Shubert Somer talk about using .NET Framework enumerations with Active Directory. Microsoft Scripting Guy, Ed Wilson, is here. Today is part 3 of a 5-part series by guest blogger Adam Haynes with help along the way from his friend Shubert Somer. You will want to go back to read part 1 and part ...

Scripting Guy!Windows PowerShellguest blogger
Jan 19, 2013
Post comments count0
Post likes count0

PowerTip: Check the Secure Boot Policy on Windows 8

Doctor Scripto

Summary: Use a Windows 8 cmdlet to detect Secure Boot policy.  How can I check my Secure Boot policy on Windows 8?  Use the Get-SecureBootPolicy cmdlet. This cmdlet must run with Admin rights. If your computer does not support Secure Boot, an error returns.  

Scripting Guy!Windows PowerShellPowerTip