Skip to main content

ما هى ال FSMO Roles

 


بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master
و هى عباره عن 5 Roles فى ال Active Directory
و هما بينقسموا لقسمين



A - Forest Roles



1- Schema Master Role
و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role
واحد فى ال Forest بيكون موجود على Domain Controller
و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC
بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd
regsvr32 schmmgmt.dll

2-Domin Naming Master


و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain
ليهم نفس الاسم فى ال Forest
و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts



B- Domain Roles



1-PDC Emulator
و هى ال Role اللى بتتحكم فى ال Password change فى ال domain
و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى
لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين
و بيتم التحكم فيها من خلال ال Active directory Users & Computers
عن طريق عمل كليك يمين على اسم الدومين و نختار operations master
فى تاب ال PDC Emulator نعمل change

2-RID Master
و هى ال Role اللى بتضمن ان كل object فى ال Active Directory ليه unique identifier
و ال RID بيعتبر الجزء الثانى من ال SID بتاع ال object
و بيتم التحكم فيها زى ال PDC بس مع اختلاف اختيار تاب ال RID

3- Infrastructure Master
ال Role دى بتتحكم فى عمليه ال Group Mempership خصوصا لو كان فى User
Member of جروب موجود فى دومين تانيه
و بيتم التحكم فيها زى ال PDC بس مع اختلاف اختيار تاب ال Infrastrucure Master

فى ملاحظه بسيطه : يفضل ان ال Global Catalog يكون على DC منفصل عن
ال DC اللى عليه ال Infrastructure Master عشان ممكن تحصل مشاكل
لأن الاتنين تقريبا بيقوموا بنفس الوظيفه و هى ال Group Membership translation
فممكن يحصل conflict ما بين الاتنين و تحصل مشاكل فيفضل الفصل ما بين الاتنين
الا لو كان فى DC واحد بس فى الدومين فحيبقى الاتنين مع بعض

Comments

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...