/build/static/layout/Breadcrumb_cap_w.png

Problem deploying visio 2003 no standard

Im having some problem deploying visio 2003 standard(norwegian) silently. I have downloaded the orktool and created the mst
Somehow my package will not run

I also made a mst for VISIO STANDARD 2003. For the US version this works great

Anyone know why it works with the us version and not with no version?

setup.exe TRANSFORMS="Y:\TCA\Kaare\Work\Ongoing\Confex\Visio\orginale\Visio2003-NO-Std\New Custom Setup File.MST" /qb-




0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 15 years ago
Red Belt
0
I don't think Setup takes arguments like that, does it? Either find out what argument format it takes or, more conventionally, use the MSI which gets extracted to %TEMP%.

I expect the US version works because that's the default.
Posted by: Bankeralle 15 years ago
Second Degree Blue Belt
0
Yes it does, i get the following message when trying do to an unatennded installation with the norwegian visio pack

This version of Microsoft Office Visio Standard 2003 do not support transformchanges for the office-guide og custom installation

(sorry about bad translation) the errormessage is given in norwegian

I think its strange that it works for the us standard version
Posted by: anonymous_9363 15 years ago
Red Belt
0
What happens if you apply the transform directly to the MSI?

BTW, doesn't Office require you to specify a language transform for non-US English deployments? Something rattling away at the back of my mind suggests that it does...
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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