Tag Info

Hot answers tagged

4

Yes, you need to ensure your published URLS for your farm are setup to use HTTP as the traffic from your Netscaler to the farm will be in HTTP. This only matters for the published URLS as these are the URLS the Netscaler will use. Don't worry about the traffic between various servers in your farm as it doesn't make a difference from a SSL offload ...


4

Just to add what punchingInApepper already stated. SNI is a wonderful thing and is available in IIS 8.0. It has been around for some time like punchingInApepper stated but I have runned into some issues with SNI and multi-webapplication farms which I have not seen documented before so a bit of a warning; WebDAV (open with file explorer) will not function ...


3

The AutoSPInstaller (http://autospinstaller.codeplex.com/) was actually creating self-signed certificates on the server that the WAC did not trust. So we had to manually create the certs and a CA so that the trust would work properly. This corrected our issue.


3

Actually, The reason you can't use one IP was a fault of IIS. There is an extension of TLS that allows a hostname to be specified. This has been around for years and is supported by all major browsers. The good news is that the latest version of IIS that comes with Windows Server 2012 supports this. So if you are running IIS 8, then good news, you can use ...


3

When you have several different websites routing to the same IP/port then the only way IIS knows where they should go is using the host header (the site address) Incoming Host Header Send to Web Application 192.168.0.1 : 80 websiteA.com A 192.168.0.1 : 80 websiteB.com B However if you're using SSL then The SSL certificiate is ...


3

you dont need to extend the web app rather you have to update the IIS bindings. On the WFE servers, Add the Binding for the SSL & attach the certs. Now update the Https entry into the AAM via Central Admin. check this guide: http://blogs.msdn.com/b/sowmyancs/archive/2010/02/12/how-to-enable-ssl-on-a-sharepoint-web-application.aspx


2

SharePoint maintains it's own store of trusted root certificate authorities for use with it's own token service. Check out the technet blog post for more details: http://blogs.technet.com/b/speschka/archive/2010/02/13/root-of-certificate-chain-not-trusted-error-with-claims-authentication.aspx Open the SharePoint Management Shell to run the PowerShell ...


2

Either use the methods in this link to turn on error messages, or you should be able to log on to the physical server to see the detailed error messages.


2

A single SP farm vs virtualizing many SP farms? A single SP farm can handle multiple SSL sites, as long as they're on unique IPs. A separate farm per site would be a waste of resources. SharePoint is designed to handle multiple. As far as maintainable, that would depend on your site collections and content databases and anticipate database sizes. Also, ...


2

Well, at last I found out what is happening. What I didn't know is that this Datapower was terminating SSL requests and forwarding in HTTP. The idea found here. Off-box termination of SSL is when a proxy server terminates an SSL request and then forwards the request to a Web server by using HTTP. I asked to the colleague that manages the Datapower and ...


2

Have you done anything specificly for SharePoint performance optimization? Object cache In SharePoint you should adjust the object and output cache. During stress load your \SharePoint Publishing Cache\Cache hit ratio should preferably be above 90% For object cache default is 100 mb. Adjust it up in 100 mb increments while measuring hit ratio and at the ...


2

Once you have your site in IIS, when you apply your SSL certificate to it, this applies to the entire site. Please read the instructions here: http://www.harbar.net/articles/ssl.aspx especially if you are using SSL for multiple sites. I found this to be invaluable when setting up SSL the first time with SharePoint.


2

The behavior is normal as the AAM doesn't know about your redirect, therefore the Workflow engine is not able to populate the proper Url. You should either use a Reverse'Proxy (e.g. ForeFront TMG, ISA 2006 ) that could automatically change your HTTP to HTTPS or Extend the Web Application to use HTTPS too. Besides you can make also enable the "Configure ...


2

So you're saying you've got name.net as well as name.com as SANs within your certificate? For your canonical names you need *.name.net as a subject alternative name if you wish to use an unlimited number of canonical names. ADFS fully supports wildcard certificates if you create them with valid subject alternative names.


2

No, this will not work if you only do that. If you make all of the configuration changes in IIS (on all of the WFE servers) to add the new binding to the IIS site, but without telling SharePoint about it then you'll get a SharePoint monster which sometimes will kind of work. Depending on how you navigate to the first page it'll show that using the https ...


2

as ryan stated but there is a vital part missing for ssl! you need to add dns record for ssl aswell as adding the host header! start -> admin tools -> dns when the app loads, go into the server or add it in, expand "forward lookup zones" , expand the domain e.g. mydomain.com if you click on the domain name, you will see to the righ some folders and files ...


2

It could easily explainable by the concept of "Application Extension" in SharePoint, which is simply a mechanism that creates a new Web Application (it could be the same Host header too, but different Protocol, HTTP vs. HTTPS - with the purpose of offerring different authentication mechanism to different targeted people, e.g. Intranet vs. Extranet, Employees ...


2

SSL offloading will still meet the "use SSL for SPS 2013" train of thought. Whether SSL offloading is a risk in your environment is dependent on a number of things that only you can make the call on. The traffic between the client and the load balancer will be secure and the traffic between the load balancer and the web front ends will not be. Client PC ...


2

I've been doing a great deal of research into this the past couple days as I'm in a similar situation. The evidence looks pretty strong that WebClient, the Windows service that is used by software to connect to a WebDAV resource does not support SNI. A SharePoint MVP echoed my suspicions that this is the case on another thread on the MSDN forums. At this ...


1

I actually always configure the App-Domain DNS / SSL bindings on the same web app you have used for your SharePoint sites (assuming you are using Host Named Site Collections). In the background SharePoint creates a sub-site within the same site collection but uses some clever routing to make it appear under a different URL. Also, the App Domain needs to be ...


1

If you changed the public URL in AAM & configured the IIS website to use SSL it will work without extending to a new website. However, whenever you will add a new webserver SharePoint will configure the original IIS settings that it knows about. That's why it's so important to specify the right public url & host header upon creation of a new web ...


1

For those like me who can't find certlm.msc on their Windows 2008 R2 server : Execute mmc.exe Click on file > Add/Delete Choose the "certificate" and click on "Add" Then select the "A computer account" And you are done, you can see all nodes of the Local Machine certificates.


1

You have to open the Manage Computer Certificates which is certlm.msc (and not certmgr.msc). There youll find the SharePoint node. I'm running Windows Server 2012. Screenshots for demonstration.


1

Can I assume when you say claims you actually mean Claims with Active Directory as user data store, where from your problem, right? If NOT, then you should have no issues as it all handled automatically by the claims - meaning that is all in your connection of the provider! If domainOne and domainTWO also are related to 2 AD domains, bi-directional trust ...


1

Try setting the UpdateAlert in powershell. Here is a link on the explanation http://www.wssdemo.com/Lists/stsadm/DispForm.aspx?ID=189&ContentTypeId=0x01001F9A291A8D9053488BAC958E9E294593


1

You just have to set up the calendar sync with the appropriate web address using HTTPS. The error is telling you it's trying to connect to http://oldname.com/sites/abc/develop which isn't the URL you want configured. As a fallback, it is attempting to pull the calendar from http://prodname.com/sites/abc/develop, but that's hitting your HTTP Redirect in IIS. ...


1

Did you configure SharePoint as the relying party in the "ADFS Account provider"? The "-realm" parameter of the SharePoint New-SPTrustedIdentityTokenIssuer cmdlet should be the identifier of SharePoint in ADFS. That is how ADFS knows who is requesting the token. Nothing from your resource ADFS should be configured in SharePoint. It only talks with the ...


1

The sharepoint.xyz.com, from what I have gathered, is the URL you want to use. This site should have the SSL setup on it, not sharepoint2. If users are going to use sharepoint2.xyz.com securely, that'll need the SSL as well, but I think that's not the case. If it is, then you need a unique IP per site running SSL, so you'll need 2 IPs for both sites. I ...


1

You Fiddler session shows a connect on port 443 which is the default port for SSL yet I do not see 443 configured in SharePoint. It is also worth following up on why you are supposedly going to port 8180 in the URL but connecting to 443. This almost sounds like something is not configured right in the "black box" or that you are somehow bypassing it ...


1

Found the issue. Had to use a wildcard cert. I have multiple web apps binded to port 443. I stop the web apps sites on the server that are not needed. Looks like SharePoint doesn't care that the site is stopped or started. Still need to have a correct cert in order for the sync to work properly.



Only top voted, non community-wiki answers of a minimum length are eligible