×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
1. I keep iACS on my NetServer, along with a pre-configured workstation file and keyboard map. When the Windows team is setting up a new PC, they just copy the workstation file and keyboard map to the new PC. They set the PC to open the workstation file using the iACS EXE and set the workstation ID. Last step, they manually create the desktop shortcut.
2. We don't upgrade iAccess, so migration of settings isn't a concern. Our purchasing department had a large folder of macros (for terms, specs, etc). I did have to migrate those. I don't recall the specifics, but I'm pretty sure there was a tool to migrate them en masse.
-----Original Message-----
From: Steinmetz, Paul [mailto:PSteinmetz@xxxxxxxxxx]
Sent: Tuesday, May 29, 2018 9:32 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: ACS "Generated" work station IDs / iSeries Access saving/migration of custom settings
Justin,
1) Were the "shortcuts" manually created, or possibly included with an image install.
2) Any feedback for how to handle the custom iSeries Access settings?
Paul
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
