'User Machine Mapping' was first introduced in DLO 8.0 SP2, as a feature giving the ability to create a specific association between a User and a Machine, allowing them to run the DLO Client.
In DLO 9.4 this has been improved to provide better notification and also to enforce who can or cannot access a user machine.
Previously, if a User Machine Mapping was in place and a user who was not included in that mapping attempted to run the DLO Client on that machine, the DLO Client would open and immediately close, with no other indication.
In DLO 9.4 the below warning message is now displayed, advising a user that they are unable to log on due to a defined mapping in place :

In previous versions, if a User Mapping had been defined between a User and a Machine, that User was able to run the DLO Client on that machine, but not any other. Other users were not affected by that and it was possible for a 2nd User to log on and successfully run the DLO Client on that same Machine.
In DLO 9.4 User Mapping restrictions have been enforced, which means that once a User Machine Mapping is in place for a Machine;
Below is an example of the new behaviour, when User Machine Mapping has been configured

If you require multiple Users to log on and run the DLO Client on the same Machine, where a Mapping has already been defined, additional User Machine Mapping entries will now need to be created for each of those Users. Mapping them to that Machine will allow the DLO Client to run.
For more information about User Machine Mapping, see the articles below:
'Logged on user is not mapped to this machine for backup operations' is displayed when starting the DLO Client - https://www.veritas.com/docs/100048295
Desktop and Laptop Option 9.4 Administration Guide ('Mapping User Machine' Page 128) - https://www.veritas.com/content/support/en_US/doc/DLO_94_AdminGuide