Hello
I have an addon that has to run in a very strict SBO deployment
The machine is a Windows 2008R2 server with terminal services installed on it
The machine is configured to maximum security with numerious customizations in the GPO that restrict the user from doing basically anything aside from running SBO and our addon.
The addon load perfectly under Administrative privilages on that machine
It also loads perferectly if I load it without calling Company.Connect()
COM UI also works fine.
Whenever I try to load it regularily, I get 'Failed to Load OBserverDLL.DLL" error.
I dont see anything created in the %Temp% folder - no SM_OBS_DLL dir there
The user has full access to the %Temp% folder - I checked by creating files there manually
My question is - is there some kind of minimum level of authorization, or list of privillages a user must have in order to succesfully run an addon that is based on DI?
Thanks