Home
Über uns
careers
Referenzen
Sitemap
COM FR CH 
Produkte
support
Preise
download
 
Seiten Navigation
home > de > products > user-management-resource-administrator...(Sie befinden Sich hier)
Testimonial:
UMRA is the most fantastic utility I have ever used in my 20 years of Windows Administration. With a few clicks, I am able to create and maintain our Student user and e-mail accounts with such ease, I know that I COULD NOT live without this tool for the rest of my life !! What amazes me is how much more I understand about the Windows operating system with the assistance of UMRA. This allows me to ...

Marikay Fisher
Kansas City Kansas Community College
http://www.kckcc.edu

read more...



User Management Resource Administrator: User Account Management for Windows 2003/XP/2000/NT Download UserManagemeNT Import: User Account Management for Windows 2003, XP, 2000 and NT
Live Demo Download Features Screen Shots Support Referenzen

Release Notes

10.3 Build 1601, November 19, 2009

Major changes
  1. TOPdesk connector (new): The helpdesk information system TOPdesk (TOPdesk, http://www.) is supported with a set of dedicated UMRA actions (1587, 26/August/2009)
  2. Google Apps connector (new): The information system Google Apps is supported with a set of dedicated UMRA actions (1587, 26/August/2009)
  3. TeleTOP connector (new): The student information system TeleTOP is supported with a set of dedicated UMRA actions (1587, 26/August/2009)
  4. N@tSchool connector (new): The student information system N@tSchool is supported with a set of dedicated UMRA actions (1575, 10/June/2009)
  5. It's Learning connector (new): The student information system It's Learning is supported with a set of dedicated UMRA actions (1599, 4/November/2009)
  6. Aura connector (new): The school library system Aura is supported with a set of dedicated UMRA actions (1575, 10/June/2009)
  7. Execute command line at UMRA Forms client (new): When an UMRA form is submitted, as a response, a command line can be executed by the UMRA Forms client computer. See Form action - Execute command line at client workstation for more information (1560, 2/April/2009).
  8. Get Out-Of-Office info (Exchange 2007) (new): The action collects the Out-Of-Office information of a particular account. See Script Action: Get Out-Of-Office info (Exchange 2007) for more information (1572, 2/June/2009)
  9. Set Out-Of-Office info (Exchange 2007) (new): The action sets the Out-Of-Office information of a particular account. See Script Action: Set Out-Of-Office info (Exchange 2007) for more information (1572, 2/June/2009).

Powershell
  1. Powershell Agent service - Session time to live (enhancement): The time-to-live idle time of a Powershell Agent service session can be configured by setting a registry value. See Registry settings for more information. (1570, 12/May/2009).
  2. Script action: Check Powershell Agent service session (new): The action can be used to check if an previously created Powershell Agent service action is still available and removed upon expiration. See Script Action: Check Powershell Agent service session for more information (1570, 13/May/2009).
  3. Keep-alive signalling (enhancement): To prevent expiration of idle Powershell Agent sessions, the UMRA Forms client sends keep-alive signal to the UMRA Service. The UMRA Service forwards these signals to the Powershell Agent service, keeping the sessions initialized through the UMRA Forms client alive. In case the UMRA Forms client is open for a longer period, e.g. a day, the session information is not lost.(1570, 19/May/2009)
  4. Variable list (enhancement): The available variables that can be used in script properties, generated from dynamic actions, is now limited to the properties section of the dynamic actions. In previous version, also variable names from the script section were copied to the variable list. Since these variable are not available in the UMRA variable list, these variables should not be presented to the end-user. (1570, 22/May/2009)
  5. Powershell not installed (fix): When Powershell is not installed on the machine that runs the Powershell Agent service, a correct error message is shown when executing the action Setup Powershell Agent service session. In previous versions, the Powershell Agent service and the call UMRA software could crash (1571, 25/May/2009)
  6. Powershell Agent service import library (fix): When importing the Powershell Agent service library, some incorrect error message were shown. The issue has been resolved (1571, 25/May/2009)
  7. Project execution using UMRA COM (fix): When using UMRA COM to execute projects that access the UMRA Powershell Agent service, a problem could occur causing projects not to terminate completely. The issue has been resolved. (1578, 17/June/2009)
  8. Powershell Agent service manual installation (enhancement): A online help topic is added that described how to setup the Powershell Agent service manually. See Manual installation of the Powershell Agent service for more information. (1579, 30/June/2009)

Lotus Notes
  1. Lotus Notes - action: Execute agent script (new): The action creates, executes and deletes a Lotus script agent in an existing database. The action can be used for instance to automate the approval of administration process requests. See Script Action: Execute agent script and Lotus Notes example projects for more information (1558, 30/March/2009).
  2. Lotus Notes - action: Execute agent script (enhanced): The action is extended with some new properties to better control the action. See Script Action: Execute agent script and Lotus Notes example projects for more information (1593, 28/September/2009).
  3. Lotus Notes - action: Get item size (new): The action retrieves the size of a single specified Lotus Notes document item. See Get item size for more information. (1558, 30/March/2009).
  4. Lotus Notes - action: Set item(s) (enhanced): The action now checks the total size of the item. If the action would exceed the Lotus Notes item size limit, the action is not executed. The action size limit is 32k bytes for summary items and 64k bytes for all other items. (1558, 30/March/2009)
  5. Lotus Notes - action: Set item(s) (enhanced): The action now checks the total size of the item. If the action would exceed the Lotus Notes item size limit, the action is not executed. The action size limit is 32k bytes for summary items and 64k bytes for all other items. (1558, 30/March/2009)
  6. Lotus Notes - action: Update profile document (enhanced): The action now supports different Lotus Notes type values and can also be used to delete fields and/or sign profile documents only. See Script Action: Update profile document for more information (1568, 24/April/2009).
  7. Lotus Notes - action: Update profile document (enhanced): The action is further enhanced to add a profile document field that contains the date and time of the profile document signature. See Script Action: Update profile document for more information (1569, 1/May/2009).
  8. Lotus Notes - action: Register person (advanced)(fix): The action is extended with 2 new properties, 'Roaming - Replica servers' and 'Roaming - Create replica files in background' to support roaming profiles. See Script Action: Register person (advanced) for more information. (1585, 24/July/2009)
  9. Lotus Notes - example project 'Remove Roaming profile' (new): An example project is added to show how to create an administration request to remove the roaming profile of a Lotus Notes user account. See Lotus Notes example projects for more information (1585, 24/July/2009).
  10. Lotus Notes - example project 'Lotus Notes ID Vault - Reset password (new): An example project is added show how to use the Lotus Notes ID Vault to reset password of user accounts in Lotus Notes. See ID Vault and Lotus Notes example projects for more information (1593, 28/September/2009).
  11. Lotus Notes - action: Delete document' (new): New properties are added to support another method to specify the note or document to be deleted. See Script Action: Delete document for more information (1593, 28/September/2009).

Actions
  1. Update numeric variable - Convert number to text (format) (new): The action is extended with the option to convert a number to a text value according to a C-language 'printf' format specification. See Script Action: Update numeric variable for more information (1558, 30/March/2009).
  2. Execute command line (enhanced): A property is added to specify the maximum output buffer size in case the output is to be stored in a variable. See Script Action: Execute Command Line for more information (1579, 26/June/2009).

Fixes and enhancements
  1. Action: Update date-time variable - subtract date-time value (new): A new function is added to subtract a date-time value stored in a variable from another date-time value. See Script Action: Update date-time variable for more information (1566, 17/April/2009).
  2. Action: Set variable (fix): For hidden variables, in log files, the value of the variable was not shown but when the action was executed, it was shown. The issue has been resolved (1577, June 12, 2009).
  3. Set attribute (AD) (fix): The escape sequences, introduced in UMRA build 1558, are changed to [\r], [\n], [\r\n] and [\t] to allow attribute specifications containing for instance \t: \\SERVERNAME\Share\tsmith. See Script Action: Set attribute (AD) for more information. (1563, 9/April/2009).
  4. Add action to script - window update (fix): When composing an UMRA script using menu option Add action to script, the script window is now updated correctly. In previous versions, the actions displayed were not always updated immediately. (1562, 7/April/2009)
  5. Script action: Set Terminal Services user settings (fix): In special circumstances, UMRA could crash when the action was executed and failed with the following error message: Cannot determine NETBIOS domain controller name of domain controller... The issue has been resolved (1562, 7/April/2009).
  6. Powershell Agent service (fix): When received a stop signal, the Powershell Agent service is now stopped more gracefully (1562, 8/April/2009).
  7. Generic table - LDAP table column name (fix): The name of a column of a LDAP generic table is set to the name of the attribute. This was changed in build 1558 to the display name but causes problems in existing implementations. (1565, 15/April/2009)
  8. Vista - Windows Server 2008 - UAC (fix): The UMRA Console is started with elevated administrative access on the Vista and Windows Server 2008 platforms. In previous versions, this was not the case. Depending on the system configuration access denied errors could occurs for instance when the UMRA Service was installed. (1566, 17/April/2009)
  9. Action: Update database (fix): When testing the statements of action Update database, the option to Run test on UMRA Service is no longer available. In previous version, the option could be selected but was not functional (1566, 17/April/2009).
  10. 64-bit UMRA COM DLL (fix): In UMRA 10.1, build 1577, the 64-bit UMRA Automation DLL UmraCom64.dll had an incorrect version number (1577, June 12, 2009).
  11. PSM, UMRA session (fix): When accessing an UMRA project through UMRA PSM, the global UMRA session list is now correctly updated. In previous versions, the UMRA Service was not updated correctly. (1588, August 31, 2009).

10.0 Build 1558, March 27nd, 2009

Major changes
  1. Session support of the Powershell Agent service A Powershell Agent service session allows a more interactive usage of the Powershell runtime environment. For instance to store Powershell variables that can be used in subsequent Powershell scripts. For more information, see Powershell Agent service session. (1528, 10/November/2008)
  2. SAP support (new) Over 30 actions are added to support SAP. The UMRA SAP actions can be used to create SAP accounts, reset passwords, add users roles and profiles and so on. See UMRA and SAP for more information. (1480, 5/September/2008)
  3. UMRA Console: Open referenced project (new) When configuration a project with the UMRA Console application, the menu option Open referenced project opens the associated project for For-Each and Execute script actions. (1546, 29/January/2009)

Actions
  1. Get Out-Of-Office info (Exchange 2000/2003) (new) The action collects the Out-Of-Office information of a particular account. See Script Action: Get Out-Of-Office info (Exchange 2000/2003) for more information (1539, 6/January/2009).
  2. Set Out-Of-Office info (Exchange 2000/2003) (new) The action sets the Out-Of-Office information of a particular account. See Script Action: Set Out-Of-Office info (Exchange 2000/2003) for more information (1539, 6/January/2009).
  3. Set variable - hidden variable (enhancement) With action Set variable it is possible to hide the value of the variable. In log files, the value is not shown. (1528, 6/November/2008)
  4. Edit share (enhancement) The property 'Cache parameter' is added to support share caching options (1543, 28/January/2009).
  5. Set attribute (AD) (enhancement) The action supports carriage return, line-feed insertion in the Active Directory attribute. See Script Action: Set attribute (AD) for more information. (1546, 30/January/2009).
  6. Delete multiple variables (new) The action supports deletion of multiple variables from the project variable list with a single action. (1546, 6/February/2009)

Table management
  1. Manage table data - Get the number of table columns (new) The new action is added. See Script Action: Manage table data for more information (1546, 5/February/2009).
  2. Manage table data - Copy row (new) The new action is added. See Script Action: Manage table data for more information (1546, 5/February/2009).
  3. Manage table data - Copy multiple rows (new) The new action is added. See Script Action: Manage table data for more information (1546, 5/February/2009).
  4. Manage table data - Copy table (new) The new action is added. See Script Action: Manage table data for more information (1546, 5/February/2009).
  5. Manage table data - Remove multiple rows (new) The new action is added. See Script Action: Manage table data for more information (1546, 5/February/2009).
  6. Manage table data - Remove a specified column (new) The new action is added. See Script Action: Manage table data for more information (1546, 5/February/2009).
  7. Manage table data - Sort on column name (new) The new action is added. See Script Action: Manage table data for more information (1546, 5/February/2009).
  8. Manage table data - Convert multi-value variable to table (new) The action accepts single value variables. (1546, 11/February/2009).
  9. Manage table data - Replace column name (new) The new action is added. See Script Action: Manage table data for more information (1546, 5/February/2009).
  10. Manage table data - Get column name (new) The new action is added. See Script Action: Manage table data for more information (1546, 5/February/2009).
  11. Manage table data - Search table (new) The action is extended with search features. See Script Action: Manage table data for more information (1546, 5/February/2009).

Powershell - dynamic actions
  1. Time Powershell Agent service (fix) The time as shown in log messages generated by the Powershell Agent service is now correct (1520, 21/October/2008).
  2. Upgrade of dynamic actions (fix) The upgrade procedure of dynamic actions is enhanced (1520, 17/October/2008)
  3. Directory of Powershell Agent service (enhancement) It is now possible to specify the directory where the Powershell Agent service is installed (1542, 13/January/2009).
  4. Powershell Agent service - UMRA Service (fix) When multiple ( > 10) scheduled tasks access the Powershell Agent service simultaneously from within the UMRA Service, the RPC service can become to busy, causing errors and Powershell scripts not being executed. The error is now handled correctly and the RPC call is retried until it succeeds or the expiration period is passed (1506, 7/October/2008).
  5. Powershell Agent service - UMRA Service (fix) In rare circumstances, the UMRA Service could crash when multiple scheduled tasks access the Powershell Agent service simultaneously. This is caused by some XML libraries not being thread-safe. The issue has been resolved (1506, 7/October/2008).

UMRA COM object
  1. New interface methods (new) A number of interface methods are added, mainly dealing with UMRA COM object tables. Methods are added to check license information, store tables in the variable list, manage table contents and column names using the UmraDataTable interface. See UMRA COM object reference for more information (1543, 27/January/2009).

Lotus Notes
  1. Lotus Notes - Update profile document (enhancement) The action is extended: item flags can be specified for the updated profile document and the profile document can be signed when changes are applied (1536, 12/December/2008).
  2. Lotus Notes - Copy document (new) Copy a Lotus Notes document from one database to another Lotus Notes database. See Script Action: Copy document for more information (1536, 23/December/2008).
  3. Lotus Notes - Get quota (new) Retrieve the quota and size of a Lotus Notes database. See Script Action: Get quota for more information.
  4. Lotus Notes - Update profile document, 'Log archiving' (new) Online help is updated to show how the action is used to set log archiving for a Lotus Notes database (1543, 28/January/2009).

Fixes and enhancements
  1. Password Synchronization Manager (fix) Some memory issues are resolved in the Password Synchronization Memory DLL (1480, 10/September/2008)
  2. Password Synchronization Manager (fix) An issue is fixed for domain controllers with a name of 15 characters. In previous versions, error 111 could occur, generated by the Password Synchronization DLL, running on the domain controller. (1506, 7/October/2008)
  3. XML (fix) The handling of special characters (white-space, carriage return, line feed, tab) in XML export and import procedures is now correct (1480, 5/September/2008).
  4. XML (fix) For some UMRA objects, the XML export was not complete, e.g. the result file did not contain all of the UMRA object data. This could lead to incomplete backups. (1480, 5/September/2008)
  5. XML (fix) The indentation of exported projects to XML files is now correct. (1527, 30/October/2009)
  6. XML (fix) When importing a project from an XML-file that contains a generic table with an imported file, the separator character settings are now correct. In previous version, the comma (,) separator was always selected (1546, 5 February/2009).
  7. Recent projects (fix) In rare circumstances, the UMRA Console application lost the list with recent projects. The issue has been resolved (1515, 16/October/2008)
  8. Logging of service projects cache parameters (enhancement) The projects cache parameters are now logged in the UMRA Service log in startup. The log message has the following format: Service projects cache initialized with parameters 'Enabled=1', 'Delay=300' (1522, 22/October/2008)
  9. Manage service projects (fix) When the buttons of the 'Manage service projects' are clicked in a certain order, the UMRA Console application could crash. The issue has been resolved. (1528, 7/November/2009).
  10. Thread mechanism (enhancement) To prevent delays in large networks, specific tasks are performed in separate threads. (1543, 14/January/2009).
  11. Form security - group selection (enhancement) When setting the accounts for form project security, available groups are now by default shown in the dialog to select User and/or Groups (1542, 12/January/2009).
  12. Importing project files with period (.) in file name (fix) It is now possible to import a project file with multiple periods (.) in the file name. Example: form.with.period.ufp (1543, 13/January/2009).
  13. Name generation - output variable (enhancement) The names of output variables can now be renamed when configuration name generation algorithms. (1546, 29/January/2009).

9.2 Build 1486, September 12nd, 2008   

Major changes
  1. SAP support (new): Over 30 actions are added to support SAP. The UMRA SAP actions can be used to create SAP accounts, reset passwords, add users roles and profiles and so on. See UMRA and SAP for more information. (1480, 5/September/2008)
  2. XML (fix): For some UMRA objects, the XML export was not complete, e.g. the result file did not contain all of the UMRA object data. This could lead to incomplete backups. (1480, 5/September/2008)

Enhancements
  1. Password Synchronization Manager (fix): Some memory issues are resolved in the Password Synchronization Memory DLL. (1480, 10/September/2008)

9.1 Build 1478, August 1st, 2008   

Major changes
  1. XML project file format (new): UMRA supports the XML standard to import and export UMRA projects and scripts. See UMRA XML project and script files for more information (1458, 3/June/2008).
  2. Password Synchronization Manager (PSM) (new): The new PSM module will catch every password change in a Windows Active Directory domain and start an UMRA project. The UMRA project will forward the password change to other systems and applications. Refer to the section on PSM for more information (1474, 8/July/2008).

Groups
  1. Update group memberships (AD) (new action):The new action allows the addition, removal and synchronization of group memberships for an account. Lists can be specified for each operation. For example, when synchronizing, the user account (or other type of account) will only be a member of the specified groups when the action is completed. See [Script Action: Update group memberships (AD)] for more information (1437, 2/April/2008).
  2. Create group (AD) (fix): The Common Name of a new group can now start with a #-character (1462, 12/June/2008).

Tables
  1. Manage table data, Set column name (enhancement): The action Manage table data now supports the function to set the name of a column (1433).
  2. Manage table data, Search cells with matching contents(enhancement): In a table, search through all rows and the specified or all columns to find tables cells with matching text contents (1441, 14/April/2008).
  3. Manage table data, Complete rows (enhancement): Search through all rows of a table and add empty text values to each row so that the total number of columns is equal for all rows. If all rows already have an equal number of cells, no changes are made (1441, 14/April/2008).
  4. Get user (AD) (enhancement): The action is extended with property Globally Unique Identifier (GUID). When the user object is successfully retrieved, the GUID of the user account can be stored in a variable (1458, 2/June/2008).
  5. Get users table (locked out/Disabled/Password) (AD) (fix): When the domain Account lockout duration is specified as 0 (account is locked out until administrator unlocks it), the action functions correctly (1462, 12/June/2008).
  6. Store indices of selected rows in table variable (new): The indices of the selected rows of UMRA form tables, can be stored in a table variable (11/June/2008, 1462).

Actions
  1. For Each (enhanced):The dialog window to configure the For-Each action is extended with more options to configure the column variables passed to child project (1435, 21/March/2008).
  2. Execute command line (enhanced):A property is added to allow the removal of carriage-return line-feed characters at the end of the output variable value (1438, 3/April/2008).
  3. Generate random number (enhanced):For the minimum and maximum values, variable names can now be specified. (1441, 14/April/2008).
  4. Delete directory (enhanced): The logic to calculate the correct directory name is improved to support directory names with multiple dots (.) in the full path (1441, 14/April/2008).
  5. Execute script (enhanced): The action description as shown in the script window of an UMRA project now shows the name of the script to execute (1442, 18/April/2008).
  6. Get user (AD) (fix): When an output variable is specified for the display name, and no display name is found for the user account, no UMRA error is generate. (1456, 29/May/2008).
  7. Format variable value (new):The functions of the action 'Format variable value' can now be specified using variables. Also, when formatting functions are used in name generation algorithms, variables are supported (1437, 28/March/2008).
  8. Format variable value (enhanced): The case conversion functions of the action now supports the special characters ä, Ä, ö, Ö, ü and Ü. (1471, 2/July/2008).
  9. Get attribute (AD) (fix): When an attribute is not found, and property 'Convert to text flag' is set to 'No' and no errors must be generated if not found, the action now no longer generates an error (1462, 16/June/2008).
  10. Create local group (fix): When the group cannot be created since it already exists, no error is generated if 'Error if group already exists' is set to 'No'. (1473, 9/July/2008).

Exchange
  1. Manage mailbox e-mail addresses (Exchange 2007) (enhancement): The action now contains an additional property Domain controller to allow specific server binding and avoid replication issues (1462, 16/June/2008).
  2. Enable distribution group (Exchange 2007) (new): A new action to mail-enable distribution groups (1462, 16/June/2008).
  3. Set client access attributes (Exchange 2007) (new): A new action to set client access attributes including Outlook Web Access (OWA), MAP, IMAP and POP (1462, 16/June/2008).

PowerShell
  1. Powershell agent service (enhancement): The service now supports more data types used to return output tables. For example the data of file system ACL's. (1425, 11/Feb/2008).
  2. Powershell agent service (fix): A memory issue with encrypted data has been resolved. When using encrypted script phrases, the agent service could consume little memory resources that were not released properly. Eventually (after months or years without a reboot), this might cause problems for the computer running the Powershell Agent service (1425, 18/Feb/2008).
  3. Powershell return data (new): Simple string and data values can be returned to UMRA with a more simple method. See Single value output data for more information (1467, 26/June/2008).
  4. Powershell encrypted variable input (new): For input text properties, the value can be encrypted. In this case, the actual contents of the property is not shown in log files, UMRA script files and so on. See Encrypted properties for more information (1467, 27/June/2008).
  5. Powershell - Active Directory permissions management (new): New UMRA actions are added to manage Active Directory permissions: Script Action: Get AD permissions, Script Action: Add AD permission, Script Action: Remove AD permission, Script Action: Set AD permissions (advanced), Script Action: Get owner, Script Action: Set owner (1473, 8/July/2008).
  6. Powershell - Group management (new): New UMRA actions are added to manage Active Directory groups: Script Action: Set Managed By, Script Action: Get (nested) group memberships (1473, 8/July/2008).
  7. Powershell - File system (new): A new action is added to get disk space information: Script Action: Get disk space (1473, 8/July/2008).
  8. Powershell - Active Directory utility (new): A new action is added to determine the role of the primary domain controller: Script Action: Get PDC (AD) (1473, 8/July/2008).

Lotus Notes
  1. Lotus Notes - Generate recovery password (new): Support new action to reset the password of an Lotus Notes ID file.See Lotus Notes action: Generate recovery password for more information (1433).
  2. Lotus Notes - Out-Of-Office (new): Support new action to configure Out-Of-Office. See Lotus Notes action: Out-Of-Office for more information (1433).
  3. Lotus Notes - Move person (advanced) (new) The existing action Move person cannot be used to move a person if the person is currently located in an organizational unit. To support this operation, the action Move person (advanced) is added. See [Script Action: Move person (advanced)] for more information (1438, 3/April/2008).
  4. Lotus Notes - Update profile document (new). The action can be used to specify the value of a specific field of a database' profile document. See Script Action: Update profile document for more information (1473, 8/July/2008).
  5. Lotus Notes - Sign/Unsign document (fix). In previous versions, the action could apparently execute with no error, but the resulting document (adminp request) was not accepted. The error occurred when creating administration requests for Domino version 7 servers. (For version 6.X Domino servers, the problem was not found). The issue has been resolved (1440, 9/April/2008).
  6. Lotus Notes - Update ACL (fix). The ACE name that is specified as part of the Access Control Entry specification can now hold variables. In previous versions, variables were not replace at run-time by their actual values. (1142, 21/April/2008).
  7. Lotus Notes - UMRA Service (fix). When using an initial project with UMRA Forms projects, the UMRA Service did not properly release the resources used for Lotus Notes databases that were initialized in the initial project. Eventually, this could prevent the UMRA Service and other applications being able to access Lotus Notes databases (1435, 19/March/2008).
  8. Lotus Notes - Create document (enhancement). The action now exports the document or notes ID of the created document.
  9. Lotus Notes - Register person (advanced) (enhancement). The action now supports the creation of mail file replicas using property Mail – Mail file replicas (1447, 29/April/2008).
  10. Lotus Notes - Set items (fix). The order of text item values of text list items as specified with action Set items is now preserved. (1462, 12/June/2008).
  11. Lotus Notes - Example projects (new). Several UMRA Lotus Notes example projects are added. Almost all of these project show how to setup Lotus Notes administration requests in order to manage Lotus Notes accounts and mailboxes.

Forms
  1. Variable generic table column names (new): The names of columns in a variable generic table can be specified as variables (%NameColumnA%, %NamceColumnB%, etc) (1458, 2/June/2008).
  2. Name of client computer (new): When a form is submitted by clicking a button, a variable, %UmraClientComputerName%, is generated. The variable holds the name of the client computer and can be used by the UMRA Service. See Built-in variables for more information (1462, 11/June/2008)

Database
  1. Database connection lost when database reset (fix): With UMRA Forms, an error could occur when databases were reset or restarted. In these situation, the UMRA Service was not able to reconnect to the database unless the UMRA Service was restarted. The problem was caused by an incorrect update of the database connection cache maintained by the UMRA Service (1433).
  2. UMRA Console log with test query (new): When executing a test query of a table from the UMRA Console application (Setup generic table, Run test, Test...) the query is now written to the UMRA Console log (1458, 2/June/2008).

Automation
  1. UMRA Automation 64-bit support (new): The UMRA Automation software is now available for both 32-bit and 64-bit platforms. As a result, web-pages that are part of IIS web-site can run on 32-bit and 64-bit IIS platforms. See UMRA COM on 64-bit platforms for more information (1445, 23/April/2008).
  2. Name of automation project (fix): When creating a new automation project, the new project must now have an unique name. (27/May/2008, 1455).
  3. Automation log files (fix): The specific automation log file settings, e.g. maximum log files size and maximum number of log files per project are now preserved when the UMRA Service is restarted (1462, 12/June/2008).

General
  1. UMRA on Vista and Windows Server 2008 (fix): All UMRA applications now run on Windows Vista and Windows Server 2008 with no problems (1462, 12/June/2008).
  2. Error 20403(fix): When transferring large amounts of data ( > 1 MB) from either UMRA Forms or the UMRA Console application, an error could occur with error code 20403. This specially happened when variables storing big tables were used. (1433)
  3. Project name variable (new): When a project is executed, the name of the project is now stored in a variable. Two variables are used for this purpose: %UmraProjectName% and %UmraProjectNameStack%. Variable %UmraProjectName% contains the name of the (deepest) project that is currently executed. %UmraProjectNameStack% contains the name of all projects: the deepest child project and all parent projects. See Built-in variables for more information (1435, 20/March/2008).
  4. New Build-in variables (new): When a project is executed, the following new UMRA variables are generated: %CurrentSystemDate%, %TimeStamp%, %UmraFormSubmitDomain%, %UmraFormSubmitUsername%, %UmraPath%, %SystemRoot%. See Built-in variables for more information (1455, 28/May/2008).
  5. Error importing large amount of projects (fix): An error could occur when importing large amounts (> 250) of projects in a single operation. The operation has been changed to support more projects (1433).
  6. Distinguished names with slash (fix): The following actions – properties are updated to support distinguished names containing one or more forward slashes: action Set attribute (AD), property Active Directory object LDAP name, action Create object (AD), property LDAP Container, action Set group memberships (AD), property Active Directory name, action Create user (AD), property LDAP Container, action Remove specific group memberships (AD), properties Group name (LDAP) and Account name, action Move cross domain, properties Source object and Target container, action Create contact (AD), property LDAP Container, action Get user table (…), property LDAP path, action Create group (AD), property LDAP Container, action Move – rename (AD), property OU-Container LDAP name, action Get object (AD), property LDAP name (1438, 8/April/2008).
  7. Script error handling (fix): When the error handling settings of a script action are updated, the project is now marked as dirty (e.g. needs to be saved due to changes in the project) (1458, 2/June/2008).
  8. Log variables - Display of Carriage Return Line Feed (fix): When a variable value contains carriage-return and/or line-feed characters, the action Log variables will show these characters ([cr],[lf],[crlf]).
  9. Log variables - Scheduler tab shown (fix): When an automation project is scheduled to run once, and the run time is passed, the project window now shows the scheduler tab. In previous versions, the scheduler tab was only shown if the project schedule time was in the future (1462, 11/June/2008).
  10. Drop down lists, edit field (fix): In a number of dialogs and tabbed windows, the the edit field of drop down lists now automatically scrolls in a horizontal direction when text is entered. In previous versions, the length of the entered text was limited (1462, 13/June/2008).

9.0 Build 1425, February 1st, 2008   

New Features
  1. Major new area of functionality: Support of PowerShell. The UMRA software is extended with the PowerShell Agent service. The service supports the integration of UMRA and Powershell. New actions that can use any PowerShell cmdlet can be added to UMRA in a dynamic manner to extend the functionality of UMRA. For more information, see the PowerShell Agent Service topics in the online help.
  2. Major new area of functionality: Support of Exchange 2007. Based on the new Powershell Agent service, over 25 new actions are added to UMRA to support the management of Exchange 2007 mailboxes and other resources. For more information, see the Exchange 2007 topics in the online help.

This new functionality is licensed as a separate module. Existing users should contact Tools4ever for an upgrade of their licence keys when required.

8.0 Build 1343, May 4th, 2007   

New Features
  1. Major new area of functionality: Management of IBM's Lotus Notes environments. In addition to the existing possibility to manage the Lotus Notes Directory with LDAP, UMRA has been extended to interface with native Lotus Notes environments; it can now create, delete and move Lotus Notes user's and resources directly, and perform a vast number of other Lotus Notes related actions. This functionality is completely integrated with the current functionality of UMRA. For this purpose no less then 25 new UMRA script actions have been created.

    This new functionality is licensed as a separate module. Existing users should contact Tools4ever for an upgrade of their licence keys when required

  2. New project hierarchy for server based projects.
    The projects on the server can now be organized in a tree structure. Note that the tree structure is currently only for display purposes, and is visible when the projects listed with the menu option UMRA Service, Manage server Projects.
  3. Update the license Mechanism. Updated the license mechanism to facilitate a new licence that specifically allows the SSRPM (Self Service Reset Password Management) product of Tools4ever to interface with UMRA.
  4. New Action. A new action Script Action: Count licensed - domain/OU accounts has been added. Use this action in a script to find out how many user accounts are there in the domain/ou and compare these with the number allowed according to the license. This action allows to find out if a domain is nearing the limit specified in the license. You may want to use this in a scheduled script that sends an email to an UMRA administrator if the license count is almost reached.

Enhancements
  1. Action enhanced: For Each. The maximum number of possible variables that can be coupled to the table columns in the called project, has been increased from 20 to 300. (1307-1338)
  2. Action enhanced: If - Then - Else. The variable argument was only allowed to exist of exactly a single variable. It has been modified so that is is allowed to consist of a text string that contains variables. (1307)
  3. Action enhanced: Move - rename user (AD). The action has been extended to allow for the move and rename of other objects than users, like for instance contacts. Therefore the action has been renamed to Move - rename (AD).(1307)
  4. Action enhanced: Load LDAP Modification Data. The name of the attribute to modify can now also be specified as a variable, instead of fixed in the action.
  5. Action extended: Manage Table data. The action is extended with three table data operation functions.
    1. Convert multi-text variable to table. Used to convert a variable of the type text-list to a table of a single column, and a row for each value in the text-list.
    2. Convert multi-value variable to table.
    3. Convert table column to multi text variable. Used to convert a specific column of a table to a text-list variable.

  6. Action extended: Fomat variable value.New formatting functions have been added: Delete: Leading blank characters and Delete:Trailing blank characters
  7. Logging. Added an option to be able to enable or disable logging to memory for server projects. With the project script tab selected, choose Actions, Project script properties, and select the options tab to access this functionality. switching it off may significantly increase performance when running projects from the delegation client.(1307)
  8. MySQL datatypes. For MySql server support is added for the date datatype, which contains only the date, not a time. As UMRA itself does only support date-time, as a datatype, when reading it will be converted to a date-time value with the time set at 12.00 hr pm.(1307)

Major Fixes
  1. Generic table. A memory leak has been fixed which occurred when reading multi-value values in a generic table; for instance when querying the Memberof attribute in an LDAP query. (1303)
  2. Action Create user (AD). When a user cannot be created due to password complexity requirements, the temporarily created user object is now correctly removed from Active Directory(1307)
  3. Script Action: Move Exchange Mailbox. A fix has been created for an crash problem introduced by SP2 of Exchange 2003.due to incompatiblities of the updated Exchange software.(1307)
  4. Script Action: Modify exchange mailbox permissions 2000/2003. A memory leak has been fixed (1307)
  5. Script Action: Move Exchange Mailbox. Action could cause an exception if the specified user object variable was not valid, for example if it was the result of a failed Get user Action. Now it gives a correct error message and continues with proper error handling as specified.(1311)

Minor fixes
  1. Sheduler. When a project was sheduled for daily execution, the scheduling could not be disabled (it could still be configured as never though). This has been fixed (1309)
  2. Generate generic table-LDAP Query. The LDAP query filter could not contain variables, they where not resolved at run time. This has been fixed.(1309)
  3. Script Action: Execute script. The name of the script to execute could not contain variables. now it can. (1311)
  4. Script Action: Update date-time variable. The action parameters can now contain variables. (1311)
  5. Script Action: Format variable value, the formating function Delete, all matching characters, specified as ASCII codes deleted both upper and lowercase of the specified value when applicable. That is, when specifying 97, in order to delete 'a' accidentally also all occurrences of 'A' where deleted. This has been fixed.
  6. Script Action: copy directory. When the copy fails because the destination drive is full, UMRA logged a correct error message, but the error handler (the "on error" part of the action) was not invoked. Now the error handler is invoked correctly.(1311)

7.6 Build 1302, August 23rd, 2006

New Features
  1. Project Scheduler. A major new mechanism to run projects has been added to the UMRA service: the UMRA Scheduler. UMRA projects can now be executed automatically at scheduled times by the UMRA service. Open a project and choose Actions-->Scheduler to view and specify scheduling information for the active project. Choose View-->Scheduler to see the scheduling overview of the UMRA Service. Press F1 in those windows for more information.
  2. New action - Join Table Data. The Script Action Join table data has been added.
  3. New action - Manage table data. The Script Action Manage table data  is extended with an option to sort a table based on the column name.
  4. Action extended : Generate generic table. The Script Action Generate generic table, is extended with the option to generate a table from a .csv file, and to specify the names of the columns explicitly.
  5. Security improved. All RPC communication between the UMRA console, Umra Service,Umra Com and the UMRA forms client is now encrypted by means of SSL.
  6. Aborting scripts. A mechanism has been added to see which scripts are currently actively running, and also to make it possible to abort those running scripts if required. choose UMRA Service -> Control Running projects from the menu to go to the overview.
  7. Search and Replace. An "search and replace" option is added to search (and or replace) trough all configured action property values and specifications in all projects in the active workspace. Useful for instance if you want to rename a variable that is used in a lot of places.

Enhancements
  1. Service logging. The service can be configured (choose Umra Service-->Service properties;Advanced tab) to create user specific cyclic log files rather than general ones. The names of the log files are derived from the name of the account with which the a user connects to the service.
  2. Project logging. Previously, at the start of each project execution, the values of all variables in the project where logged. This could be a lot of uninteresting data, especially if a project was called many times within a "for each" action. Now this can be switched off in the project options of a specific project (choose Actions-->Project script properties;Options tab)
  3. UMRA Com performance. UMRA Com is extended with a new interface call (EnableReturnLog) to specify whether or not the log info generated by the service should be returned to the calling Com Object. By default the log information that the called service project generates is returned to the calling Com Object, so that it can be displayed if required. If this option is switched off, no log information is returned to the calling Com object. In both cases the log information is logged in the logfiles on the server. Disabling the return of log information increases the performance.
  4. UMRA command line Application. The UMRA command line application "UmraCmd.exe", now has an extra command line option (-NoLog), which suppresses log information shown on the command line and increases performance.
  5. Column names in Database Query. Form tables with database query: When the query is run in the console in the test tab, the column names as implicitly returned by the query are stored , so that they subsequentially can be used with the specification of the columns to show.
  6. Action enhanced: Manage table data. The Script Action Manage table data is modified. Within the sub-option "Export to .csv", it is now optionally possible to write a header with the column names to the file.
  7. Extra variables in automation projects. The %NowDay%, %NowYear% default variables are now also available in automation projects.
  8. Console GUI: When creating a new project, the project name is now first proposed, before being used.
  9. Extra output variables in script actions. The actions  Create user, Create group (AD) and Create object (AD) have been extended, so they will now optionally output the Object Distinguished Name of the object they have just created, to a variable. In larger scripts, this name was often needed further on in the script. Previously it had to be explicitly retrieved by using for example the "Get attribute" script action. and that is now no longer required.
  10. Action enhanced: For-Each. The script action For-Each is extended with the possibility to specify which variables should be available to use for the called project. Making unavailable variables that are not used in the called project can drastically (> 10 times faster) improve performance.

Major Fixes
  1. Table in forms Client. When a selection was made in a table, clicking on a column header to resort the table would change which items where selected. This has been fixed.
  2. Logging mechanism. A potential critical error in the internal working of the logging mechanism on the service has been fixed. In some circumstances, when the execution of form script did not finish within the timeout period, and several other conditions where met, an error in the cyclic log mechanism could cause a critical failure in the UMRA service. This has been fixed.
  3. Script action Update date-time variable. The script action Update date-time variable did not work if the option "convert to 100ns interval since 1-1-1601" was chosen. This has been fixed.

Minor Fixes
  1. Service logging - Several log files use a method of cyclic logging; that is, when a file log1 has reached a specified limit, logging continues in file log2, etc. In some circumstances a few log messages that where generated at the time of file change, were not correctly written to file. This has been fixed.
  2. LDAP name syntax. If the name-part of an object contains a forward slash "/", the format that LDAP uses to specify the name of the object was not handled correctly by UMRA. This has bee fixed.
  3. Script action "Manage table data", option "export to .csv file". The output file contained incorrect "new line" like characters, which caused additional empty lines when the file was read by some applications (MS access for example). This has been fixed
  4. The Action "Set variable" did not write an message to the log when it was executed. It now will.
  5. When creating a completely new name generation algorithm, it was not created with the specified name, but with a number. This has been fixed.
  6. If a workspace contains more then 1 project, and has been modified, the user will be prompted to save the workspace when exiting the console.
  7. A project is now also marked dirty when a script action is removed from the script. So the user is correctly prompted to save when exiting.
  8. When using a Forms project in which inside the script of the specified "initial project", a table is read from a .csv file with the script action "Generate generic table", and this table variable is shown afterwards in a Form Table with the option to read the contents of the shown form from a variable, the order of the entries shown in the table was not the same as the order of the entries in the original file. This has been changed, so that, if no sorting method is selected, the original order of entries read from the file is maintained.
  9. When using the script action Generate generic table to perform an LDAP search query, the specified time-out values where not correctly used, which could in some circumstances cause the search to fail, for queries that tool a very long time. This has been fixed.
  10. The Ctrl-C and Ctrl-V copy and paste actionsnow also work for the static text and input text fields in the forms client
  11. The Set variable action has been modified. If the current value of a variable contains a reference to itself, it is no longer resolved even when the option "resolve now" is on.
  12. When a project is opened, and closed immediately thereafter, it is now added to the list of recent projects. previously it was not added.
  13. In the script action Create Exchange Mailbox (2003/2000). The name of the variable used for the User Object can now be specified. Previously this was always fixed to %UserObject%. and thus the action could not be used if the user object was stored in a different variable.

Cosmetic Fixes
  1. The icons in the main button bar corresponding to the project tabs (script, form ,preview, network data etc), are now checked/unchecked depending on the existence of the associated project tabs in the active project.
  2. Action format variable,sub-action "Replace substring with ASCII codes". The description field has been enlarged.
  3. Some irregularities in the display after vertically scrolling a form in the Forms Client have been fixed.
  4. The Umra log file UmraSvcFormLog.txt contained superfluous extra new line characters between log messages. This has been fixed.

7.5 Build 1263, May 12th, 2006

New features
  1. GUI - The main interface has been drastically improved. The key project concept of UMRA has always been the creation of an UMRA project script using input data from various sources ((CSV) files, databases, other applications). The main interface has been reworked to support this concept more strongly. Depending on the kind of solution you want to create (MASS, Forms, Automation), UMRA will include the relevant project components for the selected project. Also, as part of the overall interface makeover, the Personal Assistant, What's this help and Project Wizards have been removed. (1263)
  2. MASS projects - In this new release, the UMRA project type has changed. Because of this, all MASS projects created in previous versions of UMRA (.UPJ files) have to be upgraded before they can be used in the new UMRA version. Please follow the procedure Upgrading MASS projects from previous versions as described in the online Help to upgrade these files. (1263)
  3. Workspaces - A new feature is the introduction of workspaces. This allows the user to structure complex projects more efficiently. See the online Help for more information. (1263)
  4. Computer NETBIOS name - the NETBIOS name of the computer accessing the UMRA Service is now stored in the UMRA variable %UmraClientComputer%. (1263)
  5. Copy directory script action - when using this script action, the date, time and attribute stamps are now copied as well. (1263)
  6. Remove SID history script action - A script action has been added to remove the SID history of a (removed) user account. See the online Help for more information. (1263)
  7. Rename directory service object (LDAP script action - UMRA contains several script actions to manage LDAP directory services. A script action has now been added to change the distinguished name of an entry in the directory service (only available for LDAP version 3). See the online Help for more information. (1263)

Major fixes
  1. Setup LDAP session script action - in the previous UMRA version, LDAP version 3 was not correctly initialized. LDAP sessions exist in version 2 and 3. Version 3 offers more functionality, which is why UMRA initializes the session based on version 3. This was incorrectly implemented, resulting in an error on Windows 2003. This has been fixed. (1263)
  2. Command line tools script action - In previous versions, the port option of the command line did not work. This has been fixed. (1263)
  3. Modify exchange mailbox permissions (2000/2003) script action - In previous versions, an error in a scenario where you have users A, B and C. User A has a mailbox and user B gets permissions for this mailbox. If user B was removed from Active Directory and a third user granted permissions to the mailbox of user A, an error would occur. This has been fixed. (1263)
  4. Set user group memberships (AD) script action - In some rare situations, the group selections were unexpectedly cleared. This has been fixed. (1263)
  5. UMRA Service - In previous versions, if you had changed the data cache retry value, this value would be reset to the default value if the UMRA service was restarted. This has been fixed. (1263)

Cosmetic fixes
  1. Execute script script action - The combo box for the Project property has been enlarged to display long path names. (1263)

7.4 Build 1227, January 6th, 2005

Major fixes
  1. Setup Security - All directories and files for which security was set using this script action, were made read-only (using either propagation mode or not)(1225). This has been fixed.

7.4 Build 1225, December 23rd, 2005

New features
  1. Script actions have been added to manage LDAP directory services using UMRA: Setup LDAP session, Load LDAP modification data, Delete directory service object (LDAP), Add directory service object (LDAP), Modify directory service object (LDAP), Search LDAP. Examples of such directory services are Novell eDirectory, Linux OpenLDAP and Microsoft's Active Directory. All these directory services can now be managed using UMRA.
  2. New action - Delete attribute value (AD) - Script action has been added to delete a specific attribute value.
  3. New action - Execute script - Script action has been added to execute the script of another project and merge the updated variables into the current project.
  4. New action - Generate password - Script action has been added to generate a password.
  5. New action - Get user table - Script action has been added to generate a table containing information regarding locked-out users, disabled users and other user account control states.
  6. New action - List files and/or directories - Script action has been added to obtain a list of files and directories in a variable. This variable can in turn be displayed in a form table.
  7. New action - Set encrypted variable - Script action has been added to set the value of the specified variable to the encrypted value of the entered text.
  8. Enhanced - Check form input - An option has been added to check the string length of text which has been entered by the user in an input box. The variable contents check specification has been restyled.
  9. Enhanced - Format variables - The option "Conversion: Remove diacritical marks" has been added to remove diacritical marks from a string.
  10. Enhanced - Form property Initial Project - The Initial Project tab has been renamed to Execution control and now includes an option to set a time-out for script execution.
  11. Enhanced - Manage table data script action (Programming) - Option has been added to remove rows and columns of a table.
  12. Enhanced - Return project form - Option has been added to specify a variable for the returned project form.
  13. Enhanced - Table form field options - An option has been added which can be activated to execute a default button when the user doubleclicks a table entry.

Major fixes
  1. Major fixes Manage exchange recipient mail addresses (2000/2003) script action: In previous versions, UMRA would crash if a non existing AD had been specified. This has been fixed. (1225)

Minor fixes
  1. Edit User (AD) script action: In previous versions, the on error actions did not work for this script action. This has been fixed. (1225)
  2. Execute service command script action: The text in property Wait for status completion has been changed from "If set, the action will not complete until the services reports the requested state or the time-out period is expired." to "If set, the action will not complete until the service has the requested state or if the time-out period has expired." (1225)
  3. For-Each script action: In previous versions, when a network location was specified in the Script project property, the path of the standard project location was included, which resulted in an execution error. This has been fixed (1225).
  4. Form elements - Display tab: In previous versions, the option "Vertical pixel offset" would only work for text fields. It now also works for tables, checkboxes, radio buttons and standard buttons. (1225)
  5. Generate name(s) script action: In the previous versions, the text under the Iteration property read "can only be used for mass projects". This is incorrect. It can also be used for Forms projects in a loop. This text has been removed. (1225) Generic table type Variable: In previous versions, when you specified the table height in the Options tab, this specification would not be used if the variable did not contain any items. This has been fixed. (1225) LDAP attribute variables: In previous versions, when the LDAP query of an existing LDAP Search was changed, any variables assigned to these attributes would disappear. In the new build, the variable specification remains intact when you add attributes to your LDAP search. When you change the order of appearance however, the mapping will no longer be correct. This is by design. (1225) Licensing: In previous versions, when a DNS domain name had been licensed, UMRA would not accept a DNS name for the domain. This has been fixed. (1225) User name generation algorithm: In the previous version, if you specified an "Arbitrary sequence" (e.g. "01,02,03") and clicked OK and then opened the iterator again, the iteration object had changed to "01, 02, 03" (spaces added). These spaces would also end up in the user account name. Each subsequent cycle would add another space. This has been fixed. (1225) Cosmetic fixes Table columns: Table columns are now always dynamically resized when the table dimensions are adjusted. (1225) Project forms display name: Project forms now also have a display name. By default, the display name is identical to the project name and is also shown in the Forms project client tree. (1225) Project execution statu

Home |Products |Support |Pricing |Download |Press |About Us |Contact |Sitemap
QUICK LINKS:Identity and Access Management (Idm, IAM) |Self Service Password Reset Management
QUICK LINKS:Auto User Provisioning |Enterprise - Single Sign On (E-SSO) |Password Management