yes, there ist.
It should be ( I read but did not test it)
- use NTDSUTIL
- Restart server in normal mode
- Restore System Volume SYSVOL
According to what I read by microsoft,
this can be used to restore all of AD but old schema.
This notice leaves me in quite unsure state.
regards
juraj
-----Ursprüngliche Nachricht-----
Von: Remeta, Mark [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 11. Juli 2003 17:46
An: [EMAIL PROTECTED]
Betreff: Re: Active Directory Problems
Isn't there some way to, after doing a non-authoritative restore of AD with
TSM, to mark the restored database as the master and overwrite the other
existing DC's with the new restored copy?
Mark
-----Original Message-----
From: Salak Juraj [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2003 11:39 AM
To: [EMAIL PROTECTED]
Subject: AW: Active Directory Problems
which is good enough after an HW error.
But not after having repliacted an configuration error.
Juraj
-----Ursprüngliche Nachricht-----
Von: Remeta, Mark [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 11. Juli 2003 16:55
An: [EMAIL PROTECTED]
Betreff: Re: Active Directory Problems
I believe the IBM Redbook example of recovering a AD Controller is in
non-authoritative mode. It does not go into how to do a Authoritative
restore or even if one is possible. I believe they suggest you setup a new
blank DC and let AD replicate.
-----Original Message-----
From: Salak Juraj [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2003 10:52 AM
To: [EMAIL PROTECTED]
Subject: AW: Active Directory Problems
Zlatko,
how is it:
4)ignore restart message
..
6).. You will need to be in AD recovery mode in step 5
In order to be in AD recovery in step 5 I have to restart.
But a restart after (4) will probably not work because
of mismatch between system objects left from (1) installation
and files having been restored(3)
What am I missing?
Juraj
-----Ursprüngliche Nachricht-----
Von: Zlatko Krastev [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 11. Juli 2003 12:42
An: [EMAIL PROTECTED]
Betreff: Re: Active Directory Problems
Christian,
I am under impression that your posts become more and more misleading over
time! Is this because I read them selectively or for any other reason -
don't know. I would be rather happy to be proved wrong!!!
Also advertizement within any advice is against the principles of the
community on this forum. Please perform your marketing activities
privately or using a different media!!!!
Back to the topic - the problem Jacques is experiencing:
The standard Win2k recovery procedure is:
1. Install clean Windows - I install it on the *same* path and it works
fine
2. Install TSM client - personally I prefer instead of configuring it to
restore dsm.opt and restart the client
3. Restore *all program files* - if some application is installed on a
drive other than C:, its binaries is better to be restores right now
4. Ignore restart message
5. Restore System State (System Object in TSM terms) and reboot.
6. (only for the only/first domain controller in DR) Make the restored AD
data "authoritative". You will need to be in AD recovery mode in step 5.
The trick is to avoid joining to the domain at step 1!!!! Keep the system
as being part of some imaginary workgroup (better with a name which is not
known to the domain controller/master NetBIOS browser).
In step 5 all information regarding membership to the domain will be
restored and after reboot the server will be part of the domain. Think of
sequence failure-reinstall-restore-reboot as of an ordinary
shutdown-reboot with longer downtime!
Zlatko Krastev
IT Consultant
Christian Svensson <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11.07.2003 12:04
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Active Directory Problems
When you installed Windows on the machine.
Did you installed Windows in a Temp directory and then restore all data
from TSM?
Or did you installed Windows in there standard path and overwrite each
file
with TSM?
If you did the last thing. I can understand way you got that problem. That
is becuse you got a new SID and et c.
Try to install Windows in a Temp Path and restore the data from TSM to
there normal PATH. Reboot the server and boot up in Restore Directory
Service mode and restore the System Object. Reboot the server again and
remove the temp Windows installation.
Now should it work fine.
To do this much easyer. Buy a Disaster Recovery tool. Talk to IBM and they
should give you some advice. Or can you download your own eval. copy from
www.cristie.com
Best Regard / Med vänlig hälsning
Christian Svensson
Tivoli Storage Manager Certified
............................................................................
............................................................
Cristie Nordic AB
Box 2 Phone : +46-(0)8-718 43 30
SE-131 06 Nacka Mobil : +46-(0)70-325 15 77
Sweden eMail : Christian.
[EMAIL PROTECTED]
Visit : Gamla Värmdövägen 4, Plan 2
web : www.cristie.com
............................................................................
............................................................
Jacques Butcher
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
.CO.ZA> cc:
Sent by: "ADSM: Subject: Active Directory
Problems
Dist Stor
Manager" <ADSM-
[EMAIL PROTECTED]>
2003-07-11 10:53
Please respond to
"ADSM: Dist Stor
Manager"
Hi Everyone.
I've restore the system volume (c:) and all system objects
(of which I have a consistent backup of) successfully. I
can access Active Directory and see all resources. I can
even see all the resources from another machine through a
UNC path. It even prompts me for a username and and
password. I type the domain name\username and the password
and I can see all printers, etc.
I however cannot log onto or join the domain.
Did anyone else get this?
Any help will be greatly appreciated.
Thanks in advance.
==
Download ringtones, logos and picture messages at Ananzi Mobile Fun.
http://www.ananzi.co.za/cgi-bin/goto.pl?mobile
Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.
Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.
