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.


Popular posts from this blog

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664