Re: GPOs cannot be saved because files being used by another proce

Sorry type on my part

"you shouldn't have to rebuild any policies"

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no rights.

"Paul Bergson" <pbergson@xxxxxxxxxxxxxxxxx> wrote in message
news:el39ndUvGHA.1424@xxxxxxxxxxxxxxxxxxxxxxx
I'm not sure what has happened to your sysvol, but it sounds like your
permission set isn't defined correctly. If you want to reset it back to
the point of initial install try the following. This will result in the
loss of the any previous definitions you may have set, although from the
sounds of it that is what you want.

http://technet2.microsoft.com/WindowsServer/en/library/300796c6-8148-49af-a327-b5dca853ac4f1033.mspx?mfr=true

You should have to rebuild any of your policies if you followed the steps
correctly.

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no
rights.

"Ilkka Heiskanen" <IlkkaHeiskanen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:2B9488D6-9351-43D8-A160-C2AC0D416D4C@xxxxxxxxxxxxxxxx
Hello again,

I rebuild the sysvol applying the instructions in the link given
(http://support.microsoft.com/default.aspx?scid=kb;en-us;315457) but it
didn't help at all. I tried both summarized steps and detailed steps -
even
twice each, because I found the, quite contradictory.

I don't know whether I did something wrong, but on the second try after
the
Summary Step 5, I tried to open GPOs with empty sysvol folders and I
found
that all my policies were still found by gpmc but, of course, they could
not
be opened. Do I have to delete those policies from AD somehow or so???
The
strange thing was that I made a new policy when policies folder was
empty,
but I was not even able to modify that one after creation!!! Another
weird
thing was that on Detailed step 5, one DC reported that "Source domain is
linked to C:\Windows\sysvol\domain?" (yes, with the question mark!!!),
and
another DC did the same on staging/domain?. I fixed those manually but no
help at all...

According to those instructions, at first time I tries to rebuild sysvol
by
moving files back to their original locations on Summary step 6. Is that
wrong or should I somehow create totally new policies??? There are no
errors
in event logs. So what an earth to do next?

"Paul Bergson" wrote:

Just make sure you understand each step as you do it. Who ever said
patience is a virtue hit it on the head.

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no
rights.

"Ilkka Heiskanen" <IlkkaHeiskanen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:59152B47-E128-4D8C-AED0-F89C4AD97678@xxxxxxxxxxxxxxxx
Hi,

Thanks again!

Mayby I don't then have any other choice than rebuild sysvol. I have
to
read
those intructions carefully and I'll try that after backups tomorrow
morning
(CET). The low space issue has already been fixed few days ago.

I'll be back here after rebuilding sysvol..







.

Relevant Pages