Last Known Good Configuration Issue Power Outage
Of all the thing not to have and that's a good working UPS for your server. When you have duct tape around that box and need it for work the next time your IT admin tells you "Buy a Backup Power Supply" he or she isn't kidding around. The customer that doesn't buy one will end up paying for one in the long run.
One of the many issues SBS 2003 had and has depending on if you still use one. Is it's config file seems to never update if selected components have been corrupted over the years. Sure you can regedit until the cows come home but when that system shuts off from a power failure you're not talking a simple "Power State Last State".
I have this Dell that actually is an Opti type of motherboard that never returns to state after a power outage. It always has to be manually turned on and then the terminal services and NICs have to be configured.
If you run into the issue of the SBS2003 enabling disabled NICs and Terminal server configurations being lost then this might help you.
I'll post up the notes I have once I find them.
- When running last known good configuration.
- Adds disabled network card.
- Adds Remote as a Terminal server that has been disabled.
- Need to update the Last Good Configuration Registry.
- Look up Applying updates to last known good configuration.
- This must be update from a good reboot.
- If the system never reboots correctly it will not update.