I need advise on what can be best way to setup/configure SHAREPOINT 2010 Environment for 6-members teams (with 3-working at onsite and 2-working at offshore)
Currently I only had two team members but team is now increasing. What we have is DEVELOPMENT SERVER - with Visual Studio and SharePoint Server installed. Developers remote VNC to the box and do their development.
But with number of developers are increasing what should be ideal, so that team can communicate from offshore/onshore
Is this Ideal (installed on each developer laptop)
Visual Studio 2010
and
SharePoint Server (Installed on Windows Server 2008) and developers will use this rather than installing SharePoint locally (enterprise edition is very expensive)
We start to developing with SharePoint 2010 in the team one and half years ago. We try different environment structures for developing, but had many conflicts. Today everyone work in his own environment (HV) with SP enterprise edition, just sharing the code via Team System. The problem is in this set-up the content, everybody has his special content, but if it is critical for you, make backup in every environment.
So we have one SQL server, and for every developer a server with SP and VS.
By the way I think you don't need to purchase SharePoint Server for development environment. If I'm right it is free. You need purchase OS, Sql, VS, but not the SP. Please check with your Microsoft seller.
Related
I can't find this answer anywhere and maybe I'm just not getting it. I am installing TFS 2013.3 and I no matter what wizard I choose, there is no option to configure reporting services.
Environments tried:
Windows 7 Enterprise / MS SQL 2012 Express / TFS 2013.3 Express
Windows 8 Professional / MS SQL 2012 Developer / TFS 2013.3 Standard
I am about to try on a Windows Server 2012 SP1 machine shortly in case it has to be a server level machine. I looked on the MSDN for hardware and software support for both SQL/TFS and the above configurations are ok.
Pre-configuration tasks
SQL server pre-installed
SQL configured with Reporting and Analysis services enabled
User to install and configure both SQL and TFS is in the local Admin group
Used both the Basic and Advanced wizards during setup
I'm not sure what I am missing, but it seems that not doing something to be able to use the built in reports. It doesn't look like I need SharePoint for that.
Any ideas?
From MSDN:
You can install Team Foundation Server on a client computer that is
running one of the operating systems in the table. However, client
operating systems do not support integration with SharePoint Products,
reporting, or the ability to run TFS proxy. ...
If you want to use any of these features, you must install Team
Foundation Server on a server operating system.
Emphasis mine.
Perhaps this was asked before but I can't find a whole lot on this, so I would appreciate some help.
Our architecture is as follows: Win 7 desktop on a domain with VS 2010. MS Sql server R2 on Win Server 2008 R2 Ent; SharePoint 2007 on Win 2003; SharePoint 2010 on Win 2008 R2 Ent; Visual Sourcesafe on yet another separate Win Server 2008 R2 Ent server. On this server I have just installed TFS and was running Advanced Config Wizard.
As I'm new to TFS all my selected options are based on intuition and perhaps common sense but Reporting Services and SharePoint aren't working. With reporting services after I add my sql server name (and I've tried IP address and dns name) neither the Report Server URL nor Report Manager URL is populated. (Note: What do I need reporting services for anyway?)
So I've opted not to use reporting services, which as I said, I don't know what is the benefit of it.
Next, in the SharePoint configuration, I wanted to use the existing SharePoint farm which is installed on a separate servers. Testing the Site and Administration URLs would throw an error: "The following site could not be accessed. ... Either ... not installed the Team Foundation Server Extensions, or Firewall... "
I suspect it is not the firewall so then the TFS Extensions. Having search that topic as well seems to point back to the TFS's configuration, so I'm a completely at a loss.
Any ideas?
Thanks,
Risho
/posted from a smartphone since employer blocks this site/
Edited: I was looking at this article http://msdn.microsoft.com/library/dd631915.aspx but I don't have the options listed in the step-by-step solution. TFS Admin Console has this: Top tear - server name, below is Application Tear then Proxy Server, build Configuration and Logs. Expanding Application Tear shows Team Project Collections, SharePoint Web Applications, Reporting, and Lab Management.
You have to configure the SharePoint extensions on each SharePoint machine you wish to connect to TFS. Install TFS on whichever SharePoint machine (or both, if you plan to use both). In the configuration wizard, you should have the option to configure SharePoint Extensions. Once done, you should be able to re-run the readiness checks in the Advanced Wizard on your Application Tier machine.
Is it possible that can I use Sharepoint server as development machine also. My mananger has asked me to use one of the newly purchased server for Sharepoint server as well as sharepoint development.
In future we will do some small development so what type of installation do I need?
Please guide me for the following which one I should install or which one is not required.
Standalone or Farms
VM
SQL Server 2008
VS 2010
SharePoint 2010 can run on a 64-Bit Windows 7, as per instructions from Microsoft.
It does not work on 32 Bit Windows as SharePoint 2010 is 64-Bit only, and it does not work on Vista.
Yes, it is possible to use your SharePoint server as a development machine. I'd suggest using a VM as it allows you to quickly and easily switch between, revert and deploy setups should something go wrong (and things WILL go wrong with SharePoint).
At work, my machine runs Win Server 2008 and I remote into a Hyper-V hosted VM which itself runs Server 2008 - I develop and run SP on that VM. Since I have SP, SQL Server and VS2010 all running on it at the same time, I allocate the VM at least 5.5 GB of memory (and it's still hungry for more).
You can develop for SharePoint 2010 on a Windows 2008 Server x64 or on a Windows 7 64bit. A Windows 7 is of course only recommended for development.
Most developers use a standalone machine for their SharePoint 2010 development. Creating a farm is complex and $$.
Personally I develop in virtual machines. I have on clean vm image that I copy for every new project (client). You need a powerful computer to run these virtual machines. At least 4GB memory and a recent multicore cpu.
You will need Visual Studio 2010, SQL server and ofcourse SharePoint. Office can also be handy but is not needed. SQl server express is included in Visual Studio and the SharePoint install also installs SQl server if needed. Certain Visual Studio versions include an "SQL server developer" license.
I will need a Sharepoint Server 2010 install for learning purposes.. I already have a Win 7 x64 os installation with vs2010 and I use it for my current development needs.
The question is ... would you recommend to install sharepoint onto an existing win 7 installation, create a separate OS instance (win7 or win 2008 r2?) for sharepoint development purposes or maybe create a VM for that? I have 4GBs of ram and I wont be able to extend it.
What are your experiences with dev environments for sharepoint 2010? I remember that 2007 was a real resource hog - maybe there is a 'magical' switch that allows sharepoint 2010 related services to be turned off?
If you thought SharePoint 2007 is a resource hog, SharePoint 2010 is even worse. The full installation creates lots of Windows services and IIS application pools. Which makes it really hard to stop SharePoint since all those services start automatically.I agree with others that you should use the VM approach but I think you need Windows Server 2008 R2 to be able to create 64-bit VMs.
Here's a link to powershell scripts for stopping/starting SharePoint services: http://blogs.msdn.com/b/emberger/archive/2009/11/16/stop-and-go-with-sharepoint-2010-on-your-workstation.aspx
I personally always run it in a different instance - either a separate machine or a virtual machine. Sharepoint 2010 is massive, and changes your system with a magnitude not seen by any previous sharepoint version, in terms of databases, scheduled tasks, services...
You should install your SharePoint 2010 in Server2008 R2 if you can ,since then you can do a complete install and use domain account.The installation in win7 is a standalone install and only use system account.It does not match what is in production...
Or if you can, virtualize your SharePoint environment.You need to give at least 4gb ram to SharePoint VM otherwise it is running like a dog.
I am considering switching to a co-located solution running a DNN (DotNetNuke) installation and an email server that mostly just does alias forwarding. I think I can get DNS services outside of this colocation box - but that could be an issue.
I am running this website for a non-profit group and trying to stay inexpensive. Will Windows Server 2008 Web Edition be acceptable for running all of this? My research so far says it will but I am looking for anyone with any experience running web edition and what sort of pitfalls does it have?
I was going to install SQL express as the backend for the DNN site. Indications are that you can't connect to SQL from outside the Web Edition box. Does this include SQL Management studio?
Any assistance or advice on this would be appreciated.
Update:
Still looking for any specifics with Windows Server 2008 Web Edition
We tried running DNN on Windows 2008 64-bit and 32-bit a while back. Not a great experience with intermittant failures and application hangs. We had to revert back to Windows 2003.
This was on a moderately loaded site. If you want to give them any sort of guaranteed uptime/availability I would recommend Windows 2003.