I started using Windows 7 not long after it came out. It didn’t take me long to realize that it is easier to use than Windows XP and more stable that Windows “Linux is Better” (also known as Windows Vista). I had a concern that there might be problems with the vast array of software that our customers use. That turns out not to be the case….almost…
Windows 7 is a little quirky when it comes to allowing users to access some programs. This is very evident when it comes to Client Access. You install Client Access the same way you did in Windows XP. The fun begins when you start configuring it.
If you haven’t read my other Windows 7 article about setting up the Administrator account now would be a good time to do so…go ahead…I’ll wait. If you can’t find it, look in the Networking/PC Support Category on the right.
Assuming that you’ve enabled and logged onto the Administrator account, let’s proceed. To configure Client Access, click on the Start Menu and then All Programs. Click on the IBM iSeries folder, then the Emulator folder, and then the “Start or Configure Session” icon. Configure the session and save it. For instructions on configuring the Client Access sessions, email me at firstname.lastname@example.org and I’ll send you a cheat sheet that will walk you through the steps.
If you launch Client Access (and it’s configured correctly) then you should be able to log on to the server. It’s all fun and games until you change user accounts, then you’ll get so many error messages that you’ll probably start apologizing for things you didn’t even do! (I personally confessed to the Chicago fire, but after I calmed down I realized that was a bit nutty. I have since recanted.)
You see, the saved Client Access configuration is NOT placed in the Program Files/IBM/Emulator/Private folder like it is in Windows XP. Instead it’s saved in the App Data folder of the installing user account. In this case, the Administrator’s App Data folder. Since other users would not normally have access to this folder, access error messages will appear if another user tries to use Client Access.
To solve this problem, you’ll need to move and edit a few files. I’ll talk about this on the next post titled “Windows 7 – Client Access vs Windows 7, The Sequel.”