I would like to create a server infrastructure for SharePoint Server 2013. We would like to buy 2 servers, which the first one will be a domain controller and on the second there will be a SharePoint Server. Now I am thinking about Windows Server version to buy. I would like to buy Windows Server 2012 Standard R2, which will be installed on a domain controller server. On the SharePoint server I am planning to install Windows Server 2012 Essentials R2.
We will have about 100 CAL licences on AD.
The question is if it will work with Essentials server.
Thank you for you answers.
Please look at the Microsoft SharePoint Requirements page -> https://technet.microsoft.com/en-us/library/cc262485.aspx
In general it will work. The problem is the CAL number. With Essentials you can only have a max number of 75 CALs.
Here is also a good article about that topic: http://www.sbsfaq.com/?p=3617
This new Windows Server 2012 Essentials however is different again – it’s designed with a limit of 25 users. After that you need to
break it out into the normal Windows Server products with the normal
Windows Server CALs.
Related
I want to know the features and limitations of TFS express 2013. Such as Check in and check out options, how many users can be configured and regarding sql server versions it supports and so on.
I found this:
What's missing in TFS Express?
The Express edition is essentially the same TFS as you get when you
install the TFS Basic wizard except that the install is trimmed down
and streamlined to make it incredibly fast and easy. In addition to
the normal TFS Basic install limitations (no Sharepoint integration,
no reporting), TFS Express:
Is limited to no more than 5 named users.
Only supports SQL Server Express Edition (which we’ll install for you, if you don’t have it)
Can only be installed on a single server (no multi-server configurations)
Excludes the TFS Proxy and the new Preemptive analytics add-on.
And also no backlog board or task board...
I see the Backup tab is also missing...?
Backup is included in express version
Do we know whether CodeLens works with TFS Express?
CodeLens works with TFS Express.
https://lajak.wordpress.com/2013/01/09/tfs-2012-versions-of-team-foundation-server/
Team Foundation Server Express
TFS Express is a free limited version of Team Foundation Server. It is
great for small teams of up to 5 five users. TFS Express can be
downloaded from the MSDN website and it is around 500MB. Here is a
direct link to the TFS Express home page.
Pro’s
Free
Data stays inside your network
Comes with version control repository
Work item tracking
Build Automation
You have more control compared to the TFS Service
Can customize Process and Workitems template
CAL’s can be purchased in case your team grows beyond 5 users
Support for express versions of Visual Studio
Con’s
Must have own hardware or virtual machine
Not accessible from anywhere
Supports Basic installation only
Limited Agile Project management features and tools
No Reporting Integration
No SharePoint Integration
Supports only SQL Server Express Edition
Installed on one machine. Can’t scale out
Doesn’t support TFS Proxy
Excludes Preemptive analytics add-on
Need to manage your own database backups and downtimes in case of hardware failure
Buy license for the Operating System and CALs if required
social.msdn.microsoft.com/Forums/vstudio/en-US/8f99b8b8-4406-4fb4-b326-4cff50683b8c/tfs-2012-free-vs-commercial?forum=tfsversioncontrol
In addition, there are some other limitations for TFS express.
Only supports SQL server Express edition.
Can only be installed on a single server.
You can get more information form Brian Harry's blog TFS Express (blogs.msdn.com/b/bharry/archive/2012/02/23/coming-soon-tfs-express.aspx)
I am currently working on a TFS 2008 to 2012 upgrade. Here is my situation: my current TFS 2008 box is Server 2K3 with SQL Server 2005 backend. I am not entirely sure what my upgrade paths are but I think the following 2 scenarios are the most likely:
Migrate the databases from SQL 2005 to SQL 2012 and then point TFS 2008 at the new SQL Server. From there I can upgrade TFS 2008 to 2012.
Spin up a new Server 2008R2 box and do a clean install of TFS 2012 with a SQL Server 2012 backend.
The network guys would really like me to do option 2 because they want to decommission the Server 2003 box but my concern is how would I get all of the data in TFS 2008 over to the TFS 2012 instance? I have looked around the MSDN and Google but I haven't come across any documents that explain how to do this kind of upgrade.
Additionally are there any pitfalls that I should be on the look out for?
Any help would be greatly appreciated!
The Microsoft Documentation doesn't make this abundantly clear so for anyone in the future that is in a similar situation this is a great little how to. Some of the screens vary to what you actually see but it is mostly spot on.
Some points
If you spread your Data and Application Tier across multiple servers make sure the user account you specify for 'Report Reader Account' has access to both servers and has the 'Log on locally' permission.
Pitfall: After getting TFS 2012 configured I was getting a strange URL exception when VS2012 attempted to connect to the imported project collection but not when trying to connect to a project collection created from within 2012. A server bounce corrected this problem.
All and all the process is very straightforward and TFS2012 stands up pretty quickly.
There is great documentation on MSDN: http://msdn.microsoft.com/en-us/library/ms404860(v=vs.100).aspx
Here is the antenced of my story
I've got a problem with the VS or IIS. I don't know.
When in the Visual Studio 2010 I try to create website: throw up the follow errormessage:
Unable to create the Wet site'http://www.ecommerce.com'. The Web server does not appear to have FrontPage Server Extensions installe.
I download the Frontpage extension from here: http://www.iis.net/community/default.aspx?tabid=34&g=6&i=1630
Then I read how can it install, but when the article write that:
To extend a Web site using HTML Administration pages on Windows, use the following steps:
Click Start, point to Programs, point to Administrative Tools, and then click Microsoft SharePoint Administrator to open the Server Administration page.
In the list of virtual servers, click Extend next to the virtual server you want to extend.
In the Administrator box, type the user name for the administrator of the virtual server.
Click Submit.
I don't find Microsoft SharePoint Administrator on my Windows 7 Profesionnal 64 bit
or
You can extend a Web site by using the command-line tools, owsadm or owsrmadm. These tools are located in the "%ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\50\bin" folder. To extend a Web site, use the install operation, which takes the following parameters.
I don't find the Web Server Extennsions dir on my Windows 7 Profesionnal 64 bit
I have read another article where write that, Use the Visual Studio DVD go to WCU dir and into the Web Server ... dir, but I don't find...
I download the FPSE and install with my local Administration account.
But the Visaul Studio Always says: The WEb server does not appear to haver FPSE installed.
How can I fix it? Install it?
Bad news (may not be so bad): FPSE for IIS 7 and 7.5 are not supported. Alternative is to use WebDav and here's an article explaining how to migrate FPSE Sites to WebDAV.
Good News (may not be so good due to licensing part): As of December 18, 2010, Ready-to-Run Software Inc. has created Microsoft FrontPage Server Extensions (FPSE) 2002 for IIS 7 and 7.5.
See this announcement from MS: FrontPage 2002 Server Extensions for IIS 7.0 on Windows Server 2008 and Windows Vista
If the FrontPage Server Extensions are installed, this error may occur because the _vti_bin virtual directory is not marked executable. To correct this problem, run the Internet Service Manager, select the Web server having the problem, and use the Check Server Extensions task. Reference: http://msdn.microsoft.com/en-us/library/aa984224%28v=vs.71%29.aspx
Is the Windows 7 Home Premium sufficient for software development?
Development would be in Visual Studio 2010.
I'm on a budget so would rather purchase 'Home Premium' rather than 'Professional' or 'Ultimate'.
The Microsoft site says there is next to nothing functionality wise between them that developers would miss. Can anyone confirm or deny?
BTW. Does it come with a version of IIS?
I realize that this is not a technical question. But it is important to me and I'm sure other developers wonder the same thing.
Cheers,
-- Lee
Yes. I write software using VS 2010 in WIndows 7 Home Premium without any trouble.
Basically, yes, it's totally sufficient.
A big upside to professional edition, though, is that it comes with Windows XP mode, essentially a virtual machine with a built-in XP installation (and included license). That can come in handy if you do web development (test things in IE6/7) or need to test applications in the old XP GUI.
Windows XP mode can also be a lifesaver if you need to run older applications that won't run properly in 7. I personally would consider choosing the Professional Edition for that reason.
Don't purchase either, instead buy a MAPS subscription from them. In the UK these cost £199 p.a. (I imagine less in the states) for which you get virtually everything you're likely to need except Visual Studio. Currently you get
10 licences for MS Office 2007
10 for Project
10 for Visio
10 for Outlook
10 for Mappoint (North America only)
1 for Office Communications Server plus 10 CALS
10 for Windows 7 Professional
1 for Windows 7 Ultimate
1 for Windows Server 2008 R2, plus 10 Server CALS and 10 Terminal Server CALS
1 for Windows Web Server 2008 R2
1 for Windows Home Server 2008 R2
1 for Windows Business Server
1 for Windows Exchange server plus 10 CALS
1 for Windows Office Sharepoint, plus 10 CALS
1 for WIndows SQL Server standard plus 10 CALS
Plus a bunchload of other odds and sods servers and products of lesser interest.
MAPS is such good value - and I'm by no means a Microsoft fan - that purchase is pretty much a no-brainer for any software developer who runs Windows in any form.
UPDATE: Since I wrote this Microsoft now offer a Developer version of MAPS which replaces some of the more esoteric servers with Visual Studio. You still get the Office, Windows and SQL Server licences, which makes it just about perfect for any developer.
What you won't find on the Microsoft site, but on Wikipedia, is a nice Comparison Chart.
Compared to Professional, the Home Premium edition lacks:
support for more than 16 GB of memory: start worrying about that in a few years' time
network support in the Backup and Restore Center: not a problem if you handle your own backups
Remote Desktop server: not a problem if you develop only locally
some advanced disk management stuff: not a problem
features for a company network environment: not a problem
Windows XP mode: handy if you want to test on XP, but can be replaced by e.g. VMWare running an XP installation
Multilingual User Interface support: handy if you want to develop and test multilingual desktop applications
In conclusion: Professional may have some additional value if you develop Windows desktop applications for a diverse audience. If not, go for Home Premium.
Since you specifically asked:
Installing IIS 7.5 on Windows 7 Home Premium, Home Basic, or Home Starter (TechNet)
I guess in the past there were issues with developing for IIS on XP Home, but it looks like you can install IIS 7.5 on ANY version of Windows 7, including Starter, which I am surprised to see. I thought Starter was short of being useless for developers.
I agree with Pekka about XP Mode in Pro and Ultimate coming in handy if you need it. Sounds like Brian is already doing it and its working fine (I'm on Vista Ultimate until next week).
Yes. The OS you use really has little to do with development, unless you're targetting something specific to a version or edition of Windows (rare).
What are the best practices in setting up a new instance of TFS 2008 Workgroup edition?
Specifically, the constraints are as follows:
Must install on an existing Windows Server 2008 64 bit
TFS application layer is 32 bit only
Should I install SQL Server 2008, Sharepoint and the app layer in a virtual instance of Windows Server 2008 or 2003(I am already running Hyper-V) or split the layers with a database on the host OS and the app layer in a virtual machine?
Edit: Apparently, splitting the layers is not recommended
This is my recipe for installing TFS 2008 SP1.
There is no domain controller in this scenario, we are only a couple of users. If I was to do it again, I would consider changing our environement to use a active directory domain.
Host Server running Windows Server 2008 with 8GB RAM and quad processor
Fresh install of Windows Server 2008 32bit in a VM under Hyper-V
Install Application Server role with IIS
Install SQL Server 2008 Standard edition
Use a user account for Reporting Services and Analysis Services
Create a slipstreamed image of TFS 2008 with SP1 and install TFS
Install VSTS 2008
Install Team System Explorer
Install VSTS 2008 SP1
Install TFS Web Access Power tool
After installing everything, reports were not generated. Found this forum post that helped resolve the problem.
Open p://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx
Run the webservice (see above link for details), it will take a little while, the tfsWarehouse will be rebuilt
It is very important to do things in order, download the installation guide and follow it to the letter. I forgot to install the Team System Explorer until after installing SP1 and ventured into all sorts of problems. Installing SP1 once more fixed that.
One critical thing you has to keep in mind about TFS, is that it likes to have the machine all to it self. So if you have to create a separate instance on Hyper-V do it using the proven Windows Server 2003 platform with SQL Server 2005.
I am sure Microsoft has done a great job getting it to work under Windows Server 2008 and SQL Server 2008, however you don't get any additional features with this newer install and it is currently unproven in the wild.
So my recommendation is to stick with what is known until the next release of TFS comes out.
Also splitting the layers is definitely not recommended, especially in the workgroup edition where you will only be allowed to have 5 licensed users. Those 5 users will never exceed the server's needs. Also my recommendation is to not update Sharepoint if you don't need to. In my environment, we don't really use Sharepoint all that much, so I left it alone. Sharepoint is usually, in my experience, where most of the problems come from with TFS.
I just upgraded our team to TFS 2008, from TFS 2005. The hardest part was upgrading SharePoint 2.0 to 3.0, so I would make sure to do that first, if you have not already installed TFS 2008. We had a couple of other difficulties, but they were all either related to the SharePoint upgrade, or to the fact that we were using an aftermarket Policy package - Scrum for TeamSystem. We are on SQL Server 2005, so I cannot address SQL Server 2008. As for splitting the layers, we did not do this either, as we are running on Windows Server 2003 and everything ran under the host OS.
Splitting the layers is only needed for more than 450 users.
I would also recommend having the Build Server on a completely seperate machine. Building is very file system intensive. SQL Server performs best when it has complete control of a file system - so having build and TFS on the same machine may create performance issues while builds are executing.
Perhaps this can be alleviated with proper tuning and seperate physical drives - but I'd think in the long run it would be a lot simpler to just either use some old hardware - or spin up a small virtual machine on a seperate host for your builds