Since you can't take advantage of SMS (System Management Services) services, I would opt for using Windows Installer, which ships with the Microsoft Windows Server 2003 family, Windows XP, Windows 2000 and Windows Me. The Windows Installer technology consists of the Windows Installer service and the package file, file extension .msi. MSI files are actually database files which store information about every file and setting that the...
application installs or modifies. Using an MSI file has its advantages; it can create a system restore point on machines running Windows XP. It also ensures that Windows has enough information to replace any damaged or removed components. Windows Installer can help you manage the installation, addition, and deletion of software components, handling installation progress, rollbacks and reboots. You can also install applications to run directly from a network share, without the need for a local copy, or you can choose to only install the software when it's run for the first time.
You can use the WinInstall Limited Edition tool, which comes in the Valueadd folder of the Windows 2000 and 2003 CDs, to create MSI files. The tool takes a snapshot of a machine that has a clean Windows installation. You then install the application that you want to deploy to your users' machines; at this point, another snapshot is taken. WinInstall compares the snapshots and uses the differences between the two images to create an MSI file and installation package. If you want, you can install multiple applications onto the clean machine prior to taking the second snap shot. This means you can create a single MSI file and installation package that deploys multiple applications or patches. Once you have created your MSI file, you need to make it available to your network users. You can do so by copying the installation files to a network share for which everyone has read permissions. Installing from a network share avoids the need for you to copy the files to a CD and allows you to automate the installation by using a script. To do this, create a network logon script to run the MSI file the next time a user logs on. You might also want to take a look at the Windows Office XP Resource Kit's Custom Installation Wizard to help you customize your Microsoft Office installation.
Dig deeper on Windows Security: Alerts, Updates and Best Practices
Related Q&A from Michael Cobb
A reported 43% of Microsoft XML users are running vulnerable versions of the software. Security expert Michael Cobb discusses how to mitigate the ...continue reading
Security expert Michael Cobb explains what Open Authorization or OAuth 2.0 is, its pros and cons, and how it is different from bring your own ...continue reading
While the fundamentals of securing an e-commerce website haven't changed in a few years, there are new threat vectors and security risks to be aware ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.