Visio 2003 Deployment In LANDesk

its easy

first,see the source fies ...in that u will see an setup.exe and .msi file

Use microsoft resource tool kit(you should download it)... ork.exe 

using the above tool convert .msi to .mst....(after downloading and running tool ..go to program features--->microsoft office..>office tools...>custom installation wizard...follow the steps finally .mst file will be created.


Change the .ini file in setup folder

(Copy from here .....and to end)...but change the .msi and .mst names as per your source.but important to change .mst file path to landesk dumping final location

; Microsoft Office SETUP.EXE settings file.

; The MSI section gives the name of the MSI file to install. This file must be in
; the same folder as Setup.exe, and both must be in the root of the installation
; tree.

ProductName=Microsoft Office Visio Standard 2003

; The MST section gives the full path to a transform that should be applied.
;MST1=\\server\share\some transform.mst
;MST1=C:\Program Files\LANDesk\LDClient\sdmcache\packages\visio2003STD\.mst

; The option section is used for specifying individual Installer Properties.
;COMPANYNAME=my company

; The diplay section is used for overriding the default UI
; Value Default Description
; Display full Option to override the default UI
; [none, quiet, basic, reduced, full]
; CompletionNotice Yes Option to display a setup completion
; notice for otherwise quiet setup

; The logging section provides settings for controlling the Setup log files.
; Value Default Description
; Type vpiwaeo Logging modes
; [a, c, e, i, m, o, p, r, u , v,
; w, *, +]
; Path %TEMP% Path to create logfiles
; Template SetupLog(*).txt File name for log file should end in
; "(*).txt"; the * is replaced with a 4
; digit number to make the file name unique
Template=Microsoft Office Visio Standard 2003 Setup(*).txt
;Template=Product %UserName%(*).txt

; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.

; The cache section provides settings for caching the install source locally
; Value Default Description
; CDCACHE 2 Option to specify cache level
; [auto, 0, 1, 2]
; LOCALCACHEDRIVE <predefined> Option to specify a drive to cache
; the install source to
; DELETABLECACHE 1 Option to display UI to remove the
; cache at the end of setup [0,1]
; PURGE 0 Option to always remove cache at end of
; setup [0,1]




Then...everything is set..to packae in landesk


go to distribution packages and create new distri package

give a name...path of the msi where it is in the server.....

install/uninstall:  in the box type:                TRANSFORMS=VISIO2003.MST /i /quiet /norestart

click on additional files and move the required files from avilable to additional files

save it


create a deliverty method

 policy supported push

standard policy-supported push distribution


schedule a task under my packages

give task a name

and select package u want to deploy underdistribution package

and select delivery method .....policy supported push   .........standard policy-supported push distribution...save

/....then go do devices ..select all devices and in search box enter the computer name (msinfo32 is used to know sys name type it in run)to which sys u want to deploy...

then it will show up the sys name draga nd drop it to the schediuled task under my packages

and right click on the package and click  on start now and all....it will deploy....it should say error code "0" and sucessfully deployed


see the attached file its 4 office 2003 but it willl have same procedure.......

be sure to give the  .mst path in .ini file...u should give the path where landesk dump the files to a folder c:program files path above   C:\Program Files\LANDesk\LDClient\sdmcache\packages\visio2003STD\.mst


Thank you


This post is locked

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