November 8, 2012 at 23:05Migrating Domain Controller and creating Team Foundation Server on Virtual Machine on Windows Azure
Migrating Domain Controller and creating Team Foundation Server on Virtual Machine on Windows Azure.
(Platform Windows 2012 / 2008R2)
Most small and medium-sized companies use TFS on a server that performs the function of a Domain Controller (DC), sometimes this is due to economic reasons, it is especially popular if programmers are not in the office but work from home or arrive on business trips.
First we need a Windows account, Windows Live ID . Thanks to him, we create an account at http://windowsazure.net - a 90-day free account or by subscription, for example, BizSpark (a subscription for startups).
Let's look at the features of Windows Azure and select the required ones.
These are: virtual machine - to create the DC TFS 2012 server itself, web sites - to publish applications.
We create a virtual machine (VM) based on the Windows 2008R2 / 2012 platform, as shown in the article "Create VM in Azure" . Details of using VM in Azure http://habrahabr.ru/post/150341/ .
Create DC on this virtual machine, article: “Create DC on VM”. It should be noted that creating a DC on the Windows2008R2 platform and Windows2012 is slightly different; to create a DC on Windows2012, you do not need to run the dcpromo command, which is necessary to install DC on the Windows2008R2 platform. If you are migrating an existing DC, you must use standard Windows Server tools to migrate domain services and roles to VMs in Windows Azure.
Details of the migration of Windows 2008R2 between two servers in the IT infrastructure are described on TechNet .
After installing or migrating DC, we need to install SharePoint 2013 for TFS 2012 to work. A detailed description of the installation is described in this article: http://habrahabr.ru/post/153453/ . You will also need MS SQL Server 2012: http://habrahabr.ru/post/153453/.
It should be noted that SharePoint and SQL servers must be in the same virtual network and, accordingly, be in the same domain.
After installing the required components, we begin the installation of TFS from the ISO file previously downloaded from msdn.com.
Run configuration-wizard-tfs.
Select the Advanced item.
We configure all the required server parameters, such as a database, a SharePoint account, and others. Installation details are described in the English article “Installing TFS 2012” .
You can also use a ready-made VHD file (which already includes DC and TFS) and upload it to the VM (see article) , however, this method is not considered in the article.
Check the received server from VisualStudio.
You need to compare the resulting server with the existing Team Foundation Service (TF-Service) http://tfs.visualstudio.com/ . It should be noted that TF-service has several disadvantages, which are as follows:
• The number of process templates is limited. You can use only built-in templates that cannot be customized in an additional way.
• Integration with corporate services such as SharePoint, Project Server, System Centrer, etc. is not supported.
• You can only authenticate using LiveID, a federated script with Active Directory is not yet supported.
• Reporting subsystems are quite limited in their capabilities.
In turn, the created DC TFS 2012 does not have these disadvantages.
(Platform Windows 2012 / 2008R2)
Most small and medium-sized companies use TFS on a server that performs the function of a Domain Controller (DC), sometimes this is due to economic reasons, it is especially popular if programmers are not in the office but work from home or arrive on business trips.
First we need a Windows account, Windows Live ID . Thanks to him, we create an account at http://windowsazure.net - a 90-day free account or by subscription, for example, BizSpark (a subscription for startups).
Let's look at the features of Windows Azure and select the required ones.
These are: virtual machine - to create the DC TFS 2012 server itself, web sites - to publish applications.
We create a virtual machine (VM) based on the Windows 2008R2 / 2012 platform, as shown in the article "Create VM in Azure" . Details of using VM in Azure http://habrahabr.ru/post/150341/ .
Create DC on this virtual machine, article: “Create DC on VM”. It should be noted that creating a DC on the Windows2008R2 platform and Windows2012 is slightly different; to create a DC on Windows2012, you do not need to run the dcpromo command, which is necessary to install DC on the Windows2008R2 platform. If you are migrating an existing DC, you must use standard Windows Server tools to migrate domain services and roles to VMs in Windows Azure.
Details of the migration of Windows 2008R2 between two servers in the IT infrastructure are described on TechNet .
After installing or migrating DC, we need to install SharePoint 2013 for TFS 2012 to work. A detailed description of the installation is described in this article: http://habrahabr.ru/post/153453/ . You will also need MS SQL Server 2012: http://habrahabr.ru/post/153453/.
It should be noted that SharePoint and SQL servers must be in the same virtual network and, accordingly, be in the same domain.
After installing the required components, we begin the installation of TFS from the ISO file previously downloaded from msdn.com.
Run configuration-wizard-tfs.
Select the Advanced item.
We configure all the required server parameters, such as a database, a SharePoint account, and others. Installation details are described in the English article “Installing TFS 2012” .
You can also use a ready-made VHD file (which already includes DC and TFS) and upload it to the VM (see article) , however, this method is not considered in the article.
Check the received server from VisualStudio.
You need to compare the resulting server with the existing Team Foundation Service (TF-Service) http://tfs.visualstudio.com/ . It should be noted that TF-service has several disadvantages, which are as follows:
• The number of process templates is limited. You can use only built-in templates that cannot be customized in an additional way.
• Integration with corporate services such as SharePoint, Project Server, System Centrer, etc. is not supported.
• You can only authenticate using LiveID, a federated script with Active Directory is not yet supported.
• Reporting subsystems are quite limited in their capabilities.
In turn, the created DC TFS 2012 does not have these disadvantages.