This document describes the various methods a system administrator can use to install (deploy) Trimble Business Center on multiple computers on their Windows-based network (enterprise) more quickly and efficiently than copying the Installation download to each computer and performing the installation manually.
Eliot, I am so glad to found the culprit and now success. I let our Network Installation Engineer know...maybe he can prevent that in future enterprise deployments. Thanks for keeping me updated.
David
I've finally found the culprit. We have a custom report that was built by Trimble and gets deployed along with the installation, I didn't realise that it was also copying a .dll and a exe.config file to enable the report. These were causing TBC to go splat.
What a shemozzle that was. Thanks for your help David
Most of our installation testing on workstations on the network are run using a domain user account that is part of the local Admin group, so that should be working. Our execution level requirement in the install has not changed for quite some time. Are you able to install with the same user account in previous TBC releases?
If you want to share your install log, we may be able to see if there are errors related to the specific user account. The log is saved under C:\Users\<USERNAME>\AppData\Local\Temp\TBCInstall.log. Thanks.
Thanks David. A little bit of progress, I've discovered that a local admin account on a workstation can run the deployment and the installation works as expected. However, a domain user account that is part of the local Administrators group results is a broken installation.
Is this expected behavior or potentially a bug? I've always used the later as using local creds is problematic with our deployment system.
Hi Eliot,
I'm sorry for the delayed response.
This command line will install the minimum packages you specified:
setup.exe /silent /ISFeatureInstall:TBC,CSM,FDM,OS
TBC FDM and SYNC
Should all be pretty easy stuff I would have thought. I manage hundreds of packages, hopefully I'm just making a mistake and you're about to solve my issues. Appreciate the help.
I am sorry to hear that your struggles continue, Eliot. If you want to list the workflows/features that you need (or do not require), then I can send a working command line example for you to use.
A bit longer than 24 hours and a bunch of testing and I can't get 5.9 to work. The deployment gives valid success code but application either doesn't run at all or gives an error on start. I use PDQ Deploy, which works perfectly with 5.7, 5.8 and 5.81 in both push (copy to and run) and pull (run and let the process move the data). The only difference in deployment is those MSI options. Are you able to point me to the next support avenue? From previous experience, my local provider won't know what to do with this.
Eliot, I agree and will be updating the guide accordingly. Thanks.
Great thanks David.
If I can give a suggestion, it would be great if the deployment guide was dated inside the actual document, rather than the file name. Even better, what versions the document relates to. It appears I was working from a poorly named PDF.
I'll be testing the new deployment over the next 24 hours. Will report back.
The link does have the latest version that was published in May.
Our build engineer sees an issue with the command line you are using:Setup.exe /silent /ISFeatureInstall:TBC,TBC_MSI,FDM,FDM_MSI,SYNC,SYNC_MSI
The "*_MSI" features are no longer used and not referenced in the guide. Refer to page 8 "Program Features" for the list of available feature options.
Thanks, I have been following the latest documentation and I don't see any changes to the deployment. The command I've provided looks valid to me, it's pretty simple. Can you see any issue with it?
I've tested on a bunch of machines with the same result.
This is a pretty vanilla environment; Domain deployment in push or pull method using local workstation admin or domain user with local admin rights ends with the same result. Directly logged in and running the provided command with appropriate account also results in the same issue. Manual GUI install works fine.
**edit: Running "setup.exe /silent /repair" straight after deployment appears to be a work around**
A new enterprise deployment guide usually comes with each major release of TBC, so you should use the latest document for 5.9x. It appears that you are using an old set of command-line options from an earlier release.
I will make sure that the Enterprise Deployment Guide posted here is appropriate for 5.90.
I have an issue where TBC 5.9 appears to be missing out a bunch of files when installing via the setup.exe method. I'm using the same deployment method that has worked since early 5.x, reviewing the doc my install command looks fine:Setup.exe /silent /ISFeatureInstall:TBC,TBC_MSI,FDM,FDM_MSI,SYNC,SYNC_MSI
ProcMon showing "path not found" on the likes of:C:\windows\assembly\GAC_MSIL\Trimble.Sdk.DiskIO\1.0.0.0__551d74244f0db52e\Trimble.Sdk.DiskIO.dll
C:\windows\Microsoft.Net\assembly\GAC_MSIL\Trimble.Sdk.DiskIO\v4.0_1.0.0.0__551d74244f0db52e\Trimble.Sdk.DiskIO.dll
C:\windows\Microsoft.Net\assembly\GAC_64\Trimble.Sdk.DiskIO\v4.0_1.0.0.0__551d74244f0db52e\Trimble.Sdk.DiskIO.dll
A manual install works fine, any advice on what might be happening here?