Really not sure why it would do this as when I installed vCenter 4yrs ago it was just 2x DCs, this one I removed yesterday only got installed 6-8 months ago when I was going to upgrade DCs, but never got round to it, so it just kind of sat there in the interim but I no longer needed it so decided to remove. BUT, if say I go to the permissions section and try and add an account from my domain, it just sits there for a solid 3-5 mins before populating all my usernames so it is pulling from AD.
What's weird is if I try the web client a few times it sits on Authentication for a long time then eventually lets me in and all looks fine. My initial thought was SSO was pointing to the removed DC, it wasn't I checked this and it shouldn't have anyway as the one I removed was only a temp DC anyway. Anyway, last night my Veeam backups although working, took twice as long but all longs worked OK, so something seems up. Now I hadn't gone into vCenter this day but it was fine the previous day so I am not 100% sure if its related or not. (The command has timed out as the remote server is taking too long to respond.) "The server xxxxx took too long to respond. dcdiags and repadmin checks show everything going OK so I thought all good.īut then, a few hours later I went to logon to vCenter to do something else and I get Apart form a brief replication error which I think was from the changes it made all looks good. Looking into this and following the guide here I was able to change that to a correct DC and then remove the intended one all good. When I tried to remove it I hit the problem where it saysĪctive Directory domain services could not transfer the remaining data in directory partition DC=ForestDnsZone etc. Yesterday I finally got time to remove one of my legacy DCs (leaving 3x others all GCs). This is a weird one and might or might not be related but I need some help.
0 kommentar(er)
