Softlanding: SharePoint Consulting & Managed Services | Vancouver, BC

    ​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​Delivering Solutions, Empowering Clients

    Softlanding helps organizations be their best by providing technology solutions and services that make them more productive. Softlanding specializes in Microsoft enterprise technology platforms, leveraging a combination of cloud, on-premises and hybrid configurations to increase productivity from the data center on out to end business users. Platform specialties include SharePoint, Azure, Office 365, Power BI, EMS and System Center.​

    ​​

     Stay Connected

    Softlanding is on Linkedin, Facebook​ and Twitter! Subscribe to our monthly newsletter to get insider information on our upcoming events, tips and current news within the IT industry​.

     

     SharePointROI Sustainment Services

                                                           SharePointROI is a, fixed- fee managed service providing end-to-end SharePoint sustainment, user support and adoption services. Eliminate SharePoint expertise hiring headaches and get the most out of your SharePoint investment.​

        

    Learn More >>

     Current Openings


    Looking for a career? We're on the lookout for fun, talented people to join our growing teams. If you're looking to progess your career, apply here:

    Openings >>

     

     

    Takes Place:
    Description: ​Softlanding Solutions Inc. is proud to appear on the PROFIT 500 annual list for the second consecutive year as one of Canada's Fastest-Growing Companies.

     Featured Solutions

    Connecting Talent and Resources for Better Performance

    Corix finds a scalable solution to communication issues and improves organizational performance in the process. Read more here

     

     Hidden Title

    Strategic IT to Support Organizational Change

    The BC First Nations Health Authority finds a strategic partner for a major transition, plus continued IT support for successful delivery of essential services. Read more here​. 

     

     


    Posted on:
    Categories: SharePoint
    Description: Updates to Lookup List rendering in SharePoint 2013, setting the selected value using jQuery requires updates from SharePoint 2010
    A client was recently migrating from SharePoint 2010 to 2013 and discovered some issues with a jQuery script. The purpose of the script was to set the selected value of a dropdown list with a value that was passed in from a query string. The dropdown list was a Lookup list. A quick google search brought up a number of helpful sites that explained in detail how to do this… In SharePoint 2010… Here's my favourite, Setting SharePoint Lookup Lists w/ jQuery (+/- 20 items)What Happens in 2013? It looks like how the Lookup list gets rendered in SharePoint 2013 has changed again. We no longer have to deal with the "do I have more or less than 20 items" issue. The rendering is the same regardless. For comparison, let's take a look…SharePoint 2010 (less than 20 items) SharePoint 2010 (20 or more items) SharePoint 2013 All this means is that you no longer need to check to see if there are more than 20 items in the Lookup list. But it also means that if you were doing this previously in SharePoint 2010, you will need to update your jQuery for 2013.Putting it Together Here is a sample jQuery function to set the selected value of a Lookup list function setSelectedValue(fieldTitle, lookupVal) $("select[title='fieldTitle']").val(lookupVal);


    Posted on:
    Categories: System Center;Azure
    Description: The latest version of System Center Endpoint protection (4.9.218.0 - March 8, 2016) has a bug in the included Powershell Module MpProvider.psd1 located in the default directory of C:\Program Files\Microsoft Security Client\MpProvider. This causes information for Operational Insights to be reported
    The latest version of System Center Endpoint protection (4.9.218.0 - March 8, 2016) has a bug in the included PowerShell Module MpProvider.psd1 located in the default directory of C\Program Files\Microsoft Security Client\MpProvider. The bug is currently a reference to a nested module that doesn't exist, if you attempt to import this module, you'll see the following. The reason this is so important, is that the Antimalware Intelligence Pack that comes down from the "Malware Assessment" solution in Operational Insights, requires access to this module in order to gather status information regarding signature dates, definitions, malware activity, etc. You can view the code that's run on any Operational Insight agents (or SCOM connected agents) that have the Antimalware Assessment solution configured here. http//systemcentercore.com/?GetElement=CollectAntiMalwareInformation&Type=Rule&ManagementPack=Microsoft.IntelligencePacks.AntiMalware&Version=7.0.10430.0 How this script works is by attempting to import the required module "MpProvider.psd1" to gather information regarding the status of SCEP. If the import was successful, the script will continue to run gathering information about SCEP. However, if the module fails to import, the script will fall back to gathering information about the "Malicious Software & Removal Tool". You can see this in the Operations Manager event viewer (Event ID's 9991-9993). These events will show the information that's gathered by the Malware Status collection scripts, which is also the actual information that's transmitted up to Operational Insights. The quickest fix for this bug is to simply modify the MpProvider.psd1 module and remove the portion highlighted in the top screenshot of this article 'MSFT_MpWDOScan.cdxml'. The reference to this cdXML does not existing in the "C\Program Files\Microsoft Security Client\MpProvider" folder on any client I've checked. You could push this updated module file out to affected clients using Group Policy Preferences, or simply wait for a fix from Microsoft (no ETA). Or, better yet Microsoft provided me with the missing module that you could deploy to the directory in question (attached at the bottom), both fixes will work. If we modify the module, then wait for the collection cycle to re-run (default hourly), you'll NOW see in the Event Log that proper SCEP information is gathered. This information will flow up to Operational Insights and can be seen by querying for "ProtectionStatusRank = 150". It may take some time depending on your data retention for the old "Not Protected" client information to age out and be removed from Operational Insights before everything reports correctly. Also, note that "Behavior Monitoring" in SCEP MUST be Enabled in your SCEP policies for Operational Insights to properly report healthy, protected SCEP clients. MSFT_MpWDOScan.cdxml