Troubleshooting Azure Active Directory Sync error related to conflicted objects


As you know, one of the things I enjoy doing in my lab, is to break things, and once they are broken enough, I start fixing them up. Sound quite masochist but that is one of the great ways to learn.

So, I was trying to break the relationship between an account in my on-premise environment and my Azure AD and try to re-establish it. However, it is not simple as I expected because you cannot do this in a proper way. Here is what I did to break everything and eventually fix them up.

Relationship between ‘SPN Duplication’ and ‘Domain Join’ process

As you might already know, “Service Principal Names” plays an important role in authentication process of Active Directory. If you haven’t watched my video on Kerberos, I suggest you have a look at that video because I explain Kerberos and use of SPNs in Active Directory. However, I will produce a separate video dedicated to SPN later on, so make sure to follow my YouTube channel for more videos. Anyways, in this article, I am going to briefly talk about one of the common problems of authentication and consequently “Secure Channel” which falls to the category of “Duplicated SPN”.


Monitor health of DFSR and SYSVOL in your Active Directory are quite number of tasks in which an Active Directory administrator should always perform regularly during the day. These task can be varied from performing backups to troubleshooting serious problems of an Active Directory environment. Talking about tasks, some people tend to patrol through the different areas like ‘Event Viewer’ to find more information about the health of the infrastructure, some other people including me or maybe you, prefer to use other methods to do these same tasks with maximum efficiency. Some clear example of these methods are using SCOM or PowerShell scripting.

Can 'Unauthenticated' tag on NIC result to a broken secure channel?

Couple of days ago I noticed a strange behavior on network adapter of dozens of clients in my environment. The users were not able to authenticate to their workstations, throwing secure channel error. When one of the helpdesk administrators informed me about this issue, I thought it might be a typical problem of operating system including incorrect DNS configuration or duplicate names, but this was strange because basically everything related to secure channel were in place. Computer accounts were enabled in ADUC, DNS records existed, logintimestamps were updated and etc. So I tried digging in the problem to see what I can find.

The auditor of auditors: 'LepideAuditor Suite'

Today, in modern days of technology, the concept of auditing has become one of the interesting facts in Information Technology (IT). Back in days, when I was probably playing with my SNES, the concept of auditing was so hard to follow with built-in applications and consoles, but today, you can find many applications which either covers a specific part of auditing or support a huge number of services and applications. Among them, it is rare to find a solution which covers a whole range of services and audits, but ‘LepideAuditor Suite’ is one of those rare. In this article we will talk about this application.