Customer Defaults in NX3

[nxpilot]

Does anyone know why I cannot change Customer Defaults from File -> Utilities -> Customer Defaults in NX3. When I enter this option and I try to change something I get a info: You do not have access to User level defaults file. So the Default Level is User (Read Only), and there is no other option. How can I change this?
Pls help

Thanks alot

 

[Xwheelguy]

This is all covered in the Documentation, thoroughly. Here is most of it:
[start]
You can use customer defaults to customize your NX startup. The initial settings and parameters of many functions and dialogs are controlled by customer defaults. Changes that you make to customer defaults will not take effect until your next NX session. You must close and reopen NX before you will see any of the changes. You can view your current customer default settings by opening the Customer Defaults dialog at File-> Utilities-> Customer Defaults.

You should use the Customer Defaults dialog to make changes to customer defaults, instead of modifying the customer defaults files themselves. If you attempt to modify the defaults files, you might corrupt them. You can convert your pre-NX 3 customized defaults files by using the Import Defaults option on the Current Settings dialog.

Customer defaults can be controlled at three levels: site, group, and user. Site is the highest level, user is the lowest. Any or all of these levels may be available to you, based on how the customer default environment variables are defined at your site. If none of the environment variables are defined, the level is Shipped (read-only).

The Shipped level of customer defaults is not available once you or your company have defined any (or all) of the user, group, or site directories. This allows the Shipped level to be preserved in case it is ever needed.

Managers at a higher level can lock the settings of customer defaults that they do not want anyone at the lower levels to change. The group level can lock customer defaults at the user level, and the site level can lock defaults at the group and user levels. You cannot lock defaults at the user level.

Any of these levels (site, group, or user) can be read-only.

To set up a user, group, or site level, you must define the appropriate environment variable with a directory. You must first create a directory named startup where you want to store the customer defaults file for that level. See the table below for the environment variables and the name of the customer defaults file for each level.

Level Environment Variable Defaults File

user UGII_USER_DIR nx3_user.dpv
group UGII_GROUP_DIR nx3_group.dpv
site UGII_SITE_DIR nx3_site.dpv


If you are already using the UGII_USER_DIR environment variable for other purposes, you can use the UGII_LOCAL_USER_DEFAULTS environment variable. When you define the environment variable, you must point it to the .dpv file you will use (instead of just the directory, as done with the other environment variables).

Examples:

UGII_GROUP_DIR=X:\directory\subdirectory_group

UGII_LOCAL_USER_DEFAULTS=X:\directory\subdirectory\nx3_local_user.dpv

If both of these environment variables are defined, the system uses the UGII_LOCAL_USER_DEFAULTS environment variable to define the customer defaults user level. NX is shipped with this variable defined, so if you want to use a common user directory (i.e., the one defined by UGII_USER_DIR), you must remove the definition for UGII_LOCAL_USER_DEFAULTS from your environment variables file.
[end]

Make sure you have full permissions for the directory where the .dpv files are kept as well as having full permissions for the .dpv files themselves.

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com