مشکل در ارتقاء 2003 به 2008 R2
سلام دوستان عزیز ما یک forest در سطح کشور داریم توی شبکمون بصورت parent -child شبکه من که در شهرستان هستش در واقع child دامین تهران هستش همه شبکه ها 2003 بودن که ما تصمیم به migration به 2008 R2 گرفتیم وقتی یک additional اضافه کردم تا پروسه انتقال رو شروع کنم بعد از نصب ادیشنال داخل dns سرور که نگاه کردم zone __msdcs که Replication اون در سطح فارست هستش توی دی ان اس ادیشنالم نبود در صورتیکه توی دی ان اس primary بودش خلاصه شروع کردم به اداکه کار و الانم حدود 2 ماهی هستش که کلا migration به 2008 R2 انجام شده و دو تا دی سی من توی شبکه child در واقع 2008 R2 شدن
ولی بازم زون __msdcs توی هیچ کدوم از دوتا دی ان اس هام نیستم ضمنا توی Site and services هم مدتی هستش که اسم دوتا سرورم توی شاخه server داخل سایت خودم نیست و ظاهرا توی Replication با دامین parent توی تهران به مشکل خوردن هرچند که مشکلی توی عملکرد دامینم فعلا وجود نداره میخواستم ببینم که راهی وجود داره که مشکلمو حل کنم و ایا ممکنه در اینده دامینم مشکل ساز شه چون میخوایبم بقیه child هارو هم بزودی به 2008 ارتقا بدیم میترسم همه جا همین مشکل پیش بیاد همه چی بهم بریزه لطفا راهنمایی کنید
62 پاسخ
دستور بالارو بازم با یوزر اینتر پرایز روی دی سی دومم که روی محیط hyper-v هستش زدم

دوستان فقط دقت بکنید برای من فقط replication با تهران مهمه چون با بقیه استانها روت نداریم یعنی داشتمی ولی الان دیگه نداریم وخطاهایی که برای اونها میفته طبیعیه چون اصلا باهاشون روت نداریم
دوست عزیز به این شکل عکس قرار ندید فایده ای نداره و بدتر مشکل ساز میکنه تحلیلش رو ، خواهشا بعد از اجرای دستورتون در اکتیودایرکتوری بعد از دستور کلمه Clip| رو وارد کنید و نتیجه رو در یک فایل Text قرار بدید و در موضوع به شکل درج کد از ویراشگر وارد کنید تا دقیقا بشه تحلیش کرد اینجوری نمیشه عزیز من. مثلا نتیجه دستور :
dcdiag |clip
اولین نکته این هست که شما ساختار DNS خودتون رو بررسی کنید ، همه child domain controller ها آدرس IP خودشون به عنوان Primary DNS و آدرس IP دامین کنترلر ثانوی یا همون Additional DC به عنوان Secondary DNS Server باید باشند و بر روی هر کدوم از این Domain Controller ها باید یک آدرس Forwarder برای DNS سروری که Parent Domain Controller هست ایجاد بشه تا درخواست ها به سمت سرور DNS اصلی ارجاع داده بشن ، بعد از اینکار حتما کش های DNS رو در طرفین پاک کنید و سرویس DNS رو Restart کنید. حتما دستور ipconfig //registerdns رو روی همه DC ها بعد از این عملیات انجام بدید.
حتما بررسی کنید که زمان سیستم های شما چه در Parent و چه در Child ها یکسان باشه ، با توجه به خطاهایی که مشاهده شد زمان سیستم های DC شما تفاوت فاحشی داره و حتی Replication ای که انجام شده به مدت چند سال هست انجام نشده از اولین باری که انجام شده و طبیعی هست که به قول دوستموم مهندس خلیفی Tombstone Lifetime شما تموم شده ، فعلا زمان های همه DC های مجموعه Forest رو یکپارچه کنید.
طبق خطایی که در نتیجه دستورات نمایش داده شده شما DC های پایین یا همون Child ها رو به عنوان Global Catalog قرار ندادین ، اولا بررسی کنید که سرورهای Child شما حداقل یکی از DC های مجموعشون دارای Global Catalog باشن ، فقط کافیه در کنسول Site and Services و فکر می کنم تنظیمات NTDS Settings مطمئن بشید که تیک قسمت Global Catalog خورده باشه که البته این مشکل از DNS هم می تونه باشه که با اقدام بالایی احتمال برطرف شدن مشکل وجود داره. مخصوصا این موارد رو در سرور بیرجند بررسی کنید.
اما در خصوص خطای آخر که فکر می کنم اصل مطلب باشه ، این خطا اعلام می کنه که شما آخری Replication ای که بین child ها و Parent داشتین بر می گرده به سال 2009 و الان سال 2014 هستیم ، از نظر اکتیودایرکتوری دیگه ساختار زیر مجموعه ای شما وجود ندارن که بخان Replicate هم بکنن ، راهکارش همونطوری که اعلام شد حذف و راه اندازی مجدد این ساختار برای Child ها هست همونطوری که مهندس خلیفی عرض کردند ، شما چطور اصلا متوجه این موضوع نشدید ؟ زمان 4 سال زمان کمی نیست اون هم در این سطح عملیاتی بزرگ !! البته نیازی نیست همه چیز حذف بشه ، شما Connection های Child Domain ها رو بایستی حذف کنید و مجددا Trust رو بصورت Two Way Transitive بین Parent و Child ایجاد کنید و همچنین DC های مشکل دار رو هم باید حذف کنید که چون ارتباط با دامین بالاسری ندارید باید از سویچ dcpromo /forceremoval استفاده کنید ، به هر حال موارد بالا رو انجام بدید و مجددا تست کنید ، فکر نمی کنم با موارد بالا مشکل حل بشه اما انجام بدید و مجددا گزارش بگیرید و در ادامه ارسال کنید.
اره ارتباطمون با نهران از لحاظ دی ان اس مشکلی نداره بیرجند به تهران کاندیشنال فورواردینگ شده و تهران به بیرجند دلیگیت شده من از زون _msdcs یه secondary توی بیرجند ساختم بنظرتون مشکلم حل میشه؟ اینکه وقتی ارتباطم با تهران قطع میشه کاربران مشکل authentication نداشته باشن چون الان دارن
manuall connection رو هم ساختم بین دی سی تهران و بیرجند و Replicate now روهم زدم ولی خطای زیر رو داد نام سرورهامو موقعیکه میخوام این کانکشن رو بسازم پیدا میکنه ولی توی شاخه سرور سایت خودم نشون نمیده چرا؟
دستور بالارو روی دی سی بعدیم با همون یوزر دامین ادمینم زدم
این دستور بالار ور با یوزر enterprise روی دی سی دامین خودم که سه تا رول دامینم روشه زدم
مهندس نصیری من توی پنجره domain and trust ببرسی کردم ظاهرا که trust fdk دوتا وجود داره ضمن اینکه من با اکانتیکه توی تهران ساخته شدهخ دارم توی سرور بیرجند لاگین میکنم بدون مشکل البته عکسشو امتحان نکردم ببینم میشه یا نه این دلیلی بر این نیسیت که از نظر trust مشکلی ندارم؟








