I’ve been sitting on this post for a long time, and intended to write a more detailed description.
Here are some things you may need to consider (outside of the obvious like DHCP scopes, DNS server settings, Firewall settings & rules, etc) when changing the IP range your Windows network operates on:
- TCP/IP Printer ports on print server
- Printer/Copier IP/DNS/SMTP settings
- Exchange allowed relay ranges
- Any copy/print accounting devices attached to copiers
- Monitoring host settings. Eg. Big Brother/Hobbit – Both client and server side, if not configured to use DNS in config files
- Server iLO IP addresses
Some steps for changing domain controller IP addresses. Do these first before any other important servers:
- Change IP
- ipconfig /flushdns
- ipconfig /registerdns
- Either restart the Netlogon service, or run ‘nltest /dsregdns’
Disclaimer: This is by no means a complete list. Use these directions at your own risk.
This tool should be a part of any self-respecting SysAdmin’s toolkit. mRemote is “a full-featured, open source, multi-tab remote connections manager”.
What does this mean?, you say. It means you’ve got one neat console where you can manage all your remote connections in one place. mRemote currently supports these protocols:
I haven’t set it up fully yet, but it will be really handy to have all my web-based admin areas and SSH to Linux boxes in there too.
A side note, it uses the same rendering engine as Firefox, so some web-based admin pages may not display properly. This, however is no fault of mRemote or Firefox’s.
I recently figured out a better way to get MYOB Premier to deploy via MSI that the previous method that I posted. This method basically stops the MSI from checking if it’s been run by a bootstrapper (Setup.exe). I’ve tested this with Premier 11 and 12 and it deploys fine on XP and Vista.