Example of the directory structure in a large production environment.
Root level |
..\ |
..\ |
..\ |
..\ |
Description |
_System |
|
|
|
|
Miradore initial installation and client application files. |
|
_Start |
|
|
|
Files used in initial OS installation. |
|
Miradore |
|
|
|
Miradore client application files. |
|
|
_Current |
|
|
Latest versions of Miradore client media, client installation scripts and Miradore Actionset. |
|
|
Linux |
|
|
|
|
|
|
Current |
|
|
|
|
|
|
DEB |
Debian/Ubuntu client |
|
|
|
|
SUSE |
OpenSUSE/Suse Linux Enterprise client |
|
Tools |
|
|
|
DHCP and TFTP tools. |
Drivers |
|
|
|
|
Device drivers for computer initial installations. Notice! Since the new driver management in Miradore Management Suite 2.3.0, the directory structure under Drivers directory can be anything you want. It is only recommended that you have one driver per directory. |
|
<DeviceXXX> |
|
|
|
Directories containing drivers. |
OS |
|
|
|
|
Contains directories for operating system media (like WinXP, W2003SRV, etc.). Directories must align with OS short names. |
|
Linux |
|
|
|
Linux Operating system media. |
Packages |
|
|
|
|
Directory for additional files (in addition to original media) needed in installation packages. |
|
<Package name> |
|
|
|
Files are divided into directories based on package name. |
|
|
<Package version> |
|
|
Files used in different package versions are divided into version directories. |
Uninstallation_ Packages |
|
|
|
|
Directory for additional files needed in uninstallation packages. |
|
<Package ID> |
|
|
|
Files are divided into directories based on package ID. |
Setup |
|
|
|
|
|
|
Patches |
|
|
|
Directory for storing security patches. |
Software |
|
|
|
|
Structure for original installation media used in installation packages. |
|
Common |
|
|
|
Media which can be used globally. |
|
|
<Manufacturer> |
|
|
Subdirectory for each software manufacturer. |
|
|
|
<Software> |
|
Subdirectory for each software. |
|
|
|
|
<Version> |
Subdirectory for each software version. |
See also