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
- Designers new to NX: NX CAD training
- Users moving to a new NX release: NX update training
- Teamcenter data model and server: Teamcenter administration and BMIDE training
- Automation with programs: NXOpen training
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.
NX environment and customization directories
- Installation layout: UGII_BASE_DIR and the ugii and nxbin folders
- Environment variables in ugii_env.dat, and why it takes precedence over ugii_env_ug.dat
- Customization directories in custom_dirs.dat and their startup subfolders
- Site, group and user directories: UGII_SITE_DIR, UGII_GROUP_DIR and UGII_USER_DIR
- User profile files, and how to reset one user’s settings safely
Result: a documented map of where your NX installation reads its settings.
Customer defaults
- Customer defaults and preferences: company standard versus current part or session
- Site, group and user levels, inheritance and locks
- The .dpv files behind each level, and where they belong
- Finding a default, changing it and checking the effect after a restart
- 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.
Templates, drawing templates, roles and libraries
- How PAX files define the tabs and templates of the File New dialog
- Template parts with units, layers, attributes and drawing formats
- Adding a company template and testing it
- Roles: default roles, custom user roles and site roles in a shared directory
- Setting the default role for new users
- Drawing templates: borders and zones, a title block with part attributes, marked as a template and added to the File New dialog
- 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.
Licensing, installation and deployment
- License server or standalone node-locked license: how NX finds its license
- The SPLM_LICENSE_SERVER variable and typical license errors at start-up
- Unattended installation for many workstations, with features and license server set on the command line
- Functional releases and updates: each functional release in its own folder, so releases can run side by side
- Testing customizations in a new release before users get it, for example in a sandbox set up with the Siemens NX Launcher
- Advanced: software distribution with a silent installation and an installation log for every workstation
- 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.
Troubleshooting
- The NX syslog: where to find it and what to look for
- Slow start-up, missing menus, wrong templates or units: a short checklist
- Finding out whether a problem comes from the environment, the defaults, the role or the user profile
- Your own environment: reviewing your current defaults, roles and directories together
- Advanced: keeping the syslog with UGII_KEEP_SYSTEM_LOG and reading the installation log
- 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.
Teamcenter Integration for NX settings
- NX customer defaults for Teamcenter Integration and the matching Teamcenter preferences
- Settings for associated files, assembly loading, check-in and check-out, attribute mapping and JT creation
- Templates and PAX files in the Teamcenter database
- 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.
Shared environment and central administration
- NX installed once on a network share, with a local client installation on each workstation
- Site and group directories on a server share for customer defaults, roles and templates
- What belongs on the network and what stays local: user profile directory and temporary files
- 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.
Automation with journals, NX Open and macros
- Recording a journal on the Developer tab and playing it back
- Journal languages: Python on all platforms, Visual Basic .NET and C# on Windows
- Macros record keyboard and mouse input; journals are the more robust choice across NX releases
- 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
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?
What are customer defaults in Siemens NX?
What is the difference between customer defaults and preferences in Siemens NX?
How does Siemens NX find its license server?
How do you deploy Siemens NX to many workstations?
Which Siemens NX settings control the Teamcenter integration?
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 offerNX engineers as trainers · remote live or on-site · in small groups

