Spooky Spooky! IE7 is Coming! Spooky Spooky!
I did rant some time ago about how I thought auto updates were such a great thing (post) for small companies like mine with no update protocol in place. I still think it is except in times like these. So I finally focused on WSUS and planned everything to be ready by today. Nope, not happening.
1) The settings in group policy that allow changes to workstation update schedules and update site redirection just would not take effect. The parts I setup previously work fine, like the remote printer installation and drive mapping login script, but the workstations don't receive the changes to the auto update settings. I always have some quirky issue with group policies.
2) WSUS won't recognize any of the computers on the domain.
I haven't had enough time to research these issues but attempting to beat tomorrows deadline left me little choice but to go to each computer and manually change all the update settings to notify. As a simple fix, a friend suggested I could have blocked Microsoft's update sites altogether through the firewall, but there's some issue with the Sonicwall (site) and licenses. I always thought blocking websites was a basic part of firewalls. Unless I've missed something, it can't be done without the license. I miss the Fortinet (site) firewalls I used to use at the adoption agency.
IE7 seems quite harmless overall. I've noticed no problems and it seems to have a few nice influences from other browsers. The PC I'm testing on continues to behave normally, however, I'm certain the new interface will trouble many users initially. I'll release IE7 to staff eventually. It's just not that critical for all this fuss.




