Dan,
We ran into this issue years back.
Opened a PMR with IBM.
Long story short, you can no longer do network installs or check service level with iSeries Access.
Stopped working after XP.
IBM's answer.
Copy the entire Windows folder for iSeries Access to the Desktop.
Then run the iSeries Access setup.exe.
We just did about 150, no issues.
Used remote desktop.
Usually requires a reboot of the PC.
Enabled SSL and SSO for these PC at the same time.
A few other minor caveats that there are tech docs for.
We are on V7R1, latest cum, iSeries Access SL 62603.
Does work on Windows10, just not supported.
We will be migrating to the new iSeries Access Client at some future point.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Friday, July 21, 2017 12:04 PM
To: Midrange Systems Technical Discussion
Subject: Silent service pack install for Client Access for Windows
Our environment: v7r1 i/OS, Windows 7 Enterprise, i Access for Windows v7r1 (currently at SI53809), no one has admin privileges on their Windows client (so, installing software requires admin privileges). I did RTFM including a redbook "iSeries Access for Windows V5R2 Hot Topics" from 13 years ago, and Google was not my friend.
We want to *silently* apply the latest service pack (SI56695) to 200+ clients. Apparently, our infrastructure peeps can't manage to deploy this (I don't know the details, as a lot of things around here are on a need-to-know basis, as in "you don't need to know the details, but I know this won't work"). For this reason, replacing the WIndows client with the Java client (iACS) is out of the question.
I have a vague idea that an "Administration System" assigned in the i Access for Windows Properties tab by the same name can be used as the source for a service pack install, and then the Service tab allows the setting of options including silent installation. (I have access only to our dev box, but I was unable to assign it to be our administration system, with error "The specified system is not an administration system.") Does anyone have experience with how "silent" this actually is? Our users power down their Windows client every night so, ideally, the service pack would download on day 1 and install when the client is powered up on day 2. The users normally start their Client Access session almost as soon as Windows allows them to.
The big problem as I see it is, if all of our Client Access installations are like mine, neither the Administration System is defined nor is the silent installation option selected in the i Access for Windows Properties. Unless I'm unaware of some magic button that the i server has available to set those on the clients, I'm probably in the same hole as having the infrastructure peeps being unable to deploy the service pack.
Yay/nay?
- Dan
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
