K
Kyle
I am in the process of developing an OU and GPO for our Terminal
Servers to further lock them down. I have been following MS's
recommended settings article (Q278295). I have enabled both the "Hide
Drives" and "Prevent Access to Drives" policies for A,B,C,and D
drives. Once this is implemented however, when a user launches
Windows Explorer, the following error is presented:
"This operation has been cancelled due to restrictions in effect on
this computer..."
If I click OK, Windows Explorer opens and functions correctly. I can
not access nor see the C: and D: drive. Which is what I want. My
question is, Why does the error message pop up each time I launch it?
I have played around with shortcuts and changing the start-in folder
to the E: drive, and have even made a copy of explorer.exe and moved
it to the E: drive....nothing seems to work. If I disable the
"Prevent access to the drives" policy, it starts working again. That
however is not the best solution as users can then access the system
drive (which I do not want to happen).
Thank you.
Kyle
Servers to further lock them down. I have been following MS's
recommended settings article (Q278295). I have enabled both the "Hide
Drives" and "Prevent Access to Drives" policies for A,B,C,and D
drives. Once this is implemented however, when a user launches
Windows Explorer, the following error is presented:
"This operation has been cancelled due to restrictions in effect on
this computer..."
If I click OK, Windows Explorer opens and functions correctly. I can
not access nor see the C: and D: drive. Which is what I want. My
question is, Why does the error message pop up each time I launch it?
I have played around with shortcuts and changing the start-in folder
to the E: drive, and have even made a copy of explorer.exe and moved
it to the E: drive....nothing seems to work. If I disable the
"Prevent access to the drives" policy, it starts working again. That
however is not the best solution as users can then access the system
drive (which I do not want to happen).
Thank you.
Kyle