Newbe Dev Stack

Answer : Here is my recommended configuration for Windows Domain Time Synchronization, pieced together from several Microsoft TechNet articles and blog posts. If your servers are virtualized, do not use any of the VMware tools time sync features. Just let the Windows Time Service (w32time) do its job. VMware even says so. I assume the same is true for Hyper-V. Furthermore, if you have the both the VM tools and the Windows Time Service attempting to manage the system clock, you can end up with a "tug-of-war" situation where your clock will keep jumping around and never be accurate. Your Primary Domain Controller Emulator should be manually configured to sync with multiple external NTP servers (four is a good number). Using multiple NTP source provides redundancy and serves as a sanity check in case one server starts sending bad time data (it has happened before). The Active Directory assumes your PDCe is the central authoritative time source for your network. ...

Answer : Solution 1: I'd say set up a query for the user search instead of using the Find feature. It's a few extra clicks, but gives you the Attribute Editor tab properly. Make sure you set the query definition to the "Users..." type instead of the "Common Queries" type, so you get the right search behavior.. ..and the Attribute Editor tab works on the object when opened from this view. Solution 2: This seems to be a solution! http://activedirectoryfaq.com/2014/10/ad-attribute-editor-missing-make-search-visible Open de object after using "Find". Click the "Member of" tab. Open a group of which the object is a member. Close the object window. Locate the object in the group and double-click it. The object window should open with the "Attribute Editor" available. Should work. Tried it myself but I don't have an Attribute Editor available (Attribute Editor does not exist in a 2000/2003 forest). https:/...

Answer : Solution 1: Assuming you have an Active Directory environment: I believe the backslash format DOMAIN\USERNAME will search domain DOMAIN for a user object whose SAM Account Name is USERNAME. The UPN format username@domain will search the forest for a user object whose User Principle Name is username@domain. Now, normally a user account with a SAM Account Name of USERNAME has a UPN of USERNAME@DOMAIN, so either format should locate the same account, at least provided the AD is fully functional. If there are replication issues or you can't reach a global catalog, the backslash format might work in cases where the UPN format will fail. There may also be (abnormal) conditions under which the reverse applies - perhaps if no domain controllers can be reached for the target domain, for example. However: you can also explicitly configure a user account to have a UPN whose username component is different from the SAM Account Name and whose domain component is differen...

Answer : There are known issues with ADInsight and it is no longer supported or developed. It has issues loading its DLL in certain environments, specifically on VMs (see http://forum.sysinternals.com/adinsight-doesnt-work-hangs_topic18891.html and http://forum.sysinternals.com/adinsight-operation_topic18963.html) (archive links) The best solution I have found is to turn on Active Directory Diagnostic Logging as described at http://www.activedir.org/Articles/tabid/54/articleType/ArticleView/articleId/41/Default.aspx (archive link). Basically, you want to set the following registry values: Path: HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics\15 Field Engineering Type: DWORD Value: 5 Path: HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\Expensive Search Results Threshold Type: DWORD Value: 1 These changes do not require a reboot but are set per server, so implementing for an entire forest/domain would best be done via Group Policy Preferences. Once set you will...