migration

Selam ip ayarlarından IP V6 yı disable edermisin. İnternette var nasıl yapıldığı register da bir ayarda girmen gerekiyor.

Merhaba;

IPv6 disable ettim  sorun düzeldi akşam tekrar eski sunucuyu kapatıp tekrar deneyeceğim 

Teşekür ederim 

Tamamdır. İyi çalışmalar.

Merhaba;

 Eski sunucuyu sistemden cıkarınca yeni sunucu dns ve ad aktif olmuyor  

clientlere eski sunucu dns olarak dagitiliyor ise

logon olamıyor olabilirler 

aktif olmuyordan tam kastınız nedir bu arada ?

Windows 2003 olan sunucudan 2008 e migration yapmıştım 2 gün replike için bekledim daha sonra eski sunucuyu kapattım yeni sunucuda dns ve ad çalışmıyor eski sunucuyu acınca yeni sunucuda dns ve ad çalışıyor migration işleminde herhangi bir hata ile karşılaşmadım ama işlemler bitince böyle bir sorunla karşılaştım

2008 sunucuda netlogon paylaşımı oluşmamış olabilirmi  kontrol edebilirmisiniz

Merhaba;

Yeni sunucuda netlogon paylaşımı yok nasıl oluşturabilirim 

Yolda oldugum icin ayrintili yazamiyorum fakat linkteki gibi yapabilirsin

http://www.doitfixit.com/index.php?option=com_content&view=article&id=195:how-to-rebuild-the-sysvol-and-netlogon-share-step-by-step&catid=48:active-directory&Itemid=53  

bu işlemi eski sunucuda mı yeni sunucudamı yapıyoruz

bu işlemi eski sunucuda mı yeni sunucudamı yapıyoruz

yeni (2008 ) sunucuda bu işlemleri yapmanız gerek 

Merhaba;

registerde ilk işlemi yapıyorum sadece SYSVOL paylaşımı oluşuyor daha sonra ikinci işlemi yapıyorum sysvol da gidiyor ama netlogon oluşmuyor iki durumda da oluşmuyor

Merhaba;

Eski sunucuyu sistem dışı bıraktıktan sonra yeni sunucu Event hataları

+ Eski sunucu kapandıktan sonra yeni sunucuda 5 dk sonra DNS ve AD aktif oluyor 

Active Directory

Error

Active Directory Domain Services could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory Domain Services from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.
 
Source domain controller:
 cozumsrv
Failing DNS host name:
 45cf8475-b4aa-4be5-8512-645977a88aa9._msdcs.cozum.tr
 
NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur.  To log all individual failure events, set the following diagnostics registry value to 1:
 
Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client
 
User Action:
 
 1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.
 
 2) Confirm that the source domain controller is running Active Directory Domain Services and is accessible on the network by typing "net view <a href="file://\\\\<source DC name>" or "ping <source DC name>".
 
 3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns
 
  dcdiag /test:dns
 
 4) Verify that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows:
 
  dcdiag /test:dns
 
 5) For further analysis of DNS error failures see KB 824449:
   http://support.microsoft.com/?kbid=824449
 
Additional Data
Error value:
 11004 The requested name is valid, but no data of the requested type was found.

-------------------------------
warning

This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role.
 
Operations which require contacting a FSMO operation master will fail until this condition is corrected.
 
FSMO Role: DC=cozum,DC=tr
 
User Action:
 
1. Initial synchronization is the first early replications done by a system as it is starting. A failure to initially synchronize may explain why a FSMO role cannot be validated. This process is explained in KB article 305476.
2. This server has one or more replication partners, and replication is failing for all of these partners. Use the command repadmin /showrepl to display the replication errors.  Correct the error in question. For example there maybe problems with IP connectivity, DNS name resolution, or security authentication that are preventing successful replication.
3. In the rare event that all replication partners being down is an expected occurance, perhaps because of maintenance or a disaster recovery, you can force the role to be validated. This can be done by using NTDSUTIL.EXE to seize the role to the same server. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com .
 
The following operations may be impacted:
Schema: You will no longer be able to modify the schema for this forest.
Domain Naming: You will no longer be able to add or remove domains from this forest.
PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts.
RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.
Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.

------------------dns----------------------

1

The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed.
The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller.
If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another
DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer.
This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

------------------file replication service

Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller cozummsrv.cozum.tr for FRS replica set configuration information.
 
 Could not bind to a Domain Controller. Will try again at next polling cycle.

Biryerlerden destek alın bence sizin ortam biraz karışmış gibi.

Merhaba;

yeni sunucudan dc kaldırsam  2008 e transfer ettiğimiz domain yetkilerinı tekrar 2003 alabilmiyiz

kaldırmadan önce rolleri transfer etmeniz daha sağlıklı olur

Merhaba;
Sunucuyu tekrar kurulum yaptım ve adc olarak kurdum ama SYSVOL ve NETLOGON oluşmuyor(schema transferleri yapmadım)

Merhaba;

ad geçiş işlemini yaptım replike için 1 - 2  gün daha  bekliyorum  daha sonra eski suncuda exchange 2007 yeni sunucuya exchange 2010 migration yapmayı düşünüyorum

1: eski sunucudan ad kaldırdığım zaman exchange 2007 ile ilgili bir problem olurmu yoksa  exchange 2010 geçiş yaptıktan sonramı kaldırayım 

 2: yeni sunuda Raise Forest Functional Leveli 2008 R2 yükseltmek istiyorum ama aşağıdaki hata geliyor

the functional level could not be raised. this may be due to replication latency.please wait 30 minutes and try again