Many VBOs appear to be unnecessarily set to a run mode of "exclusive". If any of these VBOs are used in a process or object that is exposed as an API, we will be limited to a single instance at any given time on that resource. In order for us to advance our callable process/object capabilities, we need the flexibility to run multiple instances on a single machine.
The following is a list of VBOs that have an "Exclusive" run mode:
Email - POP3/SMTP
MS Excel VBO
MS Excel VBO - Extended
MS Outlook Email VBO
MS Outlook Email VBO 6.10.4
MS Word VBO
System - Active Directory
Utility - Encryption
Utility - HTTP
Utility - JSON
Utility - Numeric Operations
Utility - Network
Utility - Screen Capture
Webservices - OAuth2.0
Webservices - REST
I think the MS VBOs could at least be reduced to "Foreground" run mode(as they might temporarily require exclusive use of those applications), but all of the others should be changed to "Background" as there is no discernable reason that multiple instances couldn't be running at the same time. If we need to make them more exclusive, that should be our choice in our local environments, but there's no need to be so restrictive as a platform default setting.