{"id":7480,"date":"2025-01-24T16:02:40","date_gmt":"2025-01-24T16:02:40","guid":{"rendered":"https:\/\/howtogeek.blog\/lt\/?p=7480"},"modified":"2025-01-24T16:02:40","modified_gmt":"2025-01-24T16:02:40","slug":"resolving-errordsversioncheckfailure-a-stepbystep-guide","status":"publish","type":"post","link":"https:\/\/howtogeek.blog\/lt\/resolving-errordsversioncheckfailure-a-stepbystep-guide\/","title":{"rendered":"ERROR_DS_VERSION_CHECK_FAILURE sprendimas: \u017eingsnis po \u017eingsnio vadovas"},"content":{"rendered":"

ERROR_DS_VERSION_CHECK_FAILURE klaid\u0173 patikra pateikiama su kodu 643 (0x283) ir nurodo, kad yra suderinamumo problema tarp Windows versijos ir elgsenos katalog\u0173 mi\u0161ko, domeno ar domeno valdiklio versijos.<\/p>\n

\u0160i klaida paprastai atsiranda d\u0117l versijos neatitikimo Active Directory (AD) schemos naujinim\u0173, replikacijos \u012fvyki\u0173 arba operacij\u0173, susijusi\u0173 su domeno valdikliais, metu, kai yra nesuderinam\u0173 AD komponent\u0173 versij\u0173.<\/p>\n

Kaip i\u0161spr\u0119sti ERROR_DS_VERSION_CHECK_FAILURE<\/h2>\n

1.\u012evertinkite Active Directory schemos versij\u0105<\/h3>\n
    \n
  1. Paleiskite komand\u0173 eilut\u0119<\/strong> su administratoriaus teis\u0117mis spustel\u0117dami mygtuk\u0105 Prad\u0117ti<\/strong>, \u012fvesdami cmd<\/code>, de\u0161iniuoju pel\u0117s klavi\u0161u spustel\u0117dami rezultat\u0105 ir pasirinkdami Vykdyti kaip administratori\u0173<\/strong>.<\/li>\n
  2. Vykdykite \u0161i\u0105 komand\u0105, kad gautum\u0117te schemos versij\u0105:dsquery * CN=Schema, CN=Configuration, DC=YourDomain, DC=com -scope base -attr objectVersion<\/strong><\/code><\/li>\n
  3. Palyginkite i\u0161vest\u012f su numatoma konkretaus \u201eWindows Server\u201c leidimo schemos versija.<\/li>\n<\/ol>\n\n\n\n\n\n\n\n\n
    Windows Server versija<\/strong><\/th>\nSchemos versija<\/strong><\/th>\n<\/tr>\n<\/thead>\n
    Windows Server 2012 R2<\/td>\n69<\/td>\n<\/tr>\n
    Windows Server 2016<\/td>\n87<\/td>\n<\/tr>\n
    Windows Server 2019<\/td>\n88<\/td>\n<\/tr>\n
    Windows Server 2022<\/td>\n91<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
      \n
    1. Jei aptinkate pasenusi\u0105 schemos versij\u0105, gali reik\u0117ti rankiniu b\u016bdu paleisti ADPREP<\/a> prie\u0161 reklamuojant bet kokius domeno valdiklius.<\/li>\n<\/ol>\n

      2. Inicijuokite Active Directory replikacij\u0105<\/h3>\n
        \n
      1. Atidarykite padidint\u0105 komand\u0173 eilut\u0119<\/strong>, kaip apra\u0161yta ankstesniame skyriuje, ir \u012fveskite komand\u0105:repadmin \/syncall \/AdeP<\/strong><\/code><\/li>\n
      2. \u0160i komanda \u012fgyvendina vis\u0173 domeno valdikli\u0173 replikacij\u0105.<\/li>\n
      3. Nor\u0117dami patvirtinti replikacijos b\u016bsen\u0105, naudokite komand\u0105:repadmin \/showrepl<\/strong><\/code><\/li>\n<\/ol>\n

        3. Patikrinkite FSMO vaidmenis<\/h3>\n
          \n
        1. Atidarykite komand\u0173 eilut\u0119 su administratoriaus teis\u0117mis ir paleiskite:netdom query fsmo<\/strong><\/code><\/li>\n
        2. \u012esitikinkite, kad schemos valdytojo vaidmuo priskirtas patikimam ir prieinamam domeno valdikliui.<\/li>\n<\/ol>\n

          Labai svarbu, kad schemos valdytojo vaidmuo b\u016bt\u0173 priglobtas sveikame domeno valdiklyje, nes tai labai svarbu taikant bet kokius schemos naujinimus.<\/p>\n

          4. Rankiniu b\u016bdu atnaujinkite Active Directory schem\u0105<\/h3>\n
            \n
          1. Prad\u0117kite \u012fd\u0117dami \u201eWindows Server\u201c diegimo laikmen\u0105 \u012f server\u012f.<\/li>\n
          2. Atidarykite padidint\u0105 komand\u0173 eilut\u0119<\/strong> ir vykdykite:adprep \/forestprep<\/strong><\/code><\/li>\n
          3. Atlikite tai su komanda:adprep \/domainprep<\/strong><\/code><\/li>\n
          4. Galiausiai i\u0161 naujo paleiskite server\u012f ir patikrinkite, ar ERROR_DS_VERSION_CHECK_FAILURE i\u0161spr\u0119sta.<\/li>\n<\/ol>\n

            Jei rankinis schemos atnaujinimas nepavyksta, gali prireikti papildomai i\u0161 naujo paleisti pirmin\u012f domeno valdikl\u012f (PDC)<\/strong> kartu su kitais domeno valdikliais, kad b\u016bt\u0173 u\u017etikrintas tinkamas naujinim\u0173 pritaikymas.<\/p>\n

            Jei vis tiek susiduriate su klaida, apsvarstykite galimyb\u0119 atkurti i\u0161 atsargin\u0117s kopijos arba susisiekite su \u201eMicrosoft\u201c palaikymo komanda, kad gautum\u0117te tolesn\u0117s pagalbos. Bet kokios konkre\u010dios problemos ar klausimai gali b\u016bti bendrinami toliau pateiktame komentar\u0173 skyriuje.<\/p>\n

            Da\u017enai u\u017eduodami klausimai<\/h2>\n

            1. Kas sukelia ERROR_DS_VERSION_CHECK_FAILURE?<\/strong><\/h3>\n

            ERROR_DS_VERSION_CHECK_FAILURE rodo, kad yra versijos nesuderinamumas tarp \u201eWindows Server\u201c operacin\u0117s sistemos ir \u201eActive Directory\u201c schemos, vis\u0173 pirma d\u0117l neatitikim\u0173 atliekant atnaujinimus arba replikacijos veiksmus.<\/p>\n

            2. Kaip galiu patikrinti schemos versij\u0105 \u201eActive Directory\u201c?<\/strong><\/h3>\n

            \u201eActive Directory\u201c schemos versij\u0105 galite patikrinti naudodami komand\u0105: dsquery * CN=Schema, CN=Configuration, DC=YourDomain, DC=com -scope base -attr objectVersion<\/code>padidintoje komand\u0173 eilut\u0117je.<\/p>\n

            3. K\u0105 daryti, jei pritaikius auk\u0161\u010diau nurodytus sprendimus klaida i\u0161lieka?<\/strong><\/h3>\n

            Jei klaida i\u0161lieka, nepaisant trik\u010di\u0173 \u0161alinimo veiksm\u0173, apsvarstykite galimyb\u0119 atkurti i\u0161 atsargin\u0117s kopijos arba kreiptis pagalbos \u012f \u201eMicrosoft\u201c palaikymo tarnyb\u0105 d\u0117l specializuot\u0173 trik\u010di\u0173 \u0161alinimo metod\u0173.<\/p>\n

            \u0160altinis ir vaizdai<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

            ERROR_DS_VERSION_CHECK_FAILURE klaid\u0173 patikra pateikiama su kodu 643 (0x283) ir nurodo, kad yra suderinamumo problema tarp Windows versijos ir elgsenos katalog\u0173 mi\u0161ko, domeno ar domeno valdiklio versijos. \u0160i klaida paprastai atsiranda d\u0117l versijos neatitikimo Active Directory (AD) schemos naujinim\u0173, replikacijos \u012fvyki\u0173 arba operacij\u0173, susijusi\u0173 su domeno valdikliais, metu, kai yra nesuderinam\u0173 AD komponent\u0173 versij\u0173. Kaip i\u0161spr\u0119sti […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[9],"class_list":["post-7480","post","type-post","status-publish","format-standard","hentry","category-how-to","tag-windows"],"acf":[],"_links":{"self":[{"href":"https:\/\/howtogeek.blog\/lt\/wp-json\/wp\/v2\/posts\/7480","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/howtogeek.blog\/lt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/howtogeek.blog\/lt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/howtogeek.blog\/lt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/howtogeek.blog\/lt\/wp-json\/wp\/v2\/comments?post=7480"}],"version-history":[{"count":1,"href":"https:\/\/howtogeek.blog\/lt\/wp-json\/wp\/v2\/posts\/7480\/revisions"}],"predecessor-version":[{"id":7481,"href":"https:\/\/howtogeek.blog\/lt\/wp-json\/wp\/v2\/posts\/7480\/revisions\/7481"}],"wp:attachment":[{"href":"https:\/\/howtogeek.blog\/lt\/wp-json\/wp\/v2\/media?parent=7480"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/howtogeek.blog\/lt\/wp-json\/wp\/v2\/categories?post=7480"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/howtogeek.blog\/lt\/wp-json\/wp\/v2\/tags?post=7480"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}