Link to home
Start Free TrialLog in
Avatar of bank_on_it
bank_on_it

asked on

Sharepoint - Ways to create a new site collection

Hi All,
I want to create a new web application that will be different to the one currently established in terms of security and content.  The users who have access to our current one will NOT have access to the new one. The new users who will have access to the new site collection will not have access to the current.
What is the best way to go about this and how?

I know most likely using a different port will be the answer but I am wondering if there is another/easier/better way.
Any help will be appreciated!
Thanks in advance!
Avatar of quihong
quihong
Flag of United States of America image

You actually don't even need a new web application to accomplish your security requirement. You can just use a site collection. However, a new web application would be more secure since it allows you to run it under a different application pool account.

Different port doesn't make a difference.
Avatar of Brad Howe
Hi,

A web applicaiton is a logical unit in both MOSS and IIS that are used to completely separate databases, security settings, authentication providers, etc. IE this are completely different sites and dont know others exist.

A site collection is usually a "top level" collection of sites that are categorized by business units, divisions, or groups.
Site collections will allow, Dedicated Recycle bins, Dedicated usage Reports  and most importantly Distributed administration (site collection administrators). You can also limit access based on your requirements but it will need some more configuration since you will need to deny and allow on the site collection.

Breakdown:
Web App = http://www.yourdomain.com
Site Collection = Human Resources (http://www.yourdomain.com/HR
Site = Payroll (http://www.yourdomain.com/HR/Payroll

The only reason you would create a Web application is to separate your enviroment complete and provide a new domain name. www.external.yourdomain.com or www.newapplicationsite.com

As per your comment about ports, I would suggest implementing HOST HEADERS for your Web Applications first off. These can be change even after implementing your original sites. This way you are always running on port 80 and never need to worry about forgetting the port.

As per your original question, IF you are certain that the sites will NEVER share content or webparts, then a web application is perfect. IF you think in he future you will need to share webparts or permissions then i would suggest a site collection.

Hope it helps,
Hades666
Avatar of bank_on_it
bank_on_it

ASKER

Thanks for the details hades666!
I definitely need a new web application since I do not want it to be part of the current one. We are setting up the new one for users who will have extremely limited access into our network. Basically, they are not employed by our company but do have business/work with our employees. Again, they will be given extremely limited access into our network but be able to view/use anything put into the NEW web application. They will NOT have access into our currently established one.

What is the best way to do this without causing conflict in terms of connectivity? Can we run multiple web applications on the same port and have the desired security settings stated above? If so, how?

I am very interested if this is possible, especially if we can just play with host headers instead of having to use a different port.
ASKER CERTIFIED SOLUTION
Avatar of Brad Howe
Brad Howe
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks Hades666. I will see if this will work for us.
It should work without issue for you. I do this for all my clients.  If you run into any issues, you know where to find me.

cheers,
Hades666
Perfect Hades666!
Thanks so much for your help!