من تصورم این هست که Trust شما با توجه به زمانیکه از Tombstone Lifetime شما گذشته دچار مشکل و منقضی شده باشه ، وارد کنسول Active Directory Domains and Trusts بشید و Trust رو مجددا بررسی کنید ، اگر امکانش هست این Trust رو یکبار بصورت کامل حذف کنید این Trust بصورت اتوماتیک قبلا ایجاد شده ، حالا ترجیجا از مدیر شبکه Parent درخواست کنید که یک Trust دو طرفه و Transitive از بالا با بیرجند ایجاد کنه ، اینکار فقط از بالا امکانپذیر هست ، بعد از این فکر میکنم مشکل اضافه کردن Connection شما هم مرتفع بشه ، هر چند این رو حتما با هماهنگی مدیر شبکه Parent ایجاد کنید.
دستور بالارو با یوزر دامین ادمین خودم زدم روی دی سی که سه تا رولم روشه

فقط اول خدمتت بگم مهندس جان این دستورات رو با یوزری که عضو enterprise بودم زدم وواست میفرستم بعدش این دتسئورات ور با یوزر domain admin دامین خودم زدم که اونم واست میفرستم الان
من با enterprise وارد شده بودم
لطفا دستور dcdiag /fix را روی DC که مشکل داره اجرا کنین و نتیجه را برای ما بفرستین.
آیا قبل از اینکه این Zone رو درست کنید، در Child Domain شما وجود نداشت؟
دو خطای زیر مجددا همون موارد بالا رو نمایش می دن با توجه به از بین رفتن Trust ها :
Replication access denied و is dead and should be removed from the directory.
فکر نمیکنم trust بینمون از بین رفته باشه چون من با اکانتهای تهران توی بیرجند لاگین میکنم
مهندس نصیری پیشنهادتون برای حل مشکل چیه؟
روی شاخه سرور داخل سایت خودم کلیک راست میکنم میزنم new server بعدش توی پنجره اسم دی سی هامو میدم خطامیده میگه این اسم قبلا وجود داشته عکساشو زیر گذاشتم چیکارکنم؟
سلام دوست عزیز اون تیک که توی دوتا دی سی دامین خودم خورده توی دامین parent در تهران باید بگم چک کنن ضمنا میشه بگید چجوری manually connection باید بزنم؟
CALLBACK MESSAGE: The following replication is in progress: From: 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil To : 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil CALLBACK MESSAGE: The following replication completed successfully: From: 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil To : 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil CALLBACK MESSAGE: SyncAll Finished. SyncAll terminated with no errors.

با کاربر Enterprise Admin وارد بشین و Zone رو به صورت Primary ایجاد کنین. لطفا تست کنین و خبر بدین
مرسی
دستور بالا هم که dcdiag هستش که با روی دی سی اصلیم زدم
توی دامین خودم البته وقتیکه ارتباطمون با تهران قطع میشه نمیتونیم لاگین کنیم ممکنه بخاطر این باشه که دامین ما گلوبال کاتلوگ نداره؟ البته بگم که جفت دی سی های ما گلوبال کاتالوگ بودن ولی احتمالا از وقتیکه اسمشون از توی شاخه سرور سایتمون توی site and services حذف شده دیگه دامینم گلوبال کاتالوگ نداره میشه کاری کرد که گلوبال بشن دوباره؟
دمت گرم مهندس نصیری فقط میشه بگی ایا راهی هست بتونم مشکل اضافه کردن نام سرورهامو توی شاخه سرور سایت بیرجند حل کنم و با manually connection بین بیرجند وتهارن مشکل replication رو حل کنم یا نه؟
CALLBACK MESSAGE: The following replication is in progress: From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil CALLBACK MESSAGE: Error issuing replication: 8453 (0x2105): Replication access was denied. From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil CALLBACK MESSAGE: SyncAll Finished. SyncAll reported the following errors: Error issuing replication: 8453 (0x2105): Replication access was denied. From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil
CALLBACK MESSAGE: The following replication is in progress: From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil CALLBACK MESSAGE: Error issuing replication: 8453 (0x2105): Replication access was denied. From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil CALLBACK MESSAGE: SyncAll Finished. SyncAll reported the following errors: Error issuing replication: 8453 (0x2105): Replication access was denied. From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil
اینو روی دی سی دیگم زدم که روی محیط hyper v hastesh
CALLBACK MESSAGE: The following replication is in progress: From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil CALLBACK MESSAGE: Error issuing replication: 8453 (0x2105): Replication access was denied. From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil CALLBACK MESSAGE: SyncAll Finished. SyncAll reported the following errors: Error issuing replication: 8453 (0x2105): Replication access was denied. From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil
همونطور که اشاره کردم بله می تونید بصورت دستی Connection برای ارتباط با Domain های دیگه در کنسول Sites and Services ایجاد کنید ، سرور خودتون رو می تونید براحتی GC کنید این رو هم باز با راست کلیک کردن بر روی NTDS Settings مربوط به Domain خودتون می تونید انجام بدید .
همونطور که مهندس نصیری گفتن، بهتره اول مشکل Time حل بشه.
دقت کنید که Time Zone، تنظیمات DST و همینطور Time، همه باید یکسان باشند و نه فقط Time.
همینطور تست کنین ببینین آیا با ایجاد Manual Replication Topology، مشکل شما برطرف میشه یا خیر.
همینطور در مورد مشکل Tombstone Lifetime، اگر مطمئن نیستین که آیا در آینده ارتباط بین شعبه تهران و مرکز مورد نظرتون Stable باشه، میتونین مقدار Tombstone Lifetime رو بالا ببرین که اصلا توصیه نمیشه.
Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = srv-birjand2 * Identified AD Forest. Ldap search capabality attribute search failed on server SRV, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-BANDARABBAS, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SEMNAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-URMYEH, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-BOJNORD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server DC, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-BOUSHEHR, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-KERMAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SANANDAG, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ZAHEDAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-AHVAZ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SHIRAZ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-GORGAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SERVERGILAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-MASHHAD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ZANJAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-YAZD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-YASUJ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-KARAJ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ARAK1, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SHAHROD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-CHALOOS, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ILAM, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-MAHABAD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SAQEZ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-DEZFUL, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-JIROFT, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SIRJAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ISFAHAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-TABRIZ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-LORESTAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SARI, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-HAMEDAN1, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SHAHRKORD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-GOLESTAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ARDEBIL, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-QOM, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-CHABAHAR1, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Done gathering initial info. Doing initial required tests Testing server: birjand\SRV-BIRJAND2 Starting test: Connectivity ......................... SRV-BIRJAND2 passed test Connectivity Doing primary tests Testing server: birjand\SRV-BIRJAND2 Starting test: Advertising Warning: SRV-BIRJAND2 has not finished promoting to be a GC. Check the event log for domains that cannot be replicated. Warning: SRV-BIRJAND2 is not advertising as a global catalog. Check that server finished GC promotion. Check the event log on server that enough source replicas for the GC are available. ......................... SRV-BIRJAND2 failed test Advertising Starting test: FrsEvent ......................... SRV-BIRJAND2 passed test FrsEvent Starting test: DFSREvent ......................... SRV-BIRJAND2 passed test DFSREvent Starting test: SysVolCheck ......................... SRV-BIRJAND2 passed test SysVolCheck Starting test: KccEvent A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:28:10 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:28:32 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:28:53 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:28:54 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:29:16 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:29:37 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:29:58 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:30:19 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:30:41 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:31:02 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:31:23 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:31:44 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:31:46 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:07 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:08 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:08 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:08 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:09 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:09 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:09 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:10 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:11 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:11 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:12 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:12 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:12 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:13 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:13 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:13 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:14 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:14 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:14 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:15 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:15 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:15 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:15 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:16 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:16 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:16 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:17 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:17 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:17 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:18 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:18 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:18 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:19 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:19 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:19 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:20 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:20 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:20 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:32:42 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:33:03 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:33:24 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:33:46 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:34:07 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:34:28 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:34:50 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. A warning event occurred. EventID: 0x80000786 Time Generated: 02/24/2014 11:35:11 Event String: The attempt to establish a replication link to a read-only directory partition with the following parameters failed. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x40000617 Time Generated: 02/24/2014 11:41:34 Event String: The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition. An event occurred. EventID: 0x4000062A Time Generated: 02/24/2014 11:41:34 Event String: Promotion of the local domain controller to a global catalog has been delayed because the directory partition occupancy requirements have not been met. The occupancy requirement level and current domain controller level are as follows. An event occurred. EventID: 0x40000456 Time Generated: 02/24/2014 11:41:34 Event String: Promotion of this domain controller to a global catalog will be delayed for the following interval. ......................... SRV-BIRJAND2 passed test KccEvent Starting test: KnowsOfRoleHolders ......................... SRV-BIRJAND2 passed test KnowsOfRoleHolders Starting test: MachineAccount ......................... SRV-BIRJAND2 passed test MachineAccount Starting test: NCSecDesc Ldap search capabality attribute search failed on server SRV-BIRJAND2, return value = 81 ......................... SRV-BIRJAND2 failed test NCSecDesc Starting test: NetLogons [SRV-BIRJAND2] User credentials does not have permission to perform this operation. The account used for this test must have network logon privileges for this machine's domain. ......................... SRV-BIRJAND2 failed test NetLogons Starting test: ObjectsReplicated ......................... SRV-BIRJAND2 passed test ObjectsReplicated Starting test: Replications [Replications Check,SRV-BIRJAND2] DsReplicaGetInfo(PENDING_OPS, NULL) failed, error 0x2105 "Replication access was denied." ......................... SRV-BIRJAND2 failed test Replications Starting test: RidManager ......................... SRV-BIRJAND2 passed test RidManager Starting test: Services ......................... SRV-BIRJAND2 passed test Services Starting test: SystemLog A warning event occurred. EventID: 0x000003F6 Time Generated: 02/24/2014 10:44:35 Event String: Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 10:46:33 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 10:46:47 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x000003F6 Time Generated: 02/24/2014 10:48:46 Event String: Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 10:51:48 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 10:51:59 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x000003F6 Time Generated: 02/24/2014 10:52:27 Event String: Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 10:57:00 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 10:57:11 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x000003F6 Time Generated: 02/24/2014 10:58:16 Event String: Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:02:13 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:02:24 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x000003FC Time Generated: 02/24/2014 11:05:13 Event String: Scope, 172.16.10.0, is 87 percent full with only 5 IP addresses remaining. A warning event occurred. EventID: 0x000003F6 Time Generated: 02/24/2014 11:07:02 Event String: Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded. An error event occurred. EventID: 0x00000406 Time Generated: 02/24/2014 11:07:51 Event String: The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:13:25 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:13:42 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x000003F6 Time Generated: 02/24/2014 11:14:07 Event String: Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:18:43 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:18:54 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x000003F6 Time Generated: 02/24/2014 11:20:40 Event String: Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:23:55 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:24:06 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:29:08 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:29:20 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:34:21 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:34:36 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x000003F6 Time Generated: 02/24/2014 11:38:17 Event String: Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:39:38 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 11:39:49 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. ......................... SRV-BIRJAND2 failed test SystemLog Starting test: VerifyReferences ......................... SRV-BIRJAND2 passed test VerifyReferences Running partition tests on : birjand Starting test: CheckSDRefDom ......................... birjand passed test CheckSDRefDom Starting test: CrossRefValidation ......................... birjand passed test CrossRefValidation Running partition tests on : Schema Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Running partition tests on : Configuration Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Running partition tests on : ghazvin Starting test: CheckSDRefDom ......................... ghazvin passed test CheckSDRefDom Starting test: CrossRefValidation This cross-ref has a non-standard dNSRoot attribute. Cross-ref DN: CN=ghazvin,CN=Partitions,CN=Configuration,DC=Ghazae,DC=mil nCName attribute (Partition name): DC=ghazvin,DC=Ghazae,DC=mil Bad dNSRoot attribute: server.ghazvin.ghazae.mil Check with your network administrator to make sure this dNSRoot attribute is correct, and if not please change the attribute to the value below. dNSRoot should be: ghazvin.Ghazae.mil ......................... ghazvin passed test CrossRefValidation Running partition tests on : DomainDnsZones Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Starting test: CrossRefValidation This cross-ref has a non-standard dNSRoot attribute. Cross-ref DN: CN=c4b86287-12b3-4279-aed1-cbe9a3ea43b6,CN=Partitions,CN=Configuration,DC=Ghazae,DC=mil nCName attribute (Partition name): DC=DomainDnsZones,DC=bandarabbas,DC=Ghazae,DC=mil Bad dNSRoot attribute: srv-bandarabbas.bandarabbas.Ghazae.mil Check with your network administrator to make sure this dNSRoot attribute is correct, and if not please change the attribute to the value below. dNSRoot should be: DomainDnsZones.bandarabbas.Ghazae.mil It appears this partition (DC=DomainDnsZones,DC=bandarabbas,DC=Ghazae,DC=mil) failed to get completely created. This cross-ref (CN=c4b86287-12b3-4279-aed1-cbe9a3ea43b6,CN=Partitions,CN=Configuration,DC=Ghazae,DC=mil) is dead and should be removed from the directory. ......................... DomainDnsZones failed test CrossRefValidation Running partition tests on : DomainDnsZones Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Starting test: CrossRefValidation This cross-ref has a non-standard dNSRoot attribute. Cross-ref DN: CN=67238b63-70f7-4e66-aaed-9f0326055ede,CN=Partitions,CN=Configuration,DC=Ghazae,DC=mil nCName attribute (Partition name): DC=DomainDnsZones,DC=shahrekord,DC=Ghazae,DC=mil Bad dNSRoot attribute: srv-shahrekord.shahrekord.Ghazae.mil Check with your network administrator to make sure this dNSRoot attribute is correct, and if not please change the attribute to the value below. dNSRoot should be: DomainDnsZones.shahrekord.Ghazae.mil It appears this partition (DC=DomainDnsZones,DC=shahrekord,DC=Ghazae,DC=mil) failed to get completely created. This cross-ref (CN=67238b63-70f7-4e66-aaed-9f0326055ede,CN=Partitions,CN=Configuration,DC=Ghazae,DC=mil) is dead and should be removed from the directory. ......................... DomainDnsZones failed test CrossRefValidation Running enterprise tests on : Ghazae.mil Starting test: LocatorCheck ......................... Ghazae.mil passed test LocatorCheck Starting test: Intersite ......................... Ghazae.mil passed test Intersite
چجوری بفهمم با کدوم دی سی authenticate mishan?
لطفا مراحل بالا رو فراموش نکنید انجام بدید و نتیجه رو گزارش کنید ، اول از همه بصورت گرافیکی وارد کنسول Sites and Services بشید و وارد NTDS Settings مربوط به Parent DC بشید و روی Connection ای که ایجاد شده راست کلیک و گزینه Replicate Now رو بزنید و ببینید که خطایی صادر میشه یا خیر ، این بصورت گرافیکی بود اما بصورت دستی و دستوری رو با استفاده از repadmin //syncall انجام بدید و نتیجه رو گزارش کنید ، بر اینکه بتونید یک Connection برای Replication بین دومین هاتون بصورت دستی ایجاد کنید مراحل زیر رو دنبال کنید :
- وارد کنسول Sites and Services بشید.
- وارد قسمت NTDS Settings مربوط به Domain Controller ای که می خاین باهاش Replicate کنید بشید.
- راست کلیک کنید در فضای خالی و گزینه New Active Directory Connection رو انتخاب کنید.
- از قسمت Find Domain Controllers دامین کنترلری که می خاین باهاش Replicate کنید رو پیدا کنید.
- از قسمت New Object-Connection یک اسم برای این Connection انتخاب کنید و بعد Replicate رو بزنید.
از آنجایی که Trust شما از بین رفته، چک کنین ببینین میتونین از تهران به تنظیمات DNS دامین خودتون دسترسی داشته باشین یا نه. به Enterprise Admin که در تهران مستقر هست بگین این رو تست کنه. در صورتی که موفق به برقراری ارتباط شد، از ایشان بخواین که Zone مربوط به msdcs_ رو به صورت Primary در DNS شما ایجاد کنه.
به نظر میاد که شما به مشکل Tombstone Lifetime برخوردین. با توجه به اینکه این مشکل باعث میشه دیگه DC های شما برای Replication به هم Trust نداشته باشن.این مشکل معمولا به Disjoin و Rejoin برطرف میشه.ولی در مورد مشکل شما، چون سرورهای شما همگی DC هستن، ترجیحا بهتره از این روش استفاده نکنید.همچنین احتمال میدم مشکل عدم ایجاد Replication در قسمت Sites & Services هم همین موضوع باشه.پیشنهاد میکنم برای درک بهتر مفهوم Tombstone Lifetime به مقاله من در لینک زیر مراجعه کنین.
سلام گزارش اجرای Repadmin /syncall رو روی دوتا دی سی شبکه خودم رو واستنون فرستادم نتیجه dcdiag رو هم میفرستم
دستور رو به شکل زیر وارد کن و بعد یه فایل Notepad باز کن و Paste کن :
repadmin /syncall |Clip
سلام دوستان من با اینکه از زون _msdcs تهران توی بیرجند یه secondary ساختم ولی بازهم اگه ارتباطمون با تهران قطع بشه کاربرای دامینم مشکل authentication دارنو لاگین نمیکنن و فولدری که براشون روی دی سی شیر کردم نمیتونن باز کنن بنظرتون چجوری مشکل رو حل کنم و مشکل مال چی میتونه باشه؟
مهندس نصیری چی شد؟
با حساب کاربری Enterprise Admin وارد شده بودین یا با Domain Admin؟
به Root Admin در تهران بگین که از اونجا ببینه میتونه DNS شما رو باز کنه یا نه. اگر میتونه باز کنه، از اونجا این Zone رو به صورت Primary ایجاد کنه
CALLBACK MESSAGE: The following replication is in progress: From: 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil To : 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil CALLBACK MESSAGE: The following replication completed successfully: From: 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil To : 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil CALLBACK MESSAGE: SyncAll Finished. SyncAll terminated with no errors.
عزیز من اگر با یوزرهای دومین های دیگه Login می کردن تا حالا خوب Cache شده بوده و الان اجبار شده که از domain اصلی برداشت کنن ، الان این کاربری که می گین نمیتونه Login کنه تو خود domain شماست یا تو Parent هست؟
دوستان بعد این دستوراتیکه گفتین زدم همین dcdiag وrepadmin /syncall هیچ کدوم از یورزهام نمیتونن لاگین کنن میگه یوزر پسوردشون اشتباهه ریست پسورد هم میکنم نمیتونن یوزر جدید هم میسازم نمیتونن لطفا سریع کمکم کنید
CALLBACK MESSAGE: The following replication is in progress: From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil CALLBACK MESSAGE: Error issuing replication: 8453 (0x2105): Replication access was denied. From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil CALLBACK MESSAGE: SyncAll Finished. SyncAll reported the following errors: Error issuing replication: 8453 (0x2105): Replication access was denied. From: 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil To : 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil
CALLBACK MESSAGE: The following replication is in progress: From: 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil To : 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil CALLBACK MESSAGE: The following replication completed successfully: From: 7cb4f0db-1125-426a-a872-ea1adb192517._msdcs.Ghazae.mil To : 6fc9a7c0-2edf-4994-b760-4869ceae01d8._msdcs.Ghazae.mil CALLBACK MESSAGE: SyncAll Finished. SyncAll terminated with no errors.
این رو روی دی سی زدم که سه تا رول دامینم روشه
دوست عزیز عرض کردم لطفا عکس نفرستید ، متن خروجی دستور رو طبق دستوری که قبلا گفتم خروجی بگیرید در یک فایل text و بعد از وبرایشگر به جای اینکه عکس رو انتخاب کنید کد رو انتخاب کنید و بعد داخل کد خروجی دستورات رو نمایش بدید که منظم باشه بشه داخلش جستجو کرد ، موفق باشید.
کافیه توی CMD دستور زیر رو وارد کنید تا DC ای که بهش وارد میشید رو بهتون نمایش بده :
echo %LOGONSERVER%
ضمنا مشکل تیم هم نداریم همه چی بین ما و تهران از نظر تیم و تیم زون یکسانه
نتیجه دستور dcdiag /fix در بالا نوشتم
بعد از اجرای دستور به فرمتی که شما گفتی چجوری توی فایل تکست سیوش کنم چون بعد اجرا هیچ چیزی ظاهر نمیشه
؟!!
من اینطوری اجراش کردم repadmin /syncall >repadmin1
بعدش زدم
notepad repadmin1
وخروجی دستور توی فایل تکست با نام repadmin1 ذخیره شد اینجوری خوبه؟
قاعدتا شما نباید مشکلی داشته باشید ، اول یک تماس با مدیر شبکه کلیتون داشته باشید و مشکل رو در میون بزارید ببینید آیا اونها هم از وجود چنین مشکلاتی برخوردار هستند یا خیر ، ثانیا اگر کاربرای شما قرار هست به دومین بیرجند Login کنن با این تفاسیر نباید مشکلی داشته باشن ، شما بررسی کنید که کاربرای شما دارن از چه DC ای برای ورود به سیستمشون استفاده می کنن .
روی سرورهای Domain Controller از قسمت System Properties و قسمت Computer Name بررسی کنید که در Change Name و قسمت More تیک گزینه Change Primary DNS Suffix When Domain Membership Changes حتما خورده باشه روی همه Domain Controller های Child و Parent از طرفی اگر دیدید که با اینکار Connection های Replication بین سایت های شما ایجاد نشدن بصورت دستی در کنسول Sites and Services در هر کدوم از سایت هایی که لازم هست با جای دیگه Replication داشته باشه حتما Manually Connection رو ایجاد کنید ، برای اینکه مطمئن بشید فعلا در شبکه مشکلی وجود نداره ، دستور DCDIAG رو اجرا کنید و نتیجه رو اینجا قرار بدید و همچنین دستور repadmin //syncall رو هم اجرا کنید و نتیجه رو اعلام کنید ، این دو دستور رو بر روی DC هایی که فکر می کنید مشکل دارند اجرا کنید.
میخواستم بسازم این پیغام رو میده

