SharePoint geek, dev, admin – Chicago IL
SharePoint geek, dev, admin – Chicago IL

Blog

I Wanna Patch FAST

Want to patch your SharePoint farms faster?  Try running https://github.com/spjeff/sppatchify

 

The latest version (0.42) includes new PowerShell code for parallel execution of “Upgrade-SPContentDatabase.”  This was implemented with “Get-Job” and PowerShell job management to remote sessions. 

The more user content databases you have, the greater the time savings.  Below are summary statistics from patching a 9 server SharePoint 2013 farm with 200 SQL content databases in just 4 hours.  Each of the 9 servers will spawn 4 PowerShell remoting runspaces for “Upgrade-SPContentDatabase.”  With 36 concurrent worker threads, the queue of 200 content databases now becomes only 6 deep.  

Instead of waiting 200 units of time to process content databases serially, we now only wait 6 units of time for the upgrade database phase.

Larger farms with more user content (and databases) will see significant overall time savings considering how a majority of the traditional patching timeline is processing all content databases.    The binary EXE phase runs with all content databases  removed (Dismount-SPContentDatabase ) so PSCONFIG can complete sooner.    After that is done, content is introduced again (Mount-SPContentDatabase) and upgraded (Upgrade-SPContentDatabase).

 

Amazing speed!!!    Cheers 

 

 

Charts

 

image

 

image

 

image

 

Image result for i wanna go fast

 

 

SPPatchify

Open source hosted on GitHub

 

image

What’s in that patch? September 2016

NOTE – PDF format updated to include both SharePoint 2013 and 2016 notes.

 

Ever wondered what fixes are inside of a given CU?   Please see attached PDF with full detail. I wanted a new format for easy reading.   Show management and make the business case for why downtime should be taken to apply CUs.  Also posted at http://sharepointupdates.com/

If you found this helpful, please leave a comment.   

shades_smile_thumb_thumb_thumb_thumb[2]

 

Download

What’s in that patch – Sep 2016.PDF

Office 365 – How to create a Developer Tenant

I wanted to get started with SharePoint Framework and learned that an Office 365 developer tenant is required.   

Below are the steps I followed with screenshots.  Hope that helps! 

shades_smile

 

  1. Register with your Microsoft account at https://profile.microsoft.com/RegSysProfileCenter/wizardnp.aspx?wizid=14b845d0-938c-45af-b061-f798fbb4d170&lcid=1033
  2. Choose a domain prefix (____.sharepoint.com)
  3. Choose an admin username and strong password
  4. Text message verification code
  5. Azure AD is only available for paid subscriptions
  6. Browse admin center and test functionality

 

image

 

image

 

image

 

image

 

image

 

image
image
image
image
image

Save Encrypted Passwords to Registry for PowerShell

Recently I needed to save passwords to share across scripts and wanted to:

  1. Avoid clear text passwords
  2. Avoid updating anything in each PS1 script file
  3. Securely store in a central place
  4. Make future password updates easy

After testing I found that ConvertTo-SecureString can be used with Set-ItemProperty to encrypt user text input and save to the Registry Current User hive (HKCU).   From here, multiple scripts on that machine can reuse the one central password.   However, it cannot be decrypted from any other machine.    That enables us to share one credential across many PS1 scripts while keeping any password updates centralized and easy to do.    Also, the reference pointer in each script is not a file path, UNC, or network share, but simply “HKCU:\Software” for a reliable lookup pipeline.

Hope you find this useful too.  Cheers! 

shades_smile

 

Screenshot

 

image

 

image

 

 

Code

 

References

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