G
Guest
Overall a very nice app; clean and easy to use.
Still a few bugs to iron out - in particular the handling of empty folders.
Empty folders, at least in my tests, were not created and folders that were
later deleted from a source were not deleted when synchronised. I know the
latter is mentioned in the SyncToy Help but I do think that it should delete
folders (whether this is accessible as a none-default option is up to you!
I've posted the setup and some of the testing examples below (the missing
tests were duplicates of a base type)
One interface change I would make would be to open an explorer instance to
the left and right folder(s) from the SyncToy main form. (for example:
clicking on the right/left computer image; clicking on the right/left Folder
text; clicking on the right/left folder paths).
This would allow users either testing (such as me!), unsure (such as most of
our work staff!) or just a little paranoid that the files have indeed been
synchronised.
The Technical Notes state that the folder pair name cannot be changed as it
invalidates stored snapshots. Could you not use a unique identifier to
identify the folder pair and then use that UID to locate and/or edit the
friendly name? The UID/friendly name lookup tabe would then be stored in the
SyncToyDirPairs.bin.
While not the most important feature/change I want I would like it if during
the New Folder Pair wizard you could choose, perhaps via a tick-box, to use
the source-folders name as the destination folder.
An example I used was My Pictures from the users profile on the PC to a USB
drive [E:]. It currently requires the user to create a new folder for the
right side otherwise the contents of C:\Docume~1\%Username%\Favorites is
placed directly on the root of E:. By allowing the user to use a tickbox to
use the source folders name it would automatically create the Favorites
folder on E:. This may be of less use to anyone performing complicated
sync's but would remove a step for novice IT users. A tooltip would be
capable of disseminating the necessary information regarding usage.
It would be nice if the application allowed you to change the name and
location of the SyncToy data folder. Ideally you would be able to do this
during the install process but it should definitely be possible from within
SyncToy.
It would also be nice if access to advanced/technical options could be
restricted; maybe using logon credentials?
Another thing I'd like is to see user and computer configurations seperated.
Global (computer) settings could define whether users can make 'per-user'
changes (such as the name/location of the SyncToy data folder). The computer
settings could be used to provide either default settings or mandatory
settings; if neither are present then hardcoded default settings could be
used.
I'd like to see the ability to import and export folder pairs; both through
the GUI and via the command line. This would allow system administrators to
quickly roll out standardised sync profiles (such as My Docs to USB drive;
Favourites to USB Drive, etc...). If you could import multiple
profiles/pairs at once it'd be ideal! This kind of doubles up with the
granular security on the settings - you can push Folder Pair profiles to
users and/or restrict users from creating new Folder Pairs. If they are
allowed to create new pairs then you can control whether they can
import/export those profiles.
Ideally I'd like to see the config/settings files and/or the Folder Pair
profiles in files rather than registry keys; preferably in a format that can
be edited in notepad by advanced users with sufficient permissions to write
to the file (XML for example).
As you can probably tell I'm the poor sap that'll have to install and
configure this on 100's of machines. It might not take very long seperately
(or even as one if centrally deployed) but I do think that they'd prefer me
to set up the Folder Pair profiles so they just have to click a button.
That said I thank you from the bottom of my heart; this little app looks
like it'll save me an awful lot of time and energy when dealing with sync
issues (ie. users!).
SyncTest Settings
-----------------------
Left Folder
+ C:\Documents & Settings\%Username%\My Documents\SyncSource
[SyncSource]
|
|---- Folder1
| |
| |---- FolderA
| | |
| | |---- File1
| | |---- File2
| |
| |---- FolderB
|
|-- Folder2
Right Folder
+ U:\SyncDest
SyncToy Action
+ Synchronise
Options for this Folder Pair
+ All files included
+ Do not check file contents
+ Active for run all
+ All Subfolders included
+ Save overwritten files in the Recycle Bin
Process: First Run
-----------------------
An information dialog is generated. The Run Results table shows no
operations (note: this does not mean it shows 0 operations but rather the
text is missing)
The dialog takes and maintains focus within the application. The title of
the dialog is ‘SyncToy’; the image is the information bubble; the body of
text is ‘Exception during run: Requested registry access is not allowed.’ and
there is only one button ‘OK’.
Clicking ’OK‘ closes the form and returns focus to the SyncToy main form.
Examination of the folders shows that only Folder1, FolderA and both files
File1 and File2 were created in the destination; empty folders Folder2 and
FolderB were not created.
[SyncDest]
|
|---- Folder1
|
|---- FolderA
|
|---- File1
|---- File2
Process: Run SyncToy Action ‘Synchronise’ – no changes
------------------------------------------------------------------
The results form reports that there are no changes to synchronise and the
action is complete. Clicking ‘Close’ closes the form and returns focus to
the SyncToy main form.
Process: Run SyncToy Action ‘Synchronise’ – file/folder changes
--------------------------------------------------------------------------
File1 and File2 moved to FolderB
File2 renamed to FileB
[SyncSource]
|
|---- Folder1
| |
| |---- FolderA
| |
| |---- FolderB
| |
| |---- File1
| |---- FileB
|
|-- Folder2
An information dialog is generated. The Run Results table shows no
operations (note: this does not mean it shows 0 operations but rather the
text is missing)
The status text immediately above the progress bar indicates a Renaming
operation was or is currently running.
The dialog takes and maintains focus within the application. The title of
the dialog is ‘SyncToy’; the image is the information bubble; the body of
text is ‘Exception during run: Requested registry access is not allowed.’ and
there is only one button ‘OK’.
Clicking ’OK‘ closes the form and returns focus to the SyncToy main form.
Examination of the folders shows that files File1 and File2 were synchonised
and the file rename was successful. Empty folder Folder2 was not created.
[SyncDest]
|
|---- Folder1
| |
| |---- FolderA
| |
| |---- FolderB
| |
| |---- File1
| |---- FileB
|
|-- Folder2
Process: Run SyncToy Action ‘Synchronise’ – file/folder changes
--------------------------------------------------------------------------
FolderB and the files it contained were deleted
[SyncSource]
|
|---- Folder1
| |
| |---- FolderA
|
|-- Folder2
An information dialog is generated. The Run Results table shows no
operations (note: this does not mean it shows 0 operations but rather the
text is missing)
The status text immediately above the progress bar indicates a Deleting
operation was or is currently running.
The dialog takes and maintains focus within the application. The title of
the dialog is ‘SyncToy’; the image is the information bubble; the body of
text is ‘Exception during run: Requested registry access is not allowed.’ and
there is only one button ‘OK’.
Clicking ’OK‘ closes the form and returns focus to the SyncToy main form.
Examination of the folders shows that files File1 and File2 were deleted but
FolderB was not deleted. Empty folder Folder2 was not created.
[SyncDest]
|
|---- Folder1
| |
| |---- FolderA
| |
| |---- FolderB
|
|-- Folder2
---------------------------------------------------------------------
Still a few bugs to iron out - in particular the handling of empty folders.
Empty folders, at least in my tests, were not created and folders that were
later deleted from a source were not deleted when synchronised. I know the
latter is mentioned in the SyncToy Help but I do think that it should delete
folders (whether this is accessible as a none-default option is up to you!
I've posted the setup and some of the testing examples below (the missing
tests were duplicates of a base type)
One interface change I would make would be to open an explorer instance to
the left and right folder(s) from the SyncToy main form. (for example:
clicking on the right/left computer image; clicking on the right/left Folder
text; clicking on the right/left folder paths).
This would allow users either testing (such as me!), unsure (such as most of
our work staff!) or just a little paranoid that the files have indeed been
synchronised.
The Technical Notes state that the folder pair name cannot be changed as it
invalidates stored snapshots. Could you not use a unique identifier to
identify the folder pair and then use that UID to locate and/or edit the
friendly name? The UID/friendly name lookup tabe would then be stored in the
SyncToyDirPairs.bin.
While not the most important feature/change I want I would like it if during
the New Folder Pair wizard you could choose, perhaps via a tick-box, to use
the source-folders name as the destination folder.
An example I used was My Pictures from the users profile on the PC to a USB
drive [E:]. It currently requires the user to create a new folder for the
right side otherwise the contents of C:\Docume~1\%Username%\Favorites is
placed directly on the root of E:. By allowing the user to use a tickbox to
use the source folders name it would automatically create the Favorites
folder on E:. This may be of less use to anyone performing complicated
sync's but would remove a step for novice IT users. A tooltip would be
capable of disseminating the necessary information regarding usage.
It would be nice if the application allowed you to change the name and
location of the SyncToy data folder. Ideally you would be able to do this
during the install process but it should definitely be possible from within
SyncToy.
It would also be nice if access to advanced/technical options could be
restricted; maybe using logon credentials?
Another thing I'd like is to see user and computer configurations seperated.
Global (computer) settings could define whether users can make 'per-user'
changes (such as the name/location of the SyncToy data folder). The computer
settings could be used to provide either default settings or mandatory
settings; if neither are present then hardcoded default settings could be
used.
I'd like to see the ability to import and export folder pairs; both through
the GUI and via the command line. This would allow system administrators to
quickly roll out standardised sync profiles (such as My Docs to USB drive;
Favourites to USB Drive, etc...). If you could import multiple
profiles/pairs at once it'd be ideal! This kind of doubles up with the
granular security on the settings - you can push Folder Pair profiles to
users and/or restrict users from creating new Folder Pairs. If they are
allowed to create new pairs then you can control whether they can
import/export those profiles.
Ideally I'd like to see the config/settings files and/or the Folder Pair
profiles in files rather than registry keys; preferably in a format that can
be edited in notepad by advanced users with sufficient permissions to write
to the file (XML for example).
As you can probably tell I'm the poor sap that'll have to install and
configure this on 100's of machines. It might not take very long seperately
(or even as one if centrally deployed) but I do think that they'd prefer me
to set up the Folder Pair profiles so they just have to click a button.
That said I thank you from the bottom of my heart; this little app looks
like it'll save me an awful lot of time and energy when dealing with sync
issues (ie. users!).
SyncTest Settings
-----------------------
Left Folder
+ C:\Documents & Settings\%Username%\My Documents\SyncSource
[SyncSource]
|
|---- Folder1
| |
| |---- FolderA
| | |
| | |---- File1
| | |---- File2
| |
| |---- FolderB
|
|-- Folder2
Right Folder
+ U:\SyncDest
SyncToy Action
+ Synchronise
Options for this Folder Pair
+ All files included
+ Do not check file contents
+ Active for run all
+ All Subfolders included
+ Save overwritten files in the Recycle Bin
Process: First Run
-----------------------
An information dialog is generated. The Run Results table shows no
operations (note: this does not mean it shows 0 operations but rather the
text is missing)
The dialog takes and maintains focus within the application. The title of
the dialog is ‘SyncToy’; the image is the information bubble; the body of
text is ‘Exception during run: Requested registry access is not allowed.’ and
there is only one button ‘OK’.
Clicking ’OK‘ closes the form and returns focus to the SyncToy main form.
Examination of the folders shows that only Folder1, FolderA and both files
File1 and File2 were created in the destination; empty folders Folder2 and
FolderB were not created.
[SyncDest]
|
|---- Folder1
|
|---- FolderA
|
|---- File1
|---- File2
Process: Run SyncToy Action ‘Synchronise’ – no changes
------------------------------------------------------------------
The results form reports that there are no changes to synchronise and the
action is complete. Clicking ‘Close’ closes the form and returns focus to
the SyncToy main form.
Process: Run SyncToy Action ‘Synchronise’ – file/folder changes
--------------------------------------------------------------------------
File1 and File2 moved to FolderB
File2 renamed to FileB
[SyncSource]
|
|---- Folder1
| |
| |---- FolderA
| |
| |---- FolderB
| |
| |---- File1
| |---- FileB
|
|-- Folder2
An information dialog is generated. The Run Results table shows no
operations (note: this does not mean it shows 0 operations but rather the
text is missing)
The status text immediately above the progress bar indicates a Renaming
operation was or is currently running.
The dialog takes and maintains focus within the application. The title of
the dialog is ‘SyncToy’; the image is the information bubble; the body of
text is ‘Exception during run: Requested registry access is not allowed.’ and
there is only one button ‘OK’.
Clicking ’OK‘ closes the form and returns focus to the SyncToy main form.
Examination of the folders shows that files File1 and File2 were synchonised
and the file rename was successful. Empty folder Folder2 was not created.
[SyncDest]
|
|---- Folder1
| |
| |---- FolderA
| |
| |---- FolderB
| |
| |---- File1
| |---- FileB
|
|-- Folder2
Process: Run SyncToy Action ‘Synchronise’ – file/folder changes
--------------------------------------------------------------------------
FolderB and the files it contained were deleted
[SyncSource]
|
|---- Folder1
| |
| |---- FolderA
|
|-- Folder2
An information dialog is generated. The Run Results table shows no
operations (note: this does not mean it shows 0 operations but rather the
text is missing)
The status text immediately above the progress bar indicates a Deleting
operation was or is currently running.
The dialog takes and maintains focus within the application. The title of
the dialog is ‘SyncToy’; the image is the information bubble; the body of
text is ‘Exception during run: Requested registry access is not allowed.’ and
there is only one button ‘OK’.
Clicking ’OK‘ closes the form and returns focus to the SyncToy main form.
Examination of the folders shows that files File1 and File2 were deleted but
FolderB was not deleted. Empty folder Folder2 was not created.
[SyncDest]
|
|---- Folder1
| |
| |---- FolderA
| |
| |---- FolderB
|
|-- Folder2
---------------------------------------------------------------------