Based on the UIVideoProvider example from the 2017 SDK, it seems to be relatively simple to set up a virtual device. However, when the application terminates, the VMS seems to be unable to reconnect to the virtual device without going through the steps of adding the device in the administrative interface.
I.e. prototyping, rebuilding and testing becomes quite cumbersome…
Are there specific settings needed either on the server (VMS) side or the virtual client side (UIVideoProvider analogue)?
Best regards,
When I use the UIVideoProvider sample, I can close and reopen it and “accept sessions” and the reconnection is automatic. This is how it is supposed to work. If you run the UIVideoProvider sample unaltered do you see the issue?
Which version is the XProtect VMS? Which version is the Device Pack? (Please try with the newest device pack if you aren’t already using the newest version.)
For testing purposes we are running the unmodified UIVideoProvider sample, but we are using the 2017 R1 SDK and connecting to a (production) 2014 recording server (Version 7.0d, build 871).
We will try to update the Device Pack version, and later do an update to the latest released version of the VMS.
If, with the new device pack, the issue persists I would be curious what kind of error (if any) you see in the system log in the Management Client.
We have just updated the device pack to version 9.0a and the sample now works as intended. The service can be started and stopped, and the recording server will automatically connect to it.
Thank you for your assistance. 
One idea.. Is the licensing OK? If you check with the License Information in the the Management Client, is anything expired?
I guess our updates to the question crossed paths. I am glad it is working for you now!