Category:Defender cmdlets reference

From PowerGUI Wiki

Quest Defender enhances security by enabling two-factor authentication to network, Web, and applications-based resources. Defender was designed to base all administration and identity management on an organization's existing investment in Active Directory and eliminates the costs and time involved in setting up and maintaining proprietary databases. In addition, Defender works with any OATH-compliant hardware token enabling organizations to select the most appropriate token for their users.

By leveraging an organization's existing investment in Active Directory and supporting multiple token vendors, Defender enables organizations to increase security and achieve and sustain compliance in a cost-effective manner.

PowerShell Management for Defender, built on Microsoft Windows PowerShell technology, provides a commandline interface that enables automation of Defender administrative tasks. With PowerShell Management for Defender, administrators can administer token related tasks such as assigning tokens to users, assigning a PIN or checking for expired tokens.

The PowerShell Management for Defender command-line tools (cmdlets), like all the Windows PowerShell cmdlets, are designed to deal with objects—structured information that is more than just a string of characters appearing on the screen. The cmdlets do not use text as the basis for interaction with the system, but use an object model that is based on the Microsoft .NET platform. In contrast to traditional, text-based commands, the cmdlets do not require the use of text-processing tools to extract specific information. Rather, you can access portions of the data directly by using standard Windows PowerShell object manipulation commands.

Learn more about Defender at http://www.quest.com/powershell/defender.aspx

Download the PowerShell module at: http://www.quest.com/powershell/defender.aspx