It's not necessary to install Visual Studio 2012. Just copy the files in the following folder from a computer with VS2012 installed to your build server and it should work:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\WebApplications\
Login to SQL server through Management Studio and run this:
The output will likely reflect the old hostname of the server. If so, run this script, and restart the service.
exec sp_dropserver '<oldhostname>\instance'
exec sp_addserver '<newhostname>\instance' , local
Once the service is restarted, open a new query and ...
Removed the following keys from the registry and it fixed the problem.
I don't know exactly what you mean by "Self Service" but if you're looking for the Self-Service Portal that used to come with System Center Virtual Machine Manager, it has been split into a separate product called System Center App Controller.
There is not (and never was) self-service functionality built into the tools that ship with Windows Server itself (...
Git is a case sensitive version control system. Thus, it allows you to commit files and folders that differ only in case. This is perfectly legal and something that Azure DevOps and Team Foundation Server (and, really, every Git hosting provider) have to allow and support.
You can see this by running git ls-tree HEAD in your repository. It will show ...
A - This is the root node, which is also referred to as "$/" So, the path you have in the picture (A\B\C) would be $/CustomerTools/Database
Prior to TFS 2010, the root folder resides at TFS server level, so $/ is techncally the server root folder. TFS 2010 introduced a new concept named a Team Project Collection (TPC), and so in later versions $/ ...
First, if you haven't already, check out Microsoft's free hosted TFS solution. That's probably the simplest way to go.
If you still want to deploy TFS locally, you certainly can. If you have access to TFS (via a MSDN subscription, for example), it should just be a matter of downloading and running the installer. Verify that you're on a supported OS (Vista, ...
This sounds like a problem with your SQL Server topology.
It sounds like maybe you have Database Engine, Analysis services and client tools all on the SQL Server, but none of those features on the TFS server? If that's true, then you need to run the SQL Server setup on the TFS server (DEVSERVER) and install SQL Client tools on the TFS application tier, as ...
Looks like TFS 2010 isn't even supported on Windows Server 2012: http://msdn.microsoft.com/en-us/library/dd578592(v=vs.100).aspx.
Anyway, an in-place OS upgrade on a server hosting SQL Server and TFS is something I'd really prefer to avoid.
Make sure you have disabled the Firewall.
Also, disable Loopbackcheck on the TFS Server:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ...
You should move to Windows Server 2016 in case you are interested in:
Discrete Device Assignment
When you would upgrade to Windows Server 2016 I recommend the one way that always works which is a clean installation.
in the Visual Studio Command Prompt type
tf workspace /newname:YourNewWorkspaceName YourActualWorkspaceName /noprompt
(alternatively you can use the standard cmd line but then you need to locate tf.exe)
There is a process for moving TFS: it isn't just about backup & restore of the database. It is documented on MSDN Moving Team Foundation Server.
You would be better to:
Create new TFS installation on the server. Do not create any project collections.
On the PC detach each project collection.
On the PC backup each of the now disconnected project ...
Read the TFS documentation. Seriously.
You need to create a project, then give users rights in the project. This can be done within visual studio. Oncea developer is a developer for a project, he can also access it.
This is basics for TFS (only the start, it gets a lot more complicated after), so if you had no idea how rights management works, you are in ...
I'm very sorry that we made a mistake in the MSDN documentation here. The correct list of supported operating systems is on this page and it doesn't include Windows Server 2003. We will fix the mistaken page in the next two weeks.
Once again, I'm sorry for the mistake here, as I realize you'll have spent time on it.
If you delete a user account three things happen.
The account is deleted. More importantly, the SID of the user account gets deleted.
The account's SID reference is removed from all security groups.
The account's SID reference in any resource permissions becomes an orphan.
If you recreate a user account with the same name it will have a different SID. That ...
Actually you shouldn't need to do anything. As long as the computer accounts still exist in AD, the servers should initiate a machine account password change when they boot up. The machine account password change is initiated by the client, not the domain controller.
If for some reason you have problems (error messages regarding the trust relationship), you ...
First thing to check on your client that the fqdn is in the Trusted Sites zone, and the Trusted Sites zone is configured to "Automatic logon with current username and password".
I would also be inclined to create an SPN for the url if it does not exist:
You can show the spn's like this:
setspn.exe -L tfsserver.domain....
do a redirect from the root of the site to /tfs. You can do this in IIS pretty easily. If a user hits it on http://tfs.company.com/ , their browser will redirect to the sub application /tfs without having to do anything. Remember to use SSL on the internets :) if this is going to be a public web site. If it's internal, no worries. Good luck!
Account names ending in a $ are normally machine accounts, not user (even non-iterative user) accounts.
It is quite possible that TFS, or something that TFS uses, assumes this and thus blocks the name.
(Otherwise, be very sure you have correctly typed the password. I've ended up using copy and paste for both account creation and its use to allow a long and ...
It pretty much tells you what you have to do:
You must grant access for the Web application in the Team Foundation Administration Console
The Search Service is simply a search indexer and provider and has nothing to do with TFS.
Here is the relevant page on MSDN for how to grant access to the Web app:
You need to set permissions on SQL Server Reporting separately from TFS itself.
TFS, Reporting Services and SharePoint all have independent permissions. The group "Project Collection Administrators" is internal to TFS and thus only gives access to the TFS functions, not the functions it uses on other servers.
The recommended approach is to create groups in ...
Question: Is there anything about what I've said that indicates there would be a problem with using Hyper-V?
Are there any potential incompatibilities that are likely to arise with this configuration or is this an ideal environment for Hyper-V?
You haven't given any meaningful details, but VMM, Server 2012, TFS, and Hyper-V are all Microsoft products ...
The OS doesn't care and you shouldn't either. The OS isn't under memory pressure, it has 500MB free. So it doesn't care how memory is used at all.
The only thing it could do is invest CPU to reclaiming memory. But then one of two things would happen:
That memory wouldn't be used anyway. This would make the effort of making it free a total waste. And this ...
First of all I would strongly recommend that you fully virtualise this setup, given it's 100% MS I'd stick with Hyper-V on Server 2012 - it's increasingly mature and it sounds like you'll have the skills to implement it.
Obviously we don't know exactly which version of Server 2012 you have or want but they vary the number of guest OS licences they come with....