Table 4. Deployment Method Matrix
Deployment Methods | Complexity | Advantages | Disadvantages | ||
|
|
|
|
|
|
Local deployment | Relatively simple | • | Necessary if a | • | Any change requires |
(bootable media) |
| ||||
|
| network connection |
| the creation of a new | |
|
|
|
| ||
|
|
| is not available or is |
| bootable media. |
|
|
| too slow. | • | Limited space on |
|
|
|
| ||
|
| • | Can install supported |
| media for some |
|
|
| Windows operating |
| operating system |
|
|
| systems. |
| installation files. |
|
| • | Can perform | • | Deployment tasks |
|
|
| a minimal installation |
| must be performed at |
|
|
| of supported Linux |
| the individual target |
|
|
| operating systems. |
| system. |
|
|
|
| • Media are | |
|
|
|
|
| and requires the |
|
|
|
|
| creation of a |
|
|
|
|
| RAMDISK for |
|
|
|
|
| temporary data |
|
|
|
|
| storage. |
|
|
|
| • | Installation time is |
|
|
|
|
| high. |
Remote deployment | Moderate | • Everything is in one | • | Must have network | |
over a network |
| ||||
|
| place in a network |
| connection. | |
(bootable Windows |
|
|
| ||
|
| share. | • | Deployment tasks | |
PE or Linux media |
|
| |||
| • Easy to manage — | ||||
with network stack |
|
| must be performed at | ||
|
| changes have to be |
| the individual target | |
loaded) |
|
|
| ||
|
| made in a single |
| system. | |
|
|
|
| ||
|
|
| location. | • | Must locate the |
|
|
|
| ||
|
| • | Data captured |
| appropriate Windows |
|
|
| (profiles) can be |
| PE or embedded |
|
|
| stored in a network |
| Linux network drivers. |
|
|
| share. | • Not supported from a | |
|
|
|
| ||
|
| • | Data can be |
| mapped NetWare |
|
|
| replicated from a |
| system. |
|
|
| network share. |
|
|
|
| • | Can install supported |
|
|
|
|
| Windows or Linux |
|
|
|
|
| operating systems. |
|
|
Deployment solution | Mixed | • DTK can be used in | Must either acquire and | ||
framework from a |
| learn to use or have an | |||
|
| context of | |||
third‑party vendor |
|
| deployment solution | existing | |
|
|
| framework. | deployment solution | |
|
| • | framework. | ||
|
|
|
| ||
|
|
| deployment solution |
|
|
|
|
| framework is used as |
|
|
|
|
| the deployment |
|
|
|
|
| transport mechanism. |
|
|
|
| • Tasks and scripts can |
|
| |
|
|
| be pushed to the |
|
|
|
|
| target systems. |
|
|
PXE boot for Linux | High | • | Everything is in one | • | Must have |
|
|
| place on a network | ||
|
|
| share. |
| connectivity to |
|
| • Easy to manage — |
| network (LAN). |
changes have to be
17