How to Share a SolidWorks PDM Vault View

What Is a Vault View?

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

Without a Vault View, users cannot see or interact with the PDM environment — even if they have a license and proper 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 correct version of the client matches the server version exactly.
  
  
• The user has valid Windows login credentials and appropriate PDM permissions.
  
  
• The system has network access to the Archive Server and SQL Server.
  
  

If any of these are missing, the Vault View won’t work, or it will produce errors during login.

Method 1: Creating a Vault View Manually

For small teams or individual setups, the simplest way is to use 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 (e.g., map it as P:\ or place it in C:\PDM\VaultName).
   
   
7. Finish the wizard and log in to test access.
   
   

This process needs to be repeated on each workstation that should access the vault.

Method 2: Using the .cvs File for Deployment

In larger environments, you can use a vault view configuration file (.cvs) to distribute and automate the process.

1. On a system where the Vault View is already working, go to:
   
   C:\ProgramData\SOLIDWORKS\PDM\
   
   
2. Locate the .cvs file associated with the vault.
   
   
3. Copy this file to the target machine(s).
   
   
4. Double-click it, and it will launch the View Setup wizard pre-filled with server and vault information.
   
   
5. The user only needs to confirm settings and complete setup.
   
   

This method saves time and ensures consistency across all users.

Method 3: Automated Deployment via Scripts or Group Policy

IT teams managing dozens or hundreds of machines may prefer automated deployment. This can be done via:

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

These scripts can silently install the PDM client and apply the .cvs file to each workstation without user input. SolidWorks provides command-line parameters for silent installs — though detailed testing is essential.

Troubleshooting Vault View Setup

If the Vault View doesn’t work after setup, check the following:

• Ensure the Archive Server and SQL Server are reachable via ping or telnet.
  
  
• Check that the firewall isn’t blocking ports (default PDM uses 3030–3032).
  
  
• Make sure the user is added in the PDM Administration tool.
  
  
• Re-run the View Setup as administrator if permissions are an issue.
  
  

Logs are available in:

C:\Program Files\SOLIDWORKS PDM\log.txt

for client-side errors during connection or login.

Best Practices for Sharing Vault Views

• Use standard naming conventions for vault drive letters or folders across the team to avoid confusion.
  
  
• Always deploy matching client and server versions — mismatches are the most common cause of setup failures.
  
  
• Avoid creating vault views manually on dozens of machines. Use .cvs files or scripts for scale.
  
  
• For remote users, ensure that VPN access is configured before attempting to set up a Vault View.
  
  

Conclusion

Sharing a SolidWorks PDM Vault View isn’t difficult — but it’s essential. Without it, your users can’t access the system at all. Whether you’re onboarding one user or rolling out access across an enterprise, choosing the right method (manual, file-based, or automated) ensures consistency and minimizes support overhead.

Always validate connectivity, match software versions, and test logins before going live. With a bit of upfront planning, your team will be working inside the vault in no time.

‍