Connect TFS over Citrix - tfs

I have to do synchronization task between multiple instance of TFS. However, the right-hand-side TFServer is inside Citrix.
Can I connect to TFSerer inside Citrix from outside Ctrix?

Only if the TFS server inside Citrix is exposed through some other way (public URL or TFS Web Access Server, VPN connection), I see no way to connect your Local Team Explorer to the TFS server inside Citrix

Related

TFS endpoint services to external web service

I'm using TFS 2015 Update 3 with no internet access.
I'm trying to create a service endpoint for an external web service on the internet. I can add the url with auth but of course it will not work. Can I use endpoint with a proxy (I have a proxy server in my org)?
Thanks.
The proxy of course should be work, the problem for TFS server is no internet access. So you just need to configure the TFS server to access internet via the proxy server.
Reference this article : TFS 2015 behind a proxy

Cannot connect to TFS from Windows XP

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.

Legacy DCOM server on Windows Server 2008 R2

I have a legacy DCOM server and client application both written in Delphi v6. The DCOM server is currently configured to run once and service all clients. The main reason for it running once is that the server provides an interface to an accounts application and must logon and can only do this once for a given user name.
Our customer now wants to upgrade their server to Windows Server 2008 R2 leaving the clients on Windows XP but I have been unable to replicate the current set-up.
The current set up that I can get to work on a test rig is slightly odd!
I have to configure DCOM settings to allow remote launch or I get access denied on the client
If the DCOM server is not already running, when the client tries to connect to it I get server execution failed.
If the server is running and the launch permission is set to allow remote launch, the client starts a new instance of the DCOM server rather than using the instance already started. This then causes problems in the accounts application as the same user tries to logon which is not allowed.
If I close the DCOM server running on the server, the client happily works away with its own instance. I cannot see the DCOM servers main form though as its running in the background (can see it in task manager)
I've found various articles to do with this problem but nothing so far has worked. These include running the DCOM server as administrator, not running the DCOM server as administrator, allowing COM+ in the firewall, adding the DCOM server to the firewall, the DCOM server located in SysWOW64, using the 32 bit version of DCOMCNFG, etc.
Now not sure where to go...
Thanks for any help
Simon
DCOM default permissions has changed in XP SP2 and 2003 SP1. You'll need to configure the properly to make your service running properly. Usually, unless you implement the DCOM server in a service (something Delphi doesn't allow due to limited DCOM support), the DCOM server is started when a user connects, and that's why you may need the "remote launch" permissions.
Moreover a DCOM server may be started in the context of a given user, the interactive user (must be avoided for remote clients!), or the launching user. What mode are you using? - if it is set to "launching user" it will always create a new instance. How was your server instanced before the new OS? How is its class factory implemented?
See here for some interesting information about DCOM and Delphi implementations.
BTW:
Never run your DCOM server with Administrators privileges unless it really needs it. Otherwise you can create a security hole.
If a firewall is present, both the RPC endpoint port and the ports configured for DCOM must be opened to the calling clients.
Don't mess system directories with your application. There's no need, if your app works only there you have a privileges misconfiguration, and you won't solve it properly putting files where they don't belong to.

Default TFS Windows Accounts+Permissions when installed on a Windows Server that is joined to a domain

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.

How do I allow a remote user to access my local TFS server?

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.

Resources