Hi Staffan,
The Spokes Wrapper uses the Spokes .NET Interop (Interop.Plantronics.dll) to the Spokes COM Service API - an out of process COM service residing in our runtime engine "PlantronicsURE.exe". Your app instantiates a COM object for SessionManager that acts as a proxy object to the real SessionManager in our EXE.
However, this only works if both your application and PlantronicsURE.exe are running either both as the current interactive logged-on user (the usual case), or both as Adminstrator. Normally (for "non-SDK" case) PlantronicsURE.exe is by default set to run at log-on as interactive user.
On the other hand if you have the SDK installed PlantronicsURE.exe does not run at logon. When you run your application as Adminstrator requests the out of process COM service as Administrator it results in PlantronicsURE.exe (from the SDK folder) being launched as Administrator and it can see that COM object fine (there's no mismatch of users).
So in theory if you always run your app as current interactive user and not parented by another process that is running as Administrator you should not see this problem in final deployment regardless of whether you use full Spokes, Spokes RT or Spokes merge module. All of those 3 deployment vehicles for Spokes install PlantronicsURE.exe and requisite DLLs as well as a Run key in registry to start PlantronicsURE.exe at login.
Thanks,
Lewis.