Upgrading MxServe

Migration occurs automatically the first time you run MxServe 2.0. There are cases that require manual intervention however. If your token pools meet any of the following criteria, use the Kill License/Return Tokens procedure. Danlaw will reissue tokens of the proper type and duration.

•Token pools that contain both permanent and temporary tokens.

•Token pools that should contain regional floating tokens or global floating tokens. The built-in migration process treats all floating tokens as site floating, so Danlaw intervention is necessary.

•Multiple token pools on one server. In most cases, we recommend that you work with Danlaw to consolidate all tokens into a single instance of MxServe. There are some configurations where multiple instances may be necessary.

If you are upgrading a secondary token pool from MxServe 1.0 to MxServe 2.0, please follow these instructions: Upgrading the Second Token Pool

Licenses are no longer affected by third party applications such as anti-virus programs, unless those applications actually delete or modify the files.

All releases of the MxSuite work with either MxServe 1.0 or 2.0.

Messages from MxServe

Due to a change in how services interact with the desktop in Windows editions later than XP, MxServe was unable to display messages to the user in Windows Vista and Windows 7. This has been addressed in MxServe 2.0 by having MxServe Monitor handle the display of critical messages from the locally installed MxServe service.

•MxServe Monitor starts automatically when MxServe finishes installing, and is configured to launch automatically when you log into Windows

oIf you wish to stop MxServe from starting automatically on log in, you may remove the shortcut present in the All Users startup folder. This may require administrative permissions.

oIf MxServe Monitor is not running, MxServe will not be able to display critical messages to the currently logged in user.

•When MxServe Monitor is closed, the application is minimized to the system tray.

•To quit MxServe Monitor, you must right click the tray icon and select "Exit". You will prompted before the application actually exits.

oMxServe Monitor is required to be running in order to display messages from MxServe (local instance only). If MxServe Monitor is not running and MxServe tries to display a message, the message is written to file and displayed the next time MxServe Monitor is started.

▪If no user is logged in, this is the default behavior.

▪It is an absolute requirement that Windows does not disable the "All Users" user folder in XP or the "Public" user folder in Vista/Win7, as this will break the delayed reporting mechanism.

oOnly the most recent message from MxServe is queued up in this way.

•Note that this does not replace MxServe's internal logging system. Whether a message succeeds in being displayed to the user or not, it is first logged to the MxServe log files first.