none
Some Servers restart unexpectedly

    Question

  • Hi All

    From time to time we experience some servers (2003 and 2008) reboot unexpectedly during the week and business hours while updates are set to install on a Saturday at 3am. Why would these servers reboot- does anyone know or had this issue before which can help me to fix my problem please?

    Looking in the eventlog i just find event ID 22 and 18 which says that the following updates will be installed after which the server will restart but it is not configured to restart during the day via GPO. How do i go about finding the cause of this?

    Thanks in advance

    Thursday, August 22, 2013 8:18 AM

Answers

  • If i understand the log correct, it rebooted because of the option "No auto-restart with logged on users for scheduled automatic updates installations" because no one was logged onto the server at the time of the installation.

    2 Questions then

    1. Why did updates install today (Thursday evening) when the GPO is set to Auto Download and install on a Saturday 3am?

    2. How do i install the updates on my servers but DO NOT let the server auto restart after the updates have installed?

    2013-08-22 20:21:51:023  820 d44 AU Forced install timer expired for deadline install

    2013-08-22 20:21:58:308  820 d44 AU Enforcing reboot for already installed deadline expired update

    Actually it INSTALLED and REBOOTED because a DEADLINE was set on the update approval.

    While it's true that a server will reboot after installation if no user is logged on, it is not true that a server will randomly initiate an update installation. Only three things can cause an update installation to launch:

    1. A scheduled installation event, which always starts at the TOP of the hour (e.g. HH:00:00.000)
    2. A human being
    3. An expired approval deadline

    Furthermore, if a deadline expires, not even a logged on user can defer the reboot!

    In this case the issue was not that there was no user logged on when the installation finished, but rather than the installation started at all --- apparently around 8:15pm.

    The answer to question #2 is that you don't use AUOption '4'. You use AUOption '3', and launch the update installation when you're in a position to allow the server to reboot immediately.

    You also never use approval deadlines on updates for a Server operating system. :-)


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, August 23, 2013 11:18 PM
    Moderator

