EasySIGN Registry Keys for settings, plotter deployment, Intune and PC migration

Audience

This article is for administrators, technical users, and deployment teams who need to reuse or deploy EasySIGN settings on another Windows PC or in a managed deployment scenario.

Primary use cases

Use this article when:

• You want to migrate EasySIGN settings from one PC to another.

• You want to reuse EasySIGN plotter or cutter settings.

• You are preparing a new EasySIGN workstation.

• You want EasySIGN output devices to be available to all Windows users on the same PC.

• You are preparing EasySIGN settings for a managed deployment.

• You are extending an EasySIGN silent installation with validated configuration settings.

Customer scenario

An administrator has configured EasySIGN on one reference PC and wants to reuse the same configuration on another PC or in a deployment package.

The configuration may include EasySIGN preferences, plotter or cutter definitions, and related output settings.

Some settings are stored per Windows user, while others can be stored machine-wide for all users on the device. Choosing the correct registry location is important for migration, plotter deployment, and managed installation workflows.

Summary

EasySIGN stores configuration information in the Windows registry.

The main confirmed EasySIGN registry locations are:

• Computer\HKEY_CURRENT_USER\SOFTWARE\Numerical Control Design

• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Numerical Control Design

The main confirmed plotter or cutter device locations are:

• Computer\HKEY_CURRENT_USER\Software\Numerical Control Design\EasySIGN (64) PV006\Easy32\InstalledDevices

• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Numerical Control Design\EasySIGN (64) PV006\Easy32\InstalledDevices

Use HKEY_CURRENT_USER for user-specific settings.

Use HKEY_LOCAL_MACHINE when settings must be available to all users on the same device.

Always export and back up the relevant registry keys before importing, changing, or deploying them.

1. Purpose and scope

This article explains how EasySIGN registry locations can be used for settings migration, plotter deployment, managed deployment preparation, and PC migration.

It covers:

• The difference between HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE.

• Confirmed EasySIGN registry locations.

• Confirmed InstalledDevices locations for plotters and cutters.

• How plotter settings are stored.

• How to prepare a reference configuration.

• How to migrate settings to another PC.

• What to check when using registry exports in a deployment workflow.

This article is public administrator guidance.

Advanced internal Intune Shared-PC and Self-Deploying troubleshooting is not covered in this article.

2. Registry safety notes

Windows registry changes can affect EasySIGN and Windows behavior.

Only qualified administrators should export, import, or change registry settings.

Before making registry changes:

• Back up the relevant registry keys.

• Confirm the EasySIGN version on the source PC.

• Confirm the EasySIGN version on the target PC.

• Confirm whether the setting is user-specific or machine-wide.

• Test the exported settings on one target PC before wider deployment.

• Keep a copy of the original registry export.

• Do not import registry settings from an unknown or untrusted source.

• Do not export or share license keys, credentials, personal data, or unrelated registry content.

3. Registry overview

EasySIGN uses both user-specific and machine-wide registry locations.

User-specific EasySIGN settings

Use this location for settings that belong to the currently signed-in Windows user:

• Computer\HKEY_CURRENT_USER\SOFTWARE\Numerical Control Design

These settings can include personal EasySIGN preferences, such as interface-related preferences, visible toolbars, widths of interface elements, and theme-related preferences.

Machine-wide EasySIGN settings

Use this location for settings that should apply to the device and be available across Windows users:

• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Numerical Control Design

Machine-wide settings are useful when EasySIGN configuration should not depend on one specific Windows user profile.

Installed devices for all users

Use this location when plotter or cutter definitions must be available to all users on the device:

• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Numerical Control Design\EasySIGN (64) PV006\Easy32\InstalledDevices

This is the preferred location for shared devices and managed deployment scenarios where the output device configuration should be available machine-wide.

Installed devices for one user

Use this location for a single-user workstation where the plotter or cutter setup belongs to the current Windows user:

• Computer\HKEY_CURRENT_USER\Software\Numerical Control Design\EasySIGN (64) PV006\Easy32\InstalledDevices

4. HKCU versus HKLM

HKEY_CURRENT_USER stores settings for the current Windows user profile.

Use HKEY_CURRENT_USER when:

