Skip to main content

Hyena a tool integrated with active directory

 Active Directory Integration and Features

Download Now


Hyena provides full support for Active Directory (AD) Organizational Units, directory searching, universal groups, management of object properties, security auditing, and other AD mixed and native mode features. Due to Hyena's ease-of-use, most AD environments can be managed more efficiently and quickly using Hyena's AD management functions. Hyena has numerous features that you won't find in the standard built-in Microsoft administration tools.


Hyena adds a new Windows 2000 domain object class. When a Windows 2000 domain is expanded in Hyena's tree window, additional sub-objects are displayed, specifically: Containers/OUs, All Users, All Groups, Global Groups, Local Groups, and Universal Groups objects. All management of the display of Active Directory objects are handled entirely by LDAP queries to Active Directory.

Organizational Units (OUs) are fully supported, both for browsing OU contents, as well as for creating new users, groups, contacts, and computer objects directly into an OU. A powerful Find feature is available for any OU, allowing selectable criteria for finding and filtering AD information. OU properties are also available, including full support for management of Group Policy Object (GPO) information.

Hyena's Filtering Toolbar provides for powerful object filtering when browsing the contents of any OU, including traversing into sub-OUs.

Hyena is the only product that supports customizable Active Directory queries at every object level. Define your own queries, or use any of the predefined queries to display custom "views" of exactly what directory attributes you want to see for organizational units, users, groups, or computers. Hyena's queries can also contain a customized LDAP filter, if desired, for the ultimate in server-side AD filtering and query performance.
With Hyena, you can access and view any AD attribute, including, the employee ID and user photo attributes. Moreover, you can add your own custom AD attributes for managing users.


Hyena includes an extensive ADSIedit-like capability to manage any Active Directory attribute for one or more directory objects. But unlike ADSI-Edit, Hyena's AD attribute management dialogs are easy to use and understand. Plus, you can define your own attribute sets to be used over and over and visually see what the values are before and after making any changes.

Hyena supports the use of the standard shell property pages for management of many Active Directory objects, providing for full MMC-like functionality, while still providing Hyena's legendary ease-of-use and navigation. Hyena also supports the display of the shell context menu for most directory objects, providing access to popular Microsoft functions such as Exchange Tasks for email-enabled objects, as well as 3rd-party shell extensions.

Active Directory administrators know how difficult it can be to keep track of delegated security rights. Hyena makes keeping track of this much easier with Active Directory Security Listing views : Just select one or more AD objects, right click, and select List Directory Security. Its that simple.
Hyena provides access to the standard Microsoft Active Directory 'Find' dialog, but adds two important features: The selection criteria can be saved for future or external use, and the objects that are found can be returned to Hyena for further management tasks.

Hyena supports management of Exchange 5.5 and 200x mailboxes: mailbox creation, deletion, and property modification can all be easily controlled in Hyena's powerful GUI.
As always, Hyena's output window, including any Active Directory displays, can be easily exported or integrated into Hyena's built-in Microsoft Access database.

Comments

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...