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.
|Maintenance: Maintenance tasks for Windows workstations.|
Could not locate the script command lines in the Group Policy Object.
|English: Request a translation of the event description in plain English.|
In my case I solved the problem following these steps:
1) Remove computer from domain
2) Reset computer account on DC
3) Log on as local admin, delete local profile with reported errors
4) Add computer to domain
5) Add domain user account to local accounts with specified role (Admin, Advance User...)
6) Log on with specified user account without any problem
This event can be caused by:
1.Network problems that prevent the computer from accessing the domain controller or the network location of the script executable files
2.Invalid script command lines
3.Replication problems on the domain controller
See the link to "Fixing Scripts policy settings problems" for details on solving this issue.
ME258296. Exact phrase was not listed in this KB article. But the configuration I am using warented using the solution outlined in it.
This is a DHCP/DNS issue. On the DHCP servers be sure that the correct internal DNS servers are listed. Also make sure DHCP is set to "Automatically update DHCP client information in DNS", "Always update DNS", and "Discard forward lookups when lease expires".
|Private comment: Subscribers only. See example of private comment|
|Links: ME258296, Fixing Scripts policy settings problems|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated