Hot answers tagged iis7
4
You have to Create a Site Collection in your Web Application. Go to Central Administration and choose Create Site Collection in the Application Management group.
Enter a title in your Site Collection, select template to use and the primary site collection administrator:
This can be done using PowerShell as well. Don't forget to Set Execution Policy ...
3
My recommendation would be that you shouldn't.
You should start from scratch again and develop your Web-Application to be deployed below the _layouts folder in SharePoint using a WSP package and all of your code should be in code behind which is compiled into a dll deployed to the GAC.
You can technically get your solution to work, but it's a hack, that ...
3
Seems like your SharePoint WFE is out of synchronization as the web application is created in one server and it is not created in the other.
You can solve issue by deleting the web application first you just created.
Restart the timer services in both the WFE and try creating a web application
Or you can also try this STSADM command before performing ...
2
You want to do this with the SPIisSettings class. There is a method in that class called AllowAnonymous which you can set to True and then update the object. That will enable Anon for the Web Application on the specified zone.
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spiissettings_members.aspx
2
As a good practice, deploying SharePoint customizations should always be done via features, packaged into solutions. This way, SharePoint takes care of the deployment to all web servers in the farm. Of course there are also other benefits such as help with upgrading your features. More info:
...
2
when you create a webapplication in sparepoint central admin, you would then need to goto iis -> domain name -> click on "web sites".
You should be able to see a list of web applications e.g.
ssp.example.com
hello.example.com
test.example.com
that and oviously the correlating ip's and port number ect , as you can see its not sites or site collections ...
2
It may come as a surprise to you (which only shows how little it has
been written about this) but most of the ‘important’ things in
SharePoint are actually done through unmanaged code and the SharePoint
.NET object model provided by the Microsoft.SharePoint.dll is a sort
of a wrapper to this unmanaged world. Understanding how your code does
what ...
1
The normal configuration for your scenario is to rely on the alternate access mappings (AAM). I'm not sure what setup your are using for your web application, but the best practice approch would be:
Create new web applciation with SSL
Url: https://customesite.com (Zone = Default)
Add internal URL for this web app in the AAM configuration
Internal Url: ...
1
An easier no code solution is to configure IIS to handle it for you. Create a new site setup with the hostheader customsite.com, and on port 80. Within the site, select HTTP Redirect under the IIS group:
From here you can redirect to https://customsite.com.
1
The simplest solution would be to use remote blob storage to move the file content out of SQL to actual disk storage. AvePoint DocAve Extender is free. See http://www.prweb.com/releases/2010/03/prweb3743974.htm on how to get the free license.
1
It could be accomplished by specifying more narrow match pattern for url
For example, let's discuss the scenario, where requests from:
http://{ServerName}/_layouts/teamsiteA/userdisp.aspx?ID=1
should be redirected to:
http://{ServerName}/SitePages/UserInfoA.aspx?userID=1
and requests from:
http://{ServerName}/_layouts/teamsiteB/userdisp.aspx?ID=1
...
1
I seriously doubt you want to do anything to the IIS Configuration for SharePoint sites, as the Central Admin service looks after the IIS settings and the replication of those across all your servers.
Any changes you do will probably be overwritten by a future service pack or other update, and may also introduce instability in current and future versions.
1
This requirement is very specific to your project. You can fulfil it by writing a HTTP Module which intercepts every SharePoint request, and converts it to Lowercase, see below:
public void Init(System.Web.HttpApplication Appl)
{
//Hookup the function that does the lowercase
Appl.BeginRequest += new ...
Only top voted, non community-wiki answers of a minimum length are eligible
