HOWTO: Migrate from a Network Share
  • 17 Feb 2022
  • 4 Minutes to read
  • Dark
  • PDF

HOWTO: Migrate from a Network Share

  • Dark
  • PDF

How to Migrate From a Network Share to Asset Directory Using ProGet

Migrating from a network share to hosted files in an asset directory could be a smart move for teams that:

Whatever the use case, having the ability to share your files internally is a big benefit to many teams. The biggest question these teams run into when migrating is how to migrate thousands of files spread over hundreds of folders.

Using ProGet as your web-based file host makes it easy to move files over.

In this article we’ll run through a typical scenario of a company, Kramerica, looking to migrate some of their files from a network share to hosted files in an asset directory

Step 1: Plan What Files/Folders You Want to Move to Asset Directory

In ProGet, your asset directory works very similar to a file share. Folders in your asset directory can be shared easily to many users, files can be downloaded and updated.

However, unlike file share services, documents can’t be worked on directly. What that means is users must to work on a file, a user must download, work on, save, then re-upload a new version. While more difficult to work on, this means that files less likely to be accidentally saved over. ProGet is an ideal place to store and share files that are rarely changed. But not an ideal place for works in progress.

It’s important to note, users that have access to an asset directory in ProGet, will have access to all subfolders within it. So, organizations that require multiple levels of security will need to create separate asset directories that have the appropriate permissions and restrictions.

For our example, Kramerica plans to move over 2 folders:

Folder Access
Sales Assets: Including PDF’s presentations, pricing guides, etc. Sales Team
HR Guides: Including the employee handbook, dress codes, etc. Everyone

Step 2: (Optional) Integrate ProGet with Active Directory

This step is optional but recommended.

Organizations can Integrate AD with ProGet and use pre-set groups and permissions in the following steps.
Kramerica will integrate navigate to settings > “Security & Authentication” > “Change user Directory (LDAP)”

After successfully filling out the following popup, LDAP will be integrated with ProGet, allowing us to use all Kramerica’s previously configured users and groups.

Switch to Active Directory in ProGet

Step 3: Create HR-Guides Asset Directory

We’ll now create our first asset directory: HR-Guides

To do this, navigate to “Assets” > “Create New Asset Directory” > and fill in the popup with a name and optionally, a description.

Create HR-Guides Asset Directory in ProGet

Now that our feed is created, we want to enable versioning. To do this, navigate to “Manage Directory” > "Properties" > "Asset Directory Settings" > "Versioning"

Once versioning is enabled, old versions of files will be retained after they are overwritten.

ProGet Manage Feed of HR Guide

Now that our asset directory is configured, we can start uploading HR files and folders. Simply navigate to the asset directory and click “Add/Upload files”. A popup will allow you to select how you’d like to add an asset.

For this example, we’ll choose to “Upload Files” using the browser since it’s the simplest.

ProGet Add Assets

After locating the desired folder, we will drag and drop files into the asset directory.

Asset Directory Upload Files Drag-and-Drop

Step 4: Grant Permissions

Now that our “HR-Guide” asset directory is created, we must make sure users have access to it. By default, all groups in ProGet have zero permissions.

Tasks and permissions can get very granular and organizations with complex team structures might take longer to set up than others. Fortunately, asset directory permissions in ProGet are simple. Users will either have read permissions, write permissions, or no permissions.

Kramerica would like the ProGet built-in pseudo group “Everyone” (all users) to have access to “View & Download Packages” from the “HR-Guide” asset directory.

To do this, we’ll navigate to Settings > "Security & Authentication" > Users & Tasks > "Tasks" > "Add Permissions".

Add Privilege to HR Guides Directory

Now all Kramerica’s ProGet users will be able to see, view, and download all “HR-Guides” documents.

Step 5: Create Sales-Assets Active Directory

Next, we’ll create another active directory sales-assets.

We’ll do this by repeating the same thing we did in Step 3.

Create New Sales Assets Active Directory

Step 6: Give Sales Group Permission

In ProGet, limiting active directory permissions to separate groups is easy. For our example, only sales team members should have access to the “sales-assets” active directory.

To set this up, navigate to Settings > Security & Authentication > Users & Tasks > "Tasks" > "Add Permissions" and give permission to Kramerica’s “Sales Team” to “View & Download Packages” from “sales-assets”. After setting this up, our tasks overview page looks like this:

Tasks and Feeds Configured

Using Your Asset Directory

Now that you have all your asset directories, groups, and permissions set up, you can do many things like:

  • Have restricted internet access but do not want to use a network share.
  • Would like to host and access files without the requirement of a VPN.
  • Would like to leverage Replication and High Availability in ProGet for the uses of Edge Computing, Federated Development, and Disaster Recovery
  • Easily hyperlink to web-based files compared to network shares.

Was this article helpful?