Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The account <computer name>$ cannot be converted to be a domain controller account as its object class attribute in the directory is not computer or is not derived from computer.If this is caused by an attempt to install a pre windows 2000 domain controller in a windows 2000 domain, then you should precreate the account for the domain controller with the correct object class.
|English: Request a translation of the event description in plain English.|
As per Microsoft: "This behavior occurs because the Windows NT 4.0 Setup routine creates an account of class User instead of class computer. To add a Windows NT 4.0-based BDC to a domain with a Windows 2000 client as the PDC, use the Srvmgr tool that is included with Windows 2000. You should run this version of the tool only on the Windows 2000 client to pre-create the computer account for the BDC. After you create the account, the BDC installation should finish successfully. See the link below for more details.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated