upgrade server 2003 Std to 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-2086132%22%20slang%3D%22en-US%22%3Eupgrade%20server%202003%20Std%20to%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2086132%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%20I%20have%20posted%20my%20question%20before%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-server-for-it-pro%2Ffor-upgrade-server-2003-std-to-2019%2Fm-p%2F2082373%2Femcs_t%2FS2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufEtLNlg1R1U2QllBOFh8MjA4MjM3M3xTVUJTQ1JJUFRJT05TfGhL%23M4363%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-server-for-it-pro%2Ffor-upgrade-server-2003-std-to-2019%2Fm-p%2F2082373%2Femcs_t%2FS2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufEtLNlg1R1U2QllBOFh8MjA4MjM3M3xTVUJTQ1JJUFRJT05TfGhL%23M4363%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebut%20it%20would%20be%20more%20appropriate%20to%20start%20a%20new%20discussion%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20all%2C%20I%20face%20the%20similar%20scenario%3A%20migrating%20from%202003%20to%202019.%26nbsp%3B%20I%20find%20answers%20here%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fwindowsserver%2Fen-US%2F914aa5f5-432c-46e2-b6b2-ce1da0d07091%2Fserver-2003-to-2019-alternative-way-to-migrate-users-and-shares%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fwindowsserver%2Fen-US%2F914aa5f5-432c-46e2-b6b2-ce1da0d07091...%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20when%20I%20use%20dcdiag%20in%20my%202003%20server%2C%20there%20is%20only%201%20error%3A%3C%2FP%3E%3CP%3E%3CEM%3EStarting%20test%3A%20frsevent%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EThere%20are%20warning%20or%20error%20events%20within%20the%20last%2024%20hours%20after%20the%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ESYSVOL%20has%20been%20shared.%20Failing%20SYSVOL%20replication%20problems%20may%20cause%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EGroup%20Policy%20problems.%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E.........................%20(dc%20name)%20failed%20test%20frsevent%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20it%20matter%3F%20Will%20it%20stop%20my%20from%20migrating%3F%20Where%20can%20I%20fix%20this%20problem%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20if%20I%20have%20only%201%20DC%2C%20should%20I%20still%20use%20repadmin%20to%20check%20the%20replication%3F%20Or%20I%20will%20only%20use%20it%20after%20I%20have%20setup%202012%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20very%20much%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2086132%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hi all, I have posted my question before:

https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/for-upgrade-server-2003-std-to-2019...

 

but it would be more appropriate to start a new discussion here.

 

 

Hi all, I face the similar scenario: migrating from 2003 to 2019.  I find answers here:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/914aa5f5-432c-46e2-b6b2-ce1da0d07091...

 

However, when I use dcdiag in my 2003 server, there is only 1 error:

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.
......................... (dc name) failed test frsevent

 

Does it matter? Will it stop my from migrating? Where can I fix this problem?

 

Also, if I have only 1 DC, should I still use repadmin to check the replication? Or I will only use it after I have setup 2012?

 

Thank you very much

0 Replies