I keep iACS on a NetServer share and use UNC. We don't do an install.
We just:
1. Copy a generic .HOD file to the local PC
2. Right-click the HOD->Open with
3. Browse via UNC to acslaunch-win-32.exe on the NetServer (I assume it should work with the 64-bit version)
4. Done
HTH
-----Original Message-----
From: Steinmetz, Paul via MIDRANGE-L [mailto:midrange-l@xxxxxxxxxxxxxxxxxx]
Sent: Wednesday, March 06, 2019 6:39 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: ACS central deployment UNC file share issue with install_acs_64_allusers.js
I'm finalizing our ACS central deployment configuration using a central file server, which is not the IFS.
Using a mapped drive, the install_acs_64_allusers.js works fine.
However, a mapped drive is not an option because we can't ensure a common mapped drive letter across all users.
UNC file share is the next option, but , the install_acs_64_allusers.js has issues.
The acs_bak.zip file is not be deployed.
See error below.
Caused by: java.io.FileNotFoundException: \vmpsiacsapp01\ibmacsfull\current\acs_bak.zip (The system cannot find the path specified)
Is anyone in the group using ACS central deployment with a UNC file share?
Anyone have the knowledge on why UNC share fails, but the a mapped drive works?
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