تنظیمات دی ان اس هم درست بود و ارتباط دی انس مشکلی نداره
Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = srv-birjand2 * Identified AD Forest. Ldap search capabality attribute search failed on server SRV, return value =81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-BANDARABBAS, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SEMNAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-URMYEH, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-BOJNORD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server DC, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-BOUSHEHR, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-KERMAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SANANDAG, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ZAHEDAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-AHVAZ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SHIRAZ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-GORGAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SERVERGILAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-MASHHAD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ZANJAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-YAZD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-YASUJ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-KARAJ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ARAK1, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SHAHROD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-CHALOOS, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ILAM, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-MAHABAD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SAQEZ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-DEZFUL, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-JIROFT, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SIRJAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ISFAHAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-TABRIZ, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-LORESTAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SARI, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-HAMEDAN1, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-SHAHRKORD, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-GOLESTAN, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-ARDEBIL, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-QOM, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Ldap search capabality attribute search failed on server SRV-CHABAHAR1, return value = 81 Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error. Done gathering initial info. Doing initial required tests Testing server: birjand\SRV-BIRJAND2 Starting test: Connectivity ......................... SRV-BIRJAND2 passed test Connectivity Doing primary tests Testing server: birjand\SRV-BIRJAND2 Starting test: Advertising Warning: SRV-BIRJAND2 has not finished promoting to be a GC. Check the event log for domains that cannot be replicated. Warning: SRV-BIRJAND2 is not advertising as a global catalog. Check that server finished GC promotion. Check the event log on server that enough source replicas for the GC are available. ......................... SRV-BIRJAND2 failed test Advertising Starting test: FrsEvent ......................... SRV-BIRJAND2 passed test FrsEvent Starting test: DFSREvent ......................... SRV-BIRJAND2 passed test DFSREvent Starting test: SysVolCheck ......................... SRV-BIRJAND2 passed test SysVolCheck Starting test: KccEvent An error event occurred. EventID: 0xC0000748 Time Generated: 02/24/2014 09:56:02 Event String: This is the replication status for the following directory partition on this directory server. An error event occurred. EventID: 0xC0000748 Time Generated: 02/24/2014 09:56:02 Event String: This is the replication status for the following directory partition on this directory server. A warning event occurred. EventID: 0x80000829 Time Generated: 02/24/2014 09:56:02 Event String: This directory partition has not been backed up since at least the following number of days. An error event occurred. EventID: 0xC0000748 Time Generated: 02/24/2014 09:56:02 Event String: This is the replication status for the following directory partition on this directory server. An error event occurred. EventID: 0xC0000748 Time Generated: 02/24/2014 09:56:02 Event String: This is the replication status for the following directory partition on this directory server. An error event occurred. EventID: 0xC0000748 Time Generated: 02/24/2014 09:56:02 Event String: This is the replication status for the following directory partition on this directory server. An error event occurred. EventID: 0xC0000748 Time Generated: 02/24/2014 09:56:02 Event String: This is the replication status for the following directory partition on this directory server. An error event occurred. EventID: 0xC0000748 Time Generated: 02/24/2014 09:56:02 Event String: This is the replication status for the following directory partition on this directory server. An error event occurred. EventID: 0xC0000748 Time Generated: 02/24/2014 09:56:02 Event String: This is the replication status for the following directory partition on this directory server. An error event occurred. EventID: 0xC0000748 Time Generated: 02/24/2014 09:56:02 Event String: This is the replication status for the following directory partition on this directory server. An error event occurred. EventID: 0xC0000748 Time Generated: 02/24/2014 09:56:02 Event String: This is the replication status for the following directory partition on this directory server. ......................... SRV-BIRJAND2 failed test KccEvent Starting test: KnowsOfRoleHolders ......................... SRV-BIRJAND2 passed test KnowsOfRoleHolders Starting test: MachineAccount ......................... SRV-BIRJAND2 passed test MachineAccount Starting test: NCSecDesc Ldap search capabality attribute search failed on server SRV-BIRJAND2, return value = 81 ......................... SRV-BIRJAND2 failed test NCSecDesc Starting test: NetLogons ......................... SRV-BIRJAND2 passed test NetLogons Starting test: ObjectsReplicated ......................... SRV-BIRJAND2 passed test ObjectsReplicated Starting test: Replications REPLICATION-RECEIVED LATENCY WARNING SRV-BIRJAND2: Current time is 2014-02-24 09:51:27. CN=Schema,CN=Configuration,DC=Ghazae,DC=mil Last replication received from SRV-CHALOOS at 2011-08-13 09:53:07 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-SHIRAZ at 2009-03-30 17:25:57 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-YAZD at 2010-03-18 04:21:57 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-DEZFUL at 2011-09-11 10:09:59 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-QOM at 2013-10-03 11:16:06 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-MAHABAD at 2011-08-29 14:25:11 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-URMYEH at 2009-01-28 20:28:58 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-SAQEZ at 2011-08-30 09:41:43 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SERVERGILAN at 2011-08-08 04:35:53 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-YASUJ at 2010-03-18 04:22:05 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ZANJAN at 2011-08-08 04:35:58 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ISFAHAN at 2012-01-08 12:23:34 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from DC at 2009-01-29 02:25:52 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ARDEBIL at 2013-06-17 13:17:08 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-BOJNORD at 2009-01-28 20:29:00 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ARAK1 at 2011-08-08 13:23:53 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-TABRIZ at 2012-07-14 16:26:25 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV at 2011-08-08 01:11:57 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-KARAJ at 2011-08-08 04:35:31 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-GORGAN at 2010-03-18 04:22:05 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-CHABAHAR1 at 2014-01-08 08:26:02 Last replication received from SRV-AHVAZ at 2009-03-30 17:25:56 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-SHAHROD at 2011-08-10 11:23:56 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ZAHEDAN at 2009-03-30 17:25:57 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-SANANDAG at 2010-11-22 04:28:47 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-SEMNAN at 2009-03-30 17:25:42 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-GOLESTAN at 2013-03-04 16:18:17 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-BANDARABBAS at 2009-01-28 17:36:43 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-MASHHAD at 2011-08-08 04:35:58 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-LORESTAN at 2012-09-18 12:21:54 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-BOUSHEHR at 2009-03-30 02:25:43 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ILAM at 2011-08-28 16:24:32 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-JIROFT at 2011-10-09 09:26:33 WARNING: This latency is over the Tombstone Lifetime of 60 days! CN=Configuration,DC=Ghazae,DC=mil Last replication received from SRV-CHALOOS at 2011-08-13 10:09:30 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-SHIRAZ at 2009-03-30 17:25:55 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-YAZD at 2010-03-18 04:21:09 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-DEZFUL at 2011-09-11 13:01:30 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-QOM at 2013-10-03 11:16:06 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-MAHABAD at 2011-08-29 14:49:11 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-URMYEH at 2009-01-28 20:28:22 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-SAQEZ at 2011-08-30 09:44:33 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SERVERGILAN at 2011-01-10 01:26:56 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-YASUJ at 2010-03-18 04:21:30 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ZANJAN at 2011-08-08 04:35:21 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ISFAHAN at 2012-01-08 12:26:51 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from DC at 2009-01-29 02:25:47 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ARDEBIL at 2013-06-17 13:37:43 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-BOJNORD at 2009-01-28 20:28:42 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ARAK1 at 2011-08-08 13:23:53 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-TABRIZ at 2012-07-14 16:26:25 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV at 2011-01-26 05:07:21 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-KARAJ at 2011-08-08 04:35:17 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-GORGAN at 2010-03-18 04:21:19 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-CHABAHAR1 at 2014-01-08 08:38:18 Last replication received from SRV-AHVAZ at 2009-03-30 17:25:49 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-SHAHROD at 2011-08-10 11:23:53 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ZAHEDAN at 2009-03-30 17:25:54 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-SANANDAG at 2010-11-22 04:27:59 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-SEMNAN at 2009-03-30 17:25:38 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-GOLESTAN at 2013-03-04 16:17:51 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-BANDARABBAS at 2009-01-28 17:36:43 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-MASHHAD at 2011-01-12 04:19:44 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-LORESTAN at 2012-09-18 12:28:27 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-BOUSHEHR at 2009-03-30 02:25:30 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-ILAM at 2011-08-28 16:35:20 WARNING: This latency is over the Tombstone Lifetime of 60 days! Last replication received from SRV-JIROFT at 2011-10-09 09:26:33 WARNING: This latency is over the Tombstone Lifetime of 60 days! DC=qazwin,DC=Ghazae,DC=mil Last replication received from DC at 2012-06-09 17:41:02 WARNING: This latency is over the Tombstone Lifetime of 60 days! DC=shahrood,DC=Ghazae,DC=mil Last replication received from SRV-SHAHROD at 2014-01-06 04:29:31 DC=tabriz0,DC=Ghazae,DC=mil Last replication received from SRV-TABRIZ at 2012-07-14 16:26:26 WARNING: This latency is over the Tombstone Lifetime of 60 days! DC=lorestan,DC=Ghazae,DC=mil Last replication received from SRV-LORESTAN at 2012-09-18 12:21:55 WARNING: This latency is over the Tombstone Lifetime of 60 days! DC=gorgan1,DC=Ghazae,DC=mil Last replication received from SRV-GOLESTAN at 2013-03-04 16:18:38 WARNING: This latency is over the Tombstone Lifetime of 60 days! DC=ardebil1,DC=Ghazae,DC=mil Last replication received from SRV-ARDEBIL at 2013-06-17 13:17:08 WARNING: This latency is over the Tombstone Lifetime of 60 days! DC=qom1,DC=Ghazae,DC=mil Last replication received from SRV-QOM at 2013-10-03 11:16:09 WARNING: This latency is over the Tombstone Lifetime of 60 days! DC=chabahar1,DC=Ghazae,DC=mil Last replication received from SRV-CHABAHAR1 at 2014-01-08 08:41:41 REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=bandarabbas,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2009-01-28 17:19:41 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=urmyeh,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2009-01-28 20:08:48 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=bojnord,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2009-01-28 20:23:06 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=qazwin,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2009-01-29 02:16:35 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=boushehr,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2009-03-30 02:07:48 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=zahedan,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2009-03-30 16:55:10 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=semnan,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2009-03-30 17:03:25 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=ahvaz,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2009-03-30 17:06:18 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=shiraz,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2009-03-30 17:24:08 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=yazd,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2010-03-18 04:00:00 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=gorgan,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2010-03-18 04:12:01 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=yasuj,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2010-03-18 04:20:32 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=qom,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2010-07-08 00:40:39 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=sanandag,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2010-11-22 03:57:26 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=rasht,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2011-01-10 00:46:00 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=mashhad,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2011-01-12 03:52:26 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=kermanshah,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2011-01-26 04:43:50 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=karaj,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2011-08-08 04:07:21 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=zanjan-new,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2011-08-08 04:26:21 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=arak,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2011-08-08 12:45:26 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=shahrood,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2011-08-10 11:15:24 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=tabriz0,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2012-07-14 16:00:03 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=gorgan1,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2013-03-04 15:59:39 Check if source site has an elected ISTG running. Check replication from source site to this server. REPLICATION-RECEIVED LATENCY WARNING Source site: CN=NTDS Site Settings,CN=ardebil,CN=Sites,CN=Configuration,DC=Ghazae,DC=mil Current time: 2014-02-24 10:02:05 Last update time: 2013-06-17 13:37:25 Check if source site has an elected ISTG running. Check replication from source site to this server. ......................... SRV-BIRJAND2 passed test Replications Starting test: RidManager ......................... SRV-BIRJAND2 passed test RidManager Starting test: Services ......................... SRV-BIRJAND2 passed test Services Starting test: SystemLog A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:02:33 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:02:33 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x000003FC Time Generated: 02/24/2014 09:05:05 Event String: Scope, 172.16.10.0, is 87 percent full with only 5 IP addresses remaining. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:07:35 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:07:35 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. An error event occurred. EventID: 0x00000457 Time Generated: 02/24/2014 09:11:04 Event String: Driver hp LaserJet 1320 PCL 6 required for printer hp LaserJet 1320 PCL 6 is unknown. Contact the administrator to install the driver before you log in again. An error event occurred. EventID: 0x00000457 Time Generated: 02/24/2014 09:11:06 Event String: Driver CutePDF Writer required for printer CutePDF Writer is unknown. Contact the administrator to install the driver before you log in again. An error event occurred. EventID: 0x00000457 Time Generated: 02/24/2014 09:11:08 Event String: Driver PDF-XChange 4.0 required for printer PDF-XChange 4.0 is unknown. Contact the administrator to install the driver before you log in again. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:12:38 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:12:38 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. An error event occurred. EventID: 0x00000457 Time Generated: 02/24/2014 09:13:19 Event String: Driver hp LaserJet 1320 PCL 5 required for printer !!192.168.3.16!hp LaserJet 1320 PCL 5 is unknown. Contact the administrator to install the driver before you log in again. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:17:40 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:17:40 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000168D Time Generated: 02/24/2014 09:20:12 Event String: The following DNS server that is authoritative for the DNS domain controller locator records of this domain controller does not support dynamic DNS updates: A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:22:42 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:22:42 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. An error event occurred. EventID: 0x00000457 Time Generated: 02/24/2014 09:25:29 Event String: Driver hp LaserJet 1320 PCL 5 required for printer !!192.168.3.16!hp LaserJet 1320 PCL 5 is unknown. Contact the administrator to install the driver before you log in again. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:27:43 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:27:44 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x00000458 Time Generated: 02/24/2014 09:28:03 Event String: The Group Policy Client Side Extension Folder Redirection was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:28:04 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:28:21 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:33:23 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. An error event occurred. EventID: 0xC0002711 Time Generated: 02/24/2014 09:33:24 Event String: Unable to start a DCOM Server: {F87B28F1-DA9A-4F35-8EC0-800EFCF26B83} as /. The error: A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:33:34 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x00001795 Time Generated: 02/24/2014 09:37:21 Event String: The program lsass.exe, with the assigned process ID 492, could not authenticate locally by using the target name LDAP/6fc9a7c0-2edf- 4994-b760-4869ceae01d8._msdcs.Ghazae.mil. The target name used is not valid. A target name should refer to one of the local computer names, for example, the DNS host name. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:38:36 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:38:48 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:43:49 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:44:03 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x000003F6 Time Generated: 02/24/2014 09:46:04 Event String: Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:49:04 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:49:14 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:54:16 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:54:27 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:59:29 Event String: Windows failed to apply the Internet Explorer Zonemapping settings. Internet Explorer Zonemapping settings might have its own log file. Please click on the "More information" link. A warning event occurred. EventID: 0x0000043D Time Generated: 02/24/2014 09:59:41 Event String: Windows failed to apply the Group Policy Shortcuts settings. Group Policy Shortcuts settings might have its own log file. Please click on the "More information" link. ......................... SRV-BIRJAND2 failed test SystemLog Starting test: VerifyReferences ......................... SRV-BIRJAND2 passed test VerifyReferences Running partition tests on : birjand Starting test: CheckSDRefDom ......................... birjand passed test CheckSDRefDom Starting test: CrossRefValidation ......................... birjand passed test CrossRefValidation Running partition tests on : Schema Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Running partition tests on : Configuration Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Running partition tests on : ghazvin Starting test: CheckSDRefDom ......................... ghazvin passed test CheckSDRefDom Starting test: CrossRefValidation This cross-ref has a non-standard dNSRoot attribute. Cross-ref DN: CN=ghazvin,CN=Partitions,CN=Configuration,DC=Ghazae,DC=mil nCName attribute (Partition name): DC=ghazvin,DC=Ghazae,DC=mil Bad dNSRoot attribute: server.ghazvin.ghazae.mil Check with your network administrator to make sure this dNSRoot attribute is correct, and if not please change the attribute to the value below. dNSRoot should be: ghazvin.Ghazae.mil ......................... ghazvin passed test CrossRefValidation Running partition tests on : DomainDnsZones Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Starting test: CrossRefValidation This cross-ref has a non-standard dNSRoot attribute. Cross-ref DN: CN=c4b86287-12b3-4279- aed1-cbe9a3ea43b6,CN=Partitions,CN=Configuration,DC=Ghazae,DC=mil nCName attribute (Partition name): DC=DomainDnsZones,DC=bandarabbas,DC=Ghazae,DC=mil Bad dNSRoot attribute: srv-bandarabbas.bandarabbas.Ghazae.mil Check with your network administrator to make sure this dNSRoot attribute is correct, and if not please change the attribute to the value below. dNSRoot should be: DomainDnsZones.bandarabbas.Ghazae.mil It appears this partition (DC=DomainDnsZones,DC=bandarabbas,DC=Ghazae,DC=mil) failed to get completely created. This cross-ref (CN=c4b86287-12b3-4279- aed1-cbe9a3ea43b6,CN=Partitions,CN=Configuration,DC=Ghazae,DC=mil) is dead and should be removed from the directory. ......................... DomainDnsZones failed test CrossRefValidation Running partition tests on : DomainDnsZones Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Starting test: CrossRefValidation This cross-ref has a non-standard dNSRoot attribute. Cross-ref DN: CN=67238b63-70f7-4e66- aaed-9f0326055ede,CN=Partitions,CN=Configuration,DC=Ghazae,DC=mil nCName attribute (Partition name): DC=DomainDnsZones,DC=shahrekord,DC=Ghazae,DC=mil Bad dNSRoot attribute: srv-shahrekord.shahrekord.Ghazae.mil Check with your network administrator to make sure this dNSRoot attribute is correct, and if not please change the attribute to the value below. dNSRoot should be: DomainDnsZones.shahrekord.Ghazae.mil It appears this partition (DC=DomainDnsZones,DC=shahrekord,DC=Ghazae,DC=mil) failed to get completely created. This cross-ref (CN=67238b63-70f7-4e66- aaed-9f0326055ede,CN=Partitions,CN=Configuration,DC=Ghazae,DC=mil) is dead and should be removed from the directory. ......................... DomainDnsZones failed test CrossRefValidation Running enterprise tests on : Ghazae.mil Starting test: LocatorCheck ......................... Ghazae.mil passed test LocatorCheck Starting test: Intersite ......................... Ghazae.mil passed test Intersite
ضمنا هنوز نتونستم اسم سرورهامو توی شاخه سرور سایت بیرجند اضافه کنم بصورت دستی و کانکشن هاشو بسازم بخاطر خطاهایی که بالا عکسشسو گذاشتم واسه اون میشه کاری کرد؟
آیا توی DNS ، شما Forwarder یا Conditionl Forwarder به سمت تهران دارین؟
میتونین Zone مربوط بهmsdcs_ رو به صورت دستی ایجاد کنین.
معمولا خودش Record های لازم را درست میکنه. اگر درست نکرد، خودتون دستی Record ها رو ایجاد کنید.
فقط دقت کنید که Weight رو اشتباه وارد نکنید.
باهش میگم تست کنن ولی بنظرم trust بینمون وجود داره هنوز چون من دارم با اکانت تهران توی دی سی بیرجند لاگین میکنم این دلیل بر trust بین دوتا دامین نیست؟؟؟
نه از وقتی migration به 2008 کردم وجود نداشت ولی کاربرام مشکلی نداشتن ولی الان اگه ارتباطم با تهران قطع شه به مشکل میخورن این زون رو بصورت secondary ساختم بازم درست نشد