vastni
Newbie | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору Подскажите, как быть. Имеется домен, который был построен на Windows 2000 Advansed Server SP4 (PDC - krx-irk - и BDC - krx-irk2). Есть желание перевести его на 2003 с полной переустановкой ОС, но есть ряд проблем. 1. В данном домене уже более трех месяцев физически не существует BDC, но запись о нем осталась в AD. Я так понимаю, что это как-то надо вычистить, но как? 2. dcdiag выдает следующее: Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\krx-IRK Starting test: Connectivity ......................... krx-IRK passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\krx-IRK Starting test: Replications [Replications Check,krx-IRK] A recent replication attempt failed: From krx-IRK2 to krx-IRK Naming Context: CN=Schema,CN=Configuration,DC=krx,DC=local The replication generated an error (1722): Сервер RPC недоступен. The failure occurred at 2006-04-05 15:52:25. The last success occurred at 2005-12-10 21:47:36. 2778 failures have occurred since the last success. [krx-IRK2] DsBindWithSpnEx() failed with error 1722, Сервер RPC недоступен.. The source remains down. Please check the machine. [Replications Check,krx-IRK] A recent replication attempt failed: From krx-IRK2 to krx-IRK Naming Context: CN=Configuration,DC=krx,DC=local The replication generated an error (1722): Сервер RPC недоступен. The failure occurred at 2006-04-05 15:52:02. The last success occurred at 2005-12-10 21:47:36. 2778 failures have occurred since the last success. The source remains down. Please check the machine. [Replications Check,krx-IRK] A recent replication attempt failed: From krx-IRK2 to krx-IRK Naming Context: DC=krx,DC=local The replication generated an error (1722): Сервер RPC недоступен. The failure occurred at 2006-04-05 15:51:39. The last success occurred at 2005-12-10 21:50:35. 2778 failures have occurred since the last success. The source remains down. Please check the machine. ......................... krx-IRK passed test Replications Starting test: NCSecDesc Error NT AUTHORITY\КОНТРОЛЛЕРЫ ДОМЕНА ПРЕДПРИЯТИЯ doesn't have Replicating Directory Changes All access rights for the naming context: CN=Schema,CN=Configuration,DC=krx,DC=local Error BUILTIN\Администраторы doesn't have Replicating Directory Changes All access rights for the naming context: CN=Schema,CN=Configuration,DC=krx,DC=local Error NT AUTHORITY\КОНТРОЛЛЕРЫ ДОМЕНА ПРЕДПРИЯТИЯ doesn't have Replicating Directory Changes All access rights for the naming context: CN=Configuration,DC=krx,DC=local Error BUILTIN\Администраторы doesn't have Replicating Directory Changes All access rights for the naming context: CN=Configuration,DC=krx,DC=local ......................... krx-IRK failed test NCSecDesc Starting test: NetLogons ......................... krx-IRK passed test NetLogons Starting test: Advertising ......................... krx-IRK passed test Advertising Starting test: KnowsOfRoleHolders ......................... krx-IRK passed test KnowsOfRoleHolders Starting test: RidManager ......................... krx-IRK passed test RidManager Starting test: MachineAccount ......................... krx-IRK passed test MachineAccount Starting test: Services ......................... krx-IRK passed test Services Starting test: ObjectsReplicated ......................... krx-IRK passed test ObjectsReplicated Starting test: frssysvol ......................... krx-IRK passed test frssysvol Starting test: frsevent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... krx-IRK failed test frsevent Starting test: kccevent ......................... krx-IRK passed test kccevent Starting test: systemlog ......................... krx-IRK passed test systemlog Starting test: VerifyReferences ......................... krx-IRK passed test VerifyReferences Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : krx Starting test: CrossRefValidation ......................... krx passed test CrossRefValidation Starting test: CheckSDRefDom ......................... krx passed test CheckSDRefDom Running enterprise tests on : krx.local Starting test: Intersite ......................... krx.local passed test Intersite Starting test: FsmoCheck ......................... krx.local passed test FsmoCheck Как можно устранить эти ошибки? И подскажите примерный ход действий, при условии, что хотелось бы это всё провести прозрачно для пользователей, чтобы их потом не перезаводить в домен. Возможно ли это сделать так, чтобы после перехода домен назывался по-другому, и у PDC был другой IP-адрес? Или придется потом всех вновь вводить? В сети 70 машин на Windows XP. |