You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi I work in University College London, Research Data Services.
We are recommending cyberduck as a GUI based client for our new iRODS system.
We had a user that ran into difficulty on an institutional machine running Windows 7 Enterprise
double clicking the file.cyberduckprofile file that we customized didn't appear to do anything for the user.
I can see that on my own machine inside %APPDATA%\Roaming\Cyberduck
It creates a Profiles folder and copies the profile file into it.
Our user had a different setup where %APPDATA% was on a network drive accessed through Active Directory
%APPDATA% resolved to \ad.ucl.ac.uk\home<username>\AppData\
no Profiles folder was created in this case. I don't actually know if this difference was the cause of the issue though.
By manually copying the profile file over to the \ad.ucl.ac.uk\home<username>\AppData\Roaming\Cyberduck\Profiles directory from his computer, we were able to get cyberduck to accept the irods profile that we created.
Perhaps this occurs due to a false assumption made about the nature of the directory path that must be copied to when a profile is installed?
If you have some questions, I might be able to feed them through to our user.
Many thanks and thanks for making a great product!
Alastair
The text was updated successfully, but these errors were encountered:
Hi I work in University College London, Research Data Services.
We are recommending cyberduck as a GUI based client for our new iRODS system.
We had a user that ran into difficulty on an institutional machine running Windows 7 Enterprise
double clicking the file.cyberduckprofile file that we customized didn't appear to do anything for the user.
I can see that on my own machine inside %APPDATA%\Roaming\Cyberduck
It creates a Profiles folder and copies the profile file into it.
Our user had a different setup where %APPDATA% was on a network drive accessed through Active Directory
%APPDATA% resolved to \ad.ucl.ac.uk\home<username>\AppData\
no Profiles folder was created in this case. I don't actually know if this difference was the cause of the issue though.
By manually copying the profile file over to the \ad.ucl.ac.uk\home<username>\AppData\Roaming\Cyberduck\Profiles directory from his computer, we were able to get cyberduck to accept the irods profile that we created.
Perhaps this occurs due to a false assumption made about the nature of the directory path that must be copied to when a profile is installed?
If you have some questions, I might be able to feed them through to our user.
Many thanks and thanks for making a great product!
Alastair
The text was updated successfully, but these errors were encountered: