I have a client who has recently had their Windows 10 Pro workstations put on a windows domain. Since then, their OI session has been closing automatically. This is completely random and we are unable to duplicate the issue. This can happen if OI is processing or even when it is idle. Prior to the implementation of the domain, there were no issues. Once OI closes, there are no instances of it running in the Task Manager nor is there any event logs pertaining to OI closing. I have re-installed the workstations.

The clients is running on a Windows 2012 Server, OI9.4 and the UD version is 4.7

Appreciate any insight to this.

Jim

Start by checking the Windows Event logs to see what process is having problems.

Don Bakke

SRP Computer Solutions, Inc.

Hi Don

Thanks for the response. I did check the event logs. No errors around the time OI closed.

I just realized the domain policy maybe forcing the anti-virus to scan the OI directories.

Jim

Have you excluded from DEP

DEP is only turned on for essential Windows programs.

Anitvirus has been turned of for the OI folders.

OI is still closing randomly. :(

I found this article written by Martyn Phillips which may explain the issue I'm having. He mentions a profile log? How do I create this? we are using UD 4.7 and there were no issues prior to user being put on a domain.

https://revsoftuk.wordpress.com/2017/02/21/2311/

OpenInsight has stopped working and Will Close – This is a more serious issue because the operating system will forcibly close down OpenInsight. We have recently experienced that running OpenInsight with a profile log eradicates this issue and that OpenInsight again crashes when the log is removed. This has been an issue invoked by the driver in NETDRV being incorrect. One recent installation of the Universal Driver 4.7.2 was being run with the UD 4.6 driver set in OpenInsight. This was because the 4.7.2 driver was not amongst the options in NETDRV. We completed the Universal Driver installation correctly by running the UD Client Install and the system immediately began to run correctly. If you experience ‘any’ OpenInsight crashing or not responding messages, we would advise that the client driver is checked and make sure that the UD and the client are running as a pair – i.e. 4.7.2 server and 4.7.2 client.

Are you still having this issue? We had an issue similar to what you describe. The problem was group policy updates. When they occurred, they disconnected and then reconnected the user's drive mappings. To fix, we changed the group policy updates to not do the disconnect-reconnect thing.

Josh,

Very useful information. Thanks for posting that.

- Bob

View this thread on the Works forum...