I am just about to set up MIMS Explorer on Windows terminal server.
I'm wondering if anyone has experience with this - can you tell me how you handle updates?
Since starting with MIMS Explorer, we've had to Middleware updates, 4 MSQMUI updates and 3 MSQEXP updates. These files are likley to always be in use. Also we have had many other updates such as MSQ140,600,620,700,740,901 all of which are very likley to be in use at any time. For pc implementations, I copy updates to the local drive before the MSQEXP starts.
I'm thinking I might have to distribute the files to a temporary area and have a process to copy (and register?)them in on reboot.
Has anyone else dealt with the problem?
I'd also appreciate any other "tricks" which might be required for a WTS implementation.
I'm wondering if anyone has experience with this - can you tell me how you handle updates?
Since starting with MIMS Explorer, we've had to Middleware updates, 4 MSQMUI updates and 3 MSQEXP updates. These files are likley to always be in use. Also we have had many other updates such as MSQ140,600,620,700,740,901 all of which are very likley to be in use at any time. For pc implementations, I copy updates to the local drive before the MSQEXP starts.
I'm thinking I might have to distribute the files to a temporary area and have a process to copy (and register?)them in on reboot.
Has anyone else dealt with the problem?
I'd also appreciate any other "tricks" which might be required for a WTS implementation.