|
1.
|
Can DocKIT be
installed and run from a client computer (workstation)? |
|
Yes, DocKIT can be installed and
run from a Windows 7/Vista/XP client computer (desktop / workstation) with .NET
Framework 2.0 or later. |
|
Top |
|
2.
|
Can I
connect to a remote SharePoint server within my local network using DocKIT?
|
|
Yes, you can connect to a remote
Microsoft SharePoint Server 2010 / Microsoft SharePoint Foundation 2010 / MOSS
2007 / WSS v3.0 server within your local network by specifying the required user
credentials to connect to the remote SharePoint server.
|
| Top |
|
3.
|
Does DocKIT
support a batch file for import instead of setting up the import task through
the user interface?
|
|
Yes, the current version of
DocKIT supports batch import of documents using a batch descriptor file. You can
create a task of Import documents from a batch descriptor file option
and specify the import task settings to run in an interactive session or
scheduled task.
|
| Top |
| 4. |
How does
DocKIT handle document versions?
|
|
DocKIT provides options to handle
the condition where a document with the same name already exists in SharePoint,
as the one presently imported to SharePoint. You can specify whether to
overwrite the existing document in SharePoint, retain existing version and
update the latest version or to leave the document as-is in SharePoint.
If you select the 'Overwrite' option, DocKIT
deletes the document in SharePoint (along with its version history) and imports
the new document. If you select the 'Create New Version' option, DocKIT retains
existing document versions in SharePoint and updates the document as the latest
version.
|
| Top |
|
5.
|
Does DocKIT
propagate custom document properties defined in documents?
|
|
DocKIT imports the file
properties seen in the 'Summary' tab of file properties in Windows Explorer,
namely - Subject, Author, Category, Keywords, and Comments for all documents,
except image files such as JPG, GIF etc. For MS-Office documents (Word, Excel,
PowerPoint), 'Title', 'Manager', 'Company', 'Application Name', 'Word Count',
'Slide Count' etc. file properties can also be imported using DocKIT. The custom
Microsoft Office document properties (available in Custom tab in document
Properties screen) will be automatically propagated to SharePoint library
automatically, when a column with same name exists in the SharePoint library.
|
| Top |
|
6.
|
Can I import
documents and folders to multiple libraries?
|
|
Yes. DocKIT allows you to import
folders/documents to multiple libraries in a single import session. You can do
so by using the batch file task option or use the explorer like UI to
drag-and-drop documents into multiple libraries along with associated document
metadata.
|
| Top |
|
7.
|
How does
DocKIT associate the external metadata to the documents that are imported to
SharePoint?
|
|
The field names that are
specified in the HEADER of the external metadata file will be used to match the
column names in the SharePoint library. DocKIT will assign the respective
columns values specified for each document in the external metadata file to the
respective documents in the SharePoint library. You must ensure that the field
names in the metadata file and the SharePoint column names in the corresponding
SharePoint library exactly match to ensure that the respective metadata values
are assigned to the documents.
|
| Top |
| 8. |
What types
of columns cannot be included in the metadata?
|
|
DocKIT will not update System
defined, Read-only and Computed columns in a document / picture library.
|
| Top |
|
9.
|
What are the
precautions to take while migrating documents to SharePoint using DocKIT?
|
|
-
Ensure the network traffic is
minimal while copying documents / files from remote shares on the network.
-
Avoid running any other
applications in the background during the migration process.
-
Temporarily disable any
anti-virus software that may be running during the migration operation (as
necessary).
-
Good hardware configuration.
-
Run the document migration tasks
during off-peak usage of SharePoint environment (if already in operation).
|
| Top |
|
10.
|
The
application error log file DocKITErrorLog.txt in the DocKIT application path is
gradually increasing in size. Can I delete it?
|
|
Yes, you may delete this error
log file. DocKIT generates an error log file in the Log folder in the common
application data path (<Application Data Folder>\DocKIT4x). The
error log file tends to increase in size over a period of time especially if the
application meets with frequent error conditions. The application does an
"append" to the error log each time it runs. This is required for
diagnostic purposes during trouble shooting. You may delete the error log file
periodically. For each import task, DocKIT creates a task folder (same name as
task name) and the error log file is stored in the respective task folder. You
can use DocKIT's cleanup utility periodically to maintain the task files.
|
| Top |
|
11.
|
Does DocKIT
propagate the current NTFS permissions in my source folders and files to
Microsoft SharePoint Server 2010 / Microsoft SharePoint Foundation 2010 / MOSS
2007 / WSS v3.0?
|
|
No, the current version of DocKIT
does not propagate NTFS permissions to SharePoint. However, we plan to include
this feature in the next major release of the software.
|
| Top |
|
12.
|
What is the
required structure for the metadata file?
|
|
Refer to the relevant sections in
the application help document for more information.
|
| Top |
|
13.
|
Can DocKIT import Created
Date and Last Modified Date fields of folder and/or files to SharePoint? |
|
DocKIT propagates the Created
Date and Last Modified Date fields from original Source (file system or summary
properties) to the respective date fields for folders and/or files in SharePoint.
Please note that DocKIT Web Services must be
installed to activate this feature (Refer System Requirements). Also, please
ensure the user name specified in SharePoint Login dialog / user account
specified in the Run As parameter in the scheduled task is a:
-
Member of administrators group in
the local server and remote SQL Server (or)
-
Application pool user account
(or)
-
Owner of the site where the
destination library resides
Apart from the file system date
fields, DocKIT allows users to assign 'Date Created', 'Date Last Printed', 'Date
Last Saved' in MS-Office documents to be assigned to the system date fields in
SharePoint (namely, Created Date and Modified Date). |
| Top |
|
14.
|
Can DocKIT
import Created By and Modified By fields of folders and/or files to SharePoint? |
|
DocKIT propagates the Created By
and Modified By fields from original source document (namely, Author, Manager
& Last Saved By) or any other user column specified in the external metadata
file to the respective user fields for folders and/or files in SharePoint.
Please note that DocKIT Web Services must be
installed to activate this feature (Refer System Requirements). Also, please
ensure the user name specified in SharePoint Login dialog / user account
specified in the Run As parameter in the scheduled task is a:
-
Member of administrators group in
the local server and remote SQL Server (or)
-
Application pool user account
(or)
-
Owner of the site where the
destination library resides
|
|
Top |
|
15.
|
Does DocKIT
support Content Approval Status to be assigned for folders and files after
importing them to a SharePoint library? |
|
Yes, DocKIT will be able to set
the content approval status and related comments to the folders and files after
importing them to a SharePoint library. DocKIT enables you to specify the
approval status from any one of the sources such as external metadata file,
custom property of the file and specific approval status (say Draft, Pending and
Approved).
Please note that DocKIT
Web Services must be installed to activate this feature (Refer System
Requirements). Also, please ensure the user name specified in SharePoint Login
dialog / user account specified in the Run As parameter in the scheduled task is
a:
-
Member of administrators group in
the local server and remote SQL Server (or)
-
Application pool user account
(or)
-
Owner of the site where the
destination library resides
|
|
Top |
|
16.
|
What
permissions are required in SharePoint for DocKIT to import documents to a
library? |
|
-
The following permissions must be
enabled at the web application level:
-
Site Permissions - View Pages,
Use Remote Interfaces, Open
-
List Permissions - Override Check
Out, Add Items, Edit Items, Delete Items , View Items
-
For the import task to run as
expected, the given user credential must have at least View, Add, Update and
Delete permissions in the destination library.
-
For DocKIT to perform a cancel
checkout operation on a document which is currently checked out by another user,
Override Check Out must be enabled in the List Permissions. Also, the user
performing the import process must have Full Control in the destination library.
-
For updating System Dates
(Created Date and Last Modified Date), System Users (Created By and Modified By)
and Content Approval (Approved, Pending and Draft) of folders / files from
original source to the respective columns in SharePoint, the user name specified
in SharePoint login dialog / user account specified in the Run As parameter in
the scheduled task should be:
-
Member of administrators group in
the local server and remote SQL Server (or)
-
Application pool user account
(or)
-
Owner of the site where the
destination library resides
|
|
Top |
|
17.
|
Can DocKIT
import tasks be invoked from the command line or scheduled?
|
|
Yes, you can invoke import tasks
created in DocKIT application using the import task wizard from either the DOS
command prompt or Windows Task Scheduler. Please refer to the relevant sections
in the application help document for more information. |
| Top |
|
18.
|
Does DocKIT for SharePoint
2010 / 2007 support Windows Server 2008 / Windows Server 2003 64-bit platform? |
|
Yes, DocKIT supports both Windows
Server 2008 / 2003 (32-bit and 64-bit) platforms. Please note that you can use
same setup file to install DocKIT client application for both architectures
(32-bit or 64-bit platform), whereas DocKIT Web Services component have separate
setup files for the respective architecture. Please refer INSTALLATION
INSTRUCTIONS.TXT available in the downloaded zip file for more information. |
|
Top |
|
19.
|
Does DocKIT
for SharePoint 2010 / 2007 support 'Audience Targeting' available in Microsoft
SharePoint Server 2010 and MOSS 2007? |
|
Yes, DocKIT seamlessly supports
'Audience Targeting' feature available in Microsoft SharePoint Server 2010 and
Microsoft Office SharePoint Server 2007. A file / folder can be assigned
respective target audiences belonging to any of the following categories:
You can provide the respective
audience values (that belong to the above listed categories) separated with ';'
in the external metadata file in order to assign them in 'Target Audiences'
field of the respective document / folder in a SharePoint library. Please note
that DocKIT expects DocKIT Web Services component to be installed in the
destination SharePoint server (Microsoft SharePoint Server 2010 / MOSS 2007) in
order to set the values that belong either to Global Audience group or Security
/ Distribution group. |
|
Top |
|
20.
|
Does DocKIT
for SharePoint 2010 / 2007 support 'Audience Targeting' available in MOSS and
Microsoft SharePoint Server 2010?
|
|
Yes. Refer to the relevant
sections in the application help document for more information. |
| Top |
|
21.
|
What are
the authentication methods that DocKIT supports?
|
|
The current version of DocKIT
supports Windows authentication and Forms authentication methods only. DocKIT
will automatically detect the configured authentication in destination
SharePoint site and connect it by initiating respective authorization process
against SharePoint site. |
| Top |
|
22.
|
Can I use
FQDN based user credential in DocKIT?
|
| . |
Yes, DocKIT supports both NetBIOS
conventions and FQDN conventions to connect to SharePoint site.
|
| Top |