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.
Comments
As Microsoft finally has some plans around this. Here is one more idea in regards to the "Mass Activation" of POS.
One way of solving the security issue regarding the massactivation of the POS is by using a certificate or a token file that could be copied to the PC's where the POS activation is be automatated.
This file could be automatically distributed before the activation is started and then removed automatically after the activation is completed.
Looking forward to this feature ,as we are going to have several thounds CPOS activated in future.
Category: Deployment and servicing
The same exact issue has been raised as a show stopper. Most of the enterprise customers we work with has a stringent policy that all users should log in to a PC with their own windows credentials. We end up creating multiple devices to be activated on the same physical device. Just think about a store where there are 10 physical devices and 30 employees in different shifts. We create 30 devices which lead to overhead in terms of operations and device management.
Category: Deployment and servicing
Stuart Hargreaves (administrator) on 3/28/2023 2:18:41 AM
With 10.0.32 release, Store Commerce app will support device token at the machine level instead of user level.