FWIW, many larger networks do use very long leases (months). This reduces traffic and effectively gives almost everything a static IP. If you are wise, you always under allocate your IPv4 space massively with DHCP, for instance you should always have at least as much completely free space as allocated in case you need to switch out dhcp servers etc.
to save the wireless key, click on the network thing in right hand corner. edit your connection to taste. save it.
Hmmm, Microsoft recommends 16-24 days for large static environments, i've never seen lease times of months, and they only recommend that if "client computers generally remain in fixed locations and scope addresses are plentiful (at least 20 percent or more of the addresses are still available)."
Months would probably be fine for a larged fixed environment, but all the environments I support are become much less static and more mobile. Most users have laptops, smartphones, and possibly tablets, that are by no means fixed. They roam from site to site. Desktops are quickly decreasing, while laptops are quickly increasing. Plus in large sites if you are trying to limit your broadcast domains to 500 or 1000 users, they can easily push up against this limit requiring much shorter lease times.... I dont know how large of an environment your talking about.. mine is just over 20,000 ports. But I can see it varying greatly on circumstance.... the famous line of "it depends"
But I must plead ignorance as I am silohed in the network side and dont manage DHCP at all
In BAMT, I set the network key, hit apply, get connected, but when I reboot its gone, or if I bring up the network manager again its gone (even though I'm currently connected).
Love BAMT by the way, I had to do some modifications to get my cheap refurb Linksys WUSB100 wireless adapters to work, so maybe I broke something doing that. By save, if you mean "apply"... I do that, but it still seems to be sent to /null