G
Guest
While restoring a four year old archive tape, I mistakenly selected "SYSTEM
STATE" along with the other data that I needed. I redirected the restore to
another partition on our server. Active Directory was not effected. The
only problems I had were Exchange permissions were lost and my login scripts
were overwritten with old login scripts from the restore. With Microsoft's
help, I was able to restore the exchange permissions. I then re-wrote the
login scripts so that is fixed, too. Everything seems to be running fine
again.
My concern is that, as a result of restoring this old system state to
another location on one of my DC's, I now have one ADDITIONAL sysvol folder
in that new location where I placed the restored data. It is replicating
with the rest of our domain controllers. What I would like to know is how do
I delete this extra sysvol folder without messing up our existing domain
controllers?
STATE" along with the other data that I needed. I redirected the restore to
another partition on our server. Active Directory was not effected. The
only problems I had were Exchange permissions were lost and my login scripts
were overwritten with old login scripts from the restore. With Microsoft's
help, I was able to restore the exchange permissions. I then re-wrote the
login scripts so that is fixed, too. Everything seems to be running fine
again.
My concern is that, as a result of restoring this old system state to
another location on one of my DC's, I now have one ADDITIONAL sysvol folder
in that new location where I placed the restored data. It is replicating
with the rest of our domain controllers. What I would like to know is how do
I delete this extra sysvol folder without messing up our existing domain
controllers?