The activation of MPOS/CPOS needs to be per device, and not per user profile in Windows per device. As of now the activation of MPOS does not work exactly as CPOS. The CPOS activation can work and not the MPOS activation when using a partner logon at a customers environment. The activation of MPOS/CPOS is per user per device and not per device (PC).This means it is not possible to run the same MPOS with the same teraminal Id for two or more Windows users on the same PC. Even though the DLLHost.exe.config is common. It would be easier for developers if it would be switch between environments by changing the DLLHost.exe.config file. Should also be easy for developers to install one or more versions of MPOS side by side on a development box and switch between different environments. The "AllowMassActivation" parameter found in the DLLHoost.exe.config file does not seem to be supported or documented. MS support could not give any answers about it. Mass activation of devices would make implementation easier. Doing one MPOS at a time, is time consuming when dealing with many hundreds of POS. The idea should be: Device(PC) is activated and it is activated for one or several teraminal id's. (several, in the case of a development or testing) The whole thing needs to be better documentet. This include flow of tokens between system, setup paramters, etc.