Find out what services need credentials

Symptom: You need to adapt to a changing environment where certain Windows services may have been enabled under the credentials of a user who no longer has access to anything.

How do you get a list of servers, service, and credentials quickly?

wmic /node:server1,server2,server3,"server-4" services get DisplayName,StartName /Format:csv

IPSEC prevents Windows Server 2003 to connect network

Problem: Network connection fails completely on Windows Small Business Server SBS 2003. Can't ping. Can't browse the Internet.
Reason: IPSEC service doesn't start. (Usually after SP2 install)

Problem: IPSEC service doesn't start because of some "only one" error on "port"
Solution:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Reserved Ports
add:
4500-4500
to the list
restart DNS.
start IPSEC.
You should have network connection.

vmware server make isos from Microsoft Volume License exe

Some things I learned:

• the default logon and password of VMware infrastructure web access is the one you use to log on to your workstation/server
• An iso you want to map to a CD in vmware server must at least be in the Virtual Machines location.
• Microsoft .exe files from Open License should be extracted before made into an iso.
• nlite is the easiest way to make a bootable iso from disk 1.
• use your favorite iso maker to make an iso of disk 2 (ashampoo is a free option)
• Internet Exporer (or Firefox) is necessary at least initially for the Remote Console
• ctrl-alt-insert sends ctrl-alt-delete
• Windows 2003 Server forgets the AMD PCNET adapter after upgrading to SP2. Copy the windows.iso file from the VMware directory to the Virtual Machines directory and mount it via CD to install VMware tools

DNS lookups failed for a specific site

I've been using Sprint Embarq CenturyLink DNS IPs for my business network (Windows Server, but it's the provider fault, not the server config):
204.117.214.10 199.2.252.10 and they failed resolving my own (personal) domain. My DNS settings of my server forward there, and I really didn't *want* to change to higher, but it seemed to do a better job choosing a higher level DNS: one of 4.2.2.1, 4.2.2.2, 4.2.2.3, 4.2.2.4, 4.2.2.5, 4.2.2.6 (or I could probably have tried OpenDNS...)

Props to EddieOnEverything for his post.