Hello Sam,
We currently run VisualSVN server professional version, users are
> planned for migration to a new domain and would involve user SID change.
> Kindly advice on the standard operating procedure for VisualSVN user
> migration.
>
First of all, there should be SID history for your accounts. It should help
you to retain the same access permissions for all existing Active Directory
resources while the migration is still in process.
VisualSVN Server 3.4 and newer provides a number of PowerShell cmdlets for
server and repositories administration. Cmdlets to manage access rules are
among them and they should help you to automate the task of migrating
access rules to new accounts. The cmdlets that you may find helpful are
`Add-SvnAccessRule`, `Get-SvnAccessRule`, `Select-SvnAccessRule`,
`Set-SvnAccessRule` and `Remove-SvnAccessRule`. For more information about
the PowerShell cmdlets, please read the article KB88: VisualSVN Server
PowerShell Cmdlet Reference <https://www.visualsvn.com/support/topic/00088/>
.
--
With best regards,
Pavel Lyalyakin
VisualSVN Team
--
You received this message because you are subscribed to the Google Groups
"VisualSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to visualsvn+unsubscr...@googlegroups.com.
To post to this group, send email to visualsvn@googlegroups.com.
Visit this group at https://groups.google.com/group/visualsvn.
For more options, visit https://groups.google.com/d/optout.
