Has nothing to do with it being a share. But sure, if you have VSS enabled on a drive, and sysvol happens to be on that drive, then you get shadow copies.
(That’s an oversimplification, but so was the question. And the answer is accurate within the boundary of the question.) From: [email protected] [mailto:[email protected]] On Behalf Of Gantry Zettler Sent: Wednesday, October 18, 2017 11:39 PM To: [email protected] Subject: Re: [NTSysADM] Pro tip for you: free... Since sysvol is a share, does it get shadow copies when you enable it on a drive? Never had a reason to check... On Wed, Oct 18, 2017 at 2:07 PM, Kurt Buff <[email protected]<mailto:[email protected]>> wrote: On Wed, Oct 18, 2017 at 5:27 AM, Michael Leone <[email protected]<mailto:[email protected]>> wrote: > On Tue, Oct 17, 2017 at 1:24 AM, Kurt Buff > <[email protected]<mailto:[email protected]>> wrote: > >> I can't say for sure what caused it, but somewhere during this process >> about 10 out of the 70+/- GPOs got fubared, and I had to recover them >> - something I've never had to do before. Thank all the gods (and >> decent planning!) that I had snapshot backups of the DC holding all of >> the FSMO roles, and could mount the VMDK and pull out the sysvol >> directory and copy them back from the Friday night backup. > > Really. I have a scheduled task that backs up all GPOs to a central > share on the last day of the month. I always assumed that if I needed > to, I could import a GPO from there, if I needed to restore some > settings.That seems easier than having to mount a copy of the sysvol > and copy them out of that. Yes, there was a lesson in there for me, and I've learned it. Kurt