All replies

  • Hi, can you please collect and post your Windows Update logs after one of these reboots happen? You can paste them the log in this thread (please do NOT use "code blocks" as they are harder to read) or you can use an external service like www.pastebin.com or http://gist.github.com and post a link here.

    Thank you!


    Thursday, August 22, 2013 3:53 PM
    Moderator
  • I apprecaite your time Ben. See log below. The reboot happened at 20:23

    ...and as I type this post more servers are randomly rebooting. This is very confusing. We DEFINITELY do NOT set a deadline when approving updates

    I would be gratefull for help


    2013-08-22 20:21:50:992 3204 24c Handler   : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
    2013-08-22 20:21:50:992 3204 24c Handler :::::::::
    2013-08-22 20:21:50:992 3204 24c Handler ::  END  ::  Handler: Command Line Install
    2013-08-22 20:21:50:992 3204 24c Handler :::::::::::::
    2013-08-22 20:21:51:007  820 d14 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {5F46C0B9-C57C-484E-B6E5-80DDED34BFA3}, succeeded]
    2013-08-22 20:21:51:007  820 bac Report REPORT EVENT: {FE5067E5-813B-4B4A-B5D9-1DAA4CB88F8A} 2013-08-22 20:21:51:007+0200 1 183 101 {5F46C0B9-C57C-484E-B6E5-80DDED34BFA3} 100 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2 for x64-based Systems (KB2468871)
    2013-08-22 20:21:51:007  820 bac Report CWERReporter finishing event handling. (00000000)
    2013-08-22 20:21:51:007  820 bac Agent *********
    2013-08-22 20:21:51:007  820 d14 AU Install call completed.
    2013-08-22 20:21:51:007  820 bac Agent **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
    2013-08-22 20:21:51:007  820 d14 AU   # WARNING: Install call completed, reboot required = No, error = 0x00000000
    2013-08-22 20:21:51:007  820 bac Agent *************
    2013-08-22 20:21:51:007  820 d14 AU #########
    2013-08-22 20:21:51:007  820 d14 AU ##  END  ##  AU: Installing updates [CallId = {E9A7E65C-2CF0-4070-BABC-CD59FCE5CE2E}]
    2013-08-22 20:21:51:007  820 d14 AU #############
    2013-08-22 20:21:51:007  820 d14 AU Install complete for all calls, reboot NOT needed
    2013-08-22 20:21:51:023  820 d14 AU Successfully wrote event for AU health state:0
    2013-08-22 20:21:51:023  820 d14 AU AU setting pending client directive to 'Reboot Warning'
    2013-08-22 20:21:51:023  820 d14 AU AU scheduling auto reboot check since no user is logged on and reboot is required.
    2013-08-22 20:21:51:023  820 d14 AU Successfully wrote event for AU health state:0
    2013-08-22 20:21:51:023  820 d14 AU Triggering Offline detection (non-interactive)
    2013-08-22 20:21:51:023  820 d44 AU Forced install timer expired for deadline install
    2013-08-22 20:21:51:023  820 d44 AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2013-08-22 20:21:51:023  820 d44 AU Enforcing reboot for already installed deadline expired update
    2013-08-22 20:21:51:023  820 d44 AU Found a pending reboot, launching reboot UI
    2013-08-22 20:21:51:023  820 d44 AU Successfully wrote event for AU health state:0
    2013-08-22 20:21:51:023  820 d44 AU #############
    2013-08-22 20:21:51:023  820 d44 AU ## START ##  AU: Search for updates
    2013-08-22 20:21:51:023  820 d44 AU #########
    2013-08-22 20:21:51:023  820 d44 AU <<## SUBMITTED ## AU: Search for updates [CallId = {A5273900-7083-464C-A665-45C1A6B6066D}]
    2013-08-22 20:21:51:023  820 e18 Agent *************
    2013-08-22 20:21:51:023  820 e18 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-08-22 20:21:51:023  820 e18 Agent *********
    2013-08-22 20:21:51:023  820 e18 Agent   * Online = No; Ignore download priority = No
    2013-08-22 20:21:51:023  820 e18 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2013-08-22 20:21:51:023  820 e18 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-08-22 20:21:51:023  820 e18 Agent   * Search Scope = {Machine}
    2013-08-22 20:21:58:292  820 e18 Agent   * Added update {53E7AC24-9A86-4D30-9C12-5B3110176B0E}.100 to search result
    2013-08-22 20:21:58:292  820 e18 Agent   * Found 1 updates and 69 categories in search; evaluated appl. rules of 587 out of 1078 deployed entities
    2013-08-22 20:21:58:292  820 e18 Agent *********
    2013-08-22 20:21:58:292  820 e18 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-08-22 20:21:58:292  820 e18 Agent *************
    2013-08-22 20:21:58:308  820 e18 Report CWERReporter finishing event handling. (00000000)
    2013-08-22 20:21:58:308  820 d14 AU >>##  RESUMED  ## AU: Search for updates [CallId = {A5273900-7083-464C-A665-45C1A6B6066D}]
    2013-08-22 20:21:58:308  820 d14 AU   # 1 updates detected
    2013-08-22 20:21:58:308  820 d14 AU Setting next AU forced reboot timeout to 2012-10-13 22:00:10
    2013-08-22 20:21:58:308  820 d14 AU #########
    2013-08-22 20:21:58:308  820 d14 AU ##  END  ##  AU: Search for updates [CallId = {A5273900-7083-464C-A665-45C1A6B6066D}]
    2013-08-22 20:21:58:308  820 d14 AU #############
    2013-08-22 20:21:58:308  820 d14 AU Featured notifications is disabled.
    2013-08-22 20:21:58:308  820 d14 AU Successfully wrote event for AU health state:0
    2013-08-22 20:21:58:308  820 d14 AU Successfully wrote event for AU health state:0
    2013-08-22 20:21:58:308  820 d44 AU Forced install timer expired for deadline install
    2013-08-22 20:21:58:308  820 d44 AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2013-08-22 20:21:58:308  820 d44 AU Enforcing reboot for already installed deadline expired update
    2013-08-22 20:21:58:308  820 d44 AU Found a pending reboot, launching reboot UI
    2013-08-22 20:21:58:308  820 d44 AU Successfully wrote event for AU health state:0
    2013-08-22 20:22:03:316  820 e18 Report CWERReporter finishing event handling. (00000000)
    2013-08-22 20:23:51:034  820 d44 AU WARNING: Initiating reboot since no user logged on
    2013-08-22 20:23:51:034  820 d44 AU AU invoking RebootSystem (OnRebootNow)
    2013-08-22 20:23:51:065  820 d44 Misc WARNING: SUS Client is rebooting system.
    2013-08-22 20:23:51:065  820 d44 AU AU invoking RebootSystem (OnRebootRetry)
    2013-08-22 20:23:52:562  820 d44 Shutdwn user declined update at shutdown
    2013-08-22 20:23:52:578  820 d44 AU Successfully wrote event for AU health state:0
    2013-08-22 20:23:52:578  820 d44 AU AU initiates service shutdown
    2013-08-22 20:23:52:578  820 d44 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2013-08-22 20:23:52:578  820 d44 Report CWERReporter finishing event handling. (00000000)
    2013-08-22 20:23:52:703  820 d44 Service *********
    2013-08-22 20:23:52:703  820 d44 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2013-08-22 20:23:52:703  820 d44 Service *************
    2013-08-22 20:27:24:195  880 c74 Misc ===========  Logging initialized (build: 7.6.7600.256, tz: +0200)  ===========
    2013-08-22 20:27:24:195  880 c74 Misc   = Process: C:\Windows\system32\svchost.exe
    2013-08-22 20:27:24:195  880 c74 Misc   = Module: c:\windows\system32\wuaueng.dll
    2013-08-22 20:27:24:195  880 c74 Service *************
    2013-08-22 20:27:24:195  880 c74 Service ** START **  Service: Service startup
    2013-08-22 20:27:24:304  880 c74 Service *********
    2013-08-22 20:27:24:492  880 c74 Agent   * WU client version 7.6.7600.256
    2013-08-22 20:27:24:492  880 c74 Agent   * Base directory: C:\Windows\SoftwareDistribution
    2013-08-22 20:27:24:492  880 c74 Agent   * Access type: No proxy
    2013-08-22 20:27:24:492  880 c74 Agent   * Network state: Connected
    2013-08-22 20:28:11:618  880 c74 Report CWERReporter::Init succeeded
    2013-08-22 20:28:11:618  880 c74 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2013-08-22 20:28:11:618  880 c74 Agent ***********  Agent: Initializing global settings cache  ***********
    2013-08-22 20:28:11:618  880 c74 Agent   * WSUS server: http://OurWsusServerName
    2013-08-22 20:28:11:618  880 c74 Agent   * WSUS status server: http://OurWsusServerName
    2013-08-22 20:28:11:618  880 c74 Agent   * Target group: TargetedGroupInWsusWithComputers
    2013-08-22 20:28:11:618  880 c74 Agent   * Windows Update access disabled: No
    2013-08-22 20:28:11:618  880 c74 DnldMgr Download manager restoring 0 downloads
    2013-08-22 20:28:11:649  880 c74 AU ###########  AU: Initializing Automatic Updates  ###########
    2013-08-22 20:28:11:649  880 c74 AU   # WSUS server: http://OurWsusServerName
    2013-08-22 20:28:11:649  880 c74 AU   # Detection frequency: 22
    2013-08-22 20:28:11:649  880 c74 AU   # Target group: TargetedGroupInWsusWithComputers
    2013-08-22 20:28:11:649  880 c74 AU   # Approval type: Pre-install notify (Policy)
    2013-08-22 20:28:11:649  880 c74 AU   # Auto-install minor updates: Yes (Policy)
    2013-08-22 20:28:11:649  880 c74 AU   # Will interact with non-admins (Non-admins are elevated (Policy))
    2013-08-22 20:28:11:649  880 c74 AU   # Will display featured software notifications (Policy)
    2013-08-22 20:28:11:868  880 c74 Report ***********  Report: Initializing static reporting data  ***********
    2013-08-22 20:28:11:868  880 c74 Report   * OS Version = 6.1.7601.1.0.196880
    2013-08-22 20:28:11:868  880 c74 Report   * OS Product Type = 0x00000007
    2013-08-22 20:28:11:883  880 c74 Report   * Computer Brand = VMware, Inc.
    2013-08-22 20:28:11:883  880 c74 Report   * Computer Model = VMware Virtual Platform
    2013-08-22 20:28:11:883  880 c74 Report   * Bios Revision = 6.00
    2013-08-22 20:28:11:883  880 c74 Report   * Bios Name = PhoenixBIOS 4.0 Release 6.0    
    2013-08-22 20:28:11:883  880 c74 Report   * Bios Release Date = 2012-06-22T00:00:00
    2013-08-22 20:28:11:883  880 c74 Report   * Locale ID = 7177
    2013-08-22 20:28:12:164  880 c74 AU Successfully wrote event for AU health state:0
    2013-08-22 20:28:12:164  880 c74 AU Initializing featured updates
    2013-08-22 20:28:12:164  880 c74 AU Found 0 cached featured updates
    2013-08-22 20:28:12:164  880 c74 AU Successfully wrote event for AU health state:0
    2013-08-22 20:28:12:164  880 c74 AU Obtained Post reboot hr from Agent:8024000c
    2013-08-22 20:28:12:164  880 c74 AU AU setting pending client directive to 'Forced Reboot'
    2013-08-22 20:28:12:164  880 c74 AU Successfully wrote event for AU health state:0
    2013-08-22 20:28:12:164  880 c74 AU Triggering Offline detection (non-interactive)
    2013-08-22 20:28:12:164  880 c74 AU Successfully wrote event for AU health state:0
    2013-08-22 20:28:12:164  880 c74 AU AU finished delayed initialization
    2013-08-22 20:28:12:164  880 c74 AU #############
    2013-08-22 20:28:12:164  880 c74 AU ## START ##  AU: Search for updates
    2013-08-22 20:28:12:164  880 c74 AU #########
    2013-08-22 20:28:12:242  880 c74 AU <<## SUBMITTED ## AU: Search for updates [CallId = {B6E4735F-AA5B-4184-84C0-EB49EDE6C20B}]
    2013-08-22 20:28:15:565  880 f18 Report Uploading 7 events using cached cookie, reporting URL = http://OurWsusServerName/ReportingWebService/ReportingWebService.asmx
    2013-08-22 20:28:18:654  880 f18 Report Reporter successfully uploaded 7 events.
    2013-08-22 20:28:18:654  880 f18 Report REPORT EVENT: {F6F3B0C6-7F17-4EF4-8858-21707BE63392} 2013-08-22 20:28:12:164+0200 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
    2013-08-22 20:28:18:778  880 f18 Report CWERReporter finishing event handling. (00000000)
    2013-08-22 20:28:18:778  880 f18 Agent *************
    2013-08-22 20:28:18:778  880 f18 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-08-22 20:28:18:778  880 f18 Agent *********
    2013-08-22 20:28:18:778  880 f18 Agent   * Online = No; Ignore download priority = No
    2013-08-22 20:28:18:778  880 f18 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2013-08-22 20:28:18:778  880 f18 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-08-22 20:28:18:778  880 f18 Agent   * Search Scope = {Machine}
    2013-08-22 20:28:27:171  880 c74 AU WARNING: AU found no suitable session to launch client in
    2013-08-22 20:29:01:677  880 f18 Agent   * Found 0 updates and 69 categories in search; evaluated appl. rules of 587 out of 1078 deployed entities
    2013-08-22 20:29:01:693  880 f18 Agent *********
    2013-08-22 20:29:01:693  880 f18 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-08-22 20:29:01:693  880 f18 Agent *************
    2013-08-22 20:29:01:708  880 fc8 AU >>##  RESUMED  ## AU: Search for updates [CallId = {B6E4735F-AA5B-4184-84C0-EB49EDE6C20B}]
    2013-08-22 20:29:01:708  880 fc8 AU   # 0 updates detected
    2013-08-22 20:29:01:708  880 fc8 AU #########
    2013-08-22 20:29:01:708  880 fc8 AU ##  END  ##  AU: Search for updates [CallId = {B6E4735F-AA5B-4184-84C0-EB49EDE6C20B}]
    2013-08-22 20:29:01:708  880 fc8 AU #############
    2013-08-22 20:29:01:708  880 fc8 AU Featured notifications is disabled.
    2013-08-22 20:29:01:708  880 fc8 AU Successfully wrote event for AU health state:0
    2013-08-22 20:29:01:708  880 fc8 AU Successfully wrote event for AU health state:0
    2013-08-22 20:29:06:716  880 f18 Report CWERReporter finishing event handling. (00000000)
    2013-08-22 20:30:53:182  880 f18 Report Uploading 1 events using cached cookie, reporting URL = http://OurWsusServerName/ReportingWebService/ReportingWebService.asmx
    2013-08-22 20:30:53:182  880 f18 Report Reporter successfully uploaded 1 events.
    2013-08-22 20:40:11:359  880 c74 AU Launched new AU client for directive 'Forced Reboot', session id = 0x2
    2013-08-22 20:40:11:374 1488 13c Misc ===========  Logging initialized (build: 7.6.7600.256, tz: +0200)  ===========
    2013-08-22 20:40:11:374 1488 13c Misc   = Process: C:\Windows\system32\wuauclt.exe
    2013-08-22 20:40:11:374 1488 13c AUClnt Launched Client UI process
    2013-08-22 20:40:11:795 1488 13c Misc ===========  Logging initialized (build: 7.6.7600.256, tz: +0200)  ===========
    2013-08-22 20:40:11:795 1488 13c Misc   = Process: C:\Windows\system32\wuauclt.exe
    2013-08-22 20:40:11:795 1488 13c Misc   = Module: C:\Windows\system32\wucltux.dll
    2013-08-22 20:40:11:795 1488 13c CltUI AU client got new directive = 'Forced Reboot', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0
    2013-08-22 20:40:11:873 1488 13c AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x800705B4)
    2013-08-22 20:40:11:873 1488 13c AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x800705B4)
    2013-08-22 20:40:11:873 1488 13c AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x800705B4)
    2013-08-22 20:40:11:873 1488 13c AUClnt WARNING: Shell_NotifyIcon failed (dwMessage=0x0, uFlags=0x7, hr=0x800705B4)
    2013-08-22 20:40:11:983  880 c74 AU AU received handle event
    2013-08-22 20:40:12:076  880 c74 AU Successfully wrote event for AU health state:0
    2013-08-22 20:40:17:084  880 f18 Report CWERReporter finishing event handling. (00000000)

    Thursday, August 22, 2013 6:54 PM
  • If i understand the log correct, it rebooted because of the option "No auto-restart with logged on users for scheduled automatic updates installations" because no one was logged onto the server at the time of the installation.

    2 Questions then

    1. Why did updates install today (Thursday evening) when the GPO is set to Auto Download and install on a Saturday 3am?

    2. How do i install the updates on my servers but DO NOT let the server auto restart after the updates have installed?

    Thursday, August 22, 2013 8:18 PM
  • If i understand the log correct, it rebooted because of the option "No auto-restart with logged on users for scheduled automatic updates installations" because no one was logged onto the server at the time of the installation.

    2 Questions then

    1. Why did updates install today (Thursday evening) when the GPO is set to Auto Download and install on a Saturday 3am?

    2. How do i install the updates on my servers but DO NOT let the server auto restart after the updates have installed?

    2013-08-22 20:21:51:023  820 d44 AU Forced install timer expired for deadline install

    2013-08-22 20:21:58:308  820 d44 AU Enforcing reboot for already installed deadline expired update

    Actually it INSTALLED and REBOOTED because a DEADLINE was set on the update approval.

    While it's true that a server will reboot after installation if no user is logged on, it is not true that a server will randomly initiate an update installation. Only three things can cause an update installation to launch:

    1. A scheduled installation event, which always starts at the TOP of the hour (e.g. HH:00:00.000)
    2. A human being
    3. An expired approval deadline

    Furthermore, if a deadline expires, not even a logged on user can defer the reboot!

    In this case the issue was not that there was no user logged on when the installation finished, but rather than the installation started at all --- apparently around 8:15pm.

    The answer to question #2 is that you don't use AUOption '4'. You use AUOption '3', and launch the update installation when you're in a position to allow the server to reboot immediately.

    You also never use approval deadlines on updates for a Server operating system. :-)


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, August 23, 2013 11:18 PM
    Moderator
  • Thanks Lawrence

    The person approving the updates assured me that no deadlines has been set. She approved an update while I was looking the same way she would approve all the others and she would not set a deadline.

    My question - is it maybe that a default deadline is set on any update deployed? So if, you approve and deploy updates today - if it has not been installed in a months time it will automatically install and depending on the update casue the system to reboot? Would that be possible?

    Friday, August 30, 2013 6:39 AM
  • The person approving the updates assured me that no deadlines has been set. She approved an update while I was looking the same way she would approve all the others and she would not set a deadline.

    Approvals, including deadlines, are logged in %ProgramFiles%\Update Services\Logfiles\Change.LOG.

    In addition, the WindowsUpdate.log will identify explicitly which update(s) had deadlines configured that triggered the installation event.

    My question - is it maybe that a default deadline is set on any update deployed?

    There are two possible ways a deadline can get configured:

    • An administrator explicitly configures a deadline when approving the update (or modifies the deadline after approving the update).
    • An Automatic Approval rule is configured to apply deadlines to all approvals (and yes, in this method, it is possible to impose a deadline "one month" after the initial approval).

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Saturday, August 31, 2013 5:33 PM
    Moderator