Server 2003 R2 SP1 wacked after updates. Should I restore systemstate?

  • Thread starter Thread starter barretech@hotmail.com
  • Start date Start date
B

barretech@hotmail.com

Guest
HI. I have a server 2003 R2 standalone DC with SP1 that we installed
updates onto last night (about 25 updates). Now it seems to have some
kind of problem with serving files.

I have already gone into the Windows folder and one by one in proper
order used "spuninst.exe" to remove each update. Didn't reboot between
the uninstalls. Maybe I should have.

Question:Should I restore the system state from the time before the
updates were installed? I have a USB hard drive (actually two) with
system state backups. I sure hope USB is supported during system state
restores.

Do I need to use Active Directory restore mode for this?

Here is more info that led me to believe this option is my only
recourse:

The clients have Outlook 2003 with PST files ranging from 300MB to
2.3GB. Before the updates they seemed to be fine. Now we are seeing
"delayed write" errors and Outlook generally is unhappy. Outlook is
obviously asking for more than a simple file-copy does.

Thinking that maybe the probl was caused by the switch, I tried a new
one. Same problem. Thought maybe it was user-related, so I tried a new
profile of a new user. Same problem. We try to File > Open >Outlook
data file, point it at the PST file on the server, and Outlook "checks
for errors" . Eventually the network activity halts, the computer sits
for a few minutes then fails.

I tried a new NIC in the server (being sure to add it to the existing
one) and it didn't help. Same results.

Of course we can copy the files from the server to the C: drives.
1.6GB copies in about 4 minutes. And Outlook is able to open the
copies of the files from local C: drive. This is my only workaround
for now.

Please , any suggestions or experience is appreciated. Thank you in
advance.!!
 
Re: Server 2003 R2 SP1 wacked after updates. Should I restore system state?

Re: Server 2003 R2 SP1 wacked after updates. Should I restore system state?

Hello barretech@hotmail.com,

You should not restore the system state if you have no problem with AD. Also
SP2 is the lates service pack and also therefore a lot patches are avilable.
So you should update the server to the latest SP and patches and then check
for your errors. You are far behind them. If you then still have problems
i would start investigation whats going on.

Also it is not recommended to use .ost or .pst on network shares and they
should not be larger then 2GB.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> HI. I have a server 2003 R2 standalone DC with SP1 that we installed
> updates onto last night (about 25 updates). Now it seems to have some
> kind of problem with serving files.
>
> I have already gone into the Windows folder and one by one in proper
> order used "spuninst.exe" to remove each update. Didn't reboot between
> the uninstalls. Maybe I should have.
>
> Question:Should I restore the system state from the time before the
> updates were installed? I have a USB hard drive (actually two) with
> system state backups. I sure hope USB is supported during system state
> restores.
>
> Do I need to use Active Directory restore mode for this?
>
> Here is more info that led me to believe this option is my only
> recourse:
>
> The clients have Outlook 2003 with PST files ranging from 300MB to
> 2.3GB. Before the updates they seemed to be fine. Now we are seeing
> "delayed write" errors and Outlook generally is unhappy. Outlook is
> obviously asking for more than a simple file-copy does.
>
> Thinking that maybe the probl was caused by the switch, I tried a new
> one. Same problem. Thought maybe it was user-related, so I tried a new
> profile of a new user. Same problem. We try to File > Open >Outlook
> data file, point it at the PST file on the server, and Outlook "checks
> for errors" . Eventually the network activity halts, the computer sits
> for a few minutes then fails.
>
> I tried a new NIC in the server (being sure to add it to the existing
> one) and it didn't help. Same results.
>
> Of course we can copy the files from the server to the C: drives.
> 1.6GB copies in about 4 minutes. And Outlook is able to open the
> copies of the files from local C: drive. This is my only workaround
> for now.
>
> Please , any suggestions or experience is appreciated. Thank you in
> advance.!!
>
 
Re: Server 2003 R2 SP1 wacked after updates. Should I restore systemstate?

Thanks for your replies. Let me paraphrase my questions to be more
clear on the goal:

Will a system state restore put the DLL's , registry settings, and AD
back to the way they were -before the updates-?

And does a system state restore on an AD controller require booting in
AD restore mode?

And will a USB hard drive which contains the system state backup be
accessible?

---------

Thanks, I know about SP2. This problem did -not- exist before the
updates Monday night.

Thanks again for your suggestions. In order to not obscure the trail
which led us to this point, I chose to -not- install SP2 last night
even though I had it ready. It has been my experience that many
attempt to fix wacky surprise problems by installing the newest SP2 or
SP3 or whatever -- and it seldom works to fix a wacky problem like
this that pops up after an update or two are installed.

I want to know how to go back one step , and find out which KB update
screwed the server up. So I am asking about the methods of
restoration. Obviously there is no "System Restore" (XP). Surely there
is a better choice in 2K3. I am looking for that "better choice".

Thank you for any help on the three questions above. And thanks again
for your suggestions. I understand the best practice of keeping PST
files off of the server and will implement a routine that copies them
daily to the server so they can be backed up. The customer was
directed to buy Exchange before the server was purchased, but didn't.
Cheap. So they are stuck with PST files.


> > Question:Should I restore the system state from the time before the
> > updates were installed? I have a USB hard drive (actually two) with
> > system state backups. I sure hope USB is supported during system state
> > restores.

>
> > Do I need to use Active Directory restore mode for this?

>
> > Here is more info that led me to believe this option is my only
> > recourse:





On Oct 22, 1:30 am, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
> Hello barret...@hotmail.com,
>
> You should not restore the system state if you have no problem with AD. Also
> SP2 is the lates service pack and also therefore a lot patches are avilable.
> So you should update the server to the latest SP and patches and then check
> for your errors. You are far behind them. If you then still have problems
> i would start investigation whats going on.
>
> Also it is not recommended to use .ost or .pst on network shares and they
> should not be larger then 2GB.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
>
> > HI. I have a server 2003 R2 standalone DC with SP1 that we installed
> > updates onto last night (about 25 updates). Now it seems to have some
> > kind of problem with serving files.

>
> > I have already gone into the Windows folder and one by one in proper
> > order used "spuninst.exe" to remove each update. Didn't reboot between
> > the uninstalls. Maybe I should have.

>
> > Question:Should I restore the system state from the time before the
> > updates were installed?  I have a USB hard drive (actually two) with
> > system state backups. I sure hope USB is supported during system state
> > restores.

>
> > Do I need to use Active Directory restore mode for this?

>
> > Here is more info that led me to believe this option is my only
> > recourse:

>
> > The clients have Outlook 2003 with PST files ranging from 300MB to
> > 2.3GB. Before the updates they seemed to be fine. Now we are seeing
> > "delayed write" errors and Outlook generally is unhappy. Outlook is
> > obviously asking for more than a simple file-copy does.

>
> > Thinking that maybe the probl was caused by the switch, I tried a new
> > one. Same problem. Thought maybe it was user-related, so I tried a new
> > profile of a new user. Same problem. We try to File > Open >Outlook
> > data file, point it at the PST file on the server, and Outlook "checks
> > for errors" . Eventually the network activity halts, the computer sits
> > for a few minutes then fails.

>
> > I tried a new NIC in the server (being sure to add it to the existing
> > one) and it didn't help. Same results.

>
> > Of course we can copy the files from the server to the C: drives.
> > 1.6GB copies in about 4 minutes. And Outlook is able to open the
> > copies of the files from local C: drive. This is my only workaround
> > for now.

>
> > Please , any suggestions or experience is appreciated. Thank you in
> > advance.!!- Hide quoted text -

>
> - Show quoted text -
 
Re: Server 2003 R2 SP1 wacked after updates. Should I restore system state?

Re: Server 2003 R2 SP1 wacked after updates. Should I restore system state?

Hello barretech@hotmail.com,

See inline.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Thanks for your replies. Let me paraphrase my questions to be more
> clear on the goal:
>
> Will a system state restore put the DLL's , registry settings, and AD
> back to the way they were -before the updates-?


System state data is comprised of the following files:

. Boot files, including the system files, and all files protected by Windows
File Protection (WFP).
. Active Directory (on a domain controller only).
. Sysvol (on a domain controller only).
. Certificate Services (on certification authority only).
. Cluster database (on a cluster node only).
. The registry.
. Performance counter configuration information.
. Component Services Class registration database.


> And does a system state restore on an AD controller require booting in
> AD restore mode?


Yes, see here: http://technet.microsoft.com/en-us/library/cc784922.aspx

> And will a USB hard drive which contains the system state backup be
> accessible?


Should be, because the AD restore mode does start the DC without AD services
but normal GUI.

> ---------
>
> Thanks, I know about SP2. This problem did -not- exist before the
> updates Monday night.
>
> Thanks again for your suggestions. In order to not obscure the trail
> which led us to this point, I chose to -not- install SP2 last night
> even though I had it ready. It has been my experience that many
> attempt to fix wacky surprise problems by installing the newest SP2 or
> SP3 or whatever -- and it seldom works to fix a wacky problem like
> this that pops up after an update or two are installed.
>
> I want to know how to go back one step , and find out which KB update
> screwed the server up. So I am asking about the methods of
> restoration. Obviously there is no "System Restore" (XP). Surely there
> is a better choice in 2K3. I am looking for that "better choice".


As said before, do not search for a broken patch, update it until today.
We use all updates coming with WSUS and some small test before without any
problem until now, since 3 years. OS 2000 Pro, 2000 Server, 2003 Server,
XP Pro, Exchange 2000, Exchange 2003 etc.

> Thank you for any help on the three questions above. And thanks again
> for your suggestions. I understand the best practice of keeping PST
> files off of the server and will implement a routine that copies them
> daily to the server so they can be backed up. The customer was
> directed to buy Exchange before the server was purchased, but didn't.
> Cheap. So they are stuck with PST files.
>
>>> Question:Should I restore the system state from the time before the
>>> updates were installed? I have a USB hard drive (actually two) with
>>> system state backups. I sure hope USB is supported during system
>>> state restores.
>>>
>>> Do I need to use Active Directory restore mode for this?
>>>
>>> Here is more info that led me to believe this option is my only
>>> recourse:
>>>

> On Oct 22, 1:30 am, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
>
>> Hello barret...@hotmail.com,
>>
>> You should not restore the system state if you have no problem with
>> AD. Also
>> SP2 is the lates service pack and also therefore a lot patches are
>> avilable.
>> So you should update the server to the latest SP and patches and then
>> check
>> for your errors. You are far behind them. If you then still have
>> problems
>> i would start investigation whats going on.
>> Also it is not recommended to use .ost or .pst on network shares and
>> they should not be larger then 2GB.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
>>> HI. I have a server 2003 R2 standalone DC with SP1 that we installed
>>> updates onto last night (about 25 updates). Now it seems to have
>>> some kind of problem with serving files.
>>>
>>> I have already gone into the Windows folder and one by one in proper
>>> order used "spuninst.exe" to remove each update. Didn't reboot
>>> between the uninstalls. Maybe I should have.
>>>
>>> Question:Should I restore the system state from the time before the
>>> updates were installed? I have a USB hard drive (actually two) with
>>> system state backups. I sure hope USB is supported during system
>>> state restores.
>>>
>>> Do I need to use Active Directory restore mode for this?
>>>
>>> Here is more info that led me to believe this option is my only
>>> recourse:
>>>
>>> The clients have Outlook 2003 with PST files ranging from 300MB to
>>> 2.3GB. Before the updates they seemed to be fine. Now we are seeing
>>> "delayed write" errors and Outlook generally is unhappy. Outlook is
>>> obviously asking for more than a simple file-copy does.
>>>
>>> Thinking that maybe the probl was caused by the switch, I tried a
>>> new one. Same problem. Thought maybe it was user-related, so I tried
>>> a new profile of a new user. Same problem. We try to File > Open
>>> >Outlook data file, point it at the PST file on the server, and
>>> Outlook "checks for errors" . Eventually the network activity halts,
>>> the computer sits for a few minutes then fails.
>>>
>>> I tried a new NIC in the server (being sure to add it to the
>>> existing one) and it didn't help. Same results.
>>>
>>> Of course we can copy the files from the server to the C: drives.
>>> 1.6GB copies in about 4 minutes. And Outlook is able to open the
>>> copies of the files from local C: drive. This is my only workaround
>>> for now.
>>>
>>> Please , any suggestions or experience is appreciated. Thank you in
>>> advance.!!- Hide quoted text -
>>>

>> - Show quoted text -
>>
 
Re: Server 2003 R2 SP1 wacked after updates. Should I restore systemstate?

Thanks Meinolf. Will definitely update to SP2 once I can get things
fixed or do a complete backup first. And will move the PST files away
to the C: drives.


On Oct 22, 9:16 am, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
> Hello barret...@hotmail.com,
>
> See inline.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > Thanks for your replies. Let me paraphrase my questions to be more
> > clear on the goal:

>
> > Will a system state restore put the DLL's , registry settings, and AD
> > back to the way they were -before the updates-?

>
> System state data is comprised of the following files:
>
> . Boot files, including the system files, and all files protected by Windows
> File Protection (WFP).
> . Active Directory (on a domain controller only).
> . Sysvol (on a domain controller only).
> . Certificate Services (on certification authority only).
> . Cluster database (on a cluster node only).
> . The registry.
> . Performance counter configuration information.
> . Component Services Class registration database.
>
> > And does a system state restore on an AD controller require booting in
> > AD restore mode?

>
> Yes, see here:  http://technet.microsoft.com/en-us/library/cc784922.aspx
>
> > And will a USB hard drive which contains the system state backup be
> > accessible?

>
> Should be, because the AD restore mode does start the DC without AD services
> but normal GUI.
>
>
>
>
>
> > ---------

>
> > Thanks, I know about SP2.  This problem did -not- exist before the
> > updates Monday night.

>
> > Thanks again for your suggestions. In order to not obscure the trail
> > which led us to this point, I chose to -not- install SP2 last night
> > even though I had it ready. It has been my experience that many
> > attempt to fix wacky surprise problems by installing the newest SP2 or
> > SP3 or whatever -- and it seldom works to fix a wacky problem like
> > this that pops up after an update or two are installed.

>
> > I want to know how to go back one step , and find out which KB update
> > screwed the server up.  So I am asking about the methods of
> > restoration. Obviously there is no "System Restore" (XP). Surely there
> > is a better choice in 2K3. I am looking for that "better choice".

>
> As said before, do not search for a broken patch, update it until today.
> We use all updates coming with WSUS and some small test before without any
> problem until now, since 3 years. OS 2000 Pro, 2000 Server, 2003 Server,
> XP Pro, Exchange 2000, Exchange 2003 etc.
>
>
>
> > Thank you for any help on the three questions above. And thanks again
> > for your suggestions. I understand the best practice of keeping PST
> > files off of the server and will implement a routine that copies them
> > daily to the server so they can be backed up. The customer was
> > directed to buy Exchange before the server was purchased, but didn't.
> > Cheap. So they are stuck with PST files.

>
> >>> Question:Should I restore the system state from the time before the
> >>> updates were installed?  I have a USB hard drive (actually two) with
> >>> system state backups. I sure hope USB is supported during system
> >>> state restores.

>
> >>> Do I need to use Active Directory restore mode for this?

>
> >>> Here is more info that led me to believe this option is my only
> >>> recourse:

>
> > On Oct 22, 1:30 am, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:

>
> >> Hello barret...@hotmail.com,

>
> >> You should not restore the system state if you have no problem with
> >> AD. Also
> >> SP2 is the lates service pack and also therefore a lot patches are
> >> avilable.
> >> So you should update the server to the latest SP and patches and then
> >> check
> >> for your errors. You are far behind them. If you then still have
> >> problems
> >> i would start investigation whats going on.
> >> Also it is not recommended to use .ost or .pst on network shares and
> >> they should not be larger then 2GB.

>
> >> Best regards

>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> HI. I have a server 2003 R2 standalone DC with SP1 that we installed
> >>> updates onto last night (about 25 updates). Now it seems to have
> >>> some kind of problem with serving files.

>
> >>> I have already gone into the Windows folder and one by one in proper
> >>> order used "spuninst.exe" to remove each update. Didn't reboot
> >>> between the uninstalls. Maybe I should have.

>
> >>> Question:Should I restore the system state from the time before the
> >>> updates were installed?  I have a USB hard drive (actually two) with
> >>> system state backups. I sure hope USB is supported during system
> >>> state restores.

>
> >>> Do I need to use Active Directory restore mode for this?

>
> >>> Here is more info that led me to believe this option is my only
> >>> recourse:

>
> >>> The clients have Outlook 2003 with PST files ranging from 300MB to
> >>> 2.3GB. Before the updates they seemed to be fine. Now we are seeing
> >>> "delayed write" errors and Outlook generally is unhappy. Outlook is
> >>> obviously asking for more than a simple file-copy does.

>
> >>> Thinking that maybe the probl was caused by the switch, I tried a
> >>> new one. Same problem. Thought maybe it was user-related, so I tried
> >>> a new profile of a new user. Same problem. We try to File > Open
> >>> >Outlook data file, point it at the PST file on the server, and
> >>> Outlook "checks for errors" . Eventually the network activity halts,
> >>> the computer sits for a few minutes then fails.

>
> >>> I tried a new NIC in the server (being sure to add it to the
> >>> existing one) and it didn't help. Same results.

>
> >>> Of course we can copy the files from the server to the C: drives.
> >>> 1.6GB copies in about 4 minutes. And Outlook is able to open the
> >>> copies of the files from local C: drive. This is my only workaround
> >>> for now.

>
> >>> Please , any suggestions or experience is appreciated. Thank you in
> >>> advance.!!- Hide quoted text -

>
> >> - Show quoted text -- Hide quoted text -

>
> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
 
Back
Top