Author: Eric Vasbinder
ERPs Applicable:
Vista
Spectrum
ProContractor
From time to time, customers will request for various reasons that their ERP environment ecosystem servers be renamed with a custom name. For example, CUSTOMERNAME-TEST1 or DEVSERVER3. While these names may be more convenience for the customer's internal IT staff, the unfortunate reality is that these names due to their deviation from our automatically assigned server names, will cause significant issues with various critical functions within our ERP clouds. These items include but are not limited to:
Process Stability Concerns
Downgrading internal processes from automated, fully QA tested processes to bespoke, manually driven processes increases potential issues and process hand off failures.
Potential Compliance Concerns
Potential conflicts between compliance requirements that are documented in our SOC 2, type 2 processes and these new, fully customized server names
Potential Security Concerns
Due to the breaking of automated, tested processes for assigning server names, various digital certificate identities may no longer be correct, resulting in potential severing of trust relationships and increased security risk.
This is especially pronounced with a Enterprise Architecture (EA) Vista ERP environment where multiple components, such as the split app and database server, crystal reporting nodes, and (if installed) Vista Enterprise Database (VED) replicating SQL servers all depend upon carefully assigned server primary names.
Given the significant downsides to customize virtual machine server names listed above, Trimble does not support these within our ERP cloud environments.
In order to address the needs of our customers, while at the same time being cognizant of the restrictions on server naming conventions in our ERP clouds, Trimble has a number of possible alternative ways that can help meet the majority of customer needs in regard to server naming.
Customers may utilize a DNS CNAME record in their own internal DNS system, that will automatically translate the preferred name that the customer has for the virtual machine server, to the name that Trimble has assigned to that device. Please note that this will require some minor editing of your (the customer) DNS system to add the additional CNAME record.
If the customer so chooses, they may also create a new host record ("A" record) in their own DNS to allow for direct resolution to the static IP address assigned by Trimble to the virtual machine in question
Our Vista Web / HFF server does support the assignments of a slightly customized name for the web portal URL itself. This does not apply to the virtual machine that serves as the Web server. However, upon request, Trimble can change the URL of the Vista Web/HFF Portal so that the characters in front of the dash ("–") reflects the customer's preferred URL. Please note that any URL chosen must be unique and not conflict with any other customer's chosen URL. In addition, the URL chosen must have a minimal amount of customer-specific identification within it. Please see the following cloud FAQ article for more details: HFF Custom HTTPS (TLS/SSL) Certificates and Domains Not Supported
changelog
Tuesday, 24 February 2026 at 05:12PM:
Added article to clarify policy.