How to Share a SolidWorks PDM Vault View

What Is a Vault View?

The Vault View is a mapped connection between a user's local Windows machine and the central PDM server. It appears in Windows Explorer as if it were another drive or folder, and it links to the PDM Archive and SQL database.

Without a Vault View, users cannot see or interact with the PDM environment, even with a license and valid credentials.

Prerequisites Before Sharing a Vault View

Before creating or sharing a Vault View, make sure:

• The SolidWorks PDM client is installed on the target machine.
• The client version matches the server version exactly.
• The user has valid Windows login credentials and the right PDM permissions.
• The machine has network access to the Archive Server and SQL Server.

If any of these are missing, the Vault View will not work, or it will produce errors at login.

Method 1: Creating a Vault View Manually

For small teams or individual setups, the simplest route is the View Setup tool:

1. On the client machine, go to Start > All Programs > SOLIDWORKS PDM > View Setup.
2. Launch the View Setup wizard.
3. Select "Create a new vault view."
4. Enter the name of the vault and the archive server address.
5. Choose whether to create the Vault View for all users on the machine or just the current one.
6. Select the local drive location, for example map it as P:\ or place it in C:\PDM\VaultName.
7. Finish the wizard and log in to test access.

Repeat this on each workstation that needs access to the vault.

Method 2: Using the .cvs File for Deployment

In larger environments, a vault view configuration file (.cvs) distributes and automates the process.

1. On a system where the Vault View already works, go to C:\ProgramData\SOLIDWORKS\PDM\
2. Locate the .cvs file associated with the vault.
3. Copy the file to the target machines.
4. Double-click it. The View Setup wizard opens pre-filled with the server and vault information.
5. The user confirms the settings and completes setup.

This saves time and keeps the configuration consistent across users.

Method 3: Automated Deployment via Scripts or Group Policy

IT teams managing dozens or hundreds of machines usually automate it, through:

• Group Policy login scripts
• Microsoft SCCM or Intune
• Custom PowerShell scripts

These can install the PDM client silently and apply the .cvs file to each workstation with no user input. SolidWorks provides command-line parameters for silent installs. Test the sequence on a spare machine before you roll it out.

Troubleshooting Vault View Setup

If the Vault View does not work after setup, check:

• The Archive Server and SQL Server are reachable, by ping or telnet.
• The firewall is not blocking the ports (default PDM uses 3030 to 3032).
• The user is added in the PDM Administration tool.
• Re-run View Setup as administrator if permissions look like the problem.

Client-side connection and login errors are logged in C:\Program Files\SOLIDWORKS PDM\log.txt

Best Practices for Sharing Vault Views

• Use standard naming for vault drive letters or folders across the team, so support requests are easier to read.
• Deploy matching client and server versions. Version mismatches are a common cause of setup failures.
• Avoid creating vault views by hand on dozens of machines. Use .cvs files or scripts at that scale.
• For remote users, configure VPN access before setting up a Vault View.

Conclusion

Sharing a SolidWorks PDM Vault View is not difficult, but it is not optional either. Without it, users cannot reach the system at all. Whether you are onboarding one person or rolling access out across an enterprise, picking the right method (manual, file-based or automated) keeps the configuration consistent and cuts down support overhead.

Menu paths, file locations and port numbers above reflect Dassault Systemes' public SOLIDWORKS PDM documentation, checked 27 September 2026. Confirm them against the documentation for your own version before a rollout.

Related reading: cloud CAD document management for SolidWorks teams.