RE: Database Corruption after Exchange SP 2

Hi,

Thank you for your reply.
See inline:

The local security policy is not defined... BUT it will once I do the
steps below and create the new one with the Setup Security.inf right?? Will
this be the same as the one I had before >if I didn't make any changes...
in other words, is this the default SBS local Policy? Should I reapply any
other settings since the initial installation of my SBS didn't have SP1 and
now >it does?

Yes after the steps in my previous post will create a default security
database. As far as I know. SBS SP1 do not change the settings of GPO, so
you needn't apply SP1 again.


What files do I need to rename or move? Are you talking about the
%SystemRoot%\Security that is being renamed to "OldSecurity" Any other
files?

You needn't rename Security folder, just create a subfolder Oldsecurity
under Security folder. You should rename Secedit.sdb file in the
%SystemRoot%\Security\Database folder to "Secedit.old"

Hope this helps, if you have any other concerns on this issue, please do
not hesitate to let me know.

Have a nice day!

Best Regards,

Chace Zhang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
| Thread-Topic: Database Corruption after Exchange SP 2
| thread-index: Aca9V+PLhVTY8Na6RVSlx39P6lNB0w==
| X-WBNR-Posting-Host: 139.161.2.10
| From: =?Utf-8?B?UmdhcmNpYQ==?= <Rgarcia@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <1C9A32DD-414A-4333-BBAC-4864D23C6BBD@xxxxxxxxxxxxx>
<97BE0371-B5D5-4E98-8759-3326ABBD087F@xxxxxxxxxxxxx>
<bQLbUertGHA.5840@xxxxxxxxxxxxxxxxxxxxx>
<4ADDB95D-093E-4E39-9737-87429E872F4B@xxxxxxxxxxxxx>
<52BC4F43-12EF-48A1-92A5-2C234E6BF449@xxxxxxxxxxxxx>
<rPAI8QhuGHA.3920@xxxxxxxxxxxxxxxxxxxxx>
<25DD2939-C052-47CD-AFAD-49FF16EC7B57@xxxxxxxxxxxxx>
<eMPPrYOvGHA.2004@xxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: Database Corruption after Exchange SP 2
| Date: Fri, 11 Aug 2006 08:07:40 -0700
| Lines: 62
| Message-ID: <78EE1A7A-7EB0-4863-BAAF-B1528BAE29A9@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:288943
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Thanks for your continuing support.
|
| I will check the "Rename Administrator Account" MS Knowledge Base article.
|
| Regarding how to repair Secedit.sdb. A few questions:
|
|
| > NOTE: When you use this procedure, your computer is returned to the
| > original installation state; the Local Security Policy is not defined.
|
| The local security policy is not defined... BUT it will once I do the
steps
| below and create the new one with the Setup Security.inf right?? Will
this be
| the same as the one I had before if I didn't make any changes... in other
| words, is this the default SBS local Policy? Should I reapply any other
| settings since the initial installation of my SBS didn't have SP1 and now
it
| does?
|
| > Also, you may have to start your computer in Safe mode to rename or
move
| > files. For information about how to do so, see Windows 2000 Help.
|
| What files do I need to rename or move? Are you talking about the
| %SystemRoot%\Security that is being renamed to "OldSecurity"
| Any other files?
|
|
| > IMPORTANT: Before performing these steps on a Domain Controller, create
a
| > backup of the SYSVOL share. There has been an unconfirmed incident
where
| > the Default Domain Controller policy was reset when applying these
steps.
|
| Yep. Always backup.
|
| > 1. Open the %SystemRoot%\Security folder, create a new folder, and then
| > name it "OldSecurity".
| >
| > 2. Move all of the files ending in .log from the %SystemRoot%\Security
| > folder to the OldSecurity folder.
| >
| > 3. Find the Secedit.sdb file in the %SystemRoot%\Security\Database
folder,
| > and then rename this file to "Secedit.old".
| >
| > 4. Click Start, click Run, type "mmc" (without the quotation marks),
and
| > then click OK.
| >
| > 5. Click Console, click "Add/Remove Snap-in", and then add the Security
and
| > Configuration snap-in.
| >
| > 6. Right-click "Security and Configuration and Analysis", and then
click
| > Open Database.
| >
| > 7. Browse to the %SystemRoot%\Security\Database folder, type
Secedit.sdb in
| > the File name box, and then click Open.
| >
| > 8. When you are prompted to import a template, click "Setup
Security.inf",
| > and then click Open.
| >
| > NOTE: If you receive an "Access denied" message, you can safely ignore
it.
| >
| > -=-=-=-=-=-=- END -=-=-=-=-=-=-
|
| Steps are very clear. Will do this weekend.
|
| Thanks again for your support. I will let you know how it goes.
|

.

Relevant Pages

  • Re: Help With Intranet Re-Install
    ... We need to rename the folder name not the sub folder then copy it back from ... the steps we offered is only applicable for SBS ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 error during step 5
    ... have moved the Clientapps folder to other location. ... portions of SBS: ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: NTFRS 13552 and 13555 Erorrs on SBS 2003 Following Tornado
    ... restore the SYSVOL data from a domain ... a location that is on the same volume as the SYSVOL folder. ... Gather MPS network report on SBS: ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Publishing folders on companyweb
    ... I understand that you want to make a SBS ... share folder can be accessed from Internet via companweb. ... we can not access share folder from Internet. ... Partnerfeedback newsgroup to make Microsoft products easier and more ...
    (microsoft.public.windows.server.sbs)
  • Re: change administrator name
    ... but normally you wouldn't rename that account before having setup SBS ... Microsoft SBS-MVP ... "Christopher Ames MSFT" schreef in bericht ...
    (microsoft.public.windows.server.sbs)
Loading