Your problem with that user logon script is that you were trying to delete ALL users' Download contents, if that's the command you were using.
You want to delete each specific user's Downloads, surely. So if Downloads is in their profile directory:
Get-ChildItem $env:USERPROFILE\downloads | Remove-Item -recurse
You may need to sign your script or set -...
Zentyal doesn't have Failover Cluster listed as a supported feature. You can try installing Active Directory and use Zentyal as an additional one.
So as already mentioned, the backlog increase can be caused by staging quota being too small. To narrow down the issue, you should be able to trace this by 4202, 4204, 4206, 4208, 4212 events. These can be logged on source or destination servers. There are other possible reasons for the issues you are seeing. Here is an article on top 10 DFSR slow ...
This behavior has changed with recent Windows Server security updates.
Changes to Ticket-Granting Ticket (TGT) Delegation Across Trusts in Windows Server (PFE edition)
Updates to TGT delegation across incoming trusts in Windows Server
Can't enumerate group membership of groups with FSP members after running netdom /EnableTGTDelegation:No
The secure default ...
You don't mention whether this is a new DFS replica or not. Normally, it's a staging area that's too small - it must be set to greater than the sum of the size of the 32 largest files stored on the share.
Or else it's a problem with file locking.
Check this guide to see if you have any other basic configuration problems.
Then follow this guide for ...
When I ping the DOMAIN.com from the same floor or users PC internally, why the response is coming from different Domain Controllers from SIte-1, Site-2 and sometimes Site-3?
That is the expected behavior, unless the local DNS server is configured for the correct localnetpriority mask.
DFSR is a solution for files that are primarily read-only and infrequently modified. DFSR is not a solution for files that remain open or are frequently modified /by multiple users. If that is what you need, a third party product would be the solution.
I believe that GoDaddy's implementation of Office 365 uses federated users, which does not provide the same mechanism for AAD Domain join. You can find the article on doing AAD domain join with federated users here however I am not sure if GoDaddy actually provides a federated metadata endpoint.
I suspect you would have to migrate to Office 365 proper.
An in-place upgrade of the existing domain controllers is not recommended. From Upgrade Domain Controllers to Windows Server 2016:
The recommended way to upgrade a domain is to promote domain
controllers that run newer versions of Windows Server and demote the
older domain controllers as needed. That method is preferable to
upgrading the operating system of ...
Yes, you can create a conditional forwarder that isn't AD-replicated.
No, I can't think of any way you can make it AD-replicated except on one DC.
If you're concerned about deploying new DCs and them not having the conditional forwarder, you could create a startup script GPO that checks for the conditional forwarder and then creates it if it's missing, ...
I had the exact same issue, and it turned out that there are more permissions required to join a Linux system than a Windows system to the domain, though I'm not sure why that is the case.
I added additional permissions to my domain join account following this guide: https://www.computertechblog.com/active-directory-permissions-required-to-join-linux-and-...
Just had the same issue - all domain accounts giving "incorrect password" error, local user account working fine - and a reboot fixed it for me.
I realize this question is several years old, but at least here's a fix that has actually worked for the problem described in this question, at least once!