Discussion Locked

ACU allows a painless upgrade to the latest Novell client

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

8 replies

by tsvehla

We have been trying to use the ACU utility and it works great for updating workstations that have a fairly new version of client32(3.0 or higher). If the client32 is older (2.2 or older) it goes only so far and locks up the workstation. So far Novell Tech support has been of little assistance. Seems to me there are a few bugs to be resolved. Anyone had any good experiences or know of any good troubleshooting methods

by piglet4312

I used it quite a bit on our network and it works absolutely great. Had a few little bugs at first with some .ini files, but works like a champ now.

by gillett

Hello:
I am testing an automated upgraded process to hopefully implement in the next month.

1. Workstation is Win95 (fully patched) using Client 2.2 and upgrading to Client 3.3 and the server is NetWare 3.12 (fully patched)(we are migrating to NetWare 5.1 fully patched).

2. Client 2.2 "Run Scripts" option is not checked, and will not be set on the existing client. Problem: Can't run login scripts. (Thank you supervisor!)

3. Due to Client 3.3 workstation upgrade lockup issues, Iwill have to do an upgrade from Client 2.2 to Client 3.1, then Client 3.1 to Client 3.3.

4. Users will double-click on a batch job - batch1. Batch1 will copy a .PIF file to local workstation's Startup - Second.pif, then run the ACU of Client 2.2 to Client 3.1.

5. After workstation reboot and user logging back on, the .PIF file calls the batch job, batch3. Batch3 deletes the .PIF file from the local workstation startup (for house-cleaning), then runs the ACU of Client 3.1 to Client 3.3which has ACU.INI tweeks and using Unattend.txt.

The problem with lockups usually occurred during a simultaneous ACU install on multiple workstations of Client 2.2 to Client 3.3. The problem lied with the Winsock install. For some reason, doing a Client 2.2 to Client 3.1, then Client 3.1 to Client 3.3 upgrade did not encounter that issue. Weird.

One more note: This will not work with Profiles on the workstation, so the process needed to be modified, and will require a support staff to do the upgrade. My modification dumps the .PIF to a specific user's Profile Start menu, i.e. support staff user account.

Another note: There are upgrades for ACU and NCIMAN at Novell's website.

Disclaimer: I am NOT a Novell rep.

Phil G.
UWEX - IS LAN Admin
Madison, WI

by rmtracy

I tried this on a test server and client.
The client is running Windows 95 and client32
version 3.2.
The login script did not run?
Is there something beyond the line with the
path to the client?

by tsvehla

The figure in the example was cut off. The login script is pointing to the acu.exe file to execute.

by rmtracy

I am on a Netware 5.0 server and the "IF PLATFORM=WIN95" statement should be "IF PLATFORM=W95". This fixed the problem and the script ran successfully.

by nitemage

ACU doesn't seem to run properly on ThinkPad 600's (because of MWAVE.VXD. perhaps). I had to write a batch file to determine if a machine had mwve.vxd present, and if so; flag them in an output file and disable ACU.

by gillett

Sounds to me like a typical shutdown problem.
Yeah, "Stinkpads" seemed to be a world all their own, too.

This discussion is closed to new replies.