Select Page

Author: admin

NoSQL versus SQL

Already this post has started out like many other posts comparing NoSQL to SQL, pitted against each other.  So let’s change that.  The new title of this post is: NoSQL and SQL! What is NoSQL? There are two types of NoSQL: The original NoSQL, which has been around for about two decades and is a relational database, does not use the Structured Query Language (SQL). The recycled NoSQL, which comes in a variety of flavors, vendors, and either uses SQL, does not use SQL, can use SQL but does not prefer SQL, is relational or isn’t rational, and so on.  It’s new technologies borrowing an already taken moniker.  A better name might be just calling each technology what it is instead of trying to lump them together, i.e. MongoDB, Cassandra, Riak, etc. They are two different types of tools and one or the other or both can be used in the same environment to perform different tasks.  Let’s look at storing data to highlight a major difference. Data Design in SQL and NoSQL A SQL database, such as MySQL or MS SQL, traditionally stores information in tables, rows, and columns you determine during the design phase.  You end up with small, “virtual spreadsheets” that are inter-related to each other through unique identifiers.  The data going into the spreadsheet must fit the constraints of the design of the column the data is going...

Read More

Exchange: Find and Remove Emails

Scenario For whatever reason, management or enterprise security comes to you and says they need an email removed from all users who received it.  No one knows who all received it.  Luckily, your organization has an Exchange server that makes this easy to do and in a short time, depending on how specific your query below is. Get-Mailbox and Search-Mailbox with -DeleteContent You will use two commands to get a list of mailboxes and search the subject, body, or several other attributes for the string that uniquely identifies the email.  You can use * as a wildcard before and after the text as seen in the example below.  When using the wildcard, be cautious to be very specific and avoid strings that would cast too big of a net.  For example, I would probably never use -SearchQuery ‘Body:”*a*”‘ as that would delete every email that contained the letter “a” in the body.  If you believe the email has been forwarded or replied to and you are searching by Subject, adding the * wildcard before the string you are searching for in the Subject will help find emails even with multiple FW or RE strings prefixed. Login to your mail server.  Open a PowerShell session with administrator privileges. Add-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.E2010 Get-Mailbox -ResultSize Unlimited | Search-Mailbox -SearchQuery ‘Subject:”*Text that needs to be removed*”‘ -DeleteContent | Where-Object {$_.ResultItemsCount} > filename_to_save_results_into.txt For a list...

Read More

OpenType Font Driver Vulnerability – CVE-2015-2426

Microsoft has identified a vulnerability which impacts all versions of Microsoft Windows which could allow remote code execution if a user opens a specially crafted document or visits an untrusted webpage that contains embedded OpenType fonts. For Home Users and Organizations without Dedicated IT Staff If you do not have automatic updating enabled, go to Windows Update, download and install updates.  If you have automatic updates enabled, no action is necessary.  It’s that easy. For IT Professionals This small update requires a reboot so please plan accordingly. Executive Summary This security update resolves a vulnerability in Microsoft Windows. The vulnerability could allow remote code execution if a user opens a specially crafted document or visits an untrusted webpage that contains embedded OpenType fonts.This security update is rated Critical for all supported releases of Microsoft Windows. For more information, see the Affected Software section. The security update addresses the vulnerability by correcting how the Windows Adobe Type Manager Library handles OpenType fonts. For more information about the vulnerability, see the Vulnerability Information section. For more information about this update, see Microsoft Knowledge Base Article 3079904.Suggested actions. The majority of customers have automatic updating enabled and will not need to take any action because the update will be downloaded and installed automatically. Customers who have not enabled automatic updating, or who install updates manually, can use the links in the Affected Software...

Read More

Lync 2013 to Skype for Business 2015 Enterprise Edition Upgrade

The following are my notes from recently upgrading Lync 2013 Enterprise Edition to Skype for Business 2015 Enterprise Edition.  Our production environment consisted of all Microsoft Server 2012 R2 virtual servers running in a VMware environment.  Our database back-end servers are Microsoft SQL Server 2012. Pre-requisites Ensure all servers are fully patched up.  I ran updates July 16th, 2015 after Patch Tuesday and the servers running IIS 8+ were still needing the hotfix outline here (https://support.microsoft.com/en-us/kb/2982006). Edge Servers Install Microsoft .Net Framework 3.5 if you have not already.  You may also check for updates after you install .Net 3.5 as there will be updates available.  However, these updates will not prevent the successful installation of Skype for Business 2015. Front-end Servers, Persistent Chat, File Stores, Database Back-ends No additional installs. Connect to computer in the topology that does not have Lync OCSCore or any other Lync components installed. I used a database back-end.  If you try this from a computer in the topology, you will get this error message: You cannot perform this upgrade until you have used Skype for Business Server 2015, Topology Builder to upgrade the Lync Server 2013 Pools and then publish the upgraded topology. If you have already published an updated topology those changes might not have replicated to this computer. You can force an immediate replication by running the Invoke-CsManagementStoreReplication cmdlet. You can also...

Read More

SharePoint 2013: Trouble Reaching Server

The issue: In SharePoint 2013 on a Windows Server 2012 R2 web server, when trying to add a domain user to a group or permissions, you receive the following message, “Sorry, we’re having trouble reaching the server.”  You may have noticed this when trying to add users as farm administrators. Possible causes: 1: The server does not have enough resources to process the function without timing out. Verify you have the resources below (Source: http://technet.microsoft.com/en-us/library/cc262485.aspx). Installation Scenario Deployment type and scale RAM Processor Hard disk space Single server with a built-in database or single server that uses SQL Server Development or evaluation installation of SharePoint Server 2013 or SharePoint Foundation 2013 with the minimum recommended services for development environments. For information, see Minimum recommended services for development environments. 8 GB 64-bit, 4 cores 80 GB for system drive Single server with a built-in database or single server that uses SQL Server Development or evaluation installation of SharePoint Server 2013 or SharePoint Foundation 2013 running Visual Studio 2012 and the minimum recommended services for development environments. For information, see Minimum recommended services for development environments. 10 GB 64-bit, 4 cores 80 GB for system drive Single server with a built-in database or single server that uses SQL Server Development or evaluation installation of SharePoint Server 2013 running all available services. 24 GB 64-bit, 4 cores 80 GB for system drive Web server or...

Read More