This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Attachment (Use case): Here is an example of instructions I had to develop and our network and PC folk have to go through for each PC they configure. We have several though PC's in the organization and this is a lengthy and unjustifiable process. It messy. Please see the attached document.
Here is an example of instructions I had to develop and our network and PC folk have to go through for each PC they configure. We have several though PC's in the organization and this is a lengthy and unjustifiable process.
It messy.
Please see the attached document.
The RFE states the necessity to uninstall/reinstall ACS to change configured options. Though some may find that a convenient way to modify what features of ACS are currently available for a single user, that may not be the best way for lots of users...neither is it the required way. There are a variety of ways to customize the product. For example, see section 9.5 Customized Packages in the GettingStarted document.
The RFE also requested "An administration type function would be appreciated where the setup can be stored at a central point for each device." Such a function has already been provided and is documented here:
https://www.ibm.com/developerworks/ibmi/library/i-ibmi-access-client-solutions-customization-trs/index.html
The following article has already been referenced as a useful resource (including again here):
If there are additional suggestions of what is needed, please be more specific.
Guys
I know there are a huge amount of variables here, but ACS is infinitely more flexible to roll out than it's predecessors.
Most times I find that if i deploy from a Network Share, which then Sync's that version the end user it works a treat. I use a different network share for each class of user, the images are preconfigured and it works just fine if that network share is not always there.
If you are handy with GPO's then you can even do this silently accross your estate for both install and update, every time the use logs into the domain.
Forgive me if I'm telling you what you already know. But there are some great resources online that give you samples of deploying in a number of scenarios, for example, this FAQ sheet.
https://www.ibm.com/developerworks/ibmi/library/i-ibmi-access-client-solutions-2/index.html
If there is something specific that is not supported or not reliable about the way ACS is rolling out for you, then please get that level of detail into the RFE.
I am not fully sure I follow what is requested here.
I have 1,000's of users with iAccess for Windows that we have to roll out ACS to.
They fit into 1 of 3 types. 5250 only, 5250 with database, and full admins.
Our environment has the desktops locked down. So once installed, the config file cannot be edited.
(So they can't go in a grant themselves for functionality than approved for)
Each user will have to request and justify which version they want.
We package up the application into 3 different install packages.
They have disabled the Check for updates function.
We have to certify every version/upgrade that we package before it can be installed on a desktop, regardless of with of the 3 packages.
I do however agree that the support and developer folks need to be at customer sites to understand the problems, requirements and needs of the customer. Seems out of touch with reality in the real world. How we deploy things is much different that how they design it. And the config/deployment methods they use don't match what we need.
I need a way to grab a version, certify it and configure the app to check one of MY systems for updates, Not IBM. I can then stand a chance of pushing updates to user desktops as we provide them at OUR location/server once certified. Both Config files and the updated .JAR file.
Maybe that is what you are requesting and saying. Not sure.
I have several hundred users at my location and dealing with ACS is no different than the older Client Access was. So, I'm not totally sure what this customer would be dealing with. I think someone from support should be back with the customer and find out what their real needs are.
Jason