This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Is anyone running (unsupported) windows 10 on the desktop with Maximo v7.5 or pre 7606? In java enabled browser like IE 11.
We have tested the functionality that uses java applets - workflow designer, printing, attach images, asset topology, scheduler. Any other functionality issues?
________________________________
From: MAXIMO@yahoogroups.com <MAXIMO@yahoogroups.com> on behalf of richard_hoath@yahoo.com [MAXIMO] <MAXIMO@yahoogroups.com>
Sent: Thursday, September 28, 2017 11:03 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] windows 10 desktop w/ Maximo pre 7606
Is anyone running (unsupported) windows 10 on the desktop with Maximo v7.5 or pre 7606? In java enabled browser like IE 11.
We have tested the functionality that uses java applets - workflow designer, printing, attach images, asset topology, scheduler. Any other functionality issues?
Certain US Gov Facilities orgs just got rid of using Java with Maximo. Seemed it was a nightmare to administer.
We saw issues with load balancing, of all things.
Consider two desktop environments, one Win 7 Pro, one Win 10 Pro.
Both use IE 11 -- not Edge.
Both browse to our load balanced URL.
Win 7 will allow a user to work with the session timeout at 60 minutes.
Win 10 will knock the user off after two minutes.
It took us awhile to narrow it down to this scenario, but once we did, we found out our network team had an absurdly low timeout set. They bumped it to 15 minutes, so timeouts for Win10 users were lengthened.
This had zero effect on the Win7 users. So officially this is weird but reproducible.
The Java applets in Maximo were always a tough thing to support; it got better, but it was always a bit of a pain and mixed bitness didn't help either. I like how people call it "getting rid of Java".
-C