You can use nltest to:
- Get a list of domain controllers
- Force a remote shutdown
- Query the status of trust
- Test trust relationships and the state of domain controller replication in a Windows domain
- Force a user-account database to synchronize on Windows NT version 4.0 or earlier domain controllers
Nltest can test and reset the secure channel that the NetLogon service establishes between clients and the domain controller that logs them on. Clients using Kerberos authentication cannot use this secure channel.
Viewlist Global Catalogs
repadmin /viewlist GC:
nltest /dsgetdc:DOMAIN /gc
Display FSMO Roles
netdom query fsmo
Domain Controllers Diagnostic
dcdiag /v /c /d /e >>c:\dcdiag.txt
This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role.
Operations which require contacting a FSMO operation master will fail until this condition is corrected.
FSMO Role: CN=Schema,CN=Configuration,DC=domainName,DC=com
1. Initial synchronization is the first early replications done by a system as it is starting. A failure to initially synchronize may explain why a FSMO role cannot be validated. This process is explained in KB article 305476.
2. This server has one or more replication partners, and replication is failing for all of these partners. Use the command repadmin /showrepl to display the replication errors. Correct the error in question. For example there maybe problems with IP connectivity, DNS name resolution, or security authentication that are preventing successful replication.
3. In the rare event that all replication partners being down is an expected occurance, perhaps because of maintenance or a disaster recovery, you can force the role to be validated. This can be done by using NTDSUTIL.EXE to seize the role to the same server. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.
The following operations may be impacted:
Schema: You will no longer be able to modify the schema for this forest.
Domain Naming: You will no longer be able to add or remove domains from this forest.
PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts.
RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.
Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.
Unable to perform discovery in Citrix XenApp.
Administravtive Events: IMA_RESULTS_FAILURE, failed to connect to the data store.
Run Citrix Scout from a single XenDesktop controller (DDC) or XenApp server to capture key data points and CDF traces for selected computers followed by secure and reliable upload of the data package to Citrix Technical Support. Just run collect and upload not CDF trace. Upload the data to https://taas.citrix.com/AutoSupport/
Citrix Scout error on IMA Datastore
Clients can launch publish applications fine.
Citrix MFCOM Service and other Citrix Services are started normal.
Verify mf20.dsn file, ensure username/password is correct and have database write access.
You can update username/password with IMA Helper.
- Stop IMA, this won’t affect active users.
- DSMaint Config: enter the Domain, User, Password, DSN File, and click Run
- After clicking Run, a message will prompt -> Successfully connected to the datastore.
- Start IMA. Check IMA Status.