Autodesk Navisworks

[#1]

I have an existing deployment image of Navisworks 2010, for which I want to add the Service Pack to.
When I go to modify the deployment, I see no option to add this. Am I missing something, or does this option not exist as it does for other Autodesk applications?

Thanks for any help.

[#2]

Correct, the option does not exist. The service pack will need to be run after the deployment is installed.

Andy

[#3]

Thats very inconvenient. Thanks for the update, but this is needed for future releases.

[#4]

If you want to describe the nature of inconvenience, that would be helpful. At this moment, we have no plans to add the option in for 2011.

Andy

[#5]

I'm a CAD Manager for roughly 3,000 users. We roll out deployments silently and they get installed overnight.
It would be nice, like the other Autodesk applications, to be able to include the service packs into the deployment. Makes installation much easier.

[#6]

Is it not sufficient to run the service pack silently? Pass /S (note: Captial S, /s will not work) as the argument to the service pack executable.

For new installs, could you not create a batch script that first runs the deployment, then runs the service pack afterwards? A batch script to do this would look something like this:

pushd *setup.exe folder*
setup.exe /Script /Wait /Language en-US *deployment_inifile*
popd
service_pack.exe /S

Andy

[#7]

The question is not "is it not sufficient to do X Y Z workaround."

The question is why does the Navisworks team feel it's OK not to follow the same
higher and MUCh more convenient standard set by the rest of Autodesk's
applications?

Matt
matt@stachoni.com


On Tue, 24 Nov 2009 07:16:11 -0800, AndyG_ADSK <> wrote:

>Is it not sufficient to run the service pack silently? Pass /S (note: Captial S, /s will not work) as the argument to the service pack executable.
>
>For new installs, could you not create a batch script that first runs the deployment, then runs the service pack afterwards? A batch script to do this would look something like this:
>
>pushd *setup.exe folder*
>setup.exe /Script /Wait /Language en-US *deployment_inifile*
>popd
>service_pack.exe /S
>
>Andy

[#8]

Matt,

Our installer has a number of complexities not present in other Autodesk products that mean we cannot use the same service pack procedure. It is our desire to follow the standards of other Autodesk products but in some cases it is not possible.

Andy