A side effect is that when machines get reimaged users do not have to worry about recreating site settings etc, they can move around the workplace and use any machine and have thier site settings present.Ĭhange the registry location specified for other versions of dreamweaver - enjoy.Macromedia, Inc., was an American graphics, multimedia, and web development software company (1992-2005) headquartered in San Francisco, California, that made products such as Flash and Dreamweaver. Settings get imported upon launch of dreamweaver and exported upon termination of dreamweaver. This simply exports the dreamweaver registry settings from the registry that contain the site settings into a registry fil on the users network drive and reimports. The H: refers to our users mapped network home drive, change this to whatever your users use. #c:\windows\regedit /s /e H:\cfgs\reg\dreamweaver.reg "HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 6" #c:\windows\regedit /s H:\cfgs\reg\dreamweaver.reg NB You need to deny access to this registry key as the MSI tries to recreate this during install!Īs you know the site settings are the most important part of dreamweaver and having to recreate can waste a lot of time.įor other Novell network users a simple way to bypass this is to add the following to the launch application object under the run befor launching and the run after termination run object / launch script settings : This can be done by deleting following registry InstallDriver" Solution the InstallShield DCOM "Interactive User" value needs to be removed. MSI (c) (2C:20) : MainEngineThread is returning 1603 If counter >= 0, shutdown will be denied. MSI (c) (2C:20) : Decrementing counter to disable shutdown. MSI (s) (2C:24) : Custom Action Manager thread ending.
MSI (s) (2C:C8) : Destroying RemoteAPI object. MSI (s) (2C:30) : MainEngineThread is returning 1603 MSI (s) (2C:30) : Deleting URL local copy C:\WINDOWS\Installer\MSI9.tmp.
MSI (s) (2C:30) : Cleaning up uninstalled install packages, if any exist
MSI (s) (2C:30) : Attempting to delete file C:\WINDOWS\Installer\55e793.mst MSI (s) (2C:30) : Product: Macromedia Dreamweaver 8 - Installation operation failed. Installing using Software distribution tool logged on as a locked down user receive the following error. msiexec.exe /i "Macromedia_Dreamweaver_8.msi" TRANSFORMS="Macromedia_Dreamweaver_8.mst" /qb-! The command-line I used to fire the package off is this.
In the SMS source folder, I have the original Macromedia_Dreamweaver_8.msi file, the. In AdminStudio's Tuner app, you can drag the entire original Macromedia folder (that contains the license files several folders below) over to the CommonAppDataFolder section inside the "Destination Computer's Folders" window. MST needs is the files from the C:\Documents and Settings\All Users\Macromedia folder (and all sub-folders/files). mst transform using AdminStudio's Tuner by opening the main Macromedia_Dreamweaver_8.msi file.
Here's how I did it.Īfter installing Dreamweaver manually and entering the registration info, I created an. CAB containing the license folders/files and pass it to the original 8.0 MSI file, which will accept a /qb-! silent command-line option. Using the original version 8.0 msi from the cd and an MST transform I created, I was able to execute a silent install through SMS. The license.mlf should be copied to the -Macromedia-Licensing-Products\Dreamweaver 8.0
I also took the license.mlf that is created after inputing your serial # and company information and added it to the MST file which incorporated it into the MSI. I created an MST file and added the registry keys from HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Dreamweaver\8\Registration Before launching the application I ran filemon and regmon to capture the necessary information to keep the user from having to register.
I used msiexec /a then applied the current patch to the admin install(/p). On the Dreamweaver Media there is a folder named FSCOMMAND where the MSI resides that you can successfully use to create the Admin install. If the user is not an adminsitrator they will get an error because the installscript.msi is trying to write to the all users application data directory which a non admin has no rights. The following information is used and it is assumed that the user running the installation is an Administrator.