Autodesk Design Review 2008 and Autodesk DWF Writer 2008 MSI files

We had and still have many requests to provide access to the Autodesk Design Review 2008 MSI file. During the Nile Beta we decided not to share it on a large scale but did provide access on a “per request basis” – that seemed to have worked well.

Now with the Autodesk Design Review 2008 product having been released, there is no further reason to stop distributing the MSI file on a larger scale. You will also find a link to the DWF Writer MSI file.

Download DesignReview2008.msi (37321.0K)
Download DWFWriter2008.msi (19642.5K)

These MSI files contain the exact same versions of the applications that you would get if you installed them using the EXE-based installers. We also take the opportunity to share some tips with you that should make the whole deployment experience easier for you.

To create the MST file and deploy the program:

1. Download orca (In the Windows SDK)
   http://msdn2.microsoft.com/en-us/library/aa370557.aspx.
2. Read Autodesk instructions for a silent install http://dwf.blogs.com/beyond_the_paper/2007/02/free_autodesk_d.html.
3. Watch this introduction to creating MST's with Orca
   http://www.software-repackaging.com/files/flash/orca.htm.
4. Open the MSI file, create a MST, and add the two required parameters.
5. Create a group policy object to deploy the program, making sure you choose advanced and add the transform file you just created.

Happy Deployment!

--Volker

Comments

[Mike Perry]

Hi Volker and Scott
Quick question if I may...
Is the above DWFWriter2008.msi the *same* DWFWriter as DWFWriter3.5Setup.exe (currently available via http://www.autodesk.com/dwfwriter - just distributed in a different format?
Take care, Mike

[Scott Sheppard]

The MSI for these installers contains the same components as those for the released versions of these products. So DWFWriter2008.msi is the same as SetupDWFWriter3.5.exe. DWF Writer 3.5 is an update from the previous DWF Writer 3.0; however many of our applications are flying under their 2008 names now.

[Mike Perry]

Hi Scott
Thanks for the prompt and helpful reply :)
Just a suggestion: To help prevent any confusion would it not make more sense to distribute both packages under the same name e.g.
DWFWriter2008.msi & DWFWriter2008Setup.exe
OR
DWFWriter3.5.msi & DWFWriter3.5Setup.exe
OR
...
Take care, Mike

[Scott Sheppard]

Yes it would make more sense. I believe we listen to Talking Heads music quite frequently and had their _Stop Making Sense_ album in heavy rotation. It would take an act of God to get files renamed at this point. I will update the blog article that these items are the same. Thanks for the idea.

[Ross]

Gaaah, none of those steps are necessary, and I should know, I wrote them!

As I explained during the Beta, I discovered that Design Review will install fine without needing any of those extra steps.

You can install DR2008 via Group Policy by simply assigning the MSI file to computers.

Of course, disabling update checking is another matter... I'm still working on that one.

[Ross]

There's also no link to this page from the main autodesk site, the DR2008 product page, the support pages, or the knowledgebase.

I only knew about it because I'd read of it during the beta, on a forum that's now closed.

How exactly are corporate customers supposed to find out about this download?

[Ross]

Recommended technique for deploying Design Review 2008.

If you don't want automatic updates, this is a better approach than using the provided MSI file:

1. Install WinInstall LE 2003 on a server (free MSI packaging tool for Windows)
2. Install a clean client PC, ensure it is fully patched with latest windows installer
3. Run the WinInstall discover tool
4. Run the Design Review 2008 installation
5. Run Design Review 2008 once
6. Edit the registry, turn off all auto update settings
7. Run the WinInstall discover tool again to create the custom MSI
8. Run WinInstall on the server to edit the package, remove the Microsoft registry entries that will not be needed

You now have a MSI file that can be used to deploy Design Review 2008 across your network, without it checking for updates.

[Volker Joseph]

Thank you for the feedback.

We are looking at options as to how to better integrate the blog into the world of DWF and I will provide an update as soon as available.
I would like to provide an updated post on your new deployment suggestion, ensuring that I make good on me failing to mention you in the earlier article, aside from sharing your new idea with our readers.

[Craig Walsh]

Have you guys got a similar MSI installer for Autodesks Motion Builder 7.5??

[GCW Jeff]

Winstall isn't going to stop the thing for checking for new versions. It will on the installation profile... but...

I edited the base MSI provided here, and it works great on the installation profile. But other profiles (especially newly created ones and even more especially user profiles - as opposed to admin or power user) don't pull the data from the HKLM - I'm assuming because it doesn't have write access to it, it makes new (default, hard set) reg keys in HKCU.

Seriously, you guys can't make something work properly on user-level logins? I'm being very stern here, but think about it:
If a USER cannot write to HKLM, they can't install or update software. If they can't install software, they shouldn't be trying to update DR at all, and chances are that the user won't be able to hit the network in the way you want to see if there's an update to begin with.