Ga naar inhoud

verwijderen exchange en AD


anoniem

Aanbevolen berichten

beste mensen, ik heb een probleem met het verwijderen van een server (optimus) uit de forest. wanneer ik de AD-service wil verwijderen van de server krijg ik volgende foutmelding: [code:1:b1666005d2]The operation failed because: managing the network session with zeus.myhood.fabstar81.com failed. "logon failure: the target account name is incorrect"[/code:1:b1666005d2] deze server heeft maanden uitgestaan omdat ik toendertijd ook al moeite had hem uit de AD te verwijderen. nu is het toch maar eens tijd hem definitief netjes eruit te halen. de enige pc waarmee deze pc wel kan communiceren is de nieuwe server "megatron" die server "zeus" gaat vervangen. Zeus heeft nog alle services draaiende. Hij houdt de profielen, netwerkshares, printserver, exchange (al wel overgenomen door megatron maar nogs teeds niet helemaal gedeinstalled op zeus), enz. wanneer ik exchange op deze heel oude server wil verwijderen krijg ik volgende melding: "failed to contact the Schema Master server for this active directory forest". ten tijd toen ik megatron installeerde (na dat ik problemen had met optimus) had ik geen problemen om die te installeren of toe te voegen in de AD. kan iemand mij helpen?
Link naar reactie
ik weet bijna 100% zeker dat de oude server (zeus) de FSMO rollen heeft en schema master is. dat was nl de eerste, de rest is er later bijgezet ter backup / sync. ik moet nog even vermelden dat het domein stamt van een nog oudere server. deze server is gecrasht waarna ik via deze tutorial: http://gathering.tweakers.net/forum/list_messages/875058 de toenmalige backup server alles heb laten overnemen en de oude gecrashte uit het domein heb gehaald. de toenmalige backup server is inmiddels vervangen door zeus. de toenmalige backup server is wel netjes uit het domein verwijderd. anyway...dat terzijde. zeus heeft alle FSMO rollen die overgenomen moeten worden door megatron. overigens...wat is wijsheid; megatron gaat over 1 a 2 maanden verhuizen naar een nieuw adres en daar het domein verzorgen. het liefst wil ik via een full time VPN verbinding beide servers draaiende houden zodat ik op beide locaties met onze laptops kan inloggen zonder individueel in te loggen middels VPN naar de server op locatie 1 (zeus).
Link naar reactie
Ik vind het lastig om daar verder op in te gaan aangezien ook niet alle info voor mij duidelijk is. Kan je schematisch aangeven welke servers er draaien, welke Domaincontroller zijn en wat de gewenste situatie moet worden. De nieuwe server gaat nu taken overnemen terwijl deze er binnenkort ook weer uit gaat? Het lijkt me dan verstandig om er eerst voor te zorgen dat het basisdomein, zoals het straks moet worden, weer in orde is. Heeft Optimus ook een AD? IS deze, na het terugbrengen in het domein, weer volledig gerepliceerd? Hoe zijn de FSMO rollen destijds overgezet? Gewoon verplaatst terwijl de oude 'Master' nog in het domein zat (transfer) of zijn de rollen opnieuw toegekend (Seize)? Kortom het plaatje is mij nog niet geheel duidelijk.
Link naar reactie
zeus (oud): AD, DC, eerste exchange, alle profielen zijn ook hier opgeslagen, print, RAS VPN, DNS, WINS, global catalog, DHCP optimus (oud): AD, DC, later exchange toegevoegd. megatron (nieuw): AD, DC, later exchange toegevoegd, global catalog de FSMO rollen zijn nooit geseized met de nieuwe megatron (transfer dus). zeus heeft wel eens de rollen geseized van toendertijd "serveme" nadat die gecrasht was. daarna is optimus toegevoegd, en daarna megatron. optimus echter, moet er wel helemaal uit. ik heb per ongeluk 2 servers door elkaar gehaald. zeus blijft op het adres, megatron gaat naar andere locatie, en optimus (die dus geen connectie kan maken met de AD) moet er gewoon uit en wordt afgeschreven of wordt in later stadium een workstation. heb je zo wat meer informatie?[/b]
Link naar reactie
  • 2 weken later...
  • 4 weken later...
  • 1 jaar later...
