Updates 6-13-2012 Windows Server Web aka 2008 Vista

What to do when it's looking like the second string was in on that last update. 

If you had any issues with your automatic I think it's Patch Week of 6-13-2012 and they match anything here we know the Second String was in on the testing. 

Don't forget what we had to do with NT Server 4.0. Run the updates on a non production machine just to see if it would restart correctly. 

6-13-2012 must have forgot that step. 

1. MS Advice was to enable auto updates.

2. Some updates require reboot which for the most part work. 

3. Some reboots never finish. 

Reason for 3? Not enough testing in different environments. 

Here's my sticky notes for the updates on 6-13-2012

  1. KB2685939 Update
  2. KB2709162 Update
  3. KB2656374 Update
  4. KB2656368 Update
  5. KB890830 Update
  6. KB2686827 Update
  7. KB2686833 Update
  8. KB2699988 Update

Between 1 and 8 one of these updates didn't complete the cycle or none of them were designed to run the restart cycle or one of them was a shut down command only or one was not designed to run with the others. 

All questions and no answers this morning of 6-13-2012 because we had to address a start up issue in one of our IIS servers. 

This server functions as a normal off the shelf system. 

If you have had any restart issues and maybe a network configuration issue during these updates I'd like to hear your configuration setup.

Use the old fashioned Tech Service Desk ticket if you're still having an issue. 

Windows Server Web aka 2008 Vista version What to do when it's looking like the second string was in on that last update. If you had any issues with your automatic I think it's Patch Week of 6-13-2012 and they match anything here we know the Second String was in on the testing.