There are many advantages and disadvantages of using hosted team collaboration services like Visual Studio Online, Git and Subversion compared with the Unity Asset Server. In some situations, standing up a self-hosted source control repository is a good choice.
Unity Asset Server is only available with a Team License holder.
The following are the steps required to create a Unity Asset Server on the Azure. Assuming an Azure subscription is already in place, the first step is to provision a new virtual machine. As we do not require any additional features, a quick create will suffice:
The setup is very simple. A DNS name that has not been currently registered is required and some information about what type of VM. For my purposes I went with the most inexpensive option with the idea that I could scale up as required (an advantage of using Azure to host the VM). The user name and password specified here is primarily for remote desktop access to the VM.
Once the server has been fully created, connect to the server from the virtual machine dashboard:
Once a connection has been made then install Unity Asset Server. Before this can be done though the .Net Framework version needs to be updated to include 3.5. The first step is to start the Server Manager dashboard (at the bottom of the screen):
The next step is to enable a new feature:
The wizard will take you through several steps. Most notably are selecting the type of feature-based installation:
The particular server needs to be selected:
Finally the framework needs to be selected:
Once this is complete, then the Asset Server can be installed. The easiest way is to download the package via the Unity Collaboration page. The setup is uneventful except for an Asset Server Admin password is required. This password will be used to create projects and users on the Asset Server from the Unity IDE.
The Asset Server should then start and should display that it is running successfully:
Now for connectivity to the server remotely. Back in the Azure Management Portal, the accessible endpoints are listed on the endpoints section of the VM:
Click ADD to launch the endpoint wizard. As this is for a single VM, select the Add a stand-alone endpoint option:
On the next page the details of the endpoint are specified:
Great. We are done! The simplest way to verify the server is listening and available is to use a simple test test. I used paging as it is free and simple:
From here, there are many posts about how to setup the Asset Server including: