VMWare Synchronizer
I have just deployed my first Devolutions server, and am working on getting the RDP sessions created from VMWare. When I do the synchronizer, it seems to work, and it creates quite a lot of the environment, but not all of it. I am missing entire folders of VMs from VirtualCenter in the Devolutions server after the sync. It's not like the entries are created in the wrong folder, or some folders are missing some entries, it appears that it just doesn't create all the folders, and any VM in the folder is also not created. I don't see any logs that tell me why, just that the sync happened, was successful, and nothing more. Is there a place where the actual sync documentation lands? Any idea why only half or so of our VMs create a new RDP entry?
I do have this error in the Devolutions windows log, but it doesn't tell me much (I removed the computer name from the output):
Log Name: Devolutions
Source: DVLS
Date: 1/16/2026 2:49:46 PM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: <*computername*>
Description:
The description for Event ID 0 from source DVLS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
VMWareSynchronizer
The message resource is present but the message was not found in the message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="DVLS" />
<EventID Qualifiers="0">0</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2026-01-16T20:49:46.7233816Z" />
<EventRecordID>4881</EventRecordID>
<Correlation />
<Execution ProcessID="7204" ThreadID="0" />
<Channel>Devolutions</Channel>
<Computer><*computername*></Computer>
<Security />
</System>
<EventData>
<Data>VMWareSynchronizer</Data>
</EventData>
</Event>
All Comments (4)
Hello
Based on the behavior you’re describing, this looks very much like a permissions issue on the VMware side.
When the VMware Synchronizer runs, it will only discover folders and VMs that the credentials used for the synchronization have access to in vCenter. If entire folders (and all VMs inside them) are missing after the sync, this usually means the account does not have sufficient rights on those specific objects, or that permissions are not properly propagated to child objects.
I would recommend checking the following:
- Verify which vCenter account is used by the VMware Synchronizer.
- In vCenter, confirm that this account has at least Read / Browse access to all relevant datacenters, folders, clusters, and VMs.
- Make sure permissions are set to propagate to child objects.
- As a quick test, try running the synchronizer with a vCenter admin account to see if all folders/VMs are then created. If they are, it will confirm this is permission-related.
The Windows event you’re seeing (VMWareSynchronizer with Event ID 0) is informational and unfortunately does not provide detailed object-level errors, so missing permissions would not be explicitly logged there.
Let us know what you find after validating the vCenter permissions, and we’ll be happy to help further if needed.
Best regards,
Carl Marien
I did test that, and found that it made no difference. The account I used is a service account that has read access to everything in the vCenter. I also tried the full admin account for verification and the same thing happened. I don't think it is a permissions issue.
While digging in the logs, I found this right after the connection to vCenter is made, and before the connections are added: 2026-01-19 08:13:40.221 -06:00 [ERR] Value was either too large or too small for an Int32. - Value was either too large or too small for an Int32.
I figured this out.
When I added the authentication, I used a user that is in a group in VMWare. That only partially worked, don't know why, but it didn't give me everything. That was using my personal account that has full rights. When I added a brand new user with less rights (Read-Only) and put it in the root directly (not in a group) then everything worked. When I put that user into a group, it did not work. I assume there is some oddness wither with our setup, or with Devolutions that makes group based permissions act oddly.
Hello,
Thank you for your response!
We are glad to hear that you were able to resolve the issue. If you encounter anything else, please don't hesitate to let us know.
Best regards,
Maxim Robert