Sitecore 9 XP1 implementations establish two key Windows Services supporting xConnect (that are created as Windows Services via the SIF, but other options exist…. more on that later). These are the Sitecore Marketing Automation Engine and Sitecore XConnect Search Indexer components. Each has distinct responsibilities in ensuring that xConnect properly functions so if xConnect is …
Sitecore 9 brings a heavy paradigm with certificates and intra-machine communication when you decide to implement a scaled XP1 environment. You could have separate servers for each Sitecore role, or an architecture that has xConnect on one Server… CMS, Processing, and Reporting on another… and your CDS(s) serving public traffic. As you need to ensure communication between …
Unweaving the Client Certificates required for an XP1 scaled implementation can be a bit of a challenge, as there are several undocumented steps that need to be undertaken. Often, many will export and import the correct certificates, update connectionStrings to use the proper ThumbPrints, but not update the SSL Settings for the IIS xConnect sites …
Locking down your Content Delivery servers so external users can’t access your content management capabilities and Admin pages is one of the top security steps you need to undertake when deploying a new Sitecore environment. The first step is to implement IP-based security restrictions: Instructions for IIS 7 and greater are as follows: https://docs.microsoft.com/en-us/iis/configuration/system.webServer/security/ipSecurity/ The …
If you are using SIF Version 1.1.0 to generate Self-Signed Certificates and need to export these to other machines as part of a scaled environment, you may find that you are unable to export the Private Keys along with the certificate. In fact, the option to export is grayed out: SIF Version 1.1.0 Created Certificate: …
If you deploy xConnect using the SIF Framework, you will notice a JSON Parameter named “XConnectEnvrionment” with a description of “The configuration environment for this instance” containing a default value of “Development”. “XConnectEnvironment”: { “Type”: “string”, “DefaultValue”: “Development”, “Description”: “The configuration environment for this instance.” }, So, what is the purpose of …
Sitecore has updated the Sitecore 9 SIF to Version 1.2.0. New features include Tasks for allowing “enabling, disabling and deleting configurations by reading an IO xml file (*.ioxml)” and transforming “XML documents by applying XML Document Transformation (xdt) files”. Resolved bugs includes resolution of the “certificate private key path on Windows 8.1/2012” and corrections to input hash tables.
Full details can be viewed at: https://sitecore.myget.org/feed/sc-powershell/package/nuget/SitecoreInstallFramework/1.2.0
If you don’t want to declare the required version using PowerShellGet as stated in the Sitecore package instructions, the following PowerShell snippet will allow you to get the latest version via the Update-Module command:
# Trust PSGallery
Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
# Install SIF from GET and Check for Updates
Register-PSRepository -Name SitecoreGallery -SourceLocation https://sitecore.myget.org/F/sc-powershell/api/v2
Install-Module SitecoreInstallFramework -Force
Update-Module SitecoreInstallFramework -Force
If you are following the Sitecore 9 Update 1 Installation Guide, you may note that the prerequisites for SIF can lead to failures with SQL Communication if you are installing a scaled Sitecore environment (ex. SQL is installed on one server, while your Sitecore roles are installed on separate servers). You may not experience issues if you …
As I developed www.thepersonalfinancecenter.com with the joy of using AngularJS coupled with an Azure Mobile Services backend, the struggle was not with implementing a voting feature for social authority or providing identity management (thanks to Auth0), but rather how to ensure that AdSense would render properly and the site could be SEO compliant. Let’s address …
If you are one of the multitude of users/developers who depend on MicrosoftAjax.js via accessing it in the _layouts/15 or _layouts/ directory and found that it is now gone from your SharePoint Online tenant or local SharePoint instance, you are not alone. Microsoft deemed this unnecessary as they believed it was not in use except for legacy Excel needs. In reality, many of us depend on it for client side operations.
After conversations with Microsoft this week, they stated that a KB Article and solution will be posted in the near future but that using the CDN for MicrosoftAjax.js is acceptable. I would recommend downloading the script from the CDN and referencing it locally in case of CDN issues. The CDN is located here: https://ajax.aspnetcdn.com/ajax/4.0/1/MicrosoftAjax.js
UPDATE: After Microsoft worked internally and realized the impact, they have begun rolling back this change and restored MicrosoftAjax.js to tenants. Check to ensure yours is restored. If not, use the method above.