Failed to Install Team Foundation Server 2012 using “Standard” Mode Installation

Few weeks ago I started to doodle around with Team Foundation Server 2012 and it surprises a couple of people around who knows that I have already partially retired from the “Developer” role and people thought I would have already moved on to being an IT Professional. Well o well, I believe that it will require an Administrator or IT Professional to administer and provide the insights on how to make that piece of machine running the Team Foundation Server 2012 remaining robust so that the real Developers can just focus on producing excellent program or application! (Totally no offends to the Developers! I don’t mean that you are not qualified to maintain Team Foundation Server 2012! Just trying to offload from you folks so we IT Professional still have a piece of the cake!)

Here it goes…

I met into this problem when I am happily deploying Team Foundation Server 2012 (TFS 2012 in short) on-premises after downloading the ISO from Microsoft site. Happily doodling and clicking next till I get the following error.

If the image is too small or low-resolution, the message that was highlighted is,-

  • SharePoint Foundation 2010 can not be installed on Windows 8.
  • TF400080: Your system does not have the recommended amount of system memory available: 10 GB. While SharePoint 2010 with Team Foundation Server can operate with less than this amount of memory, the performance will be degraded. Upgrade your system memory to at least the recommended minimum for optimal performance.

I stumbled on this error and finally found out that, “Hey! I am running Windows Server 2012, not Windows 8! Why are you flagging out!”. Well-o-well, but as we all know that Windows Server 2012 and Windows 8 have similar binary used so it may explained that. The only thing that help in concluding is that, since TFS 2012 is made so easy that anyone can run it off even on Windows client computer running Windows 7 or Windows 8.

SharePoint Foundation 2010

So why it still flag the error?

Go easy… I quickly did some search online and find the following article. [http://msdn.microsoft.com/en-us/library/vstudio/dd578592.aspx]

It just simply states the following…

Because Team Foundation Server installs SharePoint Foundation 2010 with the standard configuration, you can’t use it on Windows Server 2012. If you want to install Team Foundation Server on Windows Server 2012, use the advanced configuration and skip the installation of SharePoint Foundation 2010.

It just means that, for the folks out there trying to install TFS 2012 on Windows Server 2012, you just have to do the “advanced” configuration instead of the standard configuration that usually beginners like me will go for since it is my first installation and I am just testing out the piece of software.

Prior to this, I also send the above screen capture to my Twitter where I used the #TFS hashtag which caught the response from one of the Microsoft guy (Buck Hodges – @tfsbuck) working on the TFS stuffs. He responded that I would be good with going with the “Advanced” configuration to skip the error as SharePoint Foundation 2010 cannot be installed on Windows Server 2012.

So I go ahead and popped the golden question whether SharePoint Foundation 2013 will be updated into the upcoming (perhaps) roll-out of TFS 2012. He said that it is unlikely. Therefore, I guess for Administrator or Developer, the only option to run TFS 2012 on Window Server 2012 will be to use Advanced Configuration after installing SharePoint Foundation 2013 first.

Memory (RAM) Requirements

So the question is, is it necessary to have 10GB RAM equipped for this? Yes and No, in my opinion.

Yes, because SharePoint consumes lots of memory, so if you are in for a real thing, then equipped your physical server or virtual server with adequate memory!

No, if you are doing testing, I packed mine with 4GB and things are working fine, for now!

 

In my next post, I will be writing the steps that it took for me to configure TFS 2012 with SharePoint Foundation 2013.

Cheers.

Failed to Install Team Foundation Server 2012 using “Standard” Mode Installation

I seems to love with “66”. Welcome ASUS EA-N66 to the family! :)

After the introduction of the ASUS RT-N66U to the family previously here, I am still not satisfied with the speed that I am getting through the HomePlug that I have been using all along. Just for informational sake, I am using AzTech HomePlug through out of my whole house but due to the way electricity cable is being laid, I can’t seems to get anything more than 20Mbps of speed to my lab server situated in my room.

Therefore, as a technology freak, I went ahead to do some slight research and decided that I should be doing something to further boost the ROI for the hard-earned money that I have been paying to my internet service provider monthly. Therefore, I narrowed down to using Repeater or Access Point, however, there are so many brands available in the market! How?!

Was looking at my RT-N66U box, I saw that there is this product that is compatible or somehow in the marketing term that explains it is designed to best work with the following family line of products. So I saw ASUS EA-N66 which fits my needs.

I like the packaging, it is pretty unique even though it is simple.

I like it when the design team focus a lot on telling the customer how they can make use of their product despite having a small area to work with on the creativity portion.

Some simple un-boxing to show the items within the box. Pretty organized and I love the word “VIP”. 🙂 I will be filling in with some network diagram of how I deployed it within my home and how I fully utilize the power and features of these two monsters!

Cheers.

I seems to love with “66”. Welcome ASUS EA-N66 to the family! :)