Contacts
Get in touch
Close

Contacts

Romania, Cluj-Napoca – 400157
Str. Ploiești Nr. 9

Romania, Vama – 447350
Str. Fermei Nr. 14

+40 774 463 429

info@inteliscience.net

NX Administrator Training

NX Administrator Training

NX Admin Training: Customer Defaults, Templates, Licensing and Deployment

NX admin training is a hands-on Siemens NX course for the people who set up and run NX in a company. It covers customer defaults at site, group and user level, templates and start parts, roles, environment variables, licensing, installation and deployment, the settings for Teamcenter Integration for NX, and troubleshooting. inteliScience runs this NX administrator course remote live or on-site, in small groups, on a test installation of your own NX environment if you like.

Course at a glance

Options
Basic 3 days, advanced 5 days
Format
Remote live or on-site
Group
Small groups
Level
NX users and IT staff
Exercise setup
Your test environment or ours
Language
English or German

inteliScience is a Siemens NX, NXOpen and Teamcenter specialist with NX engineers in Cluj-Napoca, Romania. The courses are given by NX engineers from our team who work in NX projects themselves.

This course is part of our Siemens NX training. It follows the path of a real NX setup: where NX reads its settings, how a company standard reaches every workstation, and how to find the cause when one seat behaves differently from the others. If you would rather hand the work over than learn it, our NX administration services take care of it as a service. For a first look at the most important settings, read our guide to NX customer defaults.

Who the NX admin training is for

A good fit

  • CAD administrators who take over an existing NX installation
  • Experienced NX users who become the NX key user or admin for their site
  • IT staff who install and deploy NX and need to understand the CAD side
  • Teams preparing a new NX standard with templates, roles and customer defaults
  • Companies that run NX with Teamcenter and want the integration settings under control

Better served elsewhere

What participants can do after the course

  • Read the NX environment: know which settings come from environment variables, the ugii_env.dat file, customization directories and customer defaults.
  • Manage customer defaults: set and lock values at site, group and user level, and trace which level a value comes from.
  • Provide templates and roles: add company templates to the File New dialog and publish site roles for your user groups.
  • Understand licensing: know how NX finds its license and solve the usual license errors at start-up.
  • Deploy NX in a repeatable way: install NX unattended on many workstations and test a new release before users get it.
  • Troubleshoot: use the NX syslog and a short checklist to find out why one seat behaves differently.
  • Automate routine tasks (advanced): record NX journals, adapt them and start them from a button.

Modules and agenda

The basic training covers modules 1 to 5. The advanced training is the basic training plus two days, structured a little differently: it goes deeper in modules 1 to 5 and adds Teamcenter integration, a shared environment and automation in modules 6 to 8.

Module 1 · basic and advanced

NX environment and customization directories

  1. Installation layout: UGII_BASE_DIR and the ugii and nxbin folders
  2. Environment variables in ugii_env.dat, and why it takes precedence over ugii_env_ug.dat
  3. Customization directories in custom_dirs.dat and their startup subfolders
  4. Site, group and user directories: UGII_SITE_DIR, UGII_GROUP_DIR and UGII_USER_DIR
  5. User profile files, and how to reset one user’s settings safely

Result: a documented map of where your NX installation reads its settings.

Module 2 · basic and advanced

Customer defaults

  1. Customer defaults and preferences: company standard versus current part or session
  2. Site, group and user levels, inheritance and locks
  3. The .dpv files behind each level, and where they belong
  4. Finding a default, changing it and checking the effect after a restart
  5. Documenting changes so the next release upgrade is easier

Result: your key defaults set at the right level and locked where your standard requires it.

Module 3 · basic and advanced

Templates, drawing templates, roles and libraries

  1. How PAX files define the tabs and templates of the File New dialog
  2. Template parts with units, layers, attributes and drawing formats
  3. Adding a company template and testing it
  4. Roles: default roles, custom user roles and site roles in a shared directory
  5. Setting the default role for new users
  6. Drawing templates: borders and zones, a title block with part attributes, marked as a template and added to the File New dialog
  7. Libraries: company folders in the Reuse Library and a shared library configuration for every user

Result: company templates, drawing templates, libraries and a site role that every user gets at start-up.

Module 4 · basic and advanced

Licensing, installation and deployment

  1. License server or standalone node-locked license: how NX finds its license
  2. The SPLM_LICENSE_SERVER variable and typical license errors at start-up
  3. Unattended installation for many workstations, with features and license server set on the command line
  4. Functional releases and updates: each functional release in its own folder, so releases can run side by side
  5. Testing customizations in a new release before users get it, for example in a sandbox set up with the Siemens NX Launcher
  6. Advanced: software distribution with a silent installation and an installation log for every workstation
  7. Advanced: startup scripts in the Siemens NX Launcher and separate environments for several NX versions on one workstation

Result: a repeatable installation and update routine for your sites.

Module 5 · basic and advanced

Troubleshooting

  1. The NX syslog: where to find it and what to look for
  2. Slow start-up, missing menus, wrong templates or units: a short checklist
  3. Finding out whether a problem comes from the environment, the defaults, the role or the user profile
  4. Your own environment: reviewing your current defaults, roles and directories together
  5. Advanced: keeping the syslog with UGII_KEEP_SYSTEM_LOG and reading the installation log
  6. Advanced: best practices for a stable environment, with a change log and a test before every release

Result: a troubleshooting checklist for your helpdesk and a short list of open points in your setup.

Module 6 · advanced, optional in basic

Teamcenter Integration for NX settings

  1. NX customer defaults for Teamcenter Integration and the matching Teamcenter preferences
  2. Settings for associated files, assembly loading, check-in and check-out, attribute mapping and JT creation
  3. Templates and PAX files in the Teamcenter database
  4. Which changes take effect at once and which need an NX restart

Result: integration settings that match your Teamcenter configuration, and a list of what to check after each change.

Module 7 · advanced

Shared environment and central administration

  1. NX installed once on a network share, with a local client installation on each workstation
  2. Site and group directories on a server share for customer defaults, roles and templates
  3. What belongs on the network and what stays local: user profile directory and temporary files
  4. Advanced customizing: PAX files, roles and library folders for several departments or sites

Result: a central NX environment that you change in one place and that every workstation follows.

Module 8 · advanced

Automation with journals, NX Open and macros

  1. Recording a journal on the Developer tab and playing it back
  2. Journal languages: Python on all platforms, Visual Basic .NET and C# on Windows
  3. Macros record keyboard and mouse input; journals are the more robust choice across NX releases
  4. From a journal to an NX Open program and a button in a role or menu, for your own customizations

Result: recorded journals for your routine admin tasks and a clear path to NX Open programs.

Licensing comes up in almost every admin course. Our overview of Siemens NX license types explains floating, node-locked and value-based licensing. When a new NX release is due, our NX release upgrade service plans and tests it with your admin.

Where AI helps: an assistant can prepare routine admin requests, such as a defaults change or a ribbon button, for the admin to review. Our article on NX administration AI shows which requests are suitable.

Course format

  • Remote live or on-site. Remote live, with every participant working on their own test workstation while the trainer shares the screen and checks the work, or on-site at your company.
  • In small groups. Small enough that every setup step gets checked.
  • On a test environment. Exercises run on a test installation of your NX environment, or on our training environment, never on your production settings.
  • Your standard. If you already have NX templates, roles and customer defaults, they become the exercise material.
  • Language. English or German.

Two options: basic or advanced NX admin training

  • Basic training, 3 days. Modules 1 to 5: installation and system architecture, licensing and environment variables, customer defaults, roles and central settings, templates, drawing templates and libraries, company standards, updates and basic troubleshooting, each with exercises on a test installation.
  • Advanced training, 5 days. The basic training plus two days, structured a little differently: advanced NX architecture with central administration and a shared environment, advanced customizing with customer defaults, templates, PAX files, roles and libraries, automation with NX journaling, NX Open and macros, deployment with software distribution, startup scripts, version management and updates, Teamcenter integration, and troubleshooting with log files and best practices.

Both options start from what the participants already know. For IT staff without NX experience, the course begins with the NX fundamentals an admin needs: the user interface, parts, assemblies and drawings, units and templates. We agree on the day-by-day agenda with you in a short call before the course.

Prerequisites

  • Working knowledge of NX as a user (parts, assemblies and drawings), or an IT background: then the course starts with the NX fundamentals.
  • Administrator rights on a test workstation or virtual machine with NX installed.
  • Access to an NX license for the test installation.
  • For module 6: a Teamcenter test environment with Teamcenter Integration for NX.
  • Optional: your current customer defaults files, templates and environment file, sent before the course.

How to book the NX admin training

Course package · NX Administrator Training

Course offer after a short call

Basic training in 3 days or advanced training in 5 days, remote live or on-site, in small groups. We choose the option and the modules with you in a short call and then send a course offer.

  • Basic: modules 1 to 5, from installation and licensing to troubleshooting
  • Advanced: modules 1 to 8, with Teamcenter integration, a shared environment and automation
  • Exercises on a test installation of your own NX environment, if you like
  • Exercise files and checklists that stay with your team
  • A short summary after the course, with open points in your NX setup
Request a course offer

What happens after: your admin runs the next change or release test on their own. For a second pair of eyes, our NX administration services can review the setup.

Before the course

A short preparation

So the course time is spent on the setup, not on access problems.

  • A short call to choose the option and the modules
  • A test workstation or virtual machine with NX
  • Your customer defaults, templates and roles, if they exist
  • Remote or on-site access to the test environment

Frequently asked questions about NX admin training

What does a Siemens NX administrator do?
A Siemens NX administrator installs and updates NX, keeps licensing working and maintains the company standard: customer defaults, templates, roles, environment variables and, where Teamcenter is used, the integration settings. The admin is also the first contact when one workstation behaves differently from the others. Our NX admin training covers these tasks in core modules, with Teamcenter Integration for NX as an optional module.
What are customer defaults in Siemens NX?
Customer defaults are the Siemens NX settings that define starting values for sessions and dialogs, for example the unit system or default options in commands. They can be set at site, group and user level; lower levels inherit from higher ones, and a lock at a higher level prevents changes below it. NX stores each level in its own .dpv file, and changes take effect after a restart. Module 2 of our course is about customer defaults, and our NX customer defaults guide gives a first overview.
What is the difference between customer defaults and preferences in Siemens NX?
Customer defaults set the company-wide starting values that Siemens NX reads at start-up, and administrators can lock them. Preferences, changed through the Preferences menu, override those values for the current part or work session without changing the defaults. A designer can deviate for one part while the standard stays in place for everyone else. We practice both in the course, including how to find which level a value comes from.
How does Siemens NX find its license server?
Siemens NX either connects to a license server running the Siemens License Server software or reads a standalone node-locked license file. The SPLM_LICENSE_SERVER environment variable points to the server as port@hostname, or to the license file, and is normally set during installation. Since NX 2212 the default port is 29000. License errors at start-up are one of the troubleshooting cases in our NX administrator course.
How do you deploy Siemens NX to many workstations?
Siemens NX can be installed unattended: the setup program passes the features, the installation folder and the license server to the Windows installer on the command line, so every workstation gets the same installation. Company settings then come from shared site directories for defaults, templates and roles. A new functional release installs to its own folder, so it can be tested before users switch. Module 4 of our course covers unattended installation and a test routine for new releases.
Which Siemens NX settings control the Teamcenter integration?
The Teamcenter integration is controlled by the Teamcenter Integration for NX customer defaults in Siemens NX and by preferences on the Teamcenter side. The NX defaults cover topics such as associated files, assembly loading, check-in and check-out, attribute mapping and JT creation, and some of them only work together with a matching Teamcenter preference. Templates for the File New dialog are imported into the Teamcenter database. This is the optional module 6 of our NX admin training.

Taking over NX administration? Learn it on your own environment.

Tell us how your NX is installed, whether you use Teamcenter, and who will run the admin role. We will propose the modules and send a course offer after a short call.

Request a course offer

NX engineers as trainers · remote live or on-site · in small groups

Cookie settings

Choose which services we may use on this website. Your choice is stored in your browser for 12 months. You can change it at any time via “Cookie settings” at the bottom of every page.

Strictly necessary

Stores your cookie choice. This cookie cannot be switched off.

Always active
Show cookies
NameProviderPurposeStorage period
is_cookie_consentinteliScienceStores your cookie choice and when you made it12 months

Google Analytics 4 measures page views, traffic sources and form use with a pseudonymous ID. Provider: Google Ireland Ltd. Data may also be processed by Google LLC in the USA (EU–US Data Privacy Framework).

Show cookies
NameProviderPurposeStorage period
_gaGoogleDistinguishes visitors with a pseudonymous ID2 years
_ga_<ID>GoogleStores the session state2 years

Google Ads measures which ads lead to enquiries (conversions) and lets us show our ads to previous visitors (remarketing). Provider: Google Ireland Ltd. Data may also be processed by Google LLC in the USA (EU–US Data Privacy Framework).

Show cookies
NameProviderPurposeStorage period
_gcl_au, _gcl_aw, _gcl_gsGoogleLinks ad clicks to enquiries90 days
_gcl_ls (local storage)GoogleLinks ad clicks to enquiries90 days
IDE (doubleclick.net)GoogleRemarketing and ad measurement13 months

Videos: YouTube videos only load when you press play (via youtube-nocookie.com). Only then does Google receive data.