ow mijn god. ik schaam me dood, maar dit probleem is nog steeds niet opgelost. ik wil net een nieuwe post plaatsen met het probleem, zie ik in de search mijn eigen post terug. meer als een jaar geleden ben ik dus begonnen met dit probleem... :( *shame on me* anyway...we zijn inmiddels wel (of niet eigenlijk) een steek verder. [b:ecf70c305e]Optimus [/b:ecf70c305e]is inmiddels gedegradeerd tot werkstation (die overigens slecht contact maakt met het domein, maar goed) dus daar hebben we geen last meer van. hij komt hier en daar nog wel terug in de foutlogs omdat ik hem hardhandig heb moeten verwijderen uit het domein. zo ook als ik bijvoorbeeld exchange postbussen wil verplaatsen dan staat ie nog steeds tussen de andere servers, ook al is ie geen server meer. [b:ecf70c305e]zeus[/b:ecf70c305e] heeft inmiddels al zijn rollen overgedragen aan megatron, de nieuwe server. De profielen zijn eindelijk na een nieuwe harddisk geplaatst te hebben overgeplaatst naar megatron. alle home folders, my docs etc. staan nu op megatron. Alle exchange mailboxen staan ook op megatron nu. De clients hebben zo op het eerste gezicht niets meer te maken met zeus. [b:ecf70c305e]megatron[/b:ecf70c305e] is op dit moment uitgerust met de volgende rollen: global catalog Schema master RID master PDC Infrastructure master exchange File Print Web Omdat ik echter niets op zeus kan deinstalleren middels de wizards en ik nog steeds problemen heb om de domain naming master van zeus naar megatron over te zetten heb ik gister middels een seize alle rollen nog eens overgezet naar megatron. alles gaat goed, behalve dus de domain naming master. ik krijg daarbij volgende melding: Via GUI: [img:ecf70c305e]http://www.fabstar81.com/images/prt_FSMO.JPG[/img:ecf70c305e] Via SEIZE: [img:ecf70c305e]http://www.fabstar81.com/images/prt_dnm.JPG[/img:ecf70c305e] De FSMO rollen zijn dus allemaal overgezet behalve de Domain naming master van zeus naar megatron. Bovenstaande melding is helaas bron van nog meer fouten en dingen die niet werken: het demoten of deinstalleren van DNS, AD, DC, exchange, WINS. Feitelijk kan ik totaal niets deinstalleren op server zeus. Alhoewel alles lijkt te werken (wanneer ik GPO aanpas wordt dat keurig gesynct, DNS tests werken) lijkt er dus toch een probleem te zijn met de communicatie tussen de 2 servers. Ook staat de event viewer helemaal vol met foutmeldingen bij DNS: [code:1:ecf70c305e]The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "000021A2: SvcErr: DSID-030A09F3, problem 5001 (BUSY), data 0". The event data contains the error.[/code:1:ecf70c305e] Exchange: [code:1:ecf70c305e]Failed to access the metabase, error code is 80080005 (Server execution failed). [/code:1:ecf70c305e] Directory service: [code:1:ecf70c305e]It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source. The reason that replication is not allowed to continue is that the two machine's views of deleted objects may now be different. The source machine may still have copies of objects that have been deleted (and garbage collected) on this machine. If they were allowed to replicate, the source machine might return objects which have already been deleted. Time of last successful replication: 2008-02-02 19:57:06 Invocation ID of source: 0006f6c8-f6b8-0006-0100-000000000000 Name of source: bf46623c-525e-4316-8f19-ccd017d25427._msdcs.myhood.fabstar81.com Tombstone lifetime (days): 60 The replication operation has failed. User Action: Determine which of the two machines was disconnected from the forest and is now out of date. You have three options: 1. Demote or reinstall the machine(s) that were disconnected. 2. Use the "repadmin /removelingeringobjects" tool to remove inconsistent deleted objects and then resume replication. 3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection. Registry Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner [/code:1:ecf70c305e] System: [code:1:ecf70c305e]The IIS Admin Service service terminated with service-specific error 2148073478 (0x80090006).[/code:1:ecf70c305e] Als ik de geschiedenis bekijk is er nogal wat gebeurd met dit domein: Primary server is gecrasht Secondary server die maar enkele malen had gereplicate heeft het na weken stilstaan overgenomen third server heeft als back up toen gedraaid naast de 2 andere servers totdat het domein volledig terug was op volle sterkte domein heeft ongeveer 2 jaar zonder problemen gedraaid totdat dus de communicatieproblemen de kop opstaken. waarna dus de derde server hardhandig uit het domein gehaald moest worden. nu is er 1 server (megatron) die over moet blijven en goed werkt, maar het domein is inmiddels een beetje vervuild. in de foutlogs komt nog steeds de derde server terug en uberhaupt zijn er dus zoals te zien in de foutmeldingen replication problemen. wat heb ik zelf gedaan: netjes geprobeerd een demote te doen via allerlei wizards geprobeerd om de rollen netjes over te dragen via seize alle rollen geprobeerd over te nemen geprobeerd om alle functies dan maar gewoon te deinstalleren niets lukt om die laatste rol over te dragen en te deinstalleren. ik wil nu nog 1 keer proberen om dit domein op te schonen. wie o wie kan mij nu eindelijk helpen zodat eindelijk zeus uit kan (na anderhalf jaar) :( en ik een schoon (genoeg) domein overhoudt?! ps: sorry voor de lange post...
Link naar reactie
Ik kan uit je verhaal niet opmaken of ALLE eventlog foutmeldingen zoals ze er staan van de Megatron afkomen of niet. Als ze van de Zeus afkomstig zijn, dan ben je eigenlijk al ver uit de brand. Megatron vind dat hij houder is van alle FSMO rollen. De 'mening' van zeus doet er dan niet meer toe; die kun je gewoon uitzetten en desnoods formatteren. Met [code:1:c51e61132f]ntdsutil /metadata cleanup[/code:1:c51e61132f] kun je dan de resten van Zeus uit AD poetsen. Het is overigens wel aan te raden een uitgebreide [code:1:c51e61132f]dcdiag[/code:1:c51e61132f] tegen Megatron aan te draaien om te kijken of ie zichzelf wel gezond vindt, VOORDAT je de Zeus afzinkt. Als de meldingen WEL allemaal uit het eventlog van Megatron komen, dan lijkt me dat je een brak domain eraan hebt overgehouden. Dat wordt dan een lastiger verhaal.
Link naar reactie
de geposte logs kwamen van ZEUS. ik heb nu even gekeken in MEGATRON en ik kwam in Directory Services deze foutlog tegen: [code:1:548436a4a5]Active Directory could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups, group policy, users and computers and their passwords, Active Directory successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller. Invalid DNS configuration may be affecting other essential operations on member computers, domain controllers or application servers in this Active Directory forest, including logon authentication or access to network resources. You should immediately resolve this DNS configuration error so that this domain controller can resolve the IP address of the source domain controller using DNS. Alternate server name: zeus Failing DNS host name: 2f8288d2-fca7-4362-935d-974d16e7acb2._msdcs.myhood.fabstar81.com NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur. To log all individual failure events, set the following diagnostics registry value to 1: Registry Path: HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client User Action: 1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498. 2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>". 3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns dcdiag /test:dns 4) Verify that that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows: dcdiag /test:dns 5) For further analysis of DNS error failures see KB 824449: http://support.microsoft.com/?kbid=824449 Additional Data Error value: 11004 The requested name is valid, but no data of the requested type was found. [/code:1:548436a4a5] in DNS: [code:1:548436a4a5]The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "000021A2: SvcErr: DSID-030A09F3, problem 5001 (BUSY), data 0". The event data contains the error.[/code:1:548436a4a5] in FRS (eindelijk goed bericht): [code:1:548436a4a5]The File Replication Service is no longer preventing the computer MEGATRON from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL. Type "net share" to check for the SYSVOL share.[/code:1:548436a4a5] System: [code:1:548436a4a5]The following DNS server that is authoritative for the DNS domain controller locator records of this domain controller does not support dynamic DNS updates: DNS server IP address: 192.168.0.89 Returned Response Code (RCODE): 4 Returned Status Code: 9004 USER ACTION Configure the DNS server to allow dynamic DNS updates or manually add the DNS records from the file '%SystemRoot%\System32\Config\Netlogon.dns' to the DNS database. [/code:1:548436a4a5] Ik heb dit inmiddels op dynamic updates gezet. Ik moet zeggen dat er op megatron nog nooit zo weinig foutmeldingen zijn geweest. :D misschien komt dit door de seize. Je zegt dat megatron denkt dat ie alle rollen heeft. er is echter 1 rol die ik niet overgedragen of geseized krijg: domain naming master. Hoe krijg ik die dan over? kan ik nu die ntdsutil draaien om de zooi uit de metadata te halen of is het beter om te wachten tot die laatste rol overgedragen is?! Uit de logs blijft echter wel naar voren komen dat de DNS niet goed werkt en dat de AD ook niet goed werkt. lees ik dat goed uit de logs? de DNS tests werken echter op beiden servers goed, maar ik denk dat ze elkaar niet goed zien of zo. ik ga nu iig even een dcdiag draaien op megatron. results post ik wel.
Link naar reactie
Dit is de dcdiag van megatron: [code:1:75750681df]Z:\>dcdiag Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site\MEGATRON Starting test: Connectivity ......................... MEGATRON passed test Connectivity Doing primary tests Testing server: Default-First-Site\MEGATRON Starting test: Replications ......................... MEGATRON passed test Replications Starting test: NCSecDesc ......................... MEGATRON passed test NCSecDesc Starting test: NetLogons ......................... MEGATRON passed test NetLogons Starting test: Advertising ......................... MEGATRON passed test Advertising Starting test: KnowsOfRoleHolders ......................... MEGATRON passed test KnowsOfRoleHolders Starting test: RidManager ......................... MEGATRON passed test RidManager Starting test: MachineAccount ......................... MEGATRON passed test MachineAccount Starting test: Services ......................... MEGATRON passed test Services Starting test: ObjectsReplicated ......................... MEGATRON passed test ObjectsReplicated Starting test: frssysvol ......................... MEGATRON passed test frssysvol Starting test: frsevent ......................... MEGATRON passed test frsevent Starting test: kccevent ......................... MEGATRON passed test kccevent Starting test: systemlog An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:22 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:23 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:24 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:24 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:25 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:26 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:42 (Event String could not be retrieved) ......................... MEGATRON failed test systemlog Starting test: VerifyReferences ......................... MEGATRON passed test VerifyReferences Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : myhood Starting test: CrossRefValidation ......................... myhood passed test CrossRefValidation Starting test: CheckSDRefDom ......................... myhood passed test CheckSDRefDom Running enterprise tests on : myhood.fabstar81.com Starting test: Intersite ......................... myhood.fabstar81.com passed test Intersite Starting test: FsmoCheck ......................... myhood.fabstar81.com passed test FsmoCheck Z:\>[/code:1:75750681df] Dit is de dcdiag van zeus: [code:1:75750681df] Z:\>dcdiag Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site\MEGATRON Starting test: Connectivity ......................... MEGATRON passed test Connectivity Doing primary tests Testing server: Default-First-Site\MEGATRON Starting test: Replications ......................... MEGATRON passed test Replications Starting test: NCSecDesc ......................... MEGATRON passed test NCSecDesc Starting test: NetLogons ......................... MEGATRON passed test NetLogons Starting test: Advertising ......................... MEGATRON passed test Advertising Starting test: KnowsOfRoleHolders ......................... MEGATRON passed test KnowsOfRoleHolders Starting test: RidManager ......................... MEGATRON passed test RidManager Starting test: MachineAccount ......................... MEGATRON passed test MachineAccount Starting test: Services ......................... MEGATRON passed test Services Starting test: ObjectsReplicated ......................... MEGATRON passed test ObjectsReplicated Starting test: frssysvol ......................... MEGATRON passed test frssysvol Starting test: frsevent ......................... MEGATRON passed test frsevent Starting test: kccevent ......................... MEGATRON passed test kccevent Starting test: systemlog An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:22 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:23 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:24 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:24 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:25 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:26 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/06/2009 10:39:42 (Event String could not be retrieved) ......................... MEGATRON failed test systemlog Starting test: VerifyReferences ......................... MEGATRON passed test VerifyReferences Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : myhood Starting test: CrossRefValidation ......................... myhood passed test CrossRefValidation Starting test: CheckSDRefDom ......................... myhood passed test CheckSDRefDom Running enterprise tests on : myhood.fabstar81.com Starting test: Intersite ......................... myhood.fabstar81.com passed test Intersite Starting test: FsmoCheck ......................... myhood.fabstar81.com passed test FsmoCheck Z:\>[/code:1:75750681df]
Link naar reactie
De foutmelding in DNS op Megatron over het niet kunnen vinden van Zeus kun je negeren. Desnoods ruim je alle resten van de Zeus later op uit DNS. Dynamic updates instellen op de Megratron is een goed idee. Ik zou in een Windows only omgeving zelfs enkel Secure Dynamic updates toestaan. Megatron heeft idd alle rollen, dat leidt ik af uit de resultaten uit de dos-box die je als plaatje in deze post hebt geplakt. Daarin staat nl. te lezen dat de rol 'Domain' aan Megatron toebehoord. Zeus kan wel vinden dat ie nog domain naming master is, maar die lijkt toch al de kluts kwijt, dus daar zou ik niet teveel op vertrouwen. De DCDIAG test heb je volgens mij 2 keer tegen megatron aan gedraaid, wat de resultaten zijn identiek ("Testing server: Default-First-Site\MEGATRON"). Draai op Megraton nog een keer het commando: [code:1:0526f93e8b]dcdiag /a /v /f:c:\dcdiagoutput.txt[/code:1:0526f93e8b] Dit test alle DC's in je Site en schrijft uitgebreide info weg in de file [b:0526f93e8b]C:\dcdiagoutput.txt[/b:0526f93e8b] Hoe eerder je die Zeus eruit krijgt hoe beter. Die gooit nu alleen maar roet in het eten. Daarna is het wel weer zaak dat je naast Megatron een nieuwe DC neerzet, tenminste da's wel aan te raden voor minimale redundantie van AD.
Link naar reactie
commando gedraaid op megatron: [code:1:b9275d3879] Domain Controller Diagnosis Performing initial setup: * Verifying that the local machine megatron, is a DC. * Connecting to directory service on server megatron. * Collecting site info. * Identifying all servers. * Identifying all NC cross-refs. * Found 2 DC(s). Testing 2 of them. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site\ZEUS Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check ......................... ZEUS passed test Connectivity Testing server: Default-First-Site\MEGATRON Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check ......................... MEGATRON passed test Connectivity Doing primary tests Testing server: Default-First-Site\ZEUS Starting test: Replications * Replications Check [Replications Check,ZEUS] A recent replication attempt failed: From MEGATRON to ZEUS Naming Context: CN=Configuration,DC=myhood,DC=fabstar81,DC=com The replication generated an error (8614): The Active Directory cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime. The failure occurred at 2009-03-10 07:49:37. The last success occurred at 2008-02-02 19:57:06. 26553 failures have occurred since the last success. * Replication Latency Check DC=ForestDnsZones,DC=myhood,DC=fabstar81,DC=com Latency information for 4 entries in the vector were ignored. 4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). DC=DomainDnsZones,DC=myhood,DC=fabstar81,DC=com Latency information for 4 entries in the vector were ignored. 4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). CN=Schema,CN=Configuration,DC=myhood,DC=fabstar81,DC=com Latency information for 8 entries in the vector were ignored. 8 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). REPLICATION-RECEIVED LATENCY WARNING ZEUS: Current time is 2009-03-10 08:03:55. CN=Configuration,DC=myhood,DC=fabstar81,DC=com Last replication recieved from MEGATRON at 2008-02-02 19:57:06. WARNING: This latency is over the Tombstone Lifetime of 60 days! Latency information for 8 entries in the vector were ignored. 8 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). DC=myhood,DC=fabstar81,DC=com Latency information for 8 entries in the vector were ignored. 8 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). * Replication Site Latency Check ......................... ZEUS passed test Replications Test omitted by user request: Topology Test omitted by user request: CutoffServers Starting test: NCSecDesc * Security Permissions Check for DC=ForestDnsZones,DC=myhood,DC=fabstar81,DC=com (NDNC,Version 2) * Security Permissions Check for DC=DomainDnsZones,DC=myhood,DC=fabstar81,DC=com (NDNC,Version 2) * Security Permissions Check for CN=Schema,CN=Configuration,DC=myhood,DC=fabstar81,DC=com (Schema,Version 2) * Security Permissions Check for CN=Configuration,DC=myhood,DC=fabstar81,DC=com (Configuration,Version 2) * Security Permissions Check for DC=myhood,DC=fabstar81,DC=com (Domain,Version 2) ......................... ZEUS passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check ......................... ZEUS passed test NetLogons Starting test: Advertising The DC ZEUS is advertising itself as a DC and having a DS. The DC ZEUS is advertising as an LDAP server The DC ZEUS is advertising as having a writeable directory The DC ZEUS is advertising as a Key Distribution Center Warning: ZEUS is not advertising as a time server. ......................... ZEUS failed test Advertising Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com Role Domain Owner = CN=NTDS Settings,CN=ZEUS,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com Role PDC Owner = CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com Role Rid Owner = CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com Role Infrastructure Update Owner = CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com ......................... ZEUS passed test KnowsOfRoleHolders Starting test: RidManager * Available RID Pool for the Domain is 6605 to 1073741823 * megatron.myhood.fabstar81.com is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 3105 to 3604 * rIDPreviousAllocationPool is 3105 to 3604 * rIDNextRID: 3172 ......................... ZEUS passed test RidManager Starting test: MachineAccount * SPN found :LDAP/zeus.myhood.fabstar81.com/myhood.fabstar81.com * SPN found :LDAP/zeus.myhood.fabstar81.com * SPN found :LDAP/ZEUS * SPN found :LDAP/zeus.myhood.fabstar81.com/MYHOOD * SPN found :LDAP/2f8288d2-fca7-4362-935d-974d16e7acb2._msdcs.myhood.fabstar81.com * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/2f8288d2-fca7-4362-935d-974d16e7acb2/myhood.fabstar81.com * SPN found :HOST/zeus.myhood.fabstar81.com/myhood.fabstar81.com * SPN found :HOST/zeus.myhood.fabstar81.com * SPN found :HOST/ZEUS * SPN found :HOST/zeus.myhood.fabstar81.com/MYHOOD * SPN found :GC/zeus.myhood.fabstar81.com/myhood.fabstar81.com ......................... ZEUS passed test MachineAccount Starting test: Services * Checking Service: Dnscache * Checking Service: NtFrs * Checking Service: IsmServ * Checking Service: kdc * Checking Service: SamSs * Checking Service: LanmanServer * Checking Service: LanmanWorkstation * Checking Service: RpcSs * Checking Service: w32time * Checking Service: NETLOGON ......................... ZEUS passed test Services Test omitted by user request: OutboundSecureChannels Starting test: ObjectsReplicated ZEUS is in domain DC=myhood,DC=fabstar81,DC=com Checking for CN=ZEUS,OU=Domain Controllers,DC=myhood,DC=fabstar81,DC=com in domain DC=myhood,DC=fabstar81,DC=com on 2 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=ZEUS,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com in domain CN=Configuration,DC=myhood,DC=fabstar81,DC=com on 2 servers Object is up-to-date on all servers. ......................... ZEUS passed test ObjectsReplicated Starting test: frssysvol * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... ZEUS passed test frssysvol Starting test: frsevent * The File Replication Service Event log test ......................... ZEUS passed test frsevent Starting test: kccevent * The KCC Event log test Found no KCC errors in Directory Service Event log in the last 15 minutes. ......................... ZEUS passed test kccevent Starting test: systemlog * The System Event log test An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:03:34 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:05:04 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:06:35 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:08:05 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:09:35 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:11:05 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:12:35 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:14:05 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:15:35 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:17:05 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:18:35 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:20:05 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:21:35 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:23:06 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:24:36 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:26:06 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:27:36 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:29:06 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:30:36 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:32:07 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:33:37 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:35:07 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:36:37 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:38:07 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:39:37 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:41:07 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:42:37 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:44:07 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:45:37 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:47:09 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:48:39 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:50:09 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:51:39 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:53:09 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:54:39 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:56:09 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:57:39 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 07:59:09 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 08:00:39 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 08:02:09 (Event String could not be retrieved) An Error Event occured. EventID: 0xC0001B70 Time Generated: 03/10/2009 08:03:40 (Event String could not be retrieved) ......................... ZEUS failed test systemlog Test omitted by user request: VerifyReplicas Starting test: VerifyReferences The system object reference (serverReference) CN=ZEUS,OU=Domain Controllers,DC=myhood,DC=fabstar81,DC=com and backlink on CN=ZEUS,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com are correct. The system object reference (frsComputerReferenceBL) CN=ZEUS,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=myhood,DC=fabstar81,DC=com and backlink on CN=ZEUS,OU=Domain Controllers,DC=myhood,DC=fabstar81,DC=com are correct. The system object reference (serverReferenceBL) CN=ZEUS,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=myhood,DC=fabstar81,DC=com and backlink on CN=NTDS Settings,CN=ZEUS,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com are correct. ......................... ZEUS passed test VerifyReferences Test omitted by user request: VerifyEnterpriseReferences Testing server: Default-First-Site\MEGATRON Starting test: Replications * Replications Check * Replication Latency Check DC=ForestDnsZones,DC=myhood,DC=fabstar81,DC=com Latency information for 4 entries in the vector were ignored. 4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). DC=DomainDnsZones,DC=myhood,DC=fabstar81,DC=com Latency information for 4 entries in the vector were ignored. 4 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). CN=Schema,CN=Configuration,DC=myhood,DC=fabstar81,DC=com Latency information for 8 entries in the vector were ignored. 8 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). CN=Configuration,DC=myhood,DC=fabstar81,DC=com Latency information for 8 entries in the vector were ignored. 8 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). DC=myhood,DC=fabstar81,DC=com Latency information for 8 entries in the vector were ignored. 8 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC). * Replication Site Latency Check ......................... MEGATRON passed test Replications Test omitted by user request: Topology Test omitted by user request: CutoffServers Starting test: NCSecDesc * Security Permissions Check for DC=ForestDnsZones,DC=myhood,DC=fabstar81,DC=com (NDNC,Version 2) * Security Permissions Check for DC=DomainDnsZones,DC=myhood,DC=fabstar81,DC=com (NDNC,Version 2) * Security Permissions Check for CN=Schema,CN=Configuration,DC=myhood,DC=fabstar81,DC=com (Schema,Version 2) * Security Permissions Check for CN=Configuration,DC=myhood,DC=fabstar81,DC=com (Configuration,Version 2) * Security Permissions Check for DC=myhood,DC=fabstar81,DC=com (Domain,Version 2) ......................... MEGATRON passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check ......................... MEGATRON passed test NetLogons Starting test: Advertising The DC MEGATRON is advertising itself as a DC and having a DS. The DC MEGATRON is advertising as an LDAP server The DC MEGATRON is advertising as having a writeable directory The DC MEGATRON is advertising as a Key Distribution Center The DC MEGATRON is advertising as a time server The DS MEGATRON is advertising as a GC. ......................... MEGATRON passed test Advertising Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com Role Domain Owner = CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com Role PDC Owner = CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com Role Rid Owner = CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com Role Infrastructure Update Owner = CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com ......................... MEGATRON passed test KnowsOfRoleHolders Starting test: RidManager * Available RID Pool for the Domain is 6605 to 1073741823 * megatron.myhood.fabstar81.com is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 6105 to 6604 * rIDPreviousAllocationPool is 6105 to 6604 * rIDNextRID: 6131 ......................... MEGATRON passed test RidManager Starting test: MachineAccount * SPN found :LDAP/megatron.myhood.fabstar81.com/myhood.fabstar81.com * SPN found :LDAP/megatron.myhood.fabstar81.com * SPN found :LDAP/MEGATRON * SPN found :LDAP/megatron.myhood.fabstar81.com/MYHOOD * SPN found :LDAP/bf46623c-525e-4316-8f19-ccd017d25427._msdcs.myhood.fabstar81.com * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/bf46623c-525e-4316-8f19-ccd017d25427/myhood.fabstar81.com * SPN found :HOST/megatron.myhood.fabstar81.com/myhood.fabstar81.com * SPN found :HOST/megatron.myhood.fabstar81.com * SPN found :HOST/MEGATRON * SPN found :HOST/megatron.myhood.fabstar81.com/MYHOOD * SPN found :GC/megatron.myhood.fabstar81.com/myhood.fabstar81.com ......................... MEGATRON passed test MachineAccount Starting test: Services * Checking Service: Dnscache * Checking Service: NtFrs * Checking Service: IsmServ * Checking Service: kdc * Checking Service: SamSs * Checking Service: LanmanServer * Checking Service: LanmanWorkstation * Checking Service: RpcSs * Checking Service: w32time * Checking Service: NETLOGON ......................... MEGATRON passed test Services Test omitted by user request: OutboundSecureChannels Starting test: ObjectsReplicated MEGATRON is in domain DC=myhood,DC=fabstar81,DC=com Checking for CN=MEGATRON,OU=Domain Controllers,DC=myhood,DC=fabstar81,DC=com in domain DC=myhood,DC=fabstar81,DC=com on 2 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com in domain CN=Configuration,DC=myhood,DC=fabstar81,DC=com on 2 servers Authoritative attribute msDS-HasInstantiatedNCs on MEGATRON (writeable) usnLocalChange = 901244 LastOriginatingDsa = MEGATRON usnOriginatingChange = 901244 timeLastOriginatingChange = 2009-03-05 09:45:56 VersionLastOriginatingChange = 9 Out-of-date attribute msDS-HasInstantiatedNCs on ZEUS (writeable) usnLocalChange = 220331 LastOriginatingDsa = MEGATRON usnOriginatingChange = 16428 timeLastOriginatingChange = 2007-07-31 22:41:01 VersionLastOriginatingChange = 3 Authoritative attribute msDS-hasMasterNCs on MEGATRON (writeable) usnLocalChange = 901244 LastOriginatingDsa = MEGATRON usnOriginatingChange = 901244 timeLastOriginatingChange = 2009-03-05 09:45:56 VersionLastOriginatingChange = 11 Out-of-date attribute msDS-hasMasterNCs on ZEUS (writeable) usnLocalChange = 220310 LastOriginatingDsa = MEGATRON usnOriginatingChange = 12617 timeLastOriginatingChange = 2007-07-31 22:30:29 VersionLastOriginatingChange = 5 ......................... MEGATRON failed test ObjectsReplicated Starting test: frssysvol * The File Replication Service SYSVOL ready test File Replication Service's SYSVOL is ready ......................... MEGATRON passed test frssysvol Starting test: frsevent * The File Replication Service Event log test ......................... MEGATRON passed test frsevent Starting test: kccevent * The KCC Event log test Found no KCC errors in Directory Service Event log in the last 15 minutes. ......................... MEGATRON passed test kccevent Starting test: systemlog * The System Event log test An Error Event occured. EventID: 0xC0000411 Time Generated: 03/10/2009 07:33:00 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 07:34:23 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 07:34:23 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 07:34:24 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 07:34:25 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 07:34:26 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 07:34:26 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 07:34:27 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 07:34:28 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 07:34:44 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 08:01:07 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 08:01:08 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 08:01:08 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 08:01:09 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 08:01:10 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 08:01:11 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 08:01:12 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 08:01:12 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/10/2009 08:01:18 (Event String could not be retrieved) ......................... MEGATRON failed test systemlog Test omitted by user request: VerifyReplicas Starting test: VerifyReferences The system object reference (serverReference) CN=MEGATRON,OU=Domain Controllers,DC=myhood,DC=fabstar81,DC=com and backlink on CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com are correct. The system object reference (frsComputerReferenceBL) CN=MEGATRON,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=myhood,DC=fabstar81,DC=com and backlink on CN=MEGATRON,OU=Domain Controllers,DC=myhood,DC=fabstar81,DC=com are correct. The system object reference (serverReferenceBL) CN=MEGATRON,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=myhood,DC=fabstar81,DC=com and backlink on CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com are correct. ......................... MEGATRON passed test VerifyReferences Test omitted by user request: VerifyEnterpriseReferences Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : myhood Starting test: CrossRefValidation ......................... myhood passed test CrossRefValidation Starting test: CheckSDRefDom ......................... myhood passed test CheckSDRefDom Running enterprise tests on : myhood.fabstar81.com Starting test: Intersite Skipping site Default-First-Site, this site is outside the scope provided by the command line arguments provided. ......................... myhood.fabstar81.com passed test Intersite Starting test: FsmoCheck GC Name: \\megatron.myhood.fabstar81.com Locator Flags: 0xe00003fd PDC Name: \\megatron.myhood.fabstar81.com Locator Flags: 0xe00003fd Time Server Name: \\megatron.myhood.fabstar81.com Locator Flags: 0xe00003fd Preferred Time Server Name: \\megatron.myhood.fabstar81.com Locator Flags: 0xe00003fd KDC Name: \\megatron.myhood.fabstar81.com Locator Flags: 0xe00003fd ......................... myhood.fabstar81.com passed test FsmoCheck [/code:1:b9275d3879] :) wat een log. trouwens...op zeus krijg ik ook exchange niet gedeinstalleerd, ook omdat ie dus denkt dat ie nog eoa rol heeft. zal er ongetwijfeld mee te maken hebben. wel heb ik ook via een knowledge base artikel alles ook weer omgezet van exchange van zeus naar megatron (public folders etc.). ik neem aan dat als ik zeus straks uit het domein haal, ik wel alle verwijzingen van zeus (ÉN OPTIMUS) uit het domein kan cancellen. Megatron moet toch ooit een keer schoon worden :) thx voor so far trouwens :)
Link naar reactie
Je hebt iig een probleem: [code:1:7a8177e5ce]Role Domain Owner = CN=NTDS Settings,CN=MEGATRON,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com[/code:1:7a8177e5ce] MEGATRON vindt zichzelf Domain naming master. [code:1:7a8177e5ce]Role Domain Owner = CN=NTDS Settings,CN=ZEUS,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=myhood,DC=fabstar81,DC=com[/code:1:7a8177e5ce]Zeus is ook in de overtuiging dat hij Domain naming master is. Omdat je een seize van de rollen op Zeus hebt uitgevoerd MOET Zeus uit! Die houdt namelijk geen rekening met de seize actie en gooit roet in het eten. Een seize van een rol is éénmalig proces; bovendien seize je alleen rollen van oude DC's die uitstaan en NOOIT meer aangezet worden... Megatron lijkt verder wel in redelijke gezondheid te verkeren. Zet zeus uit en doe een metadata cleanup in ntdsutil.
Link naar reactie
ik denk dat er nog 1 probleempje is voordat ik zeus kan uitzetten. een profiel van een gebruiker (best groot) wordt niet helemaal overgezet nog naar de geupdate lokatie van het Mijn Documenten pad. Die nieuwe is uiteraard een share op megatron maar op de ene computer doet ie wel referren naar megatron, op de andere blijft ie naar zeus verwijzen. ben dus bang dat de redirects nog niet compleet gesynct zijn voordat ik zeus uitzet. er was een log melding dat er eoa folder niet meegekopieerd kon worden naar de nieuwe lokatie. die heb ik verwijderd maar nog steeds wordt de pad niet op alle pc's geupdate.
Link naar reactie
[quote:798f36dac5="fabstar81"]er was een log melding dat er eoa folder niet meegekopieerd kon worden naar de nieuwe lokatie. die heb ik verwijderd maar nog steeds wordt de pad niet op alle pc's geupdate.[/quote:798f36dac5]Dat komt omdat Zeus zichzelf nog steeds adverteerd als werkende DC's. Clients melden zich nu OF via Zeus OF via Megatron aan. Aangezien die twee het niet met elkaar eens zijn is het dus noodzakelijk dat je Zeus uitzet.
Link naar reactie
ja, het aanmelden van die gebruiker duurt ook mega-lang. om dus uiteindelijk de redirect niet goed te doen. ik kan die folder die hij probeert te kopieerren ook niet verwijderen uit het profiel. overigens gaat het aanmelden van die gebruiker ook niet zonder fouten. op de laptop bijvoorbeeld zegt ie gewoon dat hij het profiel niet kan kopieeren van megatron. terwijl hij dat op andere pc's zonder problemen doet, maar niet de redirect voldoende uitvoert door dus die paar bestanden die hij niet mee kan kopieeren. ik denk dat als ik die map kan verwijderen uit het profiel de aanmelding wel goed zal gaan. dit is de laatste gebruiker die zijn redirects nog moet uitvoeren. de rest ging wel goed. heel het profiel wordt helaas pas gekopieerd als de gebruiker zich aanmeldt. daarna denk ik dat ik zeus kan uitzetten. ik ben anders bang dat de hele folder "mijn documenten" niet juist wordt gekopieerd.
Link naar reactie

Om een reactie te plaatsen, moet je eerst inloggen

Gast
Reageer op dit topic

×   Geplakt als verrijkte tekst.   Herstel opmaak

  Er zijn maximaal 75 emoji toegestaan.

×   Je link werd automatisch ingevoegd.   Tonen als normale link

×   Je vorige inhoud werd hersteld.   Leeg de tekstverwerker

×   Je kunt afbeeldingen niet direct plakken. Upload of voeg afbeeldingen vanaf een URL in

×
×
  • Nieuwe aanmaken...