Knowing the installation process fucntions and steps it well possible to deploy as MSI package. With 9.4 AMO and Eguide are being promised having to be MSI pacakge. With 9.1.3 was delivered with CD images. That is a relative small installation step easy to be repackaged in a MSI style. (CCM). 9.2 and 9.3 are delivered in XML approach run by a java procedure. These XML file are easy readable / re-engineerd.  It covers: - Some Windows updates files (VB COM etc) redistributables - Unpacking - unzipping placing of physical files - Adjustments in .Net  (Com settings)   when missing this step you get all installed win registered well updated. But failing in running without any clear indicators messages.    Would advice to  have 3 steps: 1/ windows updates. These MS redistributables have a check on their own. 2/ Desktop SAS:    2.1 update Winregister snapshot    2.2 placing the location of files (unpack/unzipped).   Remember: a/ a networkdrive is in zone local intranet, not local machine. (I remember caspol)                       b/ using a networkdrive may generate the url of it not the letter.   3/ Update .Net and other MS settings outside of the Window-register.     Additional ideas:  Having a well maintained fileserver approach. You could choose to place the unpacked unzipped generic file-share. - By this the only needed updates to a windows desktop are minimized (several MB's at max). - Needing an update in a file will be achieved by replacing files not by repackaging - The trade off is a slightly slower start of the tool, after that Windowsprocesses will cache a lot.     When you are dealing with AMO don not forget addtional tools like the option to switch between AMO versions  For all make sure the result should be as the SAS deployment proces (to be tested at the packaging approach). Some security policies are possible troublemakers in almost every approach. ... View more