Using microvellum remotely has been an issue. 

Issues doing it the wrong way:

1) Internet Lag ( slow connection to your work device )

2) using RDP without proper protection on both ends ( remote computer and office machine ). You open up your computer network to hacking. Insurance hates this and is considered worst practice.

3) The mouse has a severe delay ( this is a known autocad issue and autocad has no intention on fixing this, they have provided a few adjustments ), they have provided a few workarounds by fixing the mouse issue but you still have a lag or slowness problem. 

What i have found: I have spent since August of 2024 trying to make this as fast as i can for engineers, And we accomplished it and have successfully rolled it out in live environment. I can share a demo environment with you so you can see the experience that is both secure and as if your using it on your local computer. 

1) ( Security Hat on here ) Owners you really need to own the equipment that your remote employee is using for both a cyber security perspective and a liability situation. your insurance will not pay for your hack if things are not setup correctly. 

a) have a follow me firewall on your employees work computer at home that securely ties into your office computer network. from here you can use RDP that insurance will sign off on but you MUST have proper protocols in place. 

b) with the correct follow me firewall software, you can access a sql database remotely via a mapped drive. We have done this with other clients. the engineer sees absolutely no difference in work experience except when they first open the drawing. Once the drawing is open, everything is as normal. Microsoft doesn't recommend doing it this way, But, its been being down now with no issues using a mapped drive and using full SQL server or SQL Express. New technology has paved the way for this to work. 

2) Using a cloud based server way / Azure 

a) the correct virtual desktop and zone must be selected. Its all based on region and machine availability. Not every zone has the correct virtual machine. certain virtual machines in Azure are shared resources and others are dedicated. you want to use the dedicated resources one not the shared ones. 

b) Azure has to be configured correctly. Once setup correctly you can have engineers from all over the world tie into a single database and it will be fast and effective OR you can tie multiple plants together that use microvellum to a database in the cloud that the different engineers can all use. 

Let me know how we can help..