Home > Ask the Windows Experts > Questions & Answers > Deleting a policy from within the SysvolAdmPolices(policy #) in the file system
Ask The Win IT Expert: Questions & Answers
EMAIL THIS

Deleting a policy from within the SysvolAdmPolices(policy #) in the file system

Jeremy Moskowitz EXPERT RESPONSE FROM: Jeremy Moskowitz

Pose a Question
Other Win IT Categories
Meet all Win IT Experts
Become an Expert for this site


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


>
QUESTION POSED ON: 18 May 2004
What are the implications of deleting a policy from within the SysvolAdmPolices(policy #)in the file system? I am not getting any response on how to 'fix' the current warning message I am getting across my enterprise of SP4 2000 DCs which control XP, SP1 clients. The warning message comes when I access any GPO from any DC. It is always the same, only the policy number referenced is different for each DC. Here is the warning:
(policy #xxx-xxxxx-xxxxAdminetres.adm on line 158
Error # 51 Unexpected Keyword
Found: SUPPORTED
Expected: KEYNAME, VALUENAME, PART, VALUEON, VALUEOFF, ACTIONLIST

the File cannot be loaded.
I click Ok, then I get a second less threatening warning about an entry in the [strings] section is too long and has been truncated. (IPV6, PNRP). I click Ok, both errors come up a second time, and then I can do my work without any other warnings. Group Policy across the enterprise is working fine. I do not get this error if I administer GPOs from my XP SP1 client with the adminpak.

I do have two 2003 member servers. A tech loaded the administration tools on one of them without permission and did make changes in GP on that machine. Since the errors I have removed the administrative tools from the 2003 member server. Since no one is offering a fix, or even familiarity with this problem, I'm asking if deleting the SYSVOLpolicynumberAdminetres.adm that is generating the error is safe.

>
EXPERT RESPONSE
I have heard of this problem... but not precisely how you describe. That is, I have seen that there is a problem with this file in the XP/SP2 beta ... but not as you describe in the XP/SP1. Here's what I would do: track down a fresh copy of XP/SP1 and see if replacing that file helps. If not, then re-post your story on GPanswers.com, and we'll see if a group approach can help.


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary



Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice

HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT DownloadsBlogs
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 1999 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts