There's no command line shut down... I have a restart system tool on my web page but after shutting down Unity nicely it will want to restart the server itself... doesn't sound like what you're looking for.
you can always use the "kill av*.*" to stop Unity in a hurry but this isn't exactly a "nice" shutdown. It wont hurt anything but any active calls at the time will simply be terminated.
if you're wanting something different I can probably just make a little script for you that will shut Unity down without restarting the server itself in about 20 minutes. Ping my Cisco email if this is something you want to look at.
What is your recommendation in this case? Keeping in mind that there is a power outage and the UPS is running low on battery. It seems to me that, using the kill command would be fine. Any cleanup Unity needs to do as it shut down? Anything like Exchange where it's best to do a clean shutdown to avoid corruption? 3.0 maybe an issue, since it uses SQL. Any other thoughts?
No, there's no problem with using KILL to knock down the AV services, it's just abrupt and hangs up on callers rather rudely. If that's not an issue it shouldn't be a big deal.
Same deal in 3.0... in both cases the actual database we're using is external to us (i.e. the Exchange directory and/or SQL in 3.0). Killing our processes isn't giong to risk corruption. Presumably you'd use "net stop"s to take down Exchange nicely and the like... that's pretty easy to do in a batch file or something.
I highly reccommend using a batch file to stop the exchange services since exchange can take a rather long time to shut down a machine. If you stop the services ahead of time using a script, the machine will shut down nicely. You might just as well include the script to shut down Unity as well in there...
------------------------------ Michael Perbix Lower Merion School District Network Hardware Technician
That's the plan. In our testing, I stopped Unity using the systray icon, 10 min went by. Issued a kill av*, waited another 10 min. Finally, did a kill "pid". The 20 min may have been due to a port lock up issue I raised on a different thread. Since Unity is depended on Exchange. It seems better to shut down Unity, then Exchange, then W2k.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.