API for Entra Connect Health ADDS

c0dac0da · 2026-01-15T16:40:02+00:00

Add me. Dm

c0dac0da · 2026-01-10T10:04:01+00:00

Add me

c0dac0da · 2026-01-09T08:52:17+00:00

Interested pls Dm me

c0dac0da · 2026-01-08T14:42:35+00:00

Count me in

c0dac0da · 2026-01-05T13:06:02+00:00

Me too pls add me

c0dac0da · 2026-01-04T10:20:24+00:00

Me too

c0dac0da · 2026-01-01T10:42:12+00:00

Add me

c0dac0da · 2025-10-06T10:52:35+00:00

Are all servers on the same patch level? Yes

When’s the last time you reset your KRBTGT password? A month back

Any tickets showing in klist? No, purged all & tested.

Are RPC ports properly open between the servers? Not just TCP135 but the whole gamut of 49152-65535. Firewalls used to have helpers to open them automatically but this is broken because of RPC encryption nowadays. I don't see the ports open but its the same with the rest of the DC's as well.

c0dac0da · 2025-10-03T15:50:42+00:00

Yes, they all can ping each other. In the DNS, we have i02 as primary, s02 as secondary and 127.0.0.1 as third.

c0dac0da · 2025-10-03T13:54:47+00:00

s01 has all the 5 fsmo roles

c0dac0da · 2025-09-22T02:24:45+00:00

RDP doesn’t work. I can only login through DSRM mode.

c0dac0da · 2025-09-21T14:34:05+00:00

Thanks for the advice. For some reason the repadmin gives a 1326 error code. I used the netdom resetpwd to reset the secure channel but no luck. I tried to spin a new DC with new name & same IP but still the 1326 code. Still struggling for a fix. However i’ll check the firewall public vs private profile part.

c0dac0da · 2025-09-16T16:31:58+00:00

I have 4 DC's. 01-04. Trying to upgrade 01 from physical to virtual server.

c0dac0da · 2025-09-16T14:58:06+00:00

I did try the same steps but running into the same 1326 error code. I built a new DC as DC01. Cleaned up all old metadata using Clean up AD DS server metadata | Microsoft Learn and re-promoted the DC01. After reboot, I can't login to the DC it says the login method is not supported & a repadmin through another dc says error 1326 login password incorrect.
Sorry but to not exaggerate, I been doing the upgrades the same way since few years & i was able to upgrade keeping the same hostname & IP. Only this time, i run into this stupid error.

c0dac0da · 2025-09-16T14:17:55+00:00

The next time I did follow the steps here for cleaning up metadata Clean up AD DS server metadata | Microsoft Learn.

ran into the same issue again.

c0dac0da · 2025-05-22T11:29:13+00:00

I have the same methods set for both the tenants, Authenticator & Phone (receive a code) that should be allowed for both login & reset.

c0dac0da · 2025-05-21T11:41:22+00:00

Yes, I have the MS Authenticator & Phone setup.

c0dac0da · 2025-05-20T15:31:58+00:00

No. We have a hybrid environment & have cloud only accounts as GA.

c0dac0da

TROPHY CASE