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).
Related
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.
I have a Team Foundation Server 2013 installed on a server on a domain. I can connect to this server from my domain account using VS 2012.
I also have a virtual machine which runs on Windows XP and NOT part of the domain (login as a local user). I have a VB6 project running on this VM and I want to connect to the TFS to share and control my VB6 code but I keep on getting The Request Failed with HTTP status 404: Not found.
I tried creating a local user on the server with the same name as the user I use for VM but it didn't work. I cannot join the VM to the domain as well.
Hope someone has tackled this and shed me some light.
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.
I have been able to install 'VS2008 SP1' and 'VS2008 Tools for Silverlight' on my Windows Server 2008 development machine, but I have not been able to install the MSI for 'Silverlight Toolkit July 2009'. The install fails with the following:
"The system administrator has set policies to prevent this installation"
I am a local admin on the box. I have seen something similar when try to to 32-bit MSI on a 64-bit machine. Is that the problem that I am having?
I don't think that you need to install the SL toolkit on the server. At least, we haven't had to. We're using 64-bit Windows Server 2003, and any required Silverlight DLLs, etc., just get included in our .xap file, and get downloaded by the client when it downloads that file. All the server knows is that it's got to pass the .xap file down to a client when it requests it. The only thing that any server-side process might need to know about is the System.ServiceModel.PollingDuplex.dll (if you're using duplex WCF services), but if you simply install the SL 3.0 SDK on your dev machine, and then reference that DLL from your WCF project, it'll get included with your WCF project when you roll it out to the server in question.
The only reason you'd need to install those things on the server is if you're planning to do development on the server, which I suppose you might want to, but certainly isn't normal :-).