- Message Boards
- Package KB
- Software KB
- Free Videos
- MSI Errors
- Tools
- Tech Home Pages
- Reviews
- Downloads
- Articles
- FAQs
- Tips & Tricks
- Services
- News
- Newsletter
![]() |
|
|
Specops Deploy 3.0 by Bob Kelly |
Page 5 of 6 |
Package Deployment Process
I mentioned before that Specops Deploy “downloaded” the packages prior to
installation. I know it raised a flag in my head when I heard it: is the source
kept local after the installation is complete? What about MSI installation
source pointers? Worry not; the guys at Special Operations Software have it
covered.
BITS 2.0 is used to download the installation locally. This is the same
"trickle" download feature used by Windows Update and Software Update Services (SUS).
In this way, the download uses SMB and is not restricted to HTTP so you do not
have to install a web server and will have no problem installing from any
location (such as from DFS or any file share). If BITS 2.0 is not found on a
target computer, it
will automatically revert to an SMB connection for the download. Once the file
is downloaded, the installation takes place from this downloaded copy of
the installation files.
As
discussed earlier, the entire folder contents (as well as any subfolders and
their contents) are copied to target systems for the installation and are then
removed. So you are
covered if you are dealing with a legacy setup that requires multiple files (or
directories of files). If
the package is a Windows
Installer setup, the source location is pointed back to the original path on
your network in case
the package needs to be repaired or any features are set to install on demand.
During
installation, a taskbar icon appears to indicate status- click on it and get
more details as to what is going on (see screen shot).
When creating a deployment in the Specops Deploy console, you can choose a custom message to display to users but there are currently no options to allow users to abort an installation or delay its installation. The timer starts at fifteen minutes and may be initiated sooner by the user if they hit the provided "Start Now" button.
Finally, when you create a
deployment you can also specify if the installation should take place as soon as
possible (default) or not before a specified date and time. This is also where
you may dictate if the installation should take place only during startup, only
after the computer has been started (or logged on), or either.





