Hi There,
Visio is already in MSI format, which means that to start with you'll want to just create a transform or otherwise manipulate the MSI it came with. I think that Microsoft generally supports silent deployment starting with the command:
setup.exe /admin
Some links that discuss this:
Office Customization Tool (OCT) overview
http://technet.microsoft.com/en-us/library/cc764476.aspxDeploying the 2007 Office system
http://technet.microsoft.com/en-us/library/cc303395.aspxVisio Professional 2007 12.x
http://www.appdeploy.com/packages/detail.asp?id=1072As to the source of the error, I can't be entirely certain. But my educated guess has to do with how the office applications are written to run. Basically, Word.exe, Excel.exe, and I would assume Visio.exe each make Windows Installer API calls to see if the product is correctly installed, and that each keypath is present. Basically, if you rename word.exe to word1.exe it will kick off a repair.
Now, I've not seen the error message you're describing before but I would venture a guess that there's some other integrity checking that's not working quite right. The Office installs are very, very complex so it wouldn't surprise me if this was the case.
As an aside, I've generally seen that the Office applications will work Virtualized in an AppV package if you take the approach you're taking, and just build directly to AppV format, making sure to include the *.context.msi that Repackager builds.
Hope this helps!
--Cary