I'm creating a utility to "restore" our servers to their natural settings. Can anyone point me to where the Login Script information / User info is kept?
It's all in NDS. You can use DSREPAIR -RC to create a backup DIB set, but you will need the help of NTS to restore the Directory. Later version of NDS give you tools to do this on your own.
You can also use the "Backup NDS before Hardware upgrade" option in the INSTALL.NLM DO some research on this one before you use it though. It will bring your server down and lock DS when you run it. But it does give you a backup of the tree that can be restored so long as the server name and internal IPX number match.
You can also look into a backup program like BackupExec or Arcserve to do this for you.
ANd if you really want to screw things up, the NDS files are stored in a hiden directory on the sys volume called _NETWARE. If you access this directory and crash your server and screw everything up, it's not my fault, don't blaim me.
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Brent SchmidtCertified nut case
Senior Network Engineer
Is there anything in the Novell NDK that would/could automate the process of posting a standard login script from a client workstation without netadmin? I'd rather not train restaurant opperations staff how to mess around in Netadmin, or continue to be on call 24/7 when it could be scripted / programed...
In some cases, even a NON-local Gold partner with a toll free number can help
I'm actually unclear on what is being asked here. When you say Restore to natural settings... what exactly are you trying to do?
Is your server down and you're tyring to get it back running? Or is it already running but you've hosed it up really bad and need to just get it back to where it's working like it is supposed to.
I am further confused by the repeated reference to login scripts. Login scripts have nothing to do with the functionality of the server. They are solely for the purpose of configuring the workstation environment to access the server according to your needs.
We have 29 Netware 4.11 Servers at Burger King / Bogangles restaurants accross a 100 mile region. I've been keeing them up and running for nearly 2 years now, and I'm looking at ways of making my job easier. The biggest challenge is when a server goes down, trying to walk a restaurant manager through diagnosing a problem is like pulling teeth. I'd like to automate the process as much as possible, so I can say insert the emergency disk in the floppy drive and tell me what it says. One problem that I keep running into is when a hard disk gets fried, and I send someone out to replace it. I'd like for the opperations staff to be able to insert a disk and let the machines do the settings for me, instead of babysitting them.
BKtechie - if the servers are connected via a WAN, you could look at something like Remote Management - Compaq have the Remote Insight Board (RIB - Lights-out) for example which is a board that allows you to connect to the server and act as if you are at the console itself.
-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
Another important question, is why are your servers crumping so often? Not running with UPS's? Getting bumped by floor cleaning equipment? Not being kept at a reasonable temperature?
The servers are in fast food restaurants. There's enough grease in a restaurant to choke any piece of electronic equiptment to death within a couple of years. They are each on a UPS. Mangement will not spend the money to set up a "clean" environment for these computers to run in, no matter how much money it will save them in the long run.
Thankfully, I've just accepted a new job where I won't be dealing with this anymore (no netadmin duties, only programming).
There are "industrial" PC's you can get, that are designed with filters and such to handle dirty environments. Check those out, if you want to leave your successor a path to sanity....
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.