It’s this kind of thing that makes upgrades so traumatic for users.
When you have your system working properly and you install a Service pack, you at least expect it to respect your settings or at least TELL you that something major has changed and here’s where to go to fix it.
I just hate the thought of what else may come back up and haunt me later on. I’m sure I’ll hear about it though.
My Story so far —
OK – so I was the good citizen and immediately installed Windows 2003 SP 1.
I restarted my machine and what happened? First message: Windows Cannot run in this configuration, Windows will use a previously used config.
Did some research. Nope – nothing really tells me what SP1 really did to my system so it’s hard to know.
“OK – I’ll restart again for good measure. ” – Restarted.
Hmm… everything seems ok. Let’s try and browse the Internet. No problem there. Maybe I should try my LOCAL server since that’s where I have my bug tracking systems, etc.
“Cannot connect to server.” – But it’s my local server. Let’s try Localhost.
Local host worked fine. What happened? Let’s see if MS Support has anything.
Hey look! Windows 2003 Service Pack isn’t even listed on the Service Pack page. More searching for stuff. Maybe I should try a remote connection.
Hmmm. Server does not exist or is not accepting connections.
This must be a firewall. Look under Network connections.
Ok. So SP1 installed Windows Firewall. Wonder if that has anything to do with anything. I mean, I was previously using ICS so I would expect that the SP1 installer would respect those settings.
Pulled up Windows Firewall. (remember there was NO notice of what SP1 actually did to my system – I just couldn’t use my system).
Windows Firewall is ON. Let’s look at the Exceptions.
Well, I can see that Remote Desktop is listed but not checked, so I’ll reset that. But what about users on my network accessing my server? SURELY, it realized by the fact that I had IIS installed that I was sharing access.
Nope. I had to manually provide access to Port 80.
A VERY little thing but something that I can imagine many techs having to go through as they install this “recommended” update to Windows 2003 server, an otherwise GREAT product.