11 replies
by tbradley
1. Expand the client to a directory on your file server, for example f:\client
2. Ensure all users you want to upgrade have read and file scan to this directory.
3. Create a login script for the users you
want to upgrade with the following line
#//fileservername/sys/client/acu.exe
This will give you the typical install, with all current network settings being retained.
This is the bare bones simple explanation. To get more details on the advanced features, you can go to novell's website, www.novell.com, go to knowledgebase, and do a search on ACU.
by malzra
#1 has the right answer.
Use the ACU function of the client install.
Test it on your workstation, roll it out on a small number of users first, rather than everyone in your network, and have a copy of the client burnt onto CD for everyone in Tech support. If the ACU fails (expect that it will on .5-1% of machines). You will need to uninstall the old client, and then reinstall the new one. You probablly will lose connectivity to the network during that process.
Also, I would advise letting the users decide if it's a good day for them to have work interrupted or not. There is a switch which chooses to either force the upgrade to run, or skip past it, in which case, they will be prompted to install until they do install it.
Documentation at support.novell.com is very complete, and very good. You can also check out Novell's newsgroups, which you can find from links at support.novell.com.
Kev.
by malzra
by mohan
U need to use the ACU method to do the same.There are various switches u can use to install the client including /RB for rollback to the old client if the install fails or /SL: to log the status of the upgrade.Please read the January 2000 issue of Novell App notes which has a very good article on the ACU upgrade process.
If u are using Mainframe applications there is an issue of some keys in the Numeric keypad not working with this client which is related to the Remote Management agent in the client.Do not install it if u dont need it.Or download the SP for Zen3 for a patch for this problem
Mohan
by malzra
by bart777
A COUPLE OF THINGS WE FOUND.....
Just went thru this upgrade process on about 600pc's and laaptops here. Many laptops and some of out Compaq desktops seem to have a problem with the 3.3 client.
Some will start to display an error on bootup saying that the comctl32.dll has caused an error in explorer. You may need to reinstall IE to fix this if a client reinstall does not.
Also if you are using the Naldesk feature you will get several odd errors that seem to make no sense. Usually this occurs when another person has logged into the machine before the current user. The NalCache needs to be deleted. We had to build a script that removes it when the users bootup.
And the last Gotcha that we found was that the auto install seemsto blow up if you have the 3.02 client. (2.5 and 3.2 are fine.)
Best of Luck,
Hope you don't have the same issues we had.
by malzra
by jimbb
Lots of answers, but nothing about the NCIMAN... It's simple, in NCIMAN.EXE switch all the things on or off, or configure them as if you were configuring a client, according to your needs/requirements. File/Save as to "unattend.txt", and that should be in the same directory as the setup.exe you want to launch.
Next, either via a shortcut, loginscript or NAL object, run \\server\volume\directory\setup.exe /u. You can add /ACU as well, to automatically upgrade whatever there already is, without touching the parameters - except the ones you put in the "unattend.txt" file.
If you do it via a login script, don't forget to use @ or # to indicate an external command.
My experience is that about 10% of the machines has problems rebooting while the install ran fine (won't have no problems after a "manual" reboot), and a few percent mess up during the remove of the MS client, so prepare to have a Win9x CD and a client CD at hand to extinguish those little fires.
Jim
by malzra
by malzra
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending