I only installed TFS 2013 on the application tier and didn't go through the configuration wizard to upgrade to 2013.2. Do I need to restore any databases if I restore a snapshot of the application tier? (Does just installing new bits of TFS on the app tier affect the data tier?)
No installing the bits does not affect the data tier. You need to configure the application tier to point at the data tier before it will have any effect.
If you already have databases and you are upgrading in place then you can just "configure app tier only".
If you are on new hardware then you need to follow the new hardware workflow to install...
https://msdn.microsoft.com/en-us/library/ms404869.aspx
Related
I am currently building Non Production TFS 2015 environment. I am restoring database including DBs from production to the new QA DB instance. I performed DB restore using TFSRestore.exe. The restore work successfully.
In TFS QA then I install Application Tier and configure to TFS QA and TFS QA service account.
Then I did RemapDBs, Reset Owner, RegisterDB then start the service. Then I change the Notification URL to point to QA TFS Url.
What is strange is that I can see that in Applications Tiers, I can see 2 machine names display. One is TFS Prod machine and TFS QA Machine Name. How I can remove Production TFS machine name under Application Tier section.
I check the checkbox "Filter out machines that have not connected in more than 3 days"
After 3 days the TFS Prod machine is remove from the Application Tier section. Since I want to do inplace upgrade to the next version therefore is it safe to do this?, how do I know this would not impact the TFS Prod?
I did run the
TFSConfig ChangeServerID /SQLInstance:SPTEST\Contoso /DatabaseName:Tfs_Configuration /ProjectCollectionsOnly
as result, it created new hostID (Guid Number) inside TFS_configuration.tbl_ServiceHost. However, when I select a project in Team Foundation Server I receive an error TF31001: Cannot connect to Team Foundation Server at Project1. The server returned the following error. Value cannot be null. Parameter name: service Definition
Resolve this by delete anything under cache folder
c:\users[username]\Appdata\Local\Microsoft\Team Foundation\5.0\Cache
This is similar post
https://social.msdn.microsoft.com/Forums/vstudio/en-US/0ba7caad-4210-4991-b6f0-d4f1dd8c409b/removing-application-tier-server
According to your description, your scenario should be Move or Clone Team Foundation Server from one hardware to another
(Clone option) Reconfigure server IDs and remap databases:
Perform the next set of steps on the new application-tier server if
you intend to continue using the original TFS instance. These steps
are necessary to avoid the risk of corruption of one or both
deployments. If both servers are live, you could end up with
corruption, particularly if they are pointing to the same SharePoint
or reporting resources.
So, please try to Reconfigure server IDs and remap databases. If that still not work, I'm afriad that you have to remove the DB instance and reconfigure the QA envrionment step by step following the instruction mentioned here.
UPDATE:
Seems you just restored an application-tier server but not Move or Clone Team Foundation Server from one hardware to another
For restoring an application-tier server, the name of the old application-tier server remains there is expected (See the end of this article.).
Note: The name of the old application-tier server will still appear in
the list of application-tier servers in the administration console for
Team Foundation. If you select the Filter out machines that have not
connected in more than 3 days check box, the old server will disappear
from the list within three days.
So, to avoid showing the old App Tier machine name you need to follow the steps to Move or Clone Team Foundation Server from one hardware to another as I mentioned in the original answer.
Note: You must install but not configure TFS on the new data-tier
server, and then use the restore function in the Scheduled Backups
node
I am also getting this issue. I followed all the cloning steps to move to my new TFS boxes, and I got it up and running, after running the command TFSConfig ChangeServerID.
But on the new server, under Application Tier > Application Tiers, I see two servers.
The new SQL box, and the old TFS box!
This is on TFS 2017.
I am trying to migrate reports from BOBJ 4.1 SP5 Patch 3 from Development to Production using Upgrade management tool.
However after the upgrade is completed, I see that no security for folders or reports is migrated. Is there anything I need to select or the Upgrade management cannot migrate security.
Best way to "migrate" (publish I said) is Central Management Console > Promotion Management. With this option you can choose whatever you select (folders, access levels, universes, connections...)
Is this what you were looking for?
Best regards
At my company we are currently using TFS 2010 which has installed on-premise and we are developing application on it that it is contiouusly being deployed on Microsoft Azure platform.
Our plan is to upgrade our TFS 2010 to version TFS 2015 and host it on a VM on our Azure subscription since this will ease our continuous deployment speed very much by removing network latency, in addition we will be able to use TFS new features.
Question I have is,
What do we have to do to move all TFS project work items, user stories and source code to successfully finish this move and upgrade process.
Before you give your answers, please take into account that we also want to create a local users on new TFS server and map domain users which they are created on the company's active directory server, on Azure VM and during TFS movement we would like to be able to show moved changesets, workitems... everything have been created in TFS database with the newly created local users on the Azure VM.
Firstly, please have a check on this blog for the details on how to do migration upgrade for TFS: http://blogs.msdn.com/b/tfssetup/archive/2013/12/19/migration-upgrade-from-tfs-2012-to-tfs-2013-with-reporting-and-sharepoint.aspx (This blog is about how to upgrade from TFS2012 to TFS2013, it applies to TFS2010 to TFS2015 as well)
Then after the TFS server is moved/upgraded successfully, create a user on Azure.
In our organization we are using Hyper-V VMs. We are using Progress Database and apps in the workstations.
For us to migrate into the Microsoft Azure cloud, do we have to migrate our existing Progress database to SQL and rewrite our apps ?
No. You haven't given us much detail about your applications or architecture, but if I make the assumption that you are using the embedded database product by Progress software, then I see no reason that can't run on an Azure VM.
There is a WCF service which is running under IIS. This service accesses the files in its folder, it accesses a SQL Server database and it writes messages to the EventLog.
The deployment platform is Windows Server 2008 in some datacenter. I developed the service, but I'm really still a beginner.
The deployment will causes the creation of a new Windows user account and, possibly, a role that is assigned to that user. This is needed to start the service from a separate account with strictly defined rights (as I understand, this approach is recommended, but not to start the service from NT Service account).
Obviously, the deployment needs to run scripts to create database, tables, scheduling of tasks.
What tools could you advice to accomplish such a deployment? Maybe I can use the standard Setup Project? Or some third-party tools such as WiX Toolset? Should I use PowerShell to create windows user account and role?
There is also a question: should I pull the prerequisites, such as .NET framework installer, SQL Server installer?
You can rely on Windows installer using tools like WIX, InstallShield or Advanced Installer. WIX is the only free one albeit it has a higher learner curve. There are other free windows installation software solutions available as well such as NSIS. You can also write your own scripts such as in Powershell to create the IIS virtual directory, application pool and connect to the RDBMS to create the schema. You'll probably also would like to have an undeployment solution so you can uninstall it and upgrade it in the future. The Windows installer based tools almost gives you uninstall for free because it maintains a database of everything that was done during installation sans the custom actions you write such as the database schema setup.
For the user configuration part, some of these tools such as Advanced Installer can create new user accounts. However to define user rights assignment you might have to rely on a custom script using ntrights.exe from the Windows resource kit.
As of my knowledge there is no automated deployment tool available for WCF because its require lots of manual configuration.
But you can try Octopus for .NET applications
http://www.paulstovell.com/octopus/intro