We're going to upgrade our TFS 2012 to TFS 2013 in the coming month - which also means we're going to update our SQL Server 2008 R2 cluster to 2012.
Furthermore - our TFS is currently hosted in a different domain from our company default domain and we want to change that to our company default domain so it can just run under our 'normal' domain controller.
So that gives us 2 possible paths for the upgrade:
In place upgrade - then migrate to the new domain
Set up a whole new environment in the new domain, and then move the old TFS to the new. This seems to be kind-of a backup-restore
operation.
My question is: what's the recommended way - what would cause the least pain?
I suggest you to access your Windows Server and launch Server Manager dashboard and select your Role and Features.
On your domain controller you have possibility to attach specific domain to your target domain.
Related
We have two domains on our network : domain A and domain B with a trust between them. We created AuereDevops 2019 update 1.1 server as on premise in domain A and want users from Domain B to access and use this AzureDevops. Since this AzureDevops server was set to work via port 80 (not 8080), we opened access in Domain A to port 80, and also port 443 of this server (although we defined to use http not https).
Following, we can connect via web access from Domain B to the server in Domain A, but cannot do so from team explorer in visual studio, from a computer in domain A. The team explorer within Visual Studio shows only the name of the server in domain B but no siblings within it (i.e. no team projects to connect).
Another cross domain issue occurs when assigning Work Item to a user in domain A - no email is received to notify about it. Only when explicitly sending mail from the work item windows, the email is received.
Can u pls advise how to overcome this problem ? Thank u
We found where the root of the problem is and fixed it as follows.
The reason why couldn't connect from visual studio in domain A to AzureDevOps server in domain B, was because visual studio does not support suffix ".domainB" for the tfs server. We defined a DNS mapping for the server in domain A, and this resolved the issue. Now connection from VSTS is done by directly providing the server name of Domain B.
No matter what I do Visual Studio 2017 maintains an HTTP connection to TFS. Our TFS server was recently moved to an SSL/HTTPS connection. If I disconnect my connection and reconnect to:
https://tfs.myorg.com:443/tfs
The connection becomes:
http://tfs.myorg.com:8080/tfs
NO MATTER WHAT I DO, NOTHING CHANGES THIS URL. I even tried using the IP address of the server. It still shows up as 8080.
Further Information:
I discovered that both URL's are still active until every developer is migrated over to SSL. I apparently cannot migrate until the HTTP connection is removed maybe?
You could change the setting in IIS, select the TFS under Sites, then Application Settings, setting name sslOnly . If the value is false changed to ture.
Now your team can only access the TFS portal from inside and outside using https only. This means that VS can also connect to TFS via https only.
More details please take a look at this link which describing the redirect behavior from the URL.
If above still not work, try to clear TFS and VS cache and test again.
Hope you guys can give me a clue.
I recently got onto this web developer role and the former person left the company long ago. I'm completely a newbie on MVC or .net development. My knowledge area would be: html, css, java, jsp, php and etc.
There is a web form I need to redesign and I have watched video on Lynda.com:
Running with ASP.NET
ASP.NET MVC 5 Essential Training
c#
Long story short, the production development environment is set as:
use Visual Studio 2013 to develop, then check in and build.
logon to Octopus Deploy to deploy to Production or Staging
dev-portal(on the left) is the live production source code available on the VS 2013 on the local machine, this is set up by a genius guy I couldn't reach; 4.2.11_9(on the right) is the staging site I set up on the RD testing server.
I know I need to edit controller and model and view pages to modify the page, however the folders that on the server (we host these pages on our own server) is missing quite a bit. I have no idea where are those folder are hidding.
And also text strings are stored in Resources\Resources.resx
Can anyone give me a clue? This is far more complex for me to figure out, comparing to the video scenario demo on the Lynda.com example.
Many thanks!!!
Edit the code using Visual Studio and test on your local machine.
Check your code into TFS. Confirm that a server build has occurred or schedule a new build.
Log into Octopus Deploy and confirm a new release was recently created.
Deploy your release to staging. Confirm the changes. Then deploy to Prod.
I am using a virtual server hosted anywhere (the virtual machine has Windows Server 2012 Datacenter R2 installed), but is not an domain controller. Now I installed Team Foundation Server 2015 RC (it's the release candidate but I think I will get similar problems with other versions) and the URL's are populated using the machine Name.
For example if my domain is abc.de, and my hostname is vmd12345, then the populated urls are something like this:
http://vmd12345:8080/tfs
Accessing repositories from visual studio is not a problem, but when I do some actions (for example view build logs), the web application tries to request vmd12345, what in fact is not accessible outside of the server. I tried to change the urls using the change url button in the TFS admin console, but if I do the system ask for a username and password and I do not know which user account is required.
Trying to change the URL's using the admin console failed cause the system has asked by to enter the credentials (I guess the credentials of the configured service user is ment), but the credentials did not work.
Further investigations shows that this is caused by an IIS problem of the webpage the TFS deploys into the IIS. If I connect at localhost, the credentials of the user were accepted, using the domain name the credentials was not accepted. Any Idea of what the problem can be?
You need to open the administration console on the TFS server and on the "Application Tier" node click "change URL". At the public up only...
I have a question regarding Visual Studio 2010 publish feature which is used after you create a website (MVC framework) to push your dev changes to the live site.
I've never worked with MVC until a few weeks ago and
I've noticed that before pushing the website code I have to change everywhere where I have localhost in the code and replace it with the domain name I'm pushing to. Then if I want to debug anything on my local machine I have to revert everything back to localhost from domain name.
Q: Is there a way to not do this back and front url changing?
Basically I think it boils down to needing a software package or sth that knows to deploy the website with production configuration.
Maybe have a local branch and a live branch? This involves merging files all the time.
Thanks :)
I am not sure it works with MVC, but one approach we use for web services development is to use the web.config transformations.
This means that the normal development stuff is in Web.config and we have separate configurations depending on the deployment environment Web.staging.config and Web.production.config.