Release Notes for JRButils for AD v14

Changes to multiple programs

  • Fixed an issue in programs processing volume quotas where they might continue to attempt to process a quota when quotas are not supported on the target volume.
  • Updated various programs to report why they cannot resolve a path to a host name and volume. The reason is usually insufficient rights to resolve a share to its actual path. This code is used in programs dealing with disk (volume) quotas and adopenfile.
  • Fixed an issue where a byte order marker (BOM) could be written when appending to an existing non-zero length log or error file.
  • Removed minor inconsistencies between programs as to which alternative names are accepted for attribute names e.g. firstName for givenName and surname for sn. A new Appendix E has been added to the documentation listing the alternative names which are accepted.
  • Updated programs dealing with disk and directory quotas to report that privileges are not elevated when initializing the relevant quota manager fails with “access denied” for this reason.
  • Updated adgetdirquota, adquotas and adspace to retrieve directory quota information via the jrbserv system service. This provides a means to retrieve values from a workstation. The directory quota APIs can only be used on the machine on which the quotas exist. The programs, when not running on the target host, check if the system service is running, and if so, retrieve data via the service. All quota values may be retrieved via the service.
  • Updated the various programs working with quotas to accept or display values in terabytes (TB).
  • Updated further programs to work internally, entirely in unicode rather than in single byte characters. Those completed since v13 include:

    adchkval adsessions
    addelhome    adspace
    adhome jrbsrvmgr
    adprdel jrbserv

    All programs which operate solely on Windows and AD are now use only wide characters. Those program which also include code for the Micro Focus environment, remain unconverted at this time, the job being complicated by that environment featuring functions which return ASCII only, and the use of UTF-8 for the file system. However, some preliminary work towards converting these is already completed.