|
|
 |
|
 |
Last
Update |
Description |
2010.05.19 |
DSMETER Updates
[FIX]
This version adds protection for a scenario with an unexpected eDirectory NCP packet that may have been corrupt.
|
2010.05.17 |
DSMETER Updates
[FIX]
Corrected a problem where Long File Name was turning to DOS naming after clustered volume failover.
|
2010.04.15 |
DSMETER Updates
[FIX]
When FS Trustee changes are made by an NLM, the Security Change Tracking
reports will now show that they were performed by an NLM. For example, when
files and directories are restored by a backup program which also restores
their file system rights.
[FIX]
Corrected this error that sometimes occurred when running DSMETER reports:
"Error [PushLV OTF]Error Allocating Memory for LV_OTF"
|
2010.02.17 |
DSMETER Updates
[NEW]
DSMETER.NLM can now be loaded with these two new parameters:
/XST = XmitOverrideStartTime
/XET = XmitOverrideEndTime
These optional parameters can be used if you want to override the transmit
to repository interval that is set in the DSMETER interface (such as
transfer log files every 60 minutes). These parameters will send to the
repository only once per day. They will send at the time you designate, or
within a range of times that you designate during the same calendar day.
If you want to send the log files at a specific time, use the /XST switch
only. For example:
LOAD DSMETER /XST 0200
Means that transmission of log files to the repository (even if the
repository is 'on the same server') will occur once a day beginning at the
specified time (0200 or 2:00am).
If you want to send the log files within a range of times, you would use
both parameters. For example:
LOAD DSMETER /XST 1900 /XET 2359
Means that transmission will begin at a RANDOM time sometime between 7:00pm
(1900) and 11:59pm (2359). The 'random time' will be noted on the DSMETER
Messages Screen of each server.
When using XST and XET, the XST value must be specified first. Otherwise
the XET value will be ignored and there will not be any random time, and the
send will be at the time specified by XST.
If you specify an XET prior to the XST, the XET value will be ignored.
Therefore, when using both parameters to specify a time range, be sure the
two times are within the same calendar day, and that the XST time is before
the XET time.
If you specify the same exact time for XST and XET, it has the same effect
as specifying only XST.
The time specified must be NNNN (4 characters, the first two characters for
hour and the last two characters for minutes). If a number higher than 59
is put in for the minutes, it will be capped at 59 and the 'corrected'
start/end time values are noted on the Logger Screen (NW 6.0 or 6.5) or the
Server Console screen (NW 5.0 or 5.1) when DSMETER.NLM is loaded.
The parameters can be set when loading DSMETER.NLM manually, or you can
define DSMETER Server Groups and apply the parameter to multiple servers
being loaded at the same time by the Server Group. Note that the
AUTOEXEC.NCF file for each server should be edited to add the desired
parameter(s) to the DSMETER load line.
|
Last
Update |
Description |
2009.11.09 |
DSMETER Updates
[FIX]
Corrected a problem that sometimes occurred when changing fax numbers.
|
2009.10.16 |
DSMETER Updates
[NEW]
Corrects a potential problem with event chains coming from certain older versions of DS.NLM.
|
2009.09.04 |
DSMETER Updates
[NEW]
When a value of an attribute is added or modified, DSMETER can now record the new value for many attributes.
|
2009.08.21 |
DSMETER Updates
[FIX]
Corrected a problem with tracking NMAS bad password attempts.
|
2009.05.07 |
DSMETER Updates
[FIX]
Corrected a problem with initial install not completing the first time and having to run again for certain situations.
|
2009.03.27 |
DSMETER Updates
[FIX]
Corrected a problem with tracking file system rights changes.
|
Last
Update |
Description |
2008.07.09 |
DSMETER Updates
[UPDATE]
Made some updates to the Designer so a second window cannot be created and to allow to delete the report view if more than one exists.
|
2008.06.19 |
DSMETER Updates
[UPDATE]
Made some performance and memory enhancements.
|
2008.04.09 |
DSMETER Updates
[FIX]
Added load switch /NCPLoginauth to correct a problem with the previous
/NCPLogin switch that was reporting actual eDirectory Logins as Bindery
Logins.
|
2008.04.03 |
DSMETER Updates
[UPDATE]
Updating Profile Creation when using Subscription Tokens where there are fewer servers defined than exist in entire Tree.
|
2008.03.03 |
DSMETER Updates
[FIX]
Corrected a problem with Long Name reporting on clustered volumes. The tracking stays consistent upon volume failover.
|
2008.02.04 |
DSMETER Updates
[FIX]
Corrected a problem with Long Name reporting on clustered volumes.
[FIX]
Corrected the reporting of the Intruder Lockout attribute being modified upon Login.
|
Last
Update |
Description |
2007.12.11 |
DSMETER Updates
[FIX]
Low volume space is now being tracked correctly on non-clustered volumes.
[FIX]
Alerting is now working for low volume space and low cache buffers on non-clustered volumes.
|
2007.10.03 |
DSMETER Updates
[NEW]
New load parameter /NCPLogin
|
2007.07.14 |
DSMETER Updates
[NEW]
Load parameter /ExchangeEmail for using email alerts with Exchange email
[FIXES]
Fix for Unknown Alert Code 303 when alerting for copying files
Fix for incorrect server count in Insufficient Base License error messages
|
2007.07.10 |
DSMETER Updates
[FIXES]
Directory and file renames are now tracked/blocked consistently
Reporting now works correctly if the default volume/directory do not exist on the Repository Server and it uses SYS:SYSTEM\DSMETER instead
Fix for changing the Default Directory while DSMETER.NLM is loaded
|
2007.06.14 |
DSMETER Updates
[FIXES]
Copy NLMs button now only affects servers in the Install Location
Fix for monitoring cache buffers by number (rather than by percentage)
Fix for DSMETER tracking and alerting for items from a deleted profile
|
2007.05.29 |
DSMETER Updates
[NEW]
Intruder Lockout included in Failed Login Reporting
[FIXES]
Now alerts correctly for file system rights
Eliminates some duplication where there had been paired eDir logins with Bindery logins at the same time
Fix for issue renaming files via FTP on NetWare 5.1 servers
When load parameters are defined for a server group, the load parameters are now only applied when using NLM load buttons that are specifically for server groups
File tracking fix for showing the activity in all profiles if the profile definitions overlap
File tracking fix for Directory Creates
Can now load Repository Server with /L if desired
Removed messages about NDS Security Tracking alerts from Logger Screen
|
2007.05.10 |
DSMETER Updates
[NEW]
Track file copies
[FIXES]
Fix for handling container tokens
Removed debug messages from DSMETER Messages Screen
|
2007.05.08 |
DSMETER Updates
[NEW]
Support for multiple repository servers
Support for independent installations in the same Tree
Support for Clustered Volumes as Repository Host
New Profile Type: NetWare Server Activity can
monitor the following:
- CPU Utilization exceeds threshold (time-based)
- When any Volume is more than % full
- When any Volume is mounted/dismounted
- When any user has less than % disk space remaining of space restriction
- When any folder has less than % disk space remaining of directory space restriction
- When Cache Buffers are low
- When Server is rebooted/restarted
- When an NLM is loaded/unloaded
- When any replica on any server is in an
error state
Customizable alerting on NDS Security Profiles (ability to alert different people for different events, and choice of using Novell send pop-up messages and/or SMTP email messages)
NDS Security Profiles: Track individual objects
File Tracking Profiles: Exclude from tracking option (Example, track all file activity on a volume except do NOT track some specific directories or some specific files on that volume)
File Tracking Profiles: Track actions on Folders/Directories (Directory Creates, Directory Renames, Directory Erases)
Block folder/directory actions (Directory Creates, Directory Renames, Directory Erases)
Automatic Purge of Log Files based on date (Example: Delete all log files not written to in the past 365 days)
Ability to manually delete multiple log files at the same time from the Manage Log Files screen
Encrypted Log Files
Track LDAP Authentications
Track how long object was Logged In (this is shown in the Logout records)
Track what NLM authenticates the login
Track whether users logged in with a null password (did not use a password)
Custom Reports - New Rule: Activity that happened today
View Last Transfer to Repository server per DSMETER.NLM (go to DSMETER.NLM Maintenance, do "Check DSMETER Load Status", scroll all the way over to the right on the results)
View DSMETER Messages screen to see if there are any errors (go to DSMETER.NLM Maintenance, do "Check DSMETER Load Status", then use the button at the bottom of the page below the results)
Ability to maximize the screen when running Quick Reports or Custom Reports
Ability to license DSMETER for only the servers you want to load it on rather than whole Tree (note that if you choose not to load DSMETER.NLM on all servers some DSMETER features will have incomplete tracking or blocking, more details about this are available from technical support)
[FIXES]
Now tracks attribute modifies and attribute deletes correctly
Fixed certain compound rule combinations in Custom Reports
File Activity profiles will now track/block/alert for all items defined in the profile, instead of only the first match found
|
|
|