Depending on how the install was initiated, one of the MSIExec processes can be the client process. Another MSIExec process is Windows Installer service.
Any remaining MSIExec processes are usually sandbox processes for hosting custom actions. The determination as to which MSIExec process will serve as the sandbox process for a script or DLL custom action depends in part on whether the custom action will run elevated or impersonated and whether the custom action is 32-bit or 64-bit.
question is what is GUID Here while embeding and it is keep changing from system to system and across the installation...javascript:emoticon('
