Client32 Removal

You might try executing the UNC32.exe program from a login script.  I dod not know if there is a silent install parameter.  You could test this on an individual workstation with a #UNC32.exe statement in the individual's script.  The UNC32.exe could be on a server, perhaps in the Public directory or a directory setup for that purpose.  Obviously after it runs and reboots, you will have no access to the Netware servers.  This applies to WIN9X, not the NT/2000 client.

Yes, but all the clients would have to be the same version, and I'm not sure they are.

Thanks
Steven

No - you can run UNC32.EXE on different versions of the NetWare client (such as 3.3x) but I don't know about different families (such as 2.51 and 3.32).

You could also put the latest client on the server for an ACU installation and get everyone up to the latest version then run the UNC32 if you think different versions may cause a problem.

Of course, not to be a smart a** or anything, but if you are migrating away from Novell, you got other problems on your hands besides client removal ;)

defore, are you still migrating or have you found a solution to the problem either by yourself or by the suggestions made? (or perhaps realised you shouldn't migrate at all?)

Regards,

CyberWizard

Sorry for not coming back to this question. Ended up doing it at every machine. (What a pain in the @$$)

Thanks for your help

Dear expert(s),

A request has been made to close this Q in CS:
https://www.experts-exchange.com/questions/20424017/del-question.html

Without a response in 72 hrs, a moderator will finalize this question by:

 - Saving this Q as a PAQ and refunding the points to the questionner

When you agree or disagree, please add a comment here.

Thank you.

modulo

Community Support Moderator
Experts Exchange