RE: How soon is too soon? (was Re: Can iSeries Access to ACS migration be automated?)

I set up a windows .bat file to start acslaunch_win-32.exe with a generic
.hod file

start "" {path}\acslaunch_win-32.exe {path}\myconfig.hod

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Vernon Hamberg
Sent: Thursday, August 06, 2015 2:28 PM
To: Midrange Systems Technical Discussion
Subject: Re: How soon is too soon? (was Re: Can iSeries Access to ACS
migration be automated?)

Hi Gerald

I'm looking at this stuff, too - you will still need to set up the file
association on each person's machine, right? So that an HOD file calls the
ACS executable?

Now that executable can be on a network share, so you don't need to know
where it is on each machine, so far as I know.

Just putting the ACS stuff on a PC does not set up associations, as the
legacy client installation does. I guess that's partly the point, but we do
need clear ways to make this happen without running the File Associations...
tool.

I'm pretty sure these matters have been considered by IBM, and I know my
boss would want a clearly-outlined set of steps for doing this stuff.

Is there anything in the original Host-On-Demand documentation?

So I look forward to what y'all are doing!

Cheers
Vern

On 8/6/2015 1:07 PM, Gerald Magnuson wrote:

as I am trying to move to ACS, I am first attempting to.... NOT MIGRATE.

I am attempting to roll out a scenario where 95% of our users can just
have a default .hod file ( emulation settings) dropped on their
desktop, and they are done.

the other 5% who have local printer sessions, macro's, custom
keyboards will need a little bit more work.

On Thu, Aug 6, 2015 at 12:59 PM, Steinmetz, Paul
<PSteinmetz@xxxxxxxxxx>
wrote:

All good points, we have all these issues here.
I'm not suggesting to jump to W10.
I simply want to get the desktops to ACS, so we will be ready for W10.

So back to the original thread, Can iSeries Access to ACS migration
be automated?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Dan
Sent: Thursday, August 06, 2015 1:50 PM
To: Midrange Systems Technical Discussion
Subject: Re: How soon is too soon? (was Re: Can iSeries Access to ACS
migration be automated?)

...today's users are getting pretty savvy.

See, this is far from my experience in most business environments
I've been in, and is why I think in-house support resources for
Windows are going to be stretched.

Even if half of your 1000+ users are savvy enough to get through the
rough patches of a new Windows OS, that leaves 500+ that are going to
hit productivity snags. I wouldn't want to be on the receiving end
of that phone call from the CEO wondering "why the hell nothing's getting

done".

That's the kind of bleeding edge I can do without. ;-)

- 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.

--
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.

--
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.