• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1618
  • Last Modified:

Group Policy Errors

My system logs are filled with Group Policy warnings on the many of the machines in the network. The error states that "Windows failed to apply the Scripts settings. Script settings may have its own log file. Please click on........." The details of the warning make it clear that the system cannot find the file specified. The Extension Name is Scripts with the Extension ID {42B5FAA-.......}. I have looked through all of the policies and the sysvol partition trying to find this GUID. I believe that it does not exist and this is why it is failing. Where could this script be getting called from? Is there a way to search for this GUID and figure out what is calling it, and removing the reference?  
0
GFCU
Asked:
GFCU
  • 7
  • 3
1 Solution
 
PanopticComputerServicesCommented:
Are you running Small Business Server? Do you have multiple DCs?

run RSOP.msc from an affected station. I will show you what policies are having errors without having to dig around for GUIDs. If the policy shows up in rsop then your sysvol folder is correct.

I had this problem a while back and it turned out being that I was using a local path (c:\scripts\script.bat) in group policy instead of a UNC path (\\server\scripts\script.bat)

Check your policies and make sure the scripts are accessible over the network path. You may just need to check the share and security tabs for the associated folder.
0
 
GFCUAuthor Commented:
This is the output from RSOP:

Wednesday, October 26, 2011 2:16:53 PM

Scripts failed due to the error listed below.
The system cannot find the file specified.


Should I be looking in the .bat logon scripts on sysvol? I do not see anything that jumps out at me. There are no scripts configured in any GPO's. The only scripts that I know of are being called are from the user profile in AD.

Thanks
0
 
GFCUAuthor Commented:
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
PanopticComputerServicesCommented:
This looks like small business server...correct? What version?

If so check the "Windows SBS CSE Policy", there are pre-configured startup scripts in that gpo....check the paths and file permissions of they exist.
0
 
GFCUAuthor Commented:
I am running RSOP on many different machines with the same results. The screenshot is actually from a 7 workstation. The AD servers are 2003 and 2008 servers. No SBS. I have looked in the scripts area of every GPO on the servers and there is nothing in any of them. I am not sure where this error is coming form. Thanks.
0
 
PanopticComputerServicesCommented:
Check you AD server event logs for Replication errors and post. Also Please post the complete error information from a workstation.

Have you added any new gpos lately? Or removed an old domain controller? This could be many things at this point without seeing the event logs from the servers.
0
 
GFCUAuthor Commented:
Workstation error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\gpupdate
Updating Policy...

User Policy update has completed successfully.
Computer Policy update has completed successfully.

The following warnings were encountered during computer policy processing:

Windows failed to apply the Scripts settings. Scripts settings might have its ow
n log file. Please click on the "More information" link.

For more detailed information, review the event log or run GPRESULT /H GPReport.
html from the command line to access information about Group Policy results.

Server:

Log Name:      System
Source:        Microsoft-Windows-GroupPolicy
Date:          10/27/2011 10:52:36 AM
Event ID:      1085
Task Category: None
Level:         Warning
Keywords:      
User:          SYSTEM
Computer:      
Description:
Windows failed to apply the Scripts settings. Scripts settings might have its own log file. Please click on the "More information" link.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" />
    <EventID>1085</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>1</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-27T14:52:36.166307600Z" />
    <EventRecordID>4645</EventRecordID>
    <Correlation ActivityID="{527A2971-ED5C-4504-987F-969BDEF4AE7E}" />
    <Execution ProcessID="212" ThreadID="2928" />
    <Channel>System</Channel>
    <Computer></Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="SupportInfo1">1</Data>
    <Data Name="SupportInfo2">3961</Data>
    <Data Name="ProcessingMode">0</Data>
    <Data Name="ProcessingTimeInMilliseconds">1076</Data>
    <Data Name="ErrorCode">2</Data>
    <Data Name="ErrorDescription">The system cannot find the file specified. </Data>
    <Data Name="DCName">\\</Data>
    <Data Name="ExtensionName">Scripts</Data>
    <Data Name="ExtensionId">{42B5FAAE-6536-11d2-AE5A-0000F87571E3}</Data>
   </EventData>
</Event>

The referenced extension ID does not exist in SYSVOL/ Not sure where it is coming from???
0
 
GFCUAuthor Commented:
Hanve not removed a domain controller. However, I just installed another AD/DNS server and will eventually shutting an AD/DNS server.
0
 
GFCUAuthor Commented:
I downloaded the Best Practices Analyzer for GP from Microsoft and it told me what file the suspect pointer was looking for. I placed an empty file in that location and will remove the reference.
0
 
GFCUAuthor Commented:
I fugured it out.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 7
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now