Access Director Language Packs

Access Director Enterprise language packs let you to take advantage of the Multilingual User Interface.
A language file is a set of language-specific resource files that can be added to any version of Access Director Enterprise.

All language packs can be configured using your existing Group Policy Administrative Template (ADMx) or using registry entry with your package.

Released language packs:

Arabic – ar-SA
Bulgarian – bg-BG
Croatian – hr-HR
Czech – cs-CZ
Danish – da-DK
Dutch – nl-NL
English – en-US
Estonian – et-EE
Finnish – fi-FI
French – fr-FR
German – de-DE
Greek – el-GR
Hebrew – he-IL
Hungarian – hu-HU
Italian – it-IT
Japanese – ja-JP
Korean – ko-KR
Latvian – lv-LV
Lithuanian – lt-LT
Norwegian – nb-NO
Polish – pl-PL
Portuguese (Brazil) – pt-BR
Portuguese (Portugal) – pt-BR
Romanian – ro-RO
Russian – ru-RU
Serbian (Latin) – sr-Latn-CS
Simplified Chinese – zh-CN
Slovak – sk-SK
Slovenian – sl-SI
Spanish – es-ES
Swedish – sv-SE
Thai – th-TH
Traditional Chinese (Hong Kong) – zh-HK
Traditional Chinese (Taiwan) – zh-TW
Turkish – tr-TR
Ukrainian – uk-UA

Access Director Enterprise Reporting Point 3.9.1 Released

Access Director Enterprise Reporting Point 3.9.1 Released

Based on great  input, we have reviewed and added lots of new features in the reporting point

Reporting Point updates:

  • Added “needle” search for Software in Reporting page
  • Added Device page with the possibility to review verbose log files from clients
  • Added Active users and computers in Status page
  • Added Data Export to CSV or full file in the Settings page
  • Added updates to Reporting Point Authentication
  • Added optional Update Base URL in the settings page
  • Added Automatic Update interval in the settings page
  • Added JSON API using an API Key (see: Access Director Enterprise Reporting Point API)

Do you have a feature request? Don’t hesitate to contact us!

Access Director Enterprise Reporting Point API

In order to utilize the new API use following syntax:

https://<yourserver>/accessdirector/api.php?api_key=[api_key]&type=[type]

[api_key] should be equal to the generated public key (see above)

Also optional days parameter can be specified: https://<<yourserver>/accessdirector/api.php?api_key=[api_key]&type=[type]&days=[days]

If days parameter is specified then statistics data will be queried for the specified latest number of days

In case days parameter is omitted, we use default number of days: 90

The [type] may be equal to following values:

  • elevations_number
    Number of elevations was done within specified number of days
  • top_users
    Top 10 users who have elevated within specified number of days
  • apps_added_elevated_number
    Number of Applications Add (when user was elevated) within the last specified number of days
  • apps_added_not_elevated_number
    Number of Applications Add (when user was not elevated) within the last specified number of days
  • apps_removed_elevated_number
    Number of Applications Remove (when user was elevated) within the last specified number of days
  • apps_removed_not_elevated_number
    Number of Applications Remove (when user was not elevated) within the last specified number of days
  • active_computers_numberbr
    Number of computers that were active for latest specified number of days
  • active_users_number
    Number of users that were active for latest specified number of days
  • elevations_list
    List of elevated users was done within specified number of days
  • top_users_list
    Top users who have elevated within specified number of days
  • apps_added_elevated_list
    List of applications added (when user was elevated) within the last specified number of days
  • apps_added_not_elevated_list
    List of applications added (when user was not elevated) within the last specified number of days
  • apps_removed_elevated_list
    List of applications removed (when user was elevated) within the last specified number of days
  • apps_removed_not_elevated_list
    List of applications removed (when user was not elevated) within the last specified number of days
  • active_computers_list
    List of computers that were active for latest specified number of days
  • active_users_list
    List of users that were active for latest specified number of days

Access Director Enterprise 5.3.1 has been released

Access Director Enterprise 5.3.1 has been released!

Client Updates:

  • Added thread safe logic for all processing
  • Added support for HTTP & HTTPS link in “Reason for elevation” dialog
  • Added support for sending verbose log files for multiple users on the same machine
  • Added support for non-Unicode characters in some scenarios
  • The revised logic for Active Directory Connectors
  • New language packs available
    • Arabic, Bulgarian, Croatian, Czech, Dutch, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian, Polish, Portuguese (Brazil), Portuguese (Portugal), Romanian, Serbian (Latin), Simplified Chinese, Slovak, Slovenian, Spanish, Swedish, Thai, Traditional Chinese (Hong Kong), Traditional Chinese (Taiwan), Turkish, Ukrainian.

Do you have a feature request? Don’t hesitate to contact us!

Access Director – Certificate Warning

Certificate expire warning for Access Director version 2.5.
Access Director 2.5 will expire on 03/04/2018

Keep in mind, the version 2.5 is from 2014.
A lot of changes and fixes has been added since.

Also a critical security errors has been mitigated.

How can you check if your version has is expiring?

1. Browse to your installation directory – usually: C:\Program Files (x86)\Access Director
2. Right Click AccessDirectorTray.exe or AccessDirectorFramework.exe
3. Click the tab Digital Signatures
4. Click Details
5. Click View Certificate

If you see a Valid from: 29-01-2015 to 03-04-2018.  – Your version will expire!

Access Director Enterprise – Feature Update November 2017

It is now easier then ever to deploy Access Director Enterprise.
Based on input from IT-Pros we have added a standard package that removes added local administrators on first install.
This gives you are nice and clean baseline to work from.

Ready, Set, Go! Only your group policy-based changes to the local administrator’s group will be effective, all manually added users will be removed.

NOTE: if your using Group Policies to add specific users or groups to the local administrator’s group, these will still be refreshed and added.

Get input or feature requests? Let us know!