AutoSPSourceBuilder heads to the PowerShell Gallery!

Standard

File under “why didn’t I do this years ago??”

You can now easily install AutoSPSourceBuilder (my PowerShell-based utility for downloading SharePoint updates and integrating them into the installation media) from the PowerShell Gallery.

TL;DR:

Install-Module -Name AutoSPSourceBuilder

No more need to browse to the GitHub repo, download the zip, extract it, etc. The simple one-liner above will (on any modern Windows machine with installed-by-default PowerShellGet etc.) automatically download and install AutoSPSourceBuilder.ps1 to your default Scripts directory, and make it available to directly run in any PowerShell sessions you launch.

What’s more, the AutoSPInstaller.xml update inventory file, updated on a (roughly) monthly basis and previously bundled with the script, is now by default automatically downloaded at script run-time to ensure you have the latest set of SharePoint updates to choose from. If however for any reason you want to use your own XML inventory, you can opt to skip the xml download and use a local copy of the inventory file by including the new -UseExistingLocalXML switch parameter.

Now that I finally realized just how ridiculously easy it is to publish a script to the Gallery, you can expect to see some more of my stuff make its way there in the near future.

Hopefully this latest batch of changes makes it easier to keep the AutoSPSourceBuilder SharePoint update management tool… updated!

Cheers
Brian

PFE Ramblings: SharePoint 2019, SharePointDSC and AutoSPInstaller

Standard

With the recent announcement and release of the Public Preview of SharePoint Server 2019, my fellow PFE Nik Charlebois and I thought we’d record a quick chat of our thoughts on the state of things around SharePoint and two of the most popular automated installation approaches, SharePointDSC and AutoSPInstaller.

Head on over to Nik’s blog for the full run-down, and a recording of our chat as well.

Cheers

Using AutoSPSourceBuilder To Build a .NET Framework 4.6 Compatible SharePoint 2013 Installation Source

Standard

Several months back, some folks started reporting an error when attempting to install SharePoint 2013 on certain Windows servers – specifically, ones that already had the .Net Framework 4.6 installed. The error simply states: “Setup is unable to proceed due to the following error(s): This product requires Microsoft .Net Framework 4.5” – well, 4.6 is surely newer, shinier and better than 4.5, so what gives?

Though initially identified as an incompatibility between the SharePoint 2013 installer and .Net 4.6, albeit with viable but potentially cumbersome workarounds (mess around in the registry, uninstall .Net 4.6 before re-attempting the SharePoint installation, etc.), Microsoft eventually released a permanent fix that involved some manual steps to replace a setup-related DLL. All good, right?

Well if you’re lazy (erm I mean, efficient) like me, you might feel we can do one better. Since the fix involves basically downloading a file, extracting it, then replacing a file that’s part of the SharePoint 2013 installation media, it kind of fits in nicely with one of my open-source projects which performs many of the same steps for SharePoint prerequisites and updates – AutoSPSourceBuilder. So I set about incorporating the KB3087184 fix as one of SharePoint 2013’s “prerequisites” – that is, it should really be considered a prerequisite if you want to install 2013 on a server that has all Windows Updates (including .Net 4.6x) already applied to it.

Here’s how to proceed with automatically integrating the KB3087184 fix yourself, if you find yourself in that situation:

  1. Download & extract the latest AutoSPSourceBuilder after reading a little bit about it to get acquainted, if you’re not already
  2. Run the script as usual, making sure to specify:
    1. -SourceLocation <path to your SharePoint installation source/DVD/mounted ISO>
    2. -Destination <path where the assembled stuff should be saved>
    3. -GetPrerequisites:$true (this is important as we consider KB3087184 to be a SP2013 prerequisite now)
    4. -CumulativeUpdate <CU name, e.g. “October 2016”>
    5. <other optional parameters e.g. -Languages, as needed>
  3. Check the output folder that appears, especially the _SLIPSTREAMED.txt file for confirmation that you have incorporated everything you were expecting

The AutoSPSourceBuilder PowerShell script will automatically detect if the fix is required, download the fix, rename the existing svrsetup.dll, then extract the updated svrsetup.dll to the correct location. Once the script completes, you should have a .Net 4.6 compatible SharePoint 2013 source, with your choice of cumulative update, language packs, etc. ready to be installed by something like SharePointDSC, AutoSPInstaller or (gasp) a manual process.

It’s always worth mentioning that my open-source projects aren’t officially supported by Microsoft, but you can reach out to me directly if you have any specific issues or questions.

Cheers
Brian