Re: Exchange 2003 Disaster Recovery 1.mal / Wiederherstellung

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hallo Support, ich habe den 2003 Server mit Sp1 neu installiert und auch
Exchange 2003 mit SP2 !
und habe dem Exchange Server im ADS einen neuen Namen gegeben. den alten
Server habe ich im ADS gelöcht.
dcpromo auf dem neuen aus geführt.

Das Problem es scheinen jetzt alle dienste zulaufen.

Wenn ich an einem Client Outlook2003 Sttarte bekomme ich die Meldung OUTLOOK
Microsoft Office Outlook kann nicht gestartet werden. Das Outlook Fenster
kann nicht geöffner werde. Ordner konnte nicht geöffnet werden.
Und im ADS bei einem Exchange user bekomme ich die Meldung (Exchange
Erweiterung) Der Vorgang konnte nicht abgeschlossen werden, weil dieser
Informationsspeicher nicht bereitgestellt ist.
IDNr. c1041732

Wie komme ich weiter?


Gruß Ralf


"Daniel Melanchthon [MSFT]" wrote:

> Ralf Devant schrieb:
> > ich hatte einen BlueScreen auf meinen 2003 Standard Server und jetzt nach
> > der neu Installation von Exchange 2003 im ADS habe ich einige kleine Fragen!
> > Ich habe den Server per Image wieder hergestellt, was auch ohne Problem mir
> > AD geht.
>
> Das ist ein Trugschluß. Restore per Image, insbesondere von DCs, ist nicht
> supported. "USN rollbacks" können zu einem gravierenden Problem im Betrieb
> führen:
>
> Software and methodologies that cause USN rollbacks
>
> When the following environments, programs, or subsystems are used,
> administrators can bypass the checks and validations that Microsoft has
> designed to occur when the domain controller system state is restored:
>
> - Virtualized hosting environments, including but not limited to Microsoft
> Virtual Server 2005 and EMC VMWARE
>
> - Software that backs up and restores an Active Directory operating system
> installation or a hard disk volume that contains that installation
> Note Such software includes but is not limited to Norton Ghost.
>
> - Advanced disk subsystems that can selectively copy a volume that contains
> an Active Directory operating system installation that was saved in the past
>
> The following operations are not supported:
>
> 1. Starting an Active Directory domain controller whose operating system
> was restored to a hard disk by using an imaging program such as Norton Ghost
>
> 2. Starting an Active Directory domain controller whose operating system
> resides in a virtualized hosting environment such as Microsoft Virtual PC,
> Microsoft Virtual Server 2005, or EMC VMWARE
>
> 3. Starting an Active Directory domain controller that is located on a
> volume where the disk subsystem loads using previously saved images of the
> operating system without requiring a system state restoration of Active
> Directory.
>
> The only supported way to roll back the contents of Active Directory or the
> local state of an Active Directory domain controller is to use an Active
> Directory-aware backup and restoration utility to restore a system state
> backup that originated from the same operating system installation and the
> same physical or virtual computer that is being restored.
>
> Microsoft does not support any other process that takes a snapshot of the
> elements of an Active Directory domain controller’s system state and copies
> elements of that system state to an operating system image. Unless an
> administrator intervenes, such processes cause a USN rollback. This USN
> rollback causes the direct and transitive replication partners of an
> incorrectly restored domain controller to have inconsistent objects in
> their Active Directory databases.
>
> How to detect and recover from a USN rollback in Windows 2000 Server
> http://support.microsoft.com/kb/885875/en-us#5
>
> How to detect and recover from a USN rollback in Windows Server 2003
> http://support.microsoft.com/kb/875495/en-us
>
> --
> ..:Daniel Melanchthon:.
> Technologieberater - Exchange Server
> http://blogs.technet.com/dmelanchthon
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
.

Relevant Pages

  • Re: Connection to a SAMBA Active Directory
    ... Keep in mind that you're trying to setup a NT4 style trust ... if you setup the Exchange as a resource forest model, ... domain and the Exchange server in another domain will work. ... I am able to define a 2 way Realm trust using the Active Directory ...
    (microsoft.public.exchange.connectivity)
  • Re: Connection to a SAMBA Active Directory
    ... domain and the Exchange server in another domain will work. ... I am able to define a 2 way Realm trust using the Active Directory ... There is a bit of confusing on the SAMBA side. ...
    (microsoft.public.exchange.connectivity)
  • Re: Home Network Dilemma
    ... You must understand Active Directory first, in order to implement Exchange. ... Matter of fact, Exchange must alter Active Directory prior to installation, to accomodate the changes. ... On top of that, an understanding of DNS is required, because AD will not work if DNS is not implemented properly for its internal use only, and on top of that, an understanding of DNS on the internet is required in order to manipulate public records so others in the world can 'find' your mail server on your network. ...
    (microsoft.public.windows.server.networking)
  • Re: Configuration / Protocols Missing
    ... and I removed the E55 server. ... the ADCConfigCheck deployment tool (Check Exchange ... The tool searches Active Directory by ... >> its endpoints are the Site Replication Service and a global catalog ...
    (microsoft.public.exchange.setup)
  • Re: Connection to a SAMBA Active Directory
    ... I built a new Windows 2003 Server in a brand new domain. ... I am able to define a 2 way Realm trust using the Active Directory ... There is a bit of confusing on the SAMBA side. ... Active Directory components but not enough to deploy Exchange. ...
    (microsoft.public.exchange.connectivity)