Scripted removal of the Netware client

We're well versed in moving from a Microsoft-centric environment to one based on NetWare and eDirectory.  Most of us would be unlikely to have a script laying around to do that.

If you really want help with this Question, it should be asked in a Windows TA.  

I know I could do it with ZENworks, but I have no idea if SMS has the capability.  It could probably be done with one of the scripting tools available to Windows-centric environments, like VBS or Windows Script Host or something.  If you really know what you're doing, you could probably write a .BAT file to do it.

There should be uninstalls available in add/remove programs for all of the Novell client pieces.  Maybe looking at those uninstall scripts could give them an idea how to do it centrally.

Thanks.  I was afraid of that, particularly after reading information on Novell's site.

I asked the question in the Windows topic area, too.

THANKS!

Hmm, that is of course unless you may be uninstalling the client to replace it with the agent, then maybe there'd be a couple of TID's laying around to assist, :-)

Unfortunately, in this case, it is an issue of management wanting to centralize with Active Directory, but allow for communications to Linux (Samba), Novell, and Windows 2003.  So, there will still be 3 flavors of systems...they just want to get back to the basic windows client.

Honestly I am surprised that eDirectory (DirXML or whatever it is named) or MIIS is not in this.

The one that you listed touches on an unattended install.  What I am looking for is an unattended uninstall.  Do you have a TID for that?  I have already looked at a few of the other TIDs (10016356, 10024640, and 2948079).  None of them touch on a clean unattended uninstall, unfortunately.

Expanding on the first link of duncs (which kinda expands on what I said about using the uninstall from add/remove programs) if you have another scripting language that will answer prompts that can't be made into a silent uninstall, like WinBatch.  The compiler version will let you make an app and distribute it to all your PC's royalty-free.  Once the run-times are on the PC, you could even execute it from the network.

That may be something that we have to try out.  I will let you know how it goes.

WinBatch +Compiler isn't much more expensive than one copy of Microsoft Office Professional, and it has all the bells and whistles, in case you have a need for them, including all sorts of network API's and stuff (it's almost a programming language, it's so robust) and you can record a "keystroke" script including any mouse clicks that might be needed, if you don't want to write it all from scratch.

I wasn't aware of AutoIt3 before, billmercer.  I will have to check it out.  Maybe it will do all that, too, for free.  That'd be too cool...

ShineOn, I would not say AutoIt3 is equivalent to WinBatch by any means, it doesn't have an IDE with debugging and fancy editing features, and it doesn't have all the network-specific stuff. It's basically just an interpreter and compiler. But it's perfect for automating dialogs, windows, and stuff like that, and the fact that it's freeware means I can install it on every workstation.
WinBatch has been on my wish list for a while, BTW. I just can't justify the cost. But I'm also working for a small nonprofit, so I have trouble justifying $20 cables...

Thanks a bunch for the information.  There is a lot to go on and a lot to bring into the lab for testing.  Sorry for the faux pas of asking a Windows question in a Novell group.