Error When Run Command Gpupdate

baghiyat · 2024-10-09T05:10:17.803Z

I synced the clock, and now it’s giving a success message, but I don’t understand the rest.

Screenshot 2024-10-09 1908241592×536 111 KB

michaelmoore8 · 2024-10-09T05:43:29.052Z

After you now reboot the system and log back in, are you still getting the same error?

baghiyat · 2024-10-09T05:56:24.121Z

Yes

I sign out and sign in
and restart not working

adm-peters · 2024-10-09T06:56:22.571Z

After restart try wait for a while before login…

baghiyat · 2024-10-09T08:30:41.201Z

I waited for 30 minutes, but the problem still persists.

Samael1 · 2024-10-09T08:43:19.957Z

event log?

Rod-IT · 2024-10-09T09:22:22.734Z

You’re applying folder redirection to domain admins?

baghiyat · 2024-10-09T09:37:31.909Z

Yes, i use folder redirection for user and admin with this config
i even delete folder redirection from my ou but problem still persists.

Screenshot 2024-10-09 1305331881×591 27.2 KB

Rod-IT · 2024-10-09T10:37:34.533Z

You use this on DCs too, though?

baghiyat · 2024-10-09T10:45:17.285Z

no only on clients

davidpalmer7674 · 2024-10-09T10:57:15.200Z

I don’t know why the notification would persist after deleting the folder redirection policy, but I believe that message is normal if you have folder redirection along with asynchronous processing enabled. I wouldn’t consider it a problem.

Rod-IT · 2024-10-09T11:10:12.696Z

baghiyat:

no only on clients

You said initially you’d ran the command on the DC as well, hence me querying it.

What DNS do your DCs have set?

What DNS do your clients have set?

Are the DCs replicating correctly?

baghiyat · 2024-10-09T11:12:08.437Z

First, I need to thank you all, who participated and helped.
It was a DNS communication issue.
First, I cleared the DNS cache on both of my domain controllers, then repeated the same on the client.
I use a Main DC and an Additional DC.
In the first DNS field, I set the MDC IP on the ADC domain controller, and in the second field, I used 127.0.0.1.
I repeated this process on the ADC as well.
Then, I synced the two domain controllers using the following command:
repadmin /syncall /AeD
After that, I deleted the policy and restarted the system.

Rod-IT · 2024-10-09T11:17:02.546Z

baghiyat:

It was a DNS communication issue.

It always is.

For you and anyone else, please take a read here

Active Directory DNS Refresher Windows

It’s DNS. It’s always DNS. No, DNS is fine, it’s not DNS, trust me. It was DNS. I’m posting because in the last few weeks we’ve had a few posts that turned out to be misconfigurations with DNS in a domain environment. Things like Domain controllers pointing at themself first for DNS, or having a public DNS server on the NIC of the Domain Controller or the clients. Hopefully this will help some people get out in front of potential issues. The general rules for DNS in an AD E…

baghiyat · 2024-10-09T11:18:17.694Z

thank you

but i want to use redirect folder policy
how can i use it with no error ?

Rod-IT · 2024-10-09T11:28:16.855Z

Nothing is stopping you using FR, above you said sorted it - or it seemed like you had

baghiyat:

It was a DNS communication issue.

Are you saying it’s not working?

baghiyat · 2024-10-09T11:37:51.872Z

No, the issue that caused the gpupdate error after deleting the policy was resolved.
However, if I apply the policy again, the same error appears.

Evan7191 · 2024-10-09T11:48:44.951Z

That message meams that some settings van apply only during startup or logon. That is why it is asking to log off the user session.

bbeckers · 2024-10-09T13:30:43.027Z

You will always see that message.
What it’s telling you is that one or more policies are only applied upon user login.
Hence, when you run the GPUPDATE, it can’t apply all at that time.

Dashrender · 2024-10-09T15:13:56.402Z

have you checked - is folder redirection actually working? if so - ignore the error, if not - what shows in the logs?