Pages

Ads 468x60px

Labels

  • 3RD Party Software (2)
Showing posts with label 3RD Party Software. Show all posts
Showing posts with label 3RD Party Software. Show all posts

Tuesday, May 28, 2013

3rd Party Prep - AutoTURN

AutoTURN standard and Pro 3D, are products used by many for truck turning. We've always just run the .exe from the shared location on the server and removed the product through ARP or PF.

Here is an example to silently remove AT8 STD.
call "C:\Windows\AutoTURN 8.0 Workstation\uninstall.exe" "/U:C:\Windows\AutoTURN 8.0 Workstation\AutoTURN Uninstall.xml" /s

Above we are calling the local client uninstall.exe and telling it to follow the parameters of the uninstall.xml file.

Products pre version 7, you would remove using the GUID. Example to remove AT6 below
msiexec /x{51706CB6-0BB4-484B-86FC-BC3F8C9F5DBB} /quiet

To silently deploy onto clients, you can simply call the silent workstation installer from the shared server location. Example below
call "\\servername\AutoTURN Pro 3D Server\Workstation\SetupWorkstationSilent.exe.lnk"

Above we are calling the installer, which if you notice is actually a link, so you want to make sure you include "lnk" following the .exe.

If you really wanted to you can install by calling the install xml, but I fine calling the link just as easy. Example below

"\\servername\AutoTURN Pro 3D Server\Workstation\SetupWorkstation.exe" /xml "\\servername\AutoTURN Pro 3D Server\Workstation\tsInstall.xml" /type workstation /s

These can easily be added to any current script, tweaked and get you pushing the product out to many clients quickly.

For those using SCCM, you can create a package using the *.msi and include your silent paramenters (msiexec /i"SetupWorkstationSilent.msi" /qn), then make that package available for install through software center, or you make it required and force it to install on your clients. I like giving clients the option, so I make some of my packages available for install, rather require and install them.

Tuesday, April 30, 2013

3rd Party Prep - Bluebeam Revu

Many use third party add-ons like Bluebeam, AutoTURN and others within their CAD production workflow. I will share some helpful insight into these products.

Bluebeam 11 will be releasing update 11.1 this week in support of the 2014 CAD products. Previous versions will not support the 2014 CAD products.

Bluebeam Enterprise deployment link: Bluebeam Enterprise Configuration

When deploying the bluebeam client in a mass setting. You can do so easily by modifying the .msi file with orca (http://support.microsoft.com/kb/255905).

Open the .msi installer with orca, then go to the property table, then edit the following values.

BB_DEFAULTVIEWER 0 - I don't use bluebeam as the default pdf viewer
BB_DESKSHORTCUT 1 - I add a desktop shortcut
BB_PRODUCTKEY xxxxx-xxxxxxx - enter your prod key
BB_SERIALNUMBER xxxxxxx - enter your serial number











Save and close the .msi installer from orca. Now you can easily deploy Bluebeam to clients, via script, group policy, or sccm package.

A great way to keep track of your installed clients, is by using Bluebeam's reg look up page. http://www.bluebeam.com/us/support/reglookup.asp
Just plug in your license info and it will return detailed info on the number of licenses installed.