![]() ![]() You'll need to set the "connect as" user to a domain user that has access to the sharepoint folder you're connecting to.Ĭonnect to the ftp folder and you should be able to "cd" into the directory and put/get files without issue (just confirmed it myself). Give it a name and specify the sharepoint unc path for the physical path. On your ftp server, right click the ftp site in the IIS Manager and select "Add Virtual Directory". The IIS FTP server accepts UNC paths as backing storage to virtual directories. The WebDav Redirector allows you to access webdav resources (including Share Point) via UNC path, ie \yourspserver\site\doclib. It's great because it produces verbose error messages and give a lot of control, especially for the instances that SharePoint tries to block a particular filename or file extension. The best solution we've come up with for doing large file migrations into SharePoint is a mapped network drive then using a tool called FreeFileSync available at SourceForge to move your files and folders. As an opinion note though, the default view showing attributes that appear as incorrect is just plain annoying! File attributes are pretty important to my team, so we were concerned about that at the start. I particularly like the mapped network drive view of a SharePoint Document Library. Those file properties are still alive! They just need to be uncovered by a different view. As I understand it the files are actually stored in SharePoint as database objects and therefore SharePoint views display the database object (SQL object's) properties in Document Libraries where a new user would expect to see the file properties. Big edit: Have any of you figured out how to upload to SharePoint (WSS)? I've tried drive mapping and then using Robocopy and Synctoy to copy files thinking a tool might offer greater control (i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |