iMIS desktop on Windows 2008 server (32 bit) with Terminal services

We recently migrated one of our client from iMIS 10.6 to iMIS 15.1.2. We installed the iMIS desktop on a Windows 2008 Server, so that we don't have to install it on each users Desktop machine and instead users can access it using terminal services.

From what I understand from the install documentatn, iMIS desktop should have no problem on Windows 2008 server (32 bit). But what we see is that when I launch iMIS desktop and then close in on this Windows 2008 server, it doesn't close it cleanly. I can see an instance of Omnis7.exe in task manager. So when I launch the desktop next time, the application hangs.
I have to kill the instance of Omnis7.exe manually or Log off and Log in to run the iMIS desktop application.

After numerous trials on Windows 2008 server, we identified the problem with Windows 2008 Server with Terminal services.
So if we have just Windows 2008 Server and install iMIS 15 desktop on it, it works great.

As soon as we turn on terminal services, iMIS 15 desktop starts hanging. Any body else aware of this issue ??
 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Supported operating systems

From the Contents tab on docs.imis.com, iMIS Installation->Before You Begin->System Requirements.

Tthe supported operating system for iMIS Desktop version 15.1.2 as: 

Windows Vista and XP Home/Professional SP2 with critical updates, plus above, but on 32-bit operating systems only

www.imiscommunity.com lists the same:  http://www.imiscommunity.com/imis_15_1_2_system_requirements

 

I am running on a 32 Bit

I am running on a 32 Bit Windows 2008 server

Are you calling the library

Are you calling the library file or the .exe file from the desktop? You should be calling the library file.

I was able to resolve this

I was able to resolve this issue. We need to make sure that the default windows printer for each individual windows profile is NOT set to a virtual printer such as the Adobe Acrobat Distiller, Microsoft Office Image Writer, etc. as iMIS desktop tries to retain the printer settings.

 

You should run a job at

You should run a job at night to check for those and to clear it out. This is what we did here.