Silent install utility

[SWscience]

Hello all.
Does anyone use SolidWorks 2004 Silent Install Utility Version 1.2.14 ?
Is it at risk ? because solidworks doesn't warranty this utility of any kind at all.
Tell me how is it .. faster ?
Best regard

 

[SBaugh]

I have one customer using it and he fought it tooth and nail to get it running. He got some help from a user here. They wrote some type of Batch file that help them get around some issues. The post should still be here some where. I don't know the subject name for you to use in hte search. But now that it's up and running for them. As far as I know it's workign for them. They have 50 seats of SW there but they only have about 12-15 seats on the silent install.

I don't think it's any faster than just doing an admin image and having everyone load from that. Admin image is probably your best bet at this time. Silent install gives you the ability too to upgrade a users seat of SW without you leaving your seat or them being present. It upgrades it without their knowledge.

Regards,

Scott Baugh, CSWP

http://www.3dvisiontech.com

http://www.scottjbaugh.com

faq731-376

 

[ctopher]

We do not use silent install on any program. It's best to have admin image to install for everyone at same time. Keeps everyone on same page.

 

[PDMAdmin]

We do all original installations of SW manually. However, we also do silent updates in conjunction with a batch file that checks to see if users have the latest service pack. Whenever we update the admin image, we modify the batch file to check for the updated service pack, and users who are behind the times get updated automatically. We have a large user base, so the ability to do silent updates is essential.

We've never used the SolidWorks install utility; we just use the "msiexec" function. SolidWorks has a good resource here:

http://www.solidworks.com/pages/services/subscription/ServicePacks.html?PID=252

(Look under "SolidWorks installation guide.")

 

[J-C]

Can you post the batch scripts that checks for the service pack.

Also, do you run the batch file from the windows startup folder?

Jason Capriotti
ThyssenKrupp Elevator

 

[PDMAdmin]

I can't include the whole batch file because it includes some proprietary info that can't be shared with the public. However, I have included a few snippets here that should give you the right idea. We do not use the "Startup" menu; we run the scripts from the Windows logon directory on the network. This does not mean that the "Startup" menu approach is wrong; it all depends on what's easiest for you to propagate to all the users who need it. Please note that we install from an admin image on the network, and we do service pack updates to the admin image manually.

***************

rem Set SPlevel to whatever service pack is the latest for you
rem Test for update already applied
dir "%ALLUSERSPROFILE%\Start Menu\Programs" | find "SolidWorks" | find "%SPlevel%" && goto NoUpdateNeeded

rem Individual users must have admin access to install service pack updates themselves
rem Test for appropriate group membership before execution
net localgroup administrators | find "%USERNAME%" || goto ErrorNoPerms

rem Specify location of SolidWorks admin image in the variable SWinstImg
msiexec /i %SWinstImg%\english_i386_solidworks.msi INSTALLDIR="%programfiles%\SolidWorks" UPGRADESWINSTALL=1 /qb /L*v "%SystemDrive%\var\sw2004.log"

 

[Bouke]

If you run the above batch-routine, this won't be a silent install will it?? I'm running against the same problem. Having to keep up with sp's on 20 different stations but i would like to have all settings the same for everybody.

Grtz, Bouke

 

[PDMAdmin]

It depends what you mean by "silent install." To me, it's a silent installer because it doesn't require any input from the user, but it still has enough info to do what needs to be done. It also has the added benefit of providing feedback to the user so it doesn't seem like the machine froze up. (The update process can take 10-15 minutes sometimes.)

 

[CorBlimeyLimey]

For what it's worth ... "Silent" in this case would be where the end user would be totally unaware of the install process (no noticeable slow down or notification). What you describe is actually a "Remote" or "Unattended" install.

from (the City of) Barrie, Ontario.

Support bacteria - they're the only culture some people have