作者 主題: 2000 的 Active Directory Server 異常...  (閱讀 6235 次)

0 會員 與 1 訪客 正在閱讀本文。

Anonymous

  • 訪客
2000 的 Active Directory Server 異常...
« 於: 2002-03-30 22:46 »
我的公司使用 Win 2000 的 AD 作為所有使用者的登入驗證系統, 所有的使用者都必須有使用者 ID 及正確的密碼方能使用公司的網路資源 .

現在這台 AD Server 有了問題, 我試圖安奘另一台 AD Server 來同步抄寫原來的 AD Server 的使用者資料, 卻發生新的 AD Server 無法找到原來的 AD Server, 所以我想...我只有將原來的 AD Server 重新安裝或是用另一台全新的AD Server 來解決這個問題 !

但我不知該如將原有的 AD Server 內的 AD Object (含使用者帳戶及電腦帳戶 相關資料) 保留/複製 下來, 以便 AD Server 重新安裝完畢後, 企業內的用戶資料得以保留..

請教各位先進, 我該如處理這個問題, 謝謝 !!

decade_joe

  • 懷疑的國中生
  • **
  • 文章數: 66
    • 檢視個人資料
2000 的 Active Directory Server 異常...
« 回覆 #1 於: 2002-03-31 09:58 »
If your Win2k Server is run Mix Mode,
Please install NT4 server to BDC, Backup
all accounts to this BDC, Reinstall old win2k
server.

If your Win2k Server is run native Mode,
Please install Win2k Server and run AD in old AD Domian,
and then, in old Win2k server "Active Directory Domains and Trusts"
Change Operations Master to new Win2k Server.

Bye Bye !!!!!

kuolung

  • 俺是博士!
  • *****
  • 文章數: 1031
    • 檢視個人資料
    • http://www.kuolung.net
2000 的 Active Directory Server 異常...
« 回覆 #2 於: 2002-03-31 16:58 »
您好,我也有同樣的問題,但現在是當我重裝第二台 ad 時,就已找不到原來的
ad 來複製 user 和電腦帳號了,而且就算是裝好,可用,兩台同步也有問題,
就沒有辦法切 master 了,不過您說的方式我會試試
=========================
http://www.kuolung.net
==========================

huckly

  • 酷!學園 學長們
  • 俺是博士!
  • *****
  • 文章數: 3420
    • 檢視個人資料
    • http://blog.huckly.net
2000 的 Active Directory Server 異常...
« 回覆 #3 於: 2002-04-03 15:11 »
先 修復 AD 資料庫 也需ad 資料庫本身 已經有問題了
第一台正常了 再做Replication

Troubleshooting Replication

This lesson describes problems you may encounter that relate to replication. Most problems that can be remedied with Active Directory Sites and Services involve poor directory information. This can mean that

  • New directory information is not distributed in a timely fashion

  • Service requests are not handled in a timely fashion

This lesson also describes how to check replication topology.

After this lesson, you will be able to
  • Troubleshoot replication

Troubleshooting Replication

Ineffective replication can result in declining Active Directory performance, such as new users not being recognized. Ineffective replication or request handling primarily results in out-of-date directory information or unavailable domain
controllers. Each problem (cause) has one or more possible solutions. Replication troubleshooting scenarios are discussed in Table 6.1.

Table 6.1  Replication Troubleshooting Scenarios
Symptom: Replication of directory information has stopped
CauseSolution
The sites containing the clients and domain controllers are not connected by site links to domain controllers in other sites in the network. This results in a failure to exchange directory information between sites.Create a site link from the current site to a site that is connected to the rest of the sites in the network.
Symptom: Replication has slowed but not stopped
CauseSolution
Although all sites are connected by site links, your inter-site replication structure is not as complete as it might be. Directory information is replicated to all domain controllers if they are all connected by site links, but this is not optimal. If there are site links but no site link bridges, changes made to domain controllers may take an unacceptably long time to be distributed to other domain controllers that are not closely linked.Make sure Active Directory has been configured properly. To span the multiple site links that need more efficient replication, consider creating a site link bridge or consider bridging all site links.
Symptom: Replication has slowed but not stopped
CauseSolution
The current network resources are insufficient to handle the amount of replication traffic. This can affect services unrelated to Active Directory, because the exchange of directory information is consuming an inordinate amount of network resources.Increase the proportion of available network resources relative to directory traffic. Decrease the frequency of the replication schedule. Configure site link costs. To achieve network connections with more bandwidth, create site links or site link bridges.
Directory information changed at domain controllers in one site is not being updated in domain controllers in other sites in a timely fashion because inter-site replication is scheduled too infrequently.Increase the frequency of replication. If the replication is occurring over a site link bridge, check which site link is restricting replication. Increase the time range during which replication can occur or the frequency of replication can occur or the frequency of replication within the time frame for that site link.
Clients are having to request authentication, information, and services from a domain controller with a low-bandwidth connection. This may result in clients receiving a slow response for authentication, directory information, or other services.Check if there is a site that will better serve the client's subnet. If a client who is experiencing poor service is isolated from domain controllers, consider creating another site with its own domain controller that will include the client. Install a connection with more bandwidth.

Checking Replication Topology

Active Directory runs a process that considers the cost of inter-site connections, checks if any previously available domain controllers are no longer available, checks if new domain controllers have been added, and then uses this information to add or remove connection objects to create an efficient replication topology. This process does not affect manually created connection objects.

To check the replication topology
  1. Click Start, point to Programs, point to Administrative Tools, then click
    Active Directory Sites And Services.
  2. In the AD Sites and Services console tree, double-click the server that you want to use to check replication topology.
  3. Right-click NTDS Settings, point to All Tasks, and then click Check
    Replication Topology.

Lesson Summary



[ 這篇文章被編輯過:  huckly 在 2002-04-03 15:16 ]
IT doesn't matter