Well this is a new one for me...maybe you guys have seen it before but its a real pain
I was tweaking some local security settings to beef up certain things.
Users were also frequently and annoyingly sharing every cd-rom in sight so as to not have to carry CDs around
so i enabled the local security setting that allows only locally logged in user CD-rom access.
A few days later I try reformatting a system (employee managed to destroy his OS...laptop user who needs admin privs...*sigh*)
and poof, on trying to install MS apps I get read errors when attempting to access the .CAB files.
So I did some trial and error on my GPO settings and it turns out that the CDROM setting is the source of the problem.
Now is it just me or is it dumb to implement a security feature that prevents some system process/user to access files for an install iniated by a admin level user?
I was tweaking some local security settings to beef up certain things.
Users were also frequently and annoyingly sharing every cd-rom in sight so as to not have to carry CDs around
so i enabled the local security setting that allows only locally logged in user CD-rom access.
A few days later I try reformatting a system (employee managed to destroy his OS...laptop user who needs admin privs...*sigh*)
and poof, on trying to install MS apps I get read errors when attempting to access the .CAB files.
So I did some trial and error on my GPO settings and it turns out that the CDROM setting is the source of the problem.
Now is it just me or is it dumb to implement a security feature that prevents some system process/user to access files for an install iniated by a admin level user?