Article ID: K00000430
Last Updated: March 2, 2014
Summary
This article describes the changes included in adTempus version 4.0.1, released on March 2, 2014.
Version Information
After you install this update, the About box in the adTempus Console will show the following version information:
Product Version: 4.0.1
Console Version: 4.0.14060.0
Client Components Version: 4.0.14060.0
Server Version: 4.0.1 (4.0.14060.0)
If your installation shows later versions, you do not need to install this update.
Installation Notes
If you are using Distributed Scheduling, you can install the update on the Master and push it to Agents from the Remote Agents view.
Remote Consoles can be updated by choosing the Update option from the Help menu.
Obtaining the Update
See the download page to download the latest version of adTempus. The setup program will update your installation.
Changes in This Update
This release contains one minor enhancement, to support automatic login based on Active Directory group membership, and many fixes for software problems.
No database schema changes are required.
The following changes are included in this update:
| Actions |
| | Database error when job restart response runs | CR00002854
Defect | For more information see Knowledge Base article K00000423. |
|
| Console |
| | Exit code criterion may display incorrectly | CR00001853
Defect | |
If a Program Execution Task, Script Execution Task, or Response Event has an exit code rule that tests for a value equal to 0, the "0" value is not displayed in the Console (the entry box is empty). However, the criterion is still applied correctly using a value of 0. If the criterion is set to a value other than 0, it is displayed correctly.
|
| Console connection to server fails with server certificate error when using adTempus security | CR00002859
Defect | For more information see Knowledge Base article K00000426. |
| Find/Replace references does not replace some references | CR00002860
Defect | | The replace references function did not replace references to Notification Recipients. The problem was corrected. For more information see Knowledge Base article K00000427. |
|
| Data Conversion |
| | Database upgrade may fail if duplicate Credential Profiles exist | CR00001854
Defect | |
|
| Database |
| | Database Configuration Wizard does not grant permissions on local database to LocalSystem account | CR00002857
Defect | As a result adTempus cannot connect to the adTempus database if the LocalSystem account did not already have permissions for the database. Database wizard was fixed to ensure that LocalSystem account is granted permission for adTempus database. |
|
| Distributed Scheduling |
| | SSPI error when Master tries to connect to Agent or Peer when target adTempus service is running under a user account | CR00002864
Defect | | If the adTempus service on an Agent is running under a user account (instead of LocalSystem), the Master fails to connect with error "The target principal name is incorrect". This problem was resolved. |
|
| Import/Export |
| | Export file browse dialog does not include adtexport4 extension | CR00001847
Defect | |
|
| Job Execution |
| | adTempus does not set the ComputerName environment variable | CR00002855
Defect | For more information see Knowledge Base article K00000424. |
| Internal error when running two jobs at same time: An item with the same key has already been added | CR00002858
Defect | | In rare cases when two job steps are executed at exactly the same time, one job may fail with an internal error message. For more information see Knowledge Base article K00000425. |
|
| Reports |
| | Job name not shown on Job Inventory Report | CR00002863
Defect | For more information see Knowledge Base article K00000429. |
|
| Scripting |
| | MyInvocation.MyCommand not exposed correctly for external PowerShell scripts | CR00002865
Defect | | Due to the way that adTempus executed external PowerShell scripts, the $MyInvocation.MyCommand was of type Script rather than ExternalScript and did not have the Path and other properties set. This was corrected. |
| Job Variables are not expanded in parameters for PowerShell scripts | CR00002869
Defect | | If you include Job Variables in the Comand-Line Parameters for a PowerShell script run by the Script Task, the variables are not expanded before being passed to the script. |
|
| Security |
| | Add support for adTempus logins based on Active Directory groups | CR00002862
Enhancement | adTempus can now automatically create logins for users based on Active Directory group membership. See Automatic Login through Group Membership in the online help for more information. For more information see Knowledge Base article K00000428. |
| Remove access to security settings windows for users who don't have administer permission | CR00001842
Defect | | Applies to container-level security windows (Notification Recipient Security, Script Security, etc.) |
| Add button available for Jabber servers even if user has no create permission | CR00001843
Defect | |
|
| Server Tools |
| | Changed server tools to require Administrator permissions for execution | CR00002866
Defect | | The Database Configuration Wizard and Database Utility were changed to require Administrator authority for execution. |
|
| Tasks |
| | Cannot change Program Execution Task step from running batch file stored in adTempus to running external program | CR00002861
Defect | | Console gives error "The Execution Target and Batch Script cannot both be specified" when step was configured to run an internal batch script and you change it to run an external program. |
|
| Triggers |
| | File triggers that use Job Variables in the file specification do not trigger | CR00002867
Defect | | If a File Trigger includes Job Variables in the File Specification, adTempus may fail to trigger for the file(s). |
| File Trigger does not wait for multiple files | CR00002868
Defect | | If a File Trigger has more than one file specification and is configured to wait until all specifications have been matched, the Trigger ignores this setting and fires as soon as any of the specifications is matched. This problem was resolved. |
| Cannot change schedule from running on selected days to running every X days | CR00002870
Defect | | If a Schedule has been configured to run on specific days and you change it to run every X days, you get an error when you try to save the Scheduler: "Cannot specify days when Criterion Type is Interval". |
|
| User Interface |
| | Job Diagram not showing some information correctly | CR00001834
Defect | | The Job Diagram does not show Job Triggers, and may fail to draw links between jobs linked by Job Control Actions. |
|
