archive-nl.com » NL » M » MAVENTION.NL

Total: 609

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Implementing SSL with PowerShell for existing SharePoint 2013 farm - Part 4 - Blog - Mavention
    Company sni false WebApplication WebApplication name Hosting Web App type SharePoint currentUrl http hostingwebapp company com newDefaultUrl https hostingwebapp company com hasHostHeader FALSE IISBinding hostheader certificate Wildcard SPApps sni false IISBinding hostheader appcatalog company com certificate Wildcard Company sni true IISBinding hostheader search company com certificate Wildcard Company sni true IISBinding hostheader publicationcenter company com certificate Wildcard Company sni true IISBinding hostheader projectcenter company com certificate Wildcard Company sni true IISBinding hostheader makeadmin company com certificate Wildcard Company sni true WebApplication WebApplications configuration The tricky part here is our hostheader less SharePoint web application Host headers are set at the level of site collections Hence the term Host Named Site Collections Initially you will not find any binding for each host named site collection in IIS The challenge here is we need 2 SSL certificates one for the main domain COMPANY COM and one for the App domain SPAPPS COMPANY COM Remember that SharePoint creates an App site with the URL that looks like app guid spapps company com This site is part of the hostheaderless web application Since IIS 8 0 part of Windows Server 2012 you can set more than 1 SSL certificate on one IIS site SSL Scalability This is done using Server Name Indication SNI More in depth information can be read here Let s do some scripting The Script When looping through the Server elements I determine if Bindings need to be set bool setBindings System Convert ToBoolean server Bindings When that is the case I use the remote session again to get the certificate info I need later Invoke Command Session session ScriptBlock Get Certificate ThumbPrints thumbPrintWildCardSPApps Get ChildItem Path Cert LocalMachine My subject StartsWith CN spapps company com Select Object ExpandProperty Thumbprint thumbPrintWildCardCompany Get ChildItem Path Cert LocalMachine My subject StartsWith CN company com Select Object ExpandProperty Thumbprint guid guid NewGuid ToString B Each certificate has a Thumbprint property The thumbprint is a hash value computed over the complete certificate I use this value to set the SSL certificate on a binding I ll show you in a bit Then we loop through the web applications config Configuration WebApplications WebApplication iisSite Write Host iisSite name type iisSite type NoNewline webExists Invoke Command Session session ScriptBlock param iisSiteName website Get WebSite Name iisSiteName return website ne null ArgumentList iisSite name if webExists Write Host f Yellow Skipped Not present else Write Host f Green Exists iisSite IISBinding bindingConfig Write Host bindingConfig hostHeader if iisSite type eq SharePoint SharePoint Server Invoke Command Session session ScriptBlock param iisSiteName hostHeader certificate sni activeThumbPrint thumbPrintWildCardCompany if certificate ne Wildcard Company activeThumbPrint thumbPrintWildCardSPApps if hostHeader Main binding always exists so add SSL Certificate only netsh http add sslcert ipport 0 0 0 0 443 certhash activeThumbPrint appid guid certstorename MY verifyclientcertrevocation disable else sniFlag 1 if sni ne true sniFlag 0 binding Get WebBinding Name iisSiteName protocol https port 443 HostHeader hostHeader if binding eq null New WebBinding Name iisSiteName Protocol https Port 443 IPAddress HostHeader hostHeader SslFlags sniFlag

    Original URL path: http://www.mavention.nl/blog/implementing-ssl-powershell-existing-sharepoint-2013-farm-part-4 (2016-02-18)
    Open archived version from archive


  • Octavie van Haaften - Mensen - Mavention
    de grenzen van het project maar plaatst het project duidelijk in de context van de organisatie Hij heeft zowel technische als functionele kennis op het gebied van SharePoint en NET software ontwikkeling Hij kan allround worden ingezet binnen een project Van functioneel ontwerp het inrichten van SharePoint het samenstellen en aansturen van een team tot het waarborgen van de kwaliteit SharePoint WCM Specialist Mavention is specialist op het gebied van

    Original URL path: http://www.mavention.nl/mavention/mensen/octavie-van-haaften (2016-02-18)
    Open archived version from archive

  • Implementing SSL with PowerShell for existing SharePoint 2013 farm – Part 3 - Blog - Mavention
    HTTPS and SSL configured This scenario does indeed store the correct settings the configuration database and there will be an IIS site with HTTPS bindings All you have to do then is select you SSL certificate for the HTTPS binding Sounds promising doesn t it Well you ll regret it Why Because you probably have custom solutions perhaps even legacy 2010 solutions As soon as you delete your web application all your associations for the installed solutions are deleted as well They will never return when your re create your web application so you have to deploy them again to the new web application And you know you have crappy coded solutions Crappy solutions that have crappy features to be activated again and all hell breaks loose So where does it leave us now The answer is to un extend and re extend your web application 3 Un extend and re extend the web application This works very well when you have already extended your web application to another zone like Intranet Just un extend your zone and re extend it with the new HTTPS and SSL options configured Even your solutions are okay and you do not have to re deploy them However and this is an important however if you have just one zone and that will be the Default one of course you must NOT un extend and re extend that one zone Then you will be in the same dissociated crappy solutions situation All hell just broke loose again In this case you ll need to temporarily extend your web application to a dummy URL on another zone like Intranet Then you can un extend and re extend the Default zone And you re good to go don t forget the un extend the intranet zone with the dummy site The Script Let s do some un extending and extending web applications with PowerShell Again I use some XML configuration WebApplications WebApplication name MySites currentUrl http mysites company com newDefaultUrl https mysites company com hasHostHeader TRUE WebApplication name Hosting Web App currentUrl http hostingwebapp company com newDefaultUrl https hostingwebapp company com hasHostHeader FALSE WebApplications The script reads this configuration and performs the following code config WebApplications WebApplication currentURL currentUrl newDefaultURL newDefaultUrl bool hasHostHeader System Convert ToBoolean hasHostHeader webapplicationName name Write Host Write Host f Cyan Changing webapplicationName to SSL wa Get SPWebApplication webapplicationName if wa Create dummy extension Write Host Creating Dummy web application extension NoNewline wa New SPWebApplicationExtension Name DummyIntranetSite Zone Intranet URL http dummy intranet company com Write Host f Green Done Unextend the default web application Write Host Removing Default web application NoNewline wa Remove SPWebApplication Zone Default DeleteIISSite Confirm false Write Host f Green Done Create new default HTTPS web application Write Host Creating SSL Default web application extension NoNewline if hasHostHeader hostHeader newDefaultURL Replace https wa New SPWebApplicationExtension Name webapplicationName HostHeader hostHeader Zone Default URL newDefaultURL SecureSocketsLayer Port 443 else wa New SPWebApplicationExtension Name webapplicationName Zone Default URL newDefaultURL SecureSocketsLayer Port

    Original URL path: http://www.mavention.nl/blog/implementing-ssl-powershell-existing-sharepoint-2013-farm-part-3 (2016-02-18)
    Open archived version from archive

  • Implementing SSL with PowerShell for existing SharePoint 2013 farm – Part 2 - Blog - Mavention
    all the way up in the chain Therefor I also deploy the root certificate authority The Server elements describe the servers where the certificates will be deployed to The attribute certificateLocation describes the location where the files are copied to For each server element I configure which certificates I want to deploy and install Deployment Script I will provide the complete script but for the sake of readability I will describe the nifty bits First I am copying the files to all servers xml config Get Content Deploy Certificates config config Configuration Servers Server server serverName name Write Host Write Host f Cyan Server servername Create destination folder if not exists destination serverName server certificateLocation Write Host Ensuring install folder destination NoNewline if not Test Path path destination f New Item destination Type Directory Force Write Host f Green Done Copy certificate files to destination folder Write Host Copying certificate files NoNewline server Certificate certificateName Name certificate config Configuration Certificates Certificate name eq certificateName certificateFile certificate fileName f Copy Item Path currentScriptLocation Certificates certificateFile Destination destination Write Host f Green Done Secondly I open a remote PowerShell session to that server Within this session I will install the certificates into local certificate stores Install each certificate session New PsSession ComputerName serverName Write Host f White Installing certificates server Certificate certificateName Name Write Host t certificateName NoNewline certificate config Configuration Certificates Certificate name eq certificateName certificateFile certificate fileName certificatePassword certificate password certificateStore cert LocalMachine certificate store certificateLocation server certificateLocation Replace localCertificateFile certificateLocation certificateFile if certificateFile EndsWith crt Invoke Command Session session ScriptBlock param localCertificateFile certificateStore crt Import Certificate FilePath localCertificateFile CertStoreLocation certificateStore Confirm false ArgumentList localCertificateFile certificateStore else Invoke Command Session session ScriptBlock param localCertificateFile certificateStore certificatePassword securePwd ConvertTo SecureString String certificatePassword Force AsPlainText pfx Import PfxCertificate FilePath localCertificateFile CertStoreLocation certificateStore

    Original URL path: http://www.mavention.nl/blog/implementing-ssl-powershell-existing-sharepoint-2013-farm-part-2 (2016-02-18)
    Open archived version from archive

  • Implementing SSL with PowerShell for existing SharePoint 2013 farm – Part 1 - Blog - Mavention
    be equal regarding HTTP HTTPS Another requirement that came in to play was that collaboration intensified and external users needed to get access to the collaboration sites Current Environment My farm has the following configuration all servers are running Windows Server 2012 R2 6 SharePoint 2013 Servers 2 WFEs 2 APPs services and 2 dedicated for BI services Excel Reporting and PowerPivot Services 2 SQL Server 2012 with Always On Availability Groups 2 IIS Web Servers for running Provider Hosted SharePoint apps eh add ins Both SharePoint and IIS Web servers are load balanced by an F5 BIG IP In SharePoint I have 2 web applications one for the MySites and one for hosting the host named site collections and path based site collections Name URL Port MySites http mysites company com 80 Hosting Web App http hostingwebapp company com 80 Examples of host named site collections are http appcatalog company com http search company com http publicationcenter company com http projectcenter company com http makeadmin company com Examples of path based site collections are http publicationcenter company com sites marketing http projectcenter company com sharepoint migration Examples of the IIS site for the Add Ins http make company com http autofollow company com The domain for the Apps is set to spapps company com and the AppCatalog is set to http appcatalog company com in the web application Hosting Web App The F5 Load Balancer has a virtual IP configured using both SharePoint web servers listening for requests on port 80 All DNS entries are pointing to this VIP Steps to be taken Get the SSL certificates and install them on the required servers Part 2 Change the SharePoint Web Applications to use SSL and HTTPS Set the IIS Bindings for the SharePoint IIS sites to use the SSL

    Original URL path: http://www.mavention.nl/blog/implementing-ssl-powershell-existing-sharepoint-2013-farm-part-1 (2016-02-18)
    Open archived version from archive

  • Inconvenient Test-SPContentDatabase warnings - Blog - Mavention
    based On the internet I found this article Test SPContentDatabase Classic to Claims Conversion by Trevor Seward Although I was not yet interested in any solution but wanted to know why I used that SQL statement to get an answer Hopefully In SQL Server Management Studio I ran the query on a content database SELECT TOP 1 tp SiteID tp Login FROM UserInfo WITH NOLOCK WHERE tp IsActive 1 AND

    Original URL path: http://www.mavention.nl/blog/inconvenient-test-spcontentdatabase-warnings (2016-02-18)
    Open archived version from archive

  • Blog - Mavention
    10 2014 door Octavie van Haaften Updated Mavention Profile Info App Today an update for the Mavention Profile Info app is available in the Office Store Version 1 1 contains localization support for English and Dutch Aangemaakt op 3 9 2014 door Octavie van Haaften New App in Town Mavention Profile Info The Mavention Profile Info contains an app part where the list of user profile properties can be defined

    Original URL path: http://www.mavention.nl/blog?k=PublishingContactNameOWSTEXT%3a%22Octavie+van+Haaften%22&start=6 (2016-02-18)
    Open archived version from archive

  • Blog - Mavention
    door Octavie van Haaften Beware of styling changes after SP1 When planning to install Service Pack 1 you should test everything to make sure it all works as expected Aangemaakt op 12 5 2014 door Octavie van Haaften October 2013 CU issue with adding existing content database Recently I have installed a fresh new SharePoint 2013 farm based on the October 2013 CU While configuring the farm I found an

    Original URL path: http://www.mavention.nl/blog?k=PublishingContactNameOWSTEXT%3a%22Octavie+van+Haaften%22&start=11 (2016-02-18)
    Open archived version from archive



  •