exsasan
asked on
SharePoint 2010 Planning and Installation
Hi There,
I need a high level installation steps of SharePoint Server 2010 and SQL server 2008, for following scenario.
-I'm going to install SharePoint server 2010 for a company of about 20 users.
We have one brand new server, also We have one existing Windows Server 2008 server that is the only server of the company, for Sharing, Active directory, Application server, Backup server and so on.
My goal is to install the SharePoint Server 2010 in the new server also move all the applications to this new server and use the old server just for Sharing and Backup.
So I like to have following on the new server:
1. SharePoint Server 2010
2. A few web base applications, all IIS base that have SQL server in back (Very light use).
3. Domain controler (Since the company has just one server I like this server be a part of Active directory domain to have a redundancy).
My main concern is:
1. How to co-esist SQL server for SharePoint with SQL srever for applications?
- Witch SQL should be the default and with Witch one the Name server?
2. Is it OK the server be a part of Domain and keep the active directory?
Thank you in advance
I need a high level installation steps of SharePoint Server 2010 and SQL server 2008, for following scenario.
-I'm going to install SharePoint server 2010 for a company of about 20 users.
We have one brand new server, also We have one existing Windows Server 2008 server that is the only server of the company, for Sharing, Active directory, Application server, Backup server and so on.
My goal is to install the SharePoint Server 2010 in the new server also move all the applications to this new server and use the old server just for Sharing and Backup.
So I like to have following on the new server:
1. SharePoint Server 2010
2. A few web base applications, all IIS base that have SQL server in back (Very light use).
3. Domain controler (Since the company has just one server I like this server be a part of Active directory domain to have a redundancy).
My main concern is:
1. How to co-esist SQL server for SharePoint with SQL srever for applications?
- Witch SQL should be the default and with Witch one the Name server?
2. Is it OK the server be a part of Domain and keep the active directory?
Thank you in advance
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you could dedicate one Nic to SharePoint web traffic only. Meaning register the server in DNS on one Nic up, and register your SharePoint URLs in DNS as the other Nic up.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks
ASKER
I think I would setup new server as:
1. Windows server 2008 as member (Not DC),
2. Install SQL server 2008 R2 for all internal web applications.
3. Install SharePoint Server using either the same SQL Server or on a separate one. (Not sure about this part) .
Later if the company have more employee I can transfer the internal applications + related DB to a new server and keep this server just for share-point.
Also the server has 2 NIC cards, is there a way to take advantage of that, by activating both NIC card and use one somehow just for SharePoint?
Any suggestion about using second NIC, or the whole scenario??
Thanks