• The PC is used by one Windows user.

• The settings are personal preferences.

• The EasySIGN configuration should follow only that user profile.

• The plotter or cutter setup is only needed for that specific user.

HKEY_LOCAL_MACHINE stores settings for the device.

Use HKEY_LOCAL_MACHINE when:

• The same EasySIGN configuration must be available to all Windows users on the PC.

• The PC is shared by multiple users.

• Output devices must be available machine-wide.

• Settings are prepared for managed deployment.

• Configuration should not depend on the first user who signs in.

When EasySIGN is configured so the same output device data is available to all users, the device definitions should be placed under HKEY_LOCAL_MACHINE instead of HKEY_CURRENT_USER.

5. InstalledDevices and plotter settings

Installed plotters and cutters are stored under:

• EasySIGN (64) PV006\Easy32\InstalledDevices

Under the InstalledDevices key, configured plotters or cutters usually appear as numbered subkeys, for example:

• 0

• 1

• 2

• 3

Each device can contain additional subkeys, including settings for that specific device.

Important behavior:

• The InstalledDevices key contains the configured output devices.

• Numbered subkeys usually represent individual installed plotters or cutters.

• Device-specific settings can be stored under the relevant device key.

• Only deviations from default values are typically stored.

• If a plotter still uses default values, its settings key may be empty or contain fewer values than expected.

• To understand default behavior, add a new plotter of the same type and use that clean configuration as the baseline.

6. Using registry settings for managed deployment

For managed deployment, first create and validate a reference EasySIGN configuration on one PC.

Recommended workflow:

• Install EasySIGN on a reference PC.

• Configure the required plotter or cutter manually.

• Test that the output works correctly.

• Confirm whether the device settings are stored under HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE.

• Use the HKEY_LOCAL_MACHINE variant when the configuration must be available to all users on the device.

• Export only the relevant EasySIGN registry keys.

• Import the registry settings after EasySIGN has been installed on the target PC.

• Test the result on a clean target PC before deploying to more systems.

The EasySIGN setup should run with administrator rights during managed installation.

This is important because installation and registry registration can fail when the installation process is not elevated.

7. Using registry settings for PC migration

The same registry knowledge can be used when moving EasySIGN from an old PC to a new PC.

Use this workflow:

Step 1: Prepare the source PC

1. Open EasySIGN on the old PC.
2. Confirm which settings need to be migrated.
3. Confirm which plotters, cutters, or output devices are configured.
4. Test that the configuration works before exporting it.
5. Confirm the EasySIGN version.

Step 2: Export the relevant registry keys

1. Open Windows Registry Editor.
2. Export the relevant EasySIGN registry keys.
3. Use HKEY_CURRENT_USER keys for user-specific settings.
4. Use HKEY_LOCAL_MACHINE keys for machine-wide settings.
5. Save the exported registry files in a secure location.

Step 3: Prepare the target PC

1. Install EasySIGN on the new PC.
2. Install required Windows drivers.
3. Configure required COM ports, printer drivers, USB drivers, or network paths.
4. Confirm that third-party software or RIP software is installed where required.
5. Start EasySIGN once before importing settings if this is part of your deployment process.

Step 4: Import and test

1. Back up the current EasySIGN registry keys on the target PC.
2. Import the confirmed registry export.
3. Restart EasySIGN.
4. Check whether the expected settings are available.
5. Check whether the plotters or cutters are available.
6. Send a small test job if output devices are involved.

8. Third-party RIPs and path dependencies

Third-party RIP-related configuration can sometimes be transferred through registry settings, but only when the target systems match the source system closely.

Check the following before reusing such configuration:

• The same third-party RIP software is installed.

• The software is installed in the same location.

• Local folders match the source PC.

• Network paths match the source PC.

• Required drivers are installed.

• Required ports are available.

• The target PC can access the same files and folders.

If file locations, network paths, local installation folders, or device ports differ between systems, the imported configuration may not work correctly.

9. Step-by-step deployment procedure

Step 1: Create a reference setup

1. Install EasySIGN on one reference PC.
2. Configure the required plotter or cutter.
3. Configure the required EasySIGN settings.
4. Test the workflow completely.
5. Confirm that output works before exporting registry settings.

Step 2: Choose HKCU or HKLM

1. Use HKEY_CURRENT_USER if the settings are only for one Windows user.
2. Use HKEY_LOCAL_MACHINE if the settings must be available to all users on the PC.
3. For shared output device configuration, use the machine-wide InstalledDevices location where possible.
4. Document which registry location is used.

Step 3: Export the relevant registry settings

1. Open Windows Registry Editor.
2. Go to the relevant EasySIGN registry location.
3. Export the required key.
4. Do not export unrelated registry branches.
5. Store the export securely.

Step 4: Add the registry import to the deployment workflow

1. Install EasySIGN first.
2. Import the registry settings after the EasySIGN installation step.
3. Run the installation and registry import with administrator rights where required.
4. Make sure all required drivers, paths, and third-party dependencies are available.
5. Test the deployment on one clean target PC.

Step 5: Validate the target PC

1. Start EasySIGN.
2. Check whether the expected settings are present.
3. Check whether the expected plotter or cutter is available.
4. Check whether the output device uses the expected configuration.
5. Send a small test job.
6. Confirm the result before deploying to additional PCs.

10. Validation

The migration or deployment is successful when:

• EasySIGN starts correctly on the target PC.

• The expected settings are available.

• Plotters or cutters appear as expected.

• Required Windows drivers and ports are available.

• Third-party paths or RIP dependencies are valid where used.

• A small test job works.

• The exported registry settings have been tested before wider deployment.

• The administrator has a backup of the original registry settings.

11. Administrator checklist

Before using EasySIGN registry settings, check:

• Is the configuration intended for one user or all users on the same PC?

• Should the settings be stored under HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE?

• Has EasySIGN been installed on the target PC?

• Are the source and target EasySIGN versions confirmed?

• Have the required plotters or cutters been tested on the reference PC?

• Are the non-default plotter settings actually stored under the relevant settings key?

• Are the relevant registry keys exported and backed up?

• Are required drivers installed on the target PC?

• Are required COM ports, printer ports, USB drivers, or network paths available?

• Are third-party components and paths identical where required?

• Is the EasySIGN setup run with administrator rights?

• Has the configuration been tested on one clean target PC before broader deployment?

12. Important notes and limitations

• This article is intended for administrators and advanced users.

• Always back up registry keys before importing or changing them.

• Do not import registry settings from unknown sources.

• Registry settings may depend on EasySIGN version, Windows version, user profile, device drivers, ports, and installed output devices.

• Device-related settings may not work if the target PC does not have the same drivers or ports.

• Third-party RIP settings may not work if paths and software locations differ.

• Only non-default plotter settings may be stored in the registry.

• An empty or small settings key does not always mean the plotter configuration is missing.

• This article does not include internal-only Intune Shared-PC or Self-Deploying troubleshooting.

• Test on one workstation before deploying to multiple PCs.

13. Conclusion

EasySIGN registry keys can be used to support settings migration, plotter deployment, managed deployment preparation, and PC migration.

The key decision is whether the configuration belongs under HKEY_CURRENT_USER for one user or under HKEY_LOCAL_MACHINE for all users on the device.

Use a tested reference PC, export only the relevant EasySIGN keys, install EasySIGN first on the target PC, import the confirmed registry settings, and validate the result with a small test job.

Related article

• Install EasySIGN without the installation wizard

Appendix A - Confirmed registry paths

User-specific EasySIGN settings:

• Computer\HKEY_CURRENT_USER\SOFTWARE\Numerical Control Design

Machine-wide EasySIGN settings:

• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Numerical Control Design

Installed devices for all users:

• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Numerical Control Design\EasySIGN (64) PV006\Easy32\InstalledDevices

Installed devices for one user:

• Computer\HKEY_CURRENT_USER\Software\Numerical Control Design\EasySIGN (64) PV006\Easy32\InstalledDevices

Appendix B - Device key behavior

Typical behavior under InstalledDevices:

• Configured plotters or cutters usually appear as numbered subkeys.

• Examples: 0, 1, 2, 3.

• Each device can contain additional subkeys with settings.

• Only settings that differ from default values are typically stored.

• A clean plotter of the same type can be used as a baseline for default behavior.