AnsweredAssumed Answered

Update Administrative Image

Question asked by Neil Jordan on Feb 21, 2008
Latest reply on Jun 25, 2008 by 1-5J6-999

Like • Show 0 Likes0
Comment • 21

Ok, I know it has been covered and there are guides here, but I need to get it straight in my mind.

I have an administrative image installed on my server at i:\solidworks 2008\solidworks 2008 SP2 Admin Image

This I had to roll out via a batch file version of the .hta file (as it always errored out even with the right security settings - but kind of expected it the error trapping on it is "if you have an error, display the same message, even if it is nothing to do with it!")

This has worked ok on my 3 machines.

Now there is the new Service Pack.

With this installation method, I am guessing that I need to install to a new directory, then roll out with a batch file again?

Note that I didn't install via a share name, as this wasn't ever mentioned until it was too late.

Thanks

Neil

No one else has this question

Outcomes

21 Replies

Kevin Silbert Feb 21, 2008 10:00 AM
Mark Correct
Correct Answer
I think you're hosed. I'm pretty sure the share directory is of key importance, as is the fact that it's a root share. And the fact that it's not a UNC path, but the I:\ drive may also be bad, since shares use the \\server\sharename format so switching the share out for a new directory would be difficult.

But, having written that, maybe it's worth a try to rename "solidworks 2008 SP2 Admin Image" to "solidworks 2008 SP2 Admin Image-Old", then make an SP3 image in a folder called "solidworks 2008 SP2 Admin Image" (very confusing!), be sure to tell it to update any current installations, pick the "solidworks 2008 SP2 Admin Image-Old" directory when it asks for a new or existing image directory so it doesn't have to download all the files again (it will then ask you for a path to the new image directory- you'd type "solidworks 2008 SP2 Admin Image" for that) and do it's thing.

It *might* work. To be sure, have a user use start SW (not from QuickLaunch) and see if it updates after that. If it doesn't, you can delete "solidworks 2008 SP2 Admin Image" and rename -OLD back to the original state, then make "normal" SP3 images and tell people to click on the .HTA file to update manually...

Good luck! I'm curious if this works- please post back...
Like • Show 0 Likes0
Actions
- Kevin Silbert @ Kevin Silbert on Feb 21, 2008 1:54 PM
  Mark Correct
  Correct Answer
  OOPS- sorry I missed the point where you used Batch files... I Hope this didn't mess you up!
  
  You are correct- no need for a share name. Install to a new directory and send everyone a new batch file that includes updating commands.
  Like • Show 0 Likes0
  Actions
  - Neil Jordan @ Kevin Silbert on Feb 21, 2008 3:03 PM
    Mark Correct
    Correct Answer
    No, I haven't got THAT far yet!
    
    I used this to install:
    "I:\SolidWorks 2008\SolidWorks 2008 SP2 Admin Image\sldim\sldIM.exe" /adminclient /new /source "I:\SolidWorks 2008\SolidWorks 2008 SP2 Admin Image\AdminDirector.xml"
    
    Can you tell me how it needs to be for an update install?
    
    TIA
    Like • Show 0 Likes0
    Actions
    - Kevin Silbert @ Neil Jordan on Feb 21, 2008 4:01 PM
      Mark Correct
      Correct Answer
      I chose to use the Installation Manager this year, so all I have are the files I used in 2007. Here is the one that upgraded everyone from 1.0 to SP2.0. The place to see what the exact parameters are for 2008 is in http://files.solidworks.com/Su...bHelp/Installation.htm under Multiple Installations/Installation/Deploying.../Command Line Deployment
      
      OLD 2007 upgrade file:
      -----------------------------------------------------------------------
      echo off
      REM MAPCPatch20.bat by Kevin Silbert 11/2006
      
      Echo DO NOT CLOSE THIS WINDOW- It will close itself when done
      Echo Estimated time: 15 min
      
      Echo Patching SolidWorks 2007 SP2
      msiexec /i "\\ajax\share-1\MAPC-General Stuff\Software\SolidWorks\Administration\Images\SW\english_i386_solidworks.msi" ENABLEPERFORMANCE=0 INSTALLWDS=0 SERVERLIST="25734@general" SOLIDWORKSSERIALNUMBER="(insert yours here)" SWMIGRATE="SolidWorks 2007 SP1.0" UPGRADESWINSTALL=1 TOOLBOXFOLDER="\\ajax\share-1\MAPC-General Stuff\Software\SolidWorks\Common Data" /qb /Lme c:\SWUPG2.txt
      
      Echo Updating CosmosWorks to SP2.0
      msiexec /p "\\ajax\share-1\MAPC-General Stuff\Software\SolidWorks\Administration\Patches\2007_SP2.0\cw2007_sp10220_i_Eng\cw2007_sp10220_i_Eng.msp" /qb /Lim c:\cwUpgradelog.txt
      
      Echo Updating Cosmos Motion to SP2.0
      msiexec /p "\\ajax\share-1\MAPC-General Stuff\Software\SolidWorks\Administration\Patches\2007_SP2.0\cm2007_sp10220_i_Eng\cm2007_sp10220_i_Eng.msp" /qb /Lim c:\cmUpgradelog.txt
      
      Echo Installing DWGEditor 2.0
      msiexec /i "\\ajax\share-1\MAPC-General Stuff\Software\SolidWorks\Administration\Images\DWGeditor\DWGeditor.msi" LICENSETYPE=2 SERVERLIST="25734@general" /qb /Lim c:\dwgedUPDlog.txt
      
      Echo Verifying Toolbox Parameters
      REGEDIT /s /i "\\ajax\share-1\MAPC-General Stuff\Software\SolidWorks\Administration\Images\SW\ToolboxShareSettings.reg"
      
      Echo Installing SW Explorer, PDMWorks, and eDrawings SP2.0
      msiexec /i "\\ajax\share-1\MAPC-General Stuff\Software\SolidWorks\Administration\Images\SWExplorer\SolidWorks Explorer.msi" ADDLOCAL=ALL INSTALLWDS=1 INSTALLDIR="C:\Program Files\SolidWorks\SolidWorks Explorer" /qb /Lim c:\SWExplInstlog.txt
      
      Echo Consolidating Start Menu tree shortcuts
      copy "C:\Documents and Settings\All Users\Start Menu\Programs\SolidWorks\DWGeditor.lnk" "C:\Documents and Settings\All Users\Start Menu\Programs\SolidWorks 2007 SP2.0\DWGeditor.lnk"
      copy "C:\Documents and Settings\All Users\Start Menu\Programs\SolidWorks 2007\PDMWorks Workgroup VaultAdmin.lnk" "C:\Documents and Settings\All Users\Start Menu\Programs\SolidWorks 2007 SP2.0\PDMWorks Workgroup VaultAdmin.lnk"
      copy "C:\Documents and Settings\All Users\Start Menu\Programs\eDrawings 2007.lnk" "C:\Documents and Settings\All Users\Start Menu\Programs\SolidWorks 2007 SP2.0\eDrawings 2007.lnk"
      copy "C:\Documents and Settings\All Users\Start Menu\Programs\SolidWorks 2007\SolidWorks Explorer.lnk" "C:\Documents and Settings\All Users\Start Menu\Programs\SolidWorks 2007 SP2.0\SolidWorks Explorer.lnk"
      rmdir /s /q "C:\Documents and Settings\All Users\Start Menu\Programs\SolidWorks"
      rmdir /s /q "C:\Documents and Settings\All Users\Start Menu\Programs\SolidWorks 2007"
      del "C:\Documents and Settings\All Users\Start Menu\Programs\eDrawings 2007.lnk"
      
      Echo DONE!
      exit
      Like • Show 0 Likes0
      Actions
    - Jason Capriotti @ Neil Jordan on Feb 21, 2008 8:33 PM
      Mark Correct
      Correct Answer
      I think the update is the same command line if the path to the image is the same. It will update if the image has changed.
      
      I still have to call for the batch files separately though as its different for an upgrade versus a fresh install. The users would be might pissed if I reset there interface cusomtization with every service pack update.
      
      So I have a batch file that lets the user chose "New install" or "Update". "New install" applies our default settings while "Update" does not.
      Like • Show 0 Likes0
      Actions
      - Neil Jordan @ Jason Capriotti on Feb 26, 2008 12:17 PM
        Mark Correct
        Correct Answer
        Hi Jason
        
        Any chance I could see your batch file please?
        Like • Show 0 Likes0
        Actions
        Jason Capriotti @ Neil Jordan on Feb 26, 2008 1:37 PM
        Mark Correct
        Correct Answer
        I've attached a zip containing 3 batch files. The first is the menu that lets the user select some options.....depending on what they select, it kicks off the "Update" or "Install" batch files.
        
        Let me know if you have questions as they are quite involved.
        Attachments
        SolidWorks2008batch.zip4.1 KB
        Like • Show 0 Likes0
        Actions
        Neil Jordan @ Jason Capriotti on Feb 26, 2008 2:13 PM
        Mark Correct
        Correct Answer
        Blimey, someone who still can use batch files in the industry - I thought we had all died out!
        
        I think I have got the relevent information from your work - I don't think I need to go to your lengths at present though.
        
        Thanks
        Like • Show 0 Likes0
        Actions
        Jason Capriotti @ Neil Jordan on Feb 26, 2008 2:40 PM
        Mark Correct
        Correct Answer
        Not much you can't do with them and I'm still learning as I go. Not to mention its free and works on every PC.
        Like • Show 0 Likes0
        Actions
        Neil Jordan @ Jason Capriotti on Feb 26, 2008 3:01 PM
        Mark Correct
        Correct Answer
        I totally agree, and especially useful for scheduled tasks on the servers etc. Pity how people seem not to be taught it nowadays - I sound like an old man!
        Like • Show 0 Likes0
        Actions
        Neil Jordan @ Neil Jordan on Mar 7, 2008 10:38 AM
        Mark Correct
        Correct Answer
        I have managed to sucessfully update a client PC (failed on mine) to SP3 with the command line:
        
        msiexec /i "SolidWorks\English_i386_SolidWorks.Msi" INSTALLDIR="C:\Program Files\Solidworks 2008" UPGRADESWINSTALL=1 SWMIGRATE="SolidWorks 2008 SP02" /qb
        
        However, when I look at Add/Remove Programs, it lists both the install for SP2 and SP3 there.
        
        Is this simply a case that I can use Windows Installer Cleanup to remove the SP2 entry? Is it possible to correct this problem from occurring in the command line?
        Like • Show 0 Likes0
        Actions
        Jason Capriotti @ Neil Jordan on Mar 7, 2008 2:49 PM
        Mark Correct
        Correct Answer
        I had this same problem in 2007 using the command line to upgrade a service pack. Never figured out what was causing it.
        
        Funny thing is, if you uninstall the later SP, it goes really quick, I dont' think it actually removed it. The first one is the actually install. Strange but I think something is labeled wrong or something somewhere.
        Like • Show 0 Likes0
        Actions
    - Daniel Hogsett @ Neil Jordan on Mar 11, 2008 1:34 AM
      Mark Correct
      Correct Answer
      Where are you getting "I:\SolidWorks 2008\SolidWorks 2008 SP2 Admin Image\sldim\sldIM.exe" /adminclient /new /source "I:\SolidWorks 2008\SolidWorks 2008 SP2 Admin Image\AdminDirector.xml" information from? I can't find these swithes in the administration guide. The only thing I see in the admin guides is msiexec /i....... to install.
      
      Thanks,
      Dan
      Like • Show 0 Likes0
      Actions
      - Jason Capriotti @ Daniel Hogsett on Mar 11, 2008 3:44 PM
        Mark Correct
        Correct Answer
        This is in the "hta" file that the IM creates when creating an admin image. Edit it with notepad.
        
        Its undocumented but you can use the same line in a batch file.
        Like • Show 0 Likes0
        Actions
        Daniel Hogsett @ Jason Capriotti on Mar 11, 2008 10:51 PM
        Mark Correct
        Correct Answer
        I took a look at your batch files. After the initial install, do your clients auto-update when you create a patched image or do you send out a notification to users? I like the idea of checking the users.xml file to see if a user is permitted to install SW, it gives you control of who does and doesnt get SW. One final question. Even though you are using batch files to install, could a user navigate to the image directory and click on the SWInstall.hta file and install to get past your users.xml check?
        
        Thanks,
        Dan
        Like • Show 0 Likes0
        Actions
        Jason Capriotti @ Daniel Hogsett on Mar 12, 2008 5:14 PM
        Mark Correct
        Correct Answer
        I elected to not auto-update the clients for various reasons. The batch file has a "Service Pack" variable and I update it when a new SP is ready to go here. Then I send out an email with instructions to run the batch file.
        
        Techanially a user could navigate to the image and install but I have taken some measures to reduce the chances of that happens. First, the share is set to be hidden so you can't browse to the server and find the image shares. Second, I don't send the actual batch file out, I send a compiled VB program that simply kicks off the batch files. So they can't edit the batch and see where its pointing. I would do the whole thing in VB but my VB skillz are very limited.
        
        Now if someone really wanted it, they could go on someone's computer who has SolidWorks and check the registry to find the image path but I don't think most here would know how to do that.
        Like • Show 0 Likes0
        Actions
        Daniel Hogsett @ Jason Capriotti on Mar 13, 2008 2:10 AM
        Mark Correct
        Correct Answer
        In order to keep clients from auto-upgrading, do you build the image then share the directory as a different name than you entered in the IM?
        Like • Show 0 Likes0
        Actions
        Jason Capriotti @ Daniel Hogsett on Mar 13, 2008 4:00 PM
        Mark Correct
        Correct Answer
        Yes, I create a new image with a folder name that contains the sp number:
        
        sw2008x32sp2.0
        sw2008x32sp3.0
        
        Then I have a variable in our batch file for the current "service pack" so when I'm ready to roll it out, I change the variable. The users still have to run the installer but its the same installer....the batch variable tells it which folder to install from.
        
        I like the idea of it auto updating but the update takes too long and there is no option to not update which we need for engineers in the field or on slow connections. Or for those times where you're in a meeting and need pull up SolidWorks quick to show something.....waiting for it to auto-update is a party crasher in that case.
        Like • Show 0 Likes0
        Actions
        Daniel Hogsett @ Jason Capriotti on Mar 16, 2008 2:50 AM
        Mark Correct
        Correct Answer
        I noticed in your batch files, on a new install, you have the option to install eDrawings and DWGeditor separate, not SWExplorer. Is there any particular reason you install those separately? Why not install SWExplorer separately?
        
        Thanks,
        Dan
        Like • Show 0 Likes0
        Actions
        1-5J6-999 @ Jason Capriotti on May 1, 2008 2:08 PM
        Mark Correct
        Correct Answer
        Hi Jason,
        
        I'm going through the same stuff right now. Just had a few quesitons:
        
        1. What is the advantage of going with the SWIM installation as opposed to a command line install using the 'msiexe /i' if you have auto updating turned off?
        
        2. Any idea why with the admin image you now have to manually (or via batch file) install the .NET and C++ runtime files? I had to make a batch file that detected the processor and OS type in order to install the proper runtime files. I was just curious why you don't have to worry about those with individual installs but with admin image installs you do.
        
        3. Have you ever tried using the "install under different user name" option in the SWIM install? I'm curious how that works out. I'd love to not have to involve IS at all and just use my user priveleges (admin). But I've had problems with that in prior releases where I tried doing a client install for someone that hadn't been given admin rights. The install went fine but when they logged in under their own user name with restricted rights, Solidworks would not run.
        
        4. When using the (example) line "I:\SolidWorks 2008\SolidWorks 2008 SP2 Admin Image\sldim\sldIM.exe" /adminclient /new /source "I:\SolidWorks 2008\SolidWorks 2008 SP2 Admin Image\AdminDirector.xml" does this still run a 'silent' install like the Adminstrative Director used to? I don't wan't users to require any interaction with the installation.
        
        Thanks. It's tough to get this stuff staight, the documentation for this is horrible and the VARs seem clueless. Not very happy with 2008 right now... Miss the old AD already.
        
        Jeff Sauck
        Solidworks 2007 SP5.0
        User since '98
        Intellistation Z Pro 3Gb
        Quadro FX 3400
        WinXP 32
        Like • Show 0 Likes0
        Actions
- 1-5J6-999 @ Kevin Silbert on Jun 25, 2008 2:54 PM
  Mark Correct
  Correct Answer
  Just tried renaming the new image folder to the existing image folder and voila, it works! I renamed the existing image folder which was 4 levels from the root -\\server\Design\Solidworks\Installation\sw2008_SP3.1 TO \\server\Design\Solidworks\Installation\sw2008_SP3.1_OLD.
  
  Then I renamed the new SP4.0 image (\\server\Design\Solidworks\Installation\sw2008_SP4.0) back to the existing server name (\\server\Design\Solidworks\Installation\sw2008_SP3.1), thereby tricking SW clients into looking at the new image. The autoupdate worked on all computers that used the .hta file for the installation.
  
  Next time around I'll use different names so as not to confuse service packs, but this seems to be a valid workaround if (like me) you don't have access to the root share.
  Like • Show 0 Likes0
  Actions

Update Administrative Image

Outcomes

Attachments

Related Content

Recommended Content