Consider the KB29 article in order to troubleshoot possible service start failures. In the case of successful installation this service should be correctly installed and started.
VisualSVN Server setups the Windows service co-called "VisualSVN Server" that is used to run your Subversion server. Later you can enable Integrated Windows Authentication method in the VisualSVN Server Manager. It's recommended to use Windows authentication. Subversion authentication relies on the internal users list maintained by VisualSVN Server while Windows authentication relies on Active Directory credentials. VisualSVN Server supports Subversion and Windows authentication schemas. It's recommended to keep this option unchanged. VisualSVN Server supports secure connection over the HTTPS protocol. Later you can bind VisualSVN Server to specific network interface in the VisualSVN Server Manager. Switch to an alternative value if the default port is already occupied by other services such as IIS. This option specifies the TCP/IP port that will be used by VisualSVN Server. Consider the KB22 article if you're going to store your repositories on a network share. Later you can adjust this option in the VisualSVN Server Manager. To prevent possible installation failures, it's recommended to leave this option with the default value. This option specifies the folder where repositories will be stored.
Consider permissions required to run VisualSVN Server (KB37) if you are going to install VisualSVN Server into a non-default folder. This option specifies the folder to which VisualSVN Server will be installed. On the initial server configuration screen you are requested to choose the following VisualSVN Server options:
To get started with VisualSVN Server you are requested to download the installation package, run the installer and follow the installation wizard steps. For further details please consider VisualSVN Server licensing policy. The only difference between Standard and Enterprise editions is that the latter provides enterprise-grade features such as Integrated Windows Authentication and Remote Server Administration. The installer setups Standard Edition and you can later convert it to the Enterprise one. There is the same installation package for both Standard and Enterprise editions of VisualSVN Server. This getting started guide briefly describes the VisualSVN Server installation and initial configuration with the respect to Active Directory domain environment. So you're requested to grant access to selected users while keeping others from accessing confidential data in your repositories. Access is permitted for all Windows users when VisualSVN Server is initially installed. Consider best repository layout practices and organize your projects with respect to repositories hierarchies.
There are no of pre-installed Subversion repositories. It's recommended to enable Integrated Windows Authentication and allow users to access VisualSVN Server without being prompted for username and password. By default, VisualSVN Server uses Basic authentication method. Enable Integrated Windows Authentication.It's recommended to equip the server with SSL certificate that is signed by a trusted Certificate Authority. During the initial setup VisualSVN Server generates a self-signed SSL certificate that is not trusted by Subversion clients and web browsers. VisualSVN Server is distributed as an all-in-one standard Windows Installer package and the installation process is easy and painless: a ready-to-go server can be quickly installed in a Next-Next-Finish manner.īut to make VisualSVN Server perfectly fit your Windows environment, it's recommended to perform the following additional configuration steps: