Pages

Ads 468x60px

Featured 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.

Friday, May 17, 2013

C3D 2014 Installation fails

Problem:
You deploy/install Civil 3D 2014 and it does not install. (Chances are good the Microsoft Visual C++ 2008 & 2010 x86/x64 Redistributable packages are already installed on the client machine) The 2014 product dependancies require both 2008 & 2010 Microsoft Visual C++ redistributable packages.

Soution:
Uninstall the 2008 & 2010 redistributable packages, then reinstall Civil 3D and it will install successfully.

Below is a list of the 2008/2010 GUID's for each. This will save others time pulling GUID's and speed up your script building.

Microsoft Visual C++ Compilers 2008 Standard Edition - enu - x86
GUID {44D9A2CB-0692-3180-B5E2-26F4E807D067}

Microsoft Visual C++ Compilers 2008 Standard Edition - enu - x64
GUID {965DF723-5688-359E-84D2-417CAFE644B5}

Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161
GUID {9BE518E6-ECC6-35A9-88E4-87755C07200F}

Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161
GUID {5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4}

Microsoft Visual C++ 2008 Redistributable - KB2467174 - x86 9.0.30729.5570
GUID {86CE85E6-DBAC-3FFD-B977-E4B79F83C909}

Microsoft Visual C++ 2008 ATL Update kb973924 - x86 9.0.30729.4148
GUID {002D9D5E-29BA-3E6D-9BC4-3D7D6DBC735C}

Microsoft Visual C++ 2008 ATL Update kb973924 - x64 9.0.30729.4148
GUID {EE936C7A-EA40-31D5-9B65-8E3E089C3828}

Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
GUID {4B6C7001-C7D6-3710-913E-5BC23FCE91E6}

Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148
GUID {1F1C2DFC-2D24-3E06-BCB8-725134ADF989}

Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17
GUID {9A25302D-30C0-39D9-BD6F-21E6EC160475}

Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17
GUID {8220EEFE-38CD-377E-8595-13398D740ACE}

Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729
GUID {3C3D696B-0DB7-3C6D-A356-3DB8CE541918}

Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729
GUID {4FFA2088-8317-3B14-93CD-4C699DB37843}

Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022
GUID {FF66E9F6-83E7-3A3E-AF14-8DE9A809A6A4}

Microsoft Visual C++ 2008 Redistributable - KB2467174 - x64 9.0.30729.5570
GUID {8338783A-0968-3B85-AFC7-BAAE0A63DC50}

Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219
GUID {F0C3E5D1-1ADE-321E-8167-68EF0DE699A5}

Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219
GUID {1D8E6291-B0D5-35EC-8441-6616F567A0F7}

Microsoft Visual C++ 2010  x86 Runtime - 10.0.30319
GUID {6A86554B-8928-30E4-A53C-D7337689134D}

Microsoft Visual C++ 2010  x64 Runtime - 10.0.30319
GUID {94D70749-4281-39AC-AD90-B56A0E0A402E}

Microsoft Visual C++ 2010  x64 Designtime - 10.0.30319
GUID {F5079164-1DB9-3BDA-853B-F78AF67CE071}

Microsoft Visual C++  Compilers 2010 Standard - enu - x64
GUID {88387B3B-B110-392F-B919-1A15B48F21D4}

Microsoft Visual C++  Compilers 2010 Standard - enu - x86
GUID {370187B9-6964-38D0-851F-6C4898B0C2B1}

Friday, May 3, 2013

Uninstalling Autodesk products

There are many ways to remove software, but I personally prefer to extract each products GUID from the registry. After I have dumped all product GUID’s, I prepare a removal script.

You can navigate manually into your client registry to extract the product GUID’s or you can be creative and prepare a script that will export these locations to text file for you.

x86 location:
HKEY_LOCAL_MACHINE\SOFTWARE\microsoft\windows\currentversion\uninstall

x64 location:
HKEY_LOCAL_MACHINE\SOFTWARE\wow6432node\microsoft\windows\currentversion\uninstall

I prefer to remove the product silently without any UI. After the product is removed, I remove registry entries and local folders & files.

ie.
rem Uninstall product by guid
start /wait msiexec /x <GUID> /q

rem Remove registry key
reg delete "hkcu\software\autodesk\AutoCAD\R19.1" /f
reg delete "hklm\software\autodesk\AutoCAD\R19.1" /f
reg delete "hklm\software\wow6432node\autodesk\autocad\R19.1" /f

rem Delete folders & files
rd /s/q “C:\Program Files\Autodesk\Autodesk AutoCAD Civil 3D 2014"

After the removal script completes, I like to run the Microsoft Win Cleanup Utility (msicu2.exe). Then highlighting all products I removed via script, and removing any leftover instances of them via cleanup utility.

Rebooting the client after completing the removal. Using a script to remove the products using their GUID, is much faster than using programs & features. When you are handling a large number of client machines, you will want to save as much time as possible.

The 2014 product does include an uninstall tool, as well as uninstall text files under the deployment image folder "SMS_SCCM scripts". These files will include the majority of the product GUID needed to uninstall, but some products GUID won't be listed, which you would need to extract yourself.

ie.

::::== Microsoft Visual C++ 2008 x64 CRT Runtime 9.0.30729
::::Manual uninstallation only

::::== Autodesk AutoCAD Civil 3D 2014
::call :funcUninstall {5783F2D7-D000-0409-0102-0060B0CE6BBA}, "Autodesk AutoCAD Civil 3D 2014"

Something to note, Microsoft has replaced the msicu2 with Microsoft Fix it. msicu2 still works fine with Windows 7 32/64bit clients, but if you are interested in the new Fix it. You can read more about it over at Microsoft’s website. http://support.microsoft.com/mats/Program_Install_and_Uninstall

image

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.



Autodesk License file parser

When working with network license files, provided by Autodesk, we must trust the license file is accurate. No more will we have to leave this up to chance, as Autodesk offers a license file parser.

Using the license parser link: http://www.licenseparser.com/

We can now see exactly what products and versions our license file(s) include. This is a nice way to see what our license files have, as well as seeing what older license files have. Very helpful!

Friday, April 26, 2013

2014 Products are here!

With the recent release of the Autodesk 2014 product line. Many people will begin testing and standardizing this release into their current workflow, for a potential upgrade. I will be exploring the deployment and technical side of this release as I move forward.

I currently support an engineering firm with approx. 400 staff. I hope to help others in their deployment, as I prepare my firm.

Here is Autodesk's official link covering Civil 3D 2014. Full of useful information.
http://docs.autodesk.com/CIV3D/2014/ENU/index.html