Silent Uninstall Navisworks Freedom/Review 2010
Hi Guys,
Long time reader, first time poster (So please be kind) and I hope i have posted this in the correct area.
I'm hoping one of you wonderful people may be able to help me. Over the past few month's i have been writing a batch file (Yes i know batch is very very old and i should be running in at least vbs) which installs all of our required software without any user intervention (Asiding the user selecting what software they want installed)
I've now started creating an uninstall section. For the most, with each peice of software having its own quirks and silent uninstallation problems I have got everything working, Except for Autodesk's Navisworks Review and Navisworks Freedom 2010.
I have tried everything I can think of, spent hours trolling Autodesk's website and google searching on everything term/phrase i can think of. NW Review and Manage 2009 was easy to uninstall compared to 2010, it has a msi file located under the \adminimage\x86\ folder called roamer.msi. Simply executing a msiexec /x path\roamer.msi /passive it would uninstall silently without any questions.
However Autodesk in their wisdom have now removed this feature, and running roamer.msi results in "You need to run setup.exe to (un)install navisworks"
I have tried every switch I can think of to get setup.exe to uninstall. The closest I have come so far is to execute:
c:\program files\autodesk\navisworks freedom 2010\setup\uninstall.exe /P {B6265042-C13F-0000-9EAF-50C8C240434F} /M FREEDOM (got this from the registry hklm\software\microsoft\windows\currentversion\uninstall\autodesk navisworks freedom 2010)
This works, but presents the modify navisworks window, with the option to Repair or Reinstall or Uninstall.
I'm hoping someone out there may know of an extra switch that I can put in that will force it to silent uninstall for both Review and Freedom 2010
Thanks in advance
Adam
Long time reader, first time poster (So please be kind) and I hope i have posted this in the correct area.
I'm hoping one of you wonderful people may be able to help me. Over the past few month's i have been writing a batch file (Yes i know batch is very very old and i should be running in at least vbs) which installs all of our required software without any user intervention (Asiding the user selecting what software they want installed)
I've now started creating an uninstall section. For the most, with each peice of software having its own quirks and silent uninstallation problems I have got everything working, Except for Autodesk's Navisworks Review and Navisworks Freedom 2010.
I have tried everything I can think of, spent hours trolling Autodesk's website and google searching on everything term/phrase i can think of. NW Review and Manage 2009 was easy to uninstall compared to 2010, it has a msi file located under the \adminimage\x86\ folder called roamer.msi. Simply executing a msiexec /x path\roamer.msi /passive it would uninstall silently without any questions.
However Autodesk in their wisdom have now removed this feature, and running roamer.msi results in "You need to run setup.exe to (un)install navisworks"
I have tried every switch I can think of to get setup.exe to uninstall. The closest I have come so far is to execute:
c:\program files\autodesk\navisworks freedom 2010\setup\uninstall.exe /P {B6265042-C13F-0000-9EAF-50C8C240434F} /M FREEDOM (got this from the registry hklm\software\microsoft\windows\currentversion\uninstall\autodesk navisworks freedom 2010)
This works, but presents the modify navisworks window, with the option to Repair or Reinstall or Uninstall.
I'm hoping someone out there may know of an extra switch that I can put in that will force it to silent uninstall for both Review and Freedom 2010
Thanks in advance
Adam
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Nope, wrong section: should be in 'PAckage Development' :) A moderator may move it.
As for uninstall, you *may* be able to use the MSI by passing a commonly-used property to it. Many, many InstallShield-authored packages are set up this way and can be fooled into believing that they're driven by the set-up stub. Try:
As for uninstall, you *may* be able to use the MSI by passing a commonly-used property to it. Many, many InstallShield-authored packages are set up this way and can be fooled into believing that they're driven by the set-up stub. Try:
msiexec /x [path_containing_roamer.msi]roamer.msi /qb ISSETUPDRIVEN=1 [other command-line arguments]
Posted by:
adam1982
15 years ago
Thankyou for the quick reply! Sorry about posting in the wrong section.
I tried passing the ISSETUPDRIVEN=1 to it, but no success. Having never seen the ISSETUPDRIVEN=1 before, i started to google it. Do I need to install isscript install msi file as well? (I'm guessing from what i've read so far, that I need to extract the specific isscript.msi from the navisworks install by running setup.exe looking in the TMP folder for the extracted files and copying the isscript msi file out)
Is that correct? or is there another way?
Sorry for the silly questions, but thought i'd ask. Now off to google more info about issetupdriven=1 and isscript.msi files etc
Thanks in advance
Adam
I tried passing the ISSETUPDRIVEN=1 to it, but no success. Having never seen the ISSETUPDRIVEN=1 before, i started to google it. Do I need to install isscript install msi file as well? (I'm guessing from what i've read so far, that I need to extract the specific isscript.msi from the navisworks install by running setup.exe looking in the TMP folder for the extracted files and copying the isscript msi file out)
Is that correct? or is there another way?
Sorry for the silly questions, but thought i'd ask. Now off to google more info about issetupdriven=1 and isscript.msi files etc
Thanks in advance
Adam
Posted by:
abking99
15 years ago
Posted by:
adam1982
15 years ago
Posted by:
abking99
15 years ago
Posted by:
adam1982
15 years ago
Posted by:
anonymous_9363
15 years ago
Do I need to install isscript install msi file as well?Possibly. Some InstallShield-authored MSIs are almost completely driven by calls to functions in the IS DLLs, others just use some (and most of those are either spurious or can be replaced by normal MSI actions). So the answer is, it depends :) In practise, most larger shops install the IS runtimes as part of their builds: they're designed to live side-by-side (kind of) and use little by way of resources.
Posted by:
adam1982
15 years ago
Hi All,
Sorry for the delay in reply. I did as abking99 suggested and did the logging. It created a 80kb logfile for a 2second run before it errored out saying i need to run setup.exe.
I'm still reading through the log file at the moment, I havent found anything obvious just yet.
I was going to attach the log file to this post, but I just noticed that I cant attach files..?
If anyone has any free time to have a look at the log file as well, i can email?
Cheers
Adam
Sorry for the delay in reply. I did as abking99 suggested and did the logging. It created a 80kb logfile for a 2second run before it errored out saying i need to run setup.exe.
I'm still reading through the log file at the moment, I havent found anything obvious just yet.
I was going to attach the log file to this post, but I just noticed that I cant attach files..?
If anyone has any free time to have a look at the log file as well, i can email?
Cheers
Adam
Posted by:
anonymous_9363
15 years ago
Posted by:
vnerdahl
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.