Troubleshooting synchronization with Windows Azure Active Directory (WAAD) (Part 3)If you would like to read the other parts in this article series please go to: Introduction. In the first two articles of this series, we have seen how to install the built- in tools to troubleshoot filtering and synchronization. At this point in the game we have all the basic requirements to perform troubleshooting of the synchronization process. Using filtering in Office.
UPN on- premises. In some situations we may end- up having some accounts being synchronized and the username will show up in WAAD (Windows Azure Active Directory) with the default domain name (Figure 0. In our case this is ? There are a couple of ways, the simplest is using the filter feature on the Office. Logged on Office. New View (Figure 0. Figure 0. 2On the new filter wizard, define a name and select the domain, in our case the domain will be aaptricioinfo.
Source: Service Control Manager: Type: Error: Description: The <service or device name> service failed to start due to the following error: <error description>. This feature is only available to EventID.Net subscribers. It provides you with "one-click" access to the Microsoft technical article!
Find and contact HP Customer Support, download drivers, manuals and troubleshooting information for HP products, including pcs, laptops, desktops, printers, tablets.
Here we have all accounts that we need to do some work on your on- premises Active Directory (Figure 0. Figure 0. 4So, what is the solution for accounts that show up with the default domain name in Office. Usually the UPN for the account is not correct in Active Directory (Figure 0. UPN (in my case apatricio.
Figure 0. 5Troubleshooting some synchronization issues. We can look at the Application area of the Event Viewer and we will have some warnings when a new error occurs. The errors/warnings will have the FIMSynchronization. Service as source and their Event IDs can be 0 or 6.
My preferred method is using the Synchronization Service Manager (miisclient), where we can track the error down to its first appearance on our environment based on past runs. The scenario that we are going to test here will help you fix some common issues, however the most important thing is to show you how to get the information to start troubleshooting. Bear in mind that an error message can be applied to several different errors and at the end our analysis, validation, comparison with existent objects and finally testing will be the key to fix the issue. Issue #0. 1 – Attribute. Value. Must. Be. Unique (simple)Every time that we click an item in the Operations area we will have more details at the bottom of the screen in two frames (Figure 0. They are really helpful because they provide statistics and detailed information of any selected operation listed above.
Figure 0. 6In the example above we have the Export operation completed with some errors based on the Status column. If we click on that specific operation, we will have at the bottom right side two columns: Export Errors and Error(s) we can start looking around to find the issue. The first column will scare you away because it is the Distinguished Name, however let’s observe the error in the second column Attribute. Value. Must. Be. Unique. It seems to be the case where we have an attribute that is being shared among two or more objects. Click on the Attribute. Value. Must. Be. Unique (Figure 0.
Improve your productivity and save time. Let your system work for you. Das Aufsetzen einer SharePoint Multi Tenancy Farm ist auch mit SharePoint 2013 nur via PowerShell möglich. Spencer Harbar hat auf seinem Blog eine sehr aus. MicroStrategy is an easy-to-use enterprise analytics platform that delivers dashboards, visualizations, mobile apps, and more to thousands.
Click Detail.. The first step is to search the SMTP address info provided by the tool (Figure 0. Figure 0. 8Open both objects and try to find the inconsistency.
![Could Not Start Windows Sharepoint Services Administration Service Error 1053 Could Not Start Windows Sharepoint Services Administration Service Error 1053](http://static.3ice.hu/images/DpHost-DpHostW.exe-Authentication-Service-Error-1053--The-service-did-not-respond-to-the-start-or-control-request-in-a-timely-fashion.png)
![Could Not Start Windows Sharepoint Services Administration Service Error 1053 Could Not Start Windows Sharepoint Services Administration Service Error 1053](http://documentation.commvault.com/commvault/v11/images/centricstor/service.png)
In the scenario below (true story!), the Security Groups had their owner information added to the description and e- mail filed in Active Directory. In this case, the simple solution is to remove the E- mail information from the group, after all it is not even a mail- enabled object and wait or run synchronization.
Figure 0. 9Issue #0. Identity. Data. Validation. Failed. We have an error like the one shown in Figure 1. Unfortunately, this error message does not pin point the account with the issue on the detailed information, however we know that is related to the attribute . We already checked the second column in Figure 1. On the Export in Progress tab we will find information about the object that is responsible for the error (Figure 1.
Figure 1. 1Hercule Poirot will be pleased of our power of observation. Our job is to go to the account in Active Directory Users and Computers and check the username attribute (Figure 1. The issue is that there is a space in the username, correct that and in the next synchronization cycle that error message is gone. Figure 1. 2Issue #0.
Attribute. Value. Must. Be. Unique (more advanced)In the first issue of this article we found out that the e- mail field in Active Directory was messed up with some Groups and in this new issue we get the same error message (Figure 1.
However, this one will have a different outcome and we will need to go a little bit deeper to find the issue. Based on the error message the e- mail . Interesting. We can do that by placing both Active Directory users’ properties side by side and click the Attribute Editor tab and we will edit the value for proxy. Addresses. Now that we have the visual of both objects it is easy to pin point the issue: the user arg. SMTP address that is the same of the user arg. Based on the name of the users it is clear that arg. Active Directory replication to take place and in the next replication the issue will be resolved.
Figure 1. 6Issue #0. When my user was synchronized with the WAAD? That is not even an issue but sometimes I get this question from customers. They want to know if the user that was just created was part of the last synchronization cycle. Depending of the size of your Active Directory and your patience to seek through the entries, you can always go to the Export task listed in the Operations area, and on the left side below we will have the statistics. If there is a number then there is a link to retrieve more information, click on it.
The first window will be the Distinguished. Name which does not help at all in this scenario, however double click on it and since that is a new user it is expected that the column Old Value will be empty but in the New Value column we will have the info of the user that was just synchronized to WAAD. If the last user created was arg.
Windows Azure Active Directory. Figure 1. 7What is the synchronization frequency? Can I change it? By default is every 3 hours and in order to change it, we need to open the file called Microsoft. Online. Dir. Sync. Scheduler. exe. Config located in the C: \Program Files\Windows Azure Active Directory Sync and change the value for the key Sync. Time. Interval (Figure 1. Figure 1. 8The last step is to restart the service called Windows Azure Active Directory Sync Service to apply the new settings (Figure 1.
Figure 1. 9Conclusion. In this final article of our series about troubleshooting between on- premises Active Directory and Windows Azure Active Directory we validated some scenarios and troubleshooting steps to fix issues. If you would like to read the other parts in this article series please go to.