Пікірлер
@JoeHelwig
@JoeHelwig Күн бұрын
I had a the same issue on the new DC so I checked the Old DC. I foud Replication stopped working because of an unexpected shutdown and since this was the only dc for a while it didn't show I checked the logs on the new server same as what you showed but the old server below is what fixed the issue for me the command was in the event viewer. Event ID 2213 The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication. The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication. Additional Information: Volume: C: GUID: random string of charaters Recovery Steps 1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders. 2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command: wmic /namespace:\ oot\microsoftdfs path dfsrVolumeConfig where volumeGuid="random string of charaters" call ResumeReplication For more information, see support.microsoft.com/kb/2663685.
@DwayneKSmith876
@DwayneKSmith876 3 күн бұрын
I found this video while researching 2213 issue. On fixing that issue i'm now getting a 4012 issue with a primary DC that apparently has been having DFS replication issue for 7 years. Would this fix be recommended?
@cesarcaminero87
@cesarcaminero87 14 күн бұрын
Awesome man! My problem was that the nic teaming was not setup as LACP... no wonder! Thank you!
@gauravpaul100
@gauravpaul100 16 күн бұрын
Hi , Can you please help us to know how to create CMG in SCCM .
@craigsolow9003
@craigsolow9003 2 ай бұрын
Dude you are the GOAT!!!
@t4ir1
@t4ir1 2 ай бұрын
Thanks a bunch! This video helped me solve my problem! Thank you so much mate. You just got a new subscriber!
@donnyboy8195
@donnyboy8195 2 ай бұрын
cheers
@InvisibleChitChat
@InvisibleChitChat 2 ай бұрын
What if there is only one domain controller and you are getting event ID 4012 DFS Replication. How would I go about fixing this when there is only one domain controller and old domain controller was decommissioned.
@wolfgangf19
@wolfgangf19 2 ай бұрын
Great Video, that helped me so much. Thx
@Oper8or
@Oper8or 3 ай бұрын
You just helped me fix the issue and I did find another article on how to do this but the video was much better.
@dennislans9084
@dennislans9084 4 ай бұрын
I have been trying to fix this shit for hours, video saved me, THANK YOU!
@AmirSalehipour
@AmirSalehipour 4 ай бұрын
Hello Sysadmin, That worked perfectly for my issue where I had three domain controllers and migrated the FSMO roles to DC1. When I changed a policy, it didn't fully replicate to the SYSVOL, which was weird because it replicated to DC2, but when I navigated to the domain\sysvol on DC1, it was not there! Really weird! Anyway, it solved my issue. Thank you.
@Nobodyaz464
@Nobodyaz464 4 ай бұрын
But not working
@danielson1989
@danielson1989 4 ай бұрын
Just a note for your video - CU12 supported Windows Server 2022 :)
@gbryant200
@gbryant200 4 ай бұрын
This is one of the best instructional videos I have seen. Great explanations as to why you're doing what you're doing and what it's supposed to fix and how to do it. Fantastic!
@piusclement6108
@piusclement6108 4 ай бұрын
So helpful after 5 years.
@scottluebke5012
@scottluebke5012 4 ай бұрын
YOU ARE A GAWD. I'm an MCSA on Server 2016, ten years professionally doing this stuff, set up a new DC today and ran into this issue. With the move to the cloud, I don't touch servers a ton anymore, but wow did this fix the issue. I was totally lost, too.
@JonathanCarey-s5r
@JonathanCarey-s5r 4 ай бұрын
Hi Sysadmin....you are a life saver!!!!!!!! Thank you so much! This is the easiest to follow and most accurate resolution!
@vargispa4u
@vargispa4u 5 ай бұрын
Where is the first video
@HonnathalaiGuys
@HonnathalaiGuys 5 ай бұрын
Due to proxy settings... For a particular user we can't provide internet access .. it's only to block . If we try to unblock it's not working
@foxfire1112
@foxfire1112 5 ай бұрын
You're a life saver, subscribed
@williamdickinson165
@williamdickinson165 5 ай бұрын
Excellent, clear and concise walkthrough. Very much appreciated.
@Jake-Cooper
@Jake-Cooper 5 ай бұрын
Thank you very much this fixed my issue and i cant tell you how long it took me of trying before i found this video <3
@rahulmistry3777
@rahulmistry3777 5 ай бұрын
well explained
@edddy22
@edddy22 5 ай бұрын
Worked for me , awesome and concise explanation. Only thing at the end I was wondering what happened to dsrf-options value which wasn’t manually reverted to original but in my case once everything was consistent again and working the value itself got back to 0
@joerockwell9198
@joerockwell9198 6 ай бұрын
Thank you thank you thank you You saved me two days worth of headache just a discover this was the issue
@pingupongu843
@pingupongu843 6 ай бұрын
Thank you so much. This helped a lot
@Ichironiii
@Ichironiii 6 ай бұрын
I know this video is old but we are trying to set this up. I synchronize my updates and they populate in SCCM, but after awhile yours started showing up as required for your devices, some of mine do not. I have Win 10 Vms that were made around january, so they should require the latest cumulatives, however none of these are saying required? Any idea what I could look at? If it helps we are running the WSUS role and SCCM on the same server.
@TheOirishhhAmerican
@TheOirishhhAmerican 6 ай бұрын
Great stuff, just started a new sys admin role and one project was to decom 5 dc's don't ask me why there are so many which I thought that was absurd too but that's the deal haha.
@arigoldstein939
@arigoldstein939 6 ай бұрын
Completely fails for me on 2022. Does 2022 simply not sync with 2012?
@SteveRogers-k8n
@SteveRogers-k8n 6 ай бұрын
The steps in this video worked like a charm, I'd added a 2019 DC to a 2016 domain running a single DC but noticed no sysvol or netlogon on the new box. Did these steps and replication was fixed.
@James-sc1lz
@James-sc1lz 7 ай бұрын
Excellent video. What would be handy is GPO to apply proxy with the exceptions but I can look this up as I’m sure it’s easy Thanks
@Firrefirr
@Firrefirr 7 ай бұрын
Thank you so much, been stuck on this for way too long! 🙏
@ghalibakkali3813
@ghalibakkali3813 7 ай бұрын
thanks for the video. I have a question do you have any contact info
@VuTran-se2cj
@VuTran-se2cj 7 ай бұрын
Thanks bro so much as I was fighting with this case for 3 straight days. xxx
@TheChewyWun
@TheChewyWun 7 ай бұрын
I know this is an older video, but any ideas when I'm getting a RPC server is unavailable error when running the replication commands?
@varianh1455
@varianh1455 7 ай бұрын
This was the perfect tutorial, I was able to fix this issue finally. Thanks!😀
@lamok5516
@lamok5516 8 ай бұрын
why wouldn't you do a non-auth restore and it will copy changes from dc02? what is the reasoning behind doing a auth restore in this scenario -thanks
@mrp9117
@mrp9117 8 ай бұрын
This solved my domain sysvol replication issues. Thanks for a great video guide :)
@TmanaokLine
@TmanaokLine 8 ай бұрын
What a phenomenal video, even 5 years later it's helped me out. In my case, I ended up linking the policy to a security group to which the computer was applied to. Helped me out when installing complex software requiring service accounts to be local admins (but who's accounts I wanted to manage in AD).
@TheMarge99
@TheMarge99 8 ай бұрын
Just wanted to say thank you, this got my SYSVOL rep working straight away following this guide.
@tech_tutorials2053
@tech_tutorials2053 9 ай бұрын
thank you, worked like a charm!
@codenoob223
@codenoob223 9 ай бұрын
My task is "Only allow <group name> to have internet access from 6am to 21pm, from monday to friday" is it possible?
@antonybwana6766
@antonybwana6766 9 ай бұрын
Thanks, the rule tip helped
@guaripolo69
@guaripolo69 9 ай бұрын
what if nothing is syncing either way? follow the same stuff, or is there another way to approach it if no replication is happening whatsoever?
@RuneInVR
@RuneInVR 9 ай бұрын
Saved me countless hours of troubleshooting, thanks a lot.
@GabrielMontenegro-k5n
@GabrielMontenegro-k5n 9 ай бұрын
Do you need to manually configure each machine's LAN settings before creating the GPO and applying it? I followed your instructions but skipped the first part where you manually edited the LAN settings, created the GPO, applied it, but all it did was disable access to editing the LAN settings with default settings implemented. GPO did not add the customized LAN settings per your video.
@LeahLeahBurch
@LeahLeahBurch 10 ай бұрын
Whos Biden and why is this person a complete hypocrite?? Why can I only access certain crap when I am not in any group,not on a home network, not on Windows or Microsoft or in azure or anything else? My name is misty Burch and I think the administration is just a way to use my content will keeping me restricted to things like a REAL Google signin. And a real account. Answer me this with your app Stephanie
@GallagherSharp
@GallagherSharp 10 ай бұрын
Thank you!!
@thamaraipoo-rj3eo
@thamaraipoo-rj3eo 10 ай бұрын
HI there, i got an error in dcdiag User Running enterprise tests on : Jbc.local Starting test: LocatorCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, erro A Global Catalog Server could not be located - All GC's ar Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down. Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call fail A Good Time Server could not be located. ......................... Jbc.local failed test LocatorChe