Discussion Locked

Using MS default install directories

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

What is the conventional wisdom regarding the installation of Microsoft 32bit software O/S & otherwise in directories that are not the MS default?
For example
Would using non default directories provide an extra level of security against virii?
Could it provide extra protection from malicious HTML?
Can the directory names indicate to end users that they really shouldn't be exploring this folder?
Do non-default names make for technical nightmares? If so how?

Any views are appreciated

1 reply

by aclopez5

To be honest, I haven't seen to many non-default installations. But, to answer your question, it depends on the virus/malicious code. A well written app would look for the OS directory using the ADMIN$ hidden share or the WINDIR enviornment variable. But a poorly written app, or a blind hack attempt (like some of the IIS exploits) could be hampered by using a non-standard location.

As for technical issues, as long as those supporting it know where the OS is installed, it shouldn't be an issue.

This discussion is closed to new replies.