Navisworks Manage/Simulate 2012 - How to add Service pack 1 to Deployment?

[sssteve72]

Ok I am confused.  I went to modify our Navisworks Manage deployment to add in service pack 1.  There are two choices, Include it from a local drive or simply don't include it.  So I set it to local drive and downloaded the service pack from the downloads here: http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=17757207&linkID=10382102 .  And here is the problem it is looking for an MSP file type (Installer patch).  But the file type in the downloads section is an EXE file type.

Where do I get an MSP file so I can include it in the deployment install?

Do I have to use a command line switch that I read in another thread?   Do I just need to use the /a to unpack the MSP and then I can use that in the deployment?

********update********

Ok I unpacked the exe file.... and I see a couple of folders..9.1 9.3 then more folders inside x86...then a navman folder then about 10 MSP files...odbx2004.msp thru odbx2012.msp and a roamer.msp

I am guessing the 2004 thru 2012 is a year for the update to which version of Manage I have.  Can I select the odbx2012.msp file and use that in the deployment?  what is roamer.msp for?

Am I wasting my time here?  Is this just not possible to include in the deployment?  That would seem rather silly when there is a setting to select a file for use in the deployment. 

[lee.mullin · Accepted solution]

This isn't a smooth process, where possible we recommend you install silently or individually on each machine.

If your company reads and converts DWG's then we do not recommend this workflow.

If you still want to go ahead with this then: -

1. Create your deployment
2. Unpack the service pack using /a
3. Modify your created deployment, to freedom add the MSP in the 9.1\x86 (or x64)\NAVFREE\freedom.msp folder and then add 9.3\x86 (or x64)\NAVFREE\freedom.msp
4. Modify your created deployment, to manage add the MSP in the 9.1\x86 (or x64)\NAVMAN\roamer.msp folder and then add 9.3\x86 (or x64)\NAVMAN\roamer.msp OR for simulate do the same with 9.1\x86 (or x64)\NAVSIM\roamer.msp and then add 9.3\x86 (or x64)\NAVMAN\roamer.msp
5. Choose to merge the service packs into your deployment as it a) works for me and b) should be quicker to install.

NOTE: If you do read DWG's and you have gone down this route, which is not recommended or supported, you should install the RealDWG file reader (ODBX*.msp) service packs. There is currently no way to add these SPs to the deployment, so you will need to have some way of installing these MSPs after each deployment.

Please let us know if this helps.

[sssteve72]

What do you mean by reads and converts DWG's?

We use Autocad to "work on" DWG files.  You know we draw lines, circles, lots of more complicated stuff etc etc... We use Navisworks to compile our DWG's with other companies DWG's and run clash detection.  Sometimes we use a DWG file extension and sometimes they give us a nwc file.

I am just wanting to include the service packs for navisworks in the navisworks initial install so that I don't have to install the program and then run around to update each workstation with the service pack.  And to include the service pack I was not sure which MSP is the correct one as there are many. 

What problem is there with DWGS?

-------------------------------------------------------------------------------------------------------------------------------------

This isn't a smooth process, where possible we recommend you install silently or individually on each machine.

If your company reads and converts DWG's then we do not recommend this workflow.

If you still want to go ahead with this then: -

1. Create your deployment
2. Unpack the service pack using /a
3. Modify your created deployment, to freedom add the MSP in the 9.1\x86 (or x64)\NAVFREE\freedom.msp folder and then add 9.3\x86 (or x64)\NAVFREE\freedom.msp
4. Modify your created deployment, to manage add the MSP in the 9.1\x86 (or x64)\NAVMAN\roamer.msp folder and then add 9.3\x86 (or x64)\NAVMAN\roamer.msp OR for simulate do the same with 9.1\x86 (or x64)\NAVSIM\roamer.msp and then add 9.3\x86 (or x64)\NAVMAN\roamer.msp
5. Choose to merge the service packs into your deployment as it a) works for me and b) should be quicker to install.

NOTE: If you do read DWG's and you have gone down this route, which is not recommended or supported, you should install the RealDWG file reader (ODBX*.msp) service packs. There is currently no way to add these SPs to the deployment, so you will need to have some way of installing these MSPs after each deployment.

Please let us know if this helps.

[dgorsman]

Actually, that makes sense.  Navisworks uses the ODBX/RealDWG components to read DWG file contents.  If they cannot be installed outside of the SP then it can definitely be an issue.

ssteve72, we distributed the 2011 SP to users by providing a hyperlink in the email, pointing to a series of scripts that would install Simulate/Freedom, install Manage, and install the SP.  I would imagine the same thing could be done via automated script at start-up for unattended installation.

[sssteve72]

It sounds like Autodesk needs to find a way to have the deployment run the EXE service pack once it completes the standard install. 

I only have to do this on about 6 machines here.  But what a pain trying to install service packs if you had say 300 users.  I've used my email to send a link before also but even with just 6 people I run across those who simply never install it.  If service packs cannot be installed completely and usable through the deployment, just as you would had you simply clicked on the EXE file, then why even have the option in the deployment to install service packs?  All that does is leads people to think they have installed it correctly.  Then when they have problems (and they will) they will be wasting more time.  Somehwere I read they literally couldnt install through the deployment back in a 2010 thread I think it was.  I figured they finally updated their software since the option to include service packs is in the deployment setup.

[lee.mullin]

---

sssteve72 wrote:

We use Autocad to "work on" DWG files.  You know we draw lines, circles, lots of more complicated stuff etc etc... We use Navisworks to compile our DWG's with other companies DWG's and run clash detection.  Sometimes we use a DWG file extension and sometimes they give us a nwc file.

 

What problem is there with DWGS?

-------------------------------------------------------------------------------------------------------------------------------------

It sounds like Autodesk needs to find a way to have the deployment run the EXE service pack once it completes the standard install.

-------------------------------------------------------------------------------------------------------------------------------------

This would mean you would need to use dgorsman's suggestion or run the service pack in full on each machine. The RealDWG file readers are what is used to read a DWG into Navisworks, without this you are running a mix of 2012 release build and service pack build that is not supported and may cause instability.

Regarding a single deployment installer, this isn't currently possible due to the requirement for Navisworks to have multiple DWG reader loader years but this is an enhancement request for a future release as we understand the frustration with this.

[sssteve72]

Lee you said "If your company reads and converts DWG's then we do not recommend this workflow." in your first post.

I didn't understand your point so I said "What do you mean by reads and converts DWG's?  We use Autocad to "work on" DWG files.  You know we draw lines, circles, lots of more complicated stuff etc etc..."

Now you are asking "What problem is there with DWGS?"

I never said there was a problem working with drawings as I was trying to figure out what you meant by reads and converts DWGS.  So your current question of "What problem is there with DWGS" is confusing to me.  We do sometimes use DWG in navisworks and I assume that is what you meant.

I'll just accept that Navisworks is not like AutoCad in that you cannot download and nclude service packs in the deployment install of the program. 

[lee.mullin]

Apologies for the confusion, yes I simply meant if you work with DWG's in Navisworks either by opening them directly in Navisworks or you export to NWC format from AutoCAD then this workflow isn't for you.

I hope this helps.