sdRohan sdRohan

Multiplicity 4.0.0.4 Release Feedback Thread

Multiplicity 4.0.0.4 Release Feedback Thread

With the Multiplicity 4.0.0.4 release, we are creating this thread so that users can report any observed issues.  

Obtaining the product

Object Desktop members can get the release from within Object Desktop Manager 

Individual purchases (as well as Object Desktop Members) can also be obtained from your account page: https://store.stardock.com/myaccount/products

For guest check-out purchase (no account), from this link: http://www.stardock.com/support/productkeyretrieval

Reporting an issue

Please include the following for anything found:

  • Exact Windows version \ build (winver.exe)

  • Detailed steps to recreate the issue seen

  • Screenshots and videos are very helpful.  Videos can be uploaded to a cloud drive service (GoogleDrive, DropBox, OneDrive, YouTube), with a shared link included in your post.  Images can be copied and pasted directly into a post.

  • If there are specific apps that the app does not work (well) with, please note what apps and their exact versions.  If any app is not common, a link to a trial version would be appreciated.

Thank you for your interest and any time you put into making Multiplicity 4 a better product.

Sean Drohan
Stardock Support Manager

44,094 views 32 replies
Reply #26 Top

Version 4.0.0.4
If the head end PC in a seamless deployment crashes (Windows), there is a 50/50 chance the remote PCs will not be able to connect once the head end PC is back online. The only resolution is to restart the multiplicity service on the remote PCs which may be difficult if they are in a headless configuration.

Reply #27 Top

Quoting Suterusu1416, reply 26

Version 4.0.0.4
If the head end PC in a seamless deployment crashes (Windows), there is a 50/50 chance the remote PCs will not be able to connect once the head end PC is back online. The only resolution is to restart the multiplicity service on the remote PCs which may be difficult if they are in a headless configuration.

Do you mean in KVM not seamless?

Reply #28 Top

I mean in seamless mode. If my main PC I control everything from crashes, at least 1 of the 5 remote PCs will not connect once the main PC is rebooted. The only fix is to reboot the remote PC or restart the multiplicity service on it.

Reply #29 Top

Quoting Suterusu1416, reply 28

I mean in seamless mode. If my main PC I control everything from crashes, at least 1 of the 5 remote PCs will not connect once the main PC is rebooted. The only fix is to reboot the remote PC or restart the multiplicity service on it.

I am confused as you mentioned them being headless which would mean not having displays?

Reply #30 Top

Sorry that was my mistake. They do have displays attached, yes. I use a cheap keyboard/mouse receiver so Windows thinks there is an interface device attached, but I do not have any local access to the PCs and their monitors are remote via fiber optic HDMI, so accessing them directly to restart the service is not trivial. But they are all on the grid.

 

Reply #31 Top

Quoting Suterusu1416, reply 30

Sorry that was my mistake. They do have displays attached, yes. I use a cheap keyboard/mouse receiver so Windows thinks there is an interface device attached, but I do not have any local access to the PCs and their monitors are remote via fiber optic HDMI, so accessing them directly to restart the service is not trivial. But they are all on the grid.

Have you tried installing 4.01 on EACH MP PC?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #32 Top

Quoting sdrohan, reply 31


Quoting Suterusu1416,

Sorry that was my mistake. They do have displays attached, yes. I use a cheap keyboard/mouse receiver so Windows thinks there is an interface device attached, but I do not have any local access to the PCs and their monitors are remote via fiber optic HDMI, so accessing them directly to restart the service is not trivial. But they are all on the grid.



Have you tried installing 4.01 on EACH MP PC?

https://forums.stardock.com/534734/multiplicity-401-release-feedback

Sean Drohan
Stardock Product Lifecycle Manager