DESCRIPTION: A Windows Drive or Share enables you to transfer files to and from any local or mapped drive on your Windows computer. Once you have downloaded the Windows App, all you need to do is set up a Windows System before you can immediately transfer files to and from your Windows computer. To transfer files from your network, you must map the drive to your local computer (see instructions here). CIFS drives and some NFS drives are supported by this adapter.
SUPPORTED POP: Windows.
DISK OR SHARE: Select the drive from the dropdown that you want to share. (Information on mapping network drives is here). Note that the Disk or Share field only displays after you have completed the Nickname field and selected a valid Windows POP. You will further narrow your selection of subdirectories and/or files when you build your jobs.
Windows Source and Target Node Configuration
Advanced Windows Settings
Advanced settings for Windows source and target nodes are available by selecting the Advanced Options link. Most of them should be left at their default settings unless you are instructed to change them by Tervela Tech Support.
COPY SYSTEM FILES: this is another option that enables you to transfer Windows system files.
DOMAIN HOST: This field is used for Account Mapping only where the Windows computer is a source. It specifies a server (IP address or server name) within the domain to which file owners belong, and may be used in cases where the computer on which the source files reside is outside of the domain for the file owners. A computer outside the domain will generate spreadsheets that have SIDs for users rather than the actual usernames. You may leave this field blank unless instructed to complete it by Tervela Support.
DEREFERENCE LINKS: This option is selected by default. When selected, Cloud FastPath will follow the path of a symlink/shortcut to the file(s) it points to, and will transfer those files.
INCLUDE FILES: Enter a text string in conjunction with wildcard characters to limit a transfer to only the files specified. For example, if you enter ^(.*\/)?sendme.*$ in this field, all files that have a filename whose root name is ‘sendme’ will be sent, but any other files will be ignored.
MODIFIED AFTER: Enter a date into this field to limit the migration to files that have a modify date on or after the date specified.
ZIP SPECIAL MACOS FILES ON NTFS: checking this option will zip the data and resource fork files for legacy MacOS font s into zip files that are more readily transferable and stable on non-Mac platforms such as cloud providers. Consult email@example.com if you are interested in using this option.
COPY HIDDEN FILES: Copies hidden Windows system files such as .sys and .ini files. By default, CFP does not transfer these files as they are generally not of use beyond the source computer; many cloud service providers do not accept these files. Use this option and the Copy System Files option with caution, particularly if these files may eventually be downloaded to another Windows computer.
BENCHMARK MODE: If this field is selected, when the job runs, CFP will generate 100 test data files on the source in a folder called ‘cfptest,’ which will be saved as a subdirectory in the source folder as selected by the file chooser. Aside from the top level folder selected in the file chooser, any additional files and folders selected will be ignored for transfer. The CFP-generated test files will be sent to the target, and when the job completes, the CFP-generated files and ‘cfptest’ folder will be deleted. This field is intended for performance testing.
EXCLUDE FILES: Enter a text string in conjunction with regex expressions to exclude files from transfer. The default expression excludes temp files (files that start with ‘~$’ or end with ‘.tmp’), but you can add exclude instances by clicking the + button next to the Exclude field. For example, if you do not want to send .docx files, enter ^(.*\/)?*.docx in this field. This field can be useful to exclude files that are generating permissions errors, either because the files are open by an application or they have user-specific restricted access.
Account Mapping Considerations
- If you are migrating personal user folders from an Active Directory or similar server setting, you will probably want to select path based mapping in the Account Mapping modal to generate your spreadsheet. Path based mapping ensures that all content in a given personal folder will all go to a single account on the target, regardless of who owns the content in that folder.
- For project and team based folders where many users own content, owner based mapping is generally more suitable.
- Windows user sets frequently have groups such as BUILTIN\Administrators who own files or folders in the selected data set. These groups appear in the Groups tab of the spreadsheet and you must enter a target account in the Target Owner field. If you do not map the Group owner to a target account, it will generate a validation error. If the Group is not listed in the paths tab as a sharer, you may leave its Target Group field blank.