Anonymous_User Absent Member.
Absent Member.
3364 views

Office 2007 (visio)

Hi,

Just looking at how Visio 2007 installs, and from what i have read, you
cant run it from an msi, it has to be run from setup.exe.
(http://technet2.microsoft.com/Office/en-us/library/97bf0177-9438-4584-b86f-e608fc995d971033.mspx?mfr=true)

I've used OCT, and that all works, but just curious as how to use
ZENworks to deploy it. I've only deployed .msi's.

Where possible, i like to add the serial number via a property in the
MSI tab of consoleone, but i'm not sure if this will be possible using
setup.exe.

Any help appreciated.
Labels (2)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Office 2007 (visio)

I have got it all going now.

Just did the Simple application (no .msi) option. properties can still
be passed on cmd line with setup.exe (see Office 2007 setup properties:
http://office.microsoft.com/en-au/help/HA011364681033.aspx)

Only prob i have is with dependencies. From within the Visio object, i
have added XMLlite (which is an .exe too). I have tested that on it's
own, which is all ok, but when now running Visio, it has both installers
going at the same time.

Not really a problem i guess, but i would have preferred if XMLlite
finished before it started to install Visio.

On 2/07/2007 4:25 PM, Andrew Dauncey wrote:
> Hi,
>
> Just looking at how Visio 2007 installs, and from what i have read, you
> cant run it from an msi, it has to be run from setup.exe.
> (http://technet2.microsoft.com/Office/en-us/library/97bf0177-9438-4584-b86f-e608fc995d971033.mspx?mfr=true)
>
>
> I've used OCT, and that all works, but just curious as how to use
> ZENworks to deploy it. I've only deployed .msi's.
>
> Where possible, i like to add the serial number via a property in the
> MSI tab of consoleone, but i'm not sure if this will be possible using
> setup.exe.
>
> Any help appreciated.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Office 2007 (visio)

Well i shouldn't have worked on this so early..

That url was for Office XP setup properties. Office 2007 setup
properties here:
http://technet2.microsoft.com/Office/en-us/library/41f07f9b-f0d0-489d-a185-d7b96f21f5611033.mspx?mfr=true

And it doesn't take any properties on command line 😞

I unticked 'Continue distributions immediately', and now the
dependencies work.


On 5/07/2007 9:10 AM, Andrew Dauncey wrote:
> I have got it all going now.
>
> Just did the Simple application (no .msi) option. properties can still
> be passed on cmd line with setup.exe (see Office 2007 setup properties:
> http://office.microsoft.com/en-au/help/HA011364681033.aspx)
>
> Only prob i have is with dependencies. From within the Visio object, i
> have added XMLlite (which is an .exe too). I have tested that on it's
> own, which is all ok, but when now running Visio, it has both installers
> going at the same time.
>
> Not really a problem i guess, but i would have preferred if XMLlite
> finished before it started to install Visio.
>
> On 2/07/2007 4:25 PM, Andrew Dauncey wrote:
>> Hi,
>>
>> Just looking at how Visio 2007 installs, and from what i have read,
>> you cant run it from an msi, it has to be run from setup.exe.
>> (http://technet2.microsoft.com/Office/en-us/library/97bf0177-9438-4584-b86f-e608fc995d971033.mspx?mfr=true)
>>
>>
>> I've used OCT, and that all works, but just curious as how to use
>> ZENworks to deploy it. I've only deployed .msi's.
>>
>> Where possible, i like to add the serial number via a property in the
>> MSI tab of consoleone, but i'm not sure if this will be possible using
>> setup.exe.
>>
>> Any help appreciated.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.