We are using OPSHub free version for migrating On-Premises TFS 2013 to cloud (VSO 2015).
During Opshub installation we got an error message "Unable to connect to remote server, check the internet connectivity or Proxy settings and try again".
We found the following link http://www.opshub.com/main/ovsomu-proxy regarding this issue and we contacted our network team to get the proxy server details (to put them in the environment variable _JAVA_OPTIONS), but they would like to know how Opshub connects to internet and all the inbound and outbound connections from Opshub, which port it uses and if the data is encrypted during installation and migration etc. Can Opshub support help us out in providing this information?
OpsHub use the standard VSTS ports of https which is encrypted with SSL. There are no inbound coms.
I would however not recommend the OpsHub tool as you will quickly run into an upsell from them. If it works for you then awesome, but if they as you for money then switch to the TFS Integration Tools that are free and supported by the TFS product team.
Yes, OVSMU requires to connect to the OpsHub website during installation for Verification Code generation process. (Thereafter, it does not connect to our website)
Once, the utility has been installed, it occupies two ports 8989 and 9090 as long as the tool is running. For communication with end points, it uses the default TFS and VSTS ports.
Related
How hard is it to enable TFS to start using secure connections, if its not already? Does doing so affect SQL configuration also? How can we force SSL to be required?
Im looking over this reference material
https://msdn.microsoft.com/en-us/library/aa833872%28v=vs.120%29.aspx#DisAd
Reading the above, I get the impression that MS is trying to discourage someone from using SSL for TFS over the internet?
Then I stumbled on to this blocg post
http://www.jwsecure.com/2009/01/29/using-tfs-via-the-internet/
Summary = just get a ssl cert and force ssl and port-forward a high port to 443
thoughts?
Firstly, the MSDN article you posted above shows you the detailed steps on how to set up HTTPS with SSL for TFS. To summarize main steps include:
Install a certification authority, obtain and install a server certificate for servers.
Request, install and configure websites with a certificate for Team Foundation Server using Internet Information Services (IIS) Manager.
Configure Team Foundation Server to require HTTPS and SSL.
Install the certificate on client computers.
You can also check this walkthrough: https://msdn.microsoft.com/en-us/library/aa833873.aspx
Secondly, you don't need to configure SQL Server. But if you have SQL Reporting Service, you need to configure it to support HTTPS with SSL.
Thirdly, to enable TFS to be available with external connections, you need to configure it with HTTPS with SSL. Also with it, web connections to TFS are more secure. However, these process needs more administrator's configuration & maintenance work. So you need to determine whether to use it based on your requirement.
We have had an automatic Active Directory/Windows password change thrust upon us, and consequently our TFS2008 build server has broken. I have changed the password for the TFSERVICE account it runs under, and updated the Visual Studio Team Foundation Task Scheduler Service to use the correct password, and checked that the underlying Sql Server is running okay. However attempts to connect to TFS are now met with the message '..HTO Status 503: Service unavailable'.
What else needs to be started to get this up and running again?
You need to always change the password using the tools in the box. You can use the TFS Administration Console that you can launch from the start menu. Or you can use the tfsconfig.exe located in the TFS install folder.
This applies to all versions of TFS from 2010 on.
If you have TFS 2008/2005 you will need to use the tfsadminutil command: http://msdn.microsoft.com/en-us/library/bb552178(v=vs.90).aspx
Note: You need to upgrade your TFS server as soon as possible. Both the OS, SQL, and TFS pre-2010 is not well supported.
After DCpromoing and then demoting the server that TFS runs on, we cannot use WSS ("Cannot connect to the configuration database") to manage team projects. I believe that if I could find the default permissions that are set up when TFS is first installed on a server that is joined to a domain - in terms of any service accounts that are created and which accounts various services should run as - I would be able to get it back up and running again. Does anybody know the default NT accounts and permissions for Team Foundation Server?
That error sounds like a SharePoint error. This technet article outlines the permissions (server, SQL, registry) that are required for a default WSS install.
I'm new to Microsoft TFS and it seems like the default of TFS is connect via a Local Area Network (LAN).
Another team member lives in a different part of the world. How can I allow him to connect to my TFS Server, which is installed on a Vista Machine so we can share the same project?
You can either open up port 8080, or install SSL for TFS. You can find more information how to access TFS remotely at http://msdn.microsoft.com/en-us/library/bb668967.aspx. It is an article for TFS 2005, but it still applies.
Simplest is to set up a VPN, let the user log onto your network and then access the TFS server as you would locally. This is the way I do it; saves the hassle and security headaches of trying to expose TFS over the internet.
Can the TFS proxy be installed on Windows XP? I have an environment that I am not allowed to run a Windows Server; however, it is offsite, so a proxy would be very helpful.
It turns out that Microsoft changed both their deployment and pricing models from v1.0 of TFS. The proxy requires Windows Server and costs the same as a new instance of TFS.
It was my understanding that the Microsoft TFS Proxy needed to be installed on a Windows Server OS with IIS also installed on the box. You could of course use a Virtual PC image on your XP machine but I suspect that might go against the same rules that prevent you from running a server on your remote site.
Another alternative is a product called "Remote Accelerator" from Teamprise (who I work for).
http://www.teamprise.com/products/accelerator/
It is designed as a TFS proxy server for single person use, and is designed to work on client OS's such as Windows XP, Vista etc. Also with a price of $99, it is less expensive than the Microsoft TFS proxy (which has a retail licensing price comparable to another full-blown TFS server instance).