Today, MIcrosoft announced the availability of a single update rollup package for Windows 7 SP1 and Windows Server 2008 R2. Some details for the rollup are as follows:
- All security and non-security fixes since the release up to April 2016.
- One installation package.
- Optional install – not offered via Windows Update.
- Monthly rollups after April 2016.
- Security bulletins will continue to link to a direct update.
- For Windows 8.1, Windows Server 2012, and WIndows Server 2012 R2, there will be monthly rollup updates.
Thanks, Microsoft, for listening!
To get the rollups, you need Internet Explorer 6 or higher (not Edge – since this is not an update package for Windows 10). Get the updates here – http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3125574
At this stage, other browsers are not supported, although Microsoft have hinted that the site will be updated in the next few months.
I received an email from Microsoft this morning, presenting me with the 2016 Microsoft MVP Award. This is the 7th time I have received this award. I’m glad that I have been able to make a difference in enhancing and enriching the IT experience for Small and Medium Businesses. Here is a snippet from the email.
Dear Boon Tee,
Congratulations! We are pleased to present you with the 2016 Microsoft® MVP Award! This award is given to exceptional technical community leaders who actively share their high quality, real world expertise with others. We appreciate your outstanding contributions in Cloud and Datacenter Management technical communities during the past year.
The Microsoft MVP Award provides us the unique opportunity to celebrate and honor your significant contributions and say “Thank you for your technical leadership.”
Community & Advocacy Programs
I just spent the weekend working performing some SBS to Office 365 migrations.
Here are some useful links that make the process a whole lot easier.
Export mailboxes to PST for Exchange 2010 (SBS 2011 Standard)
Export mailboxes to PST for Exchange 2007 (SBS 2008)
Import PST files to Office 365
Enabling Autodiscover for Outlook in SBS Exchange Environments
Getting Outlook 2007 and Outlook 2010 to work with Office 365
- The following link lists the minimum requirements needed to quickly get your Outlook desktop client running with Office 365.
- With SBS 2011, it is necessary to remove the Service Connection Point (SCP)
- Show SCP information: Get-ClientAccessServer | Select Name, AutoDiscoverServiceInternalUri
- Remove SCP information: Set-ClientAccessServer -Identity “[Servername]” -AutoDiscoverServiceInternalUri $NULL
Importing LegacyDN information
Problems connecting Outlook to Office 365
AND if you happen to still be using SBS 2003 (I certainly hope not!), you can use Exmerge or Outlook to output individual mailboxes to PST. Do it soon!
It’s time to remind everyone again. Malware, Crypto Viruses and all kinds of nasties are still out there, and pose a bigger threat than ever.
Check out this latest ransomware variant – https://blog.knowbe4.com/its-here.-new-ransomware-hidden-in-infected-word-files
And from TrendMicro – http://blog.trendmicro.com/trendlabs-security-intelligence/recent-crypto-ransomware-attacks-a-global-threat/
And Sophos: The current state of ransomware – https://blogs.sophos.com/tag/ransomware/
Here’s a reminder from way back in 2012 on how to detect and identify these viruses when they pop up in your mailbox.
- DO NOT OPEN ZIP ATTACHMENTS.
- DO NOT OPEN ATTACHMENTS. Right click and save them to a temporary location on your computer, and check it out before opening it.
- DO NOT CLICK ON LINKS IN EMAILS. Hover your mouse over the link and be absolutely sure it is a legitimate link before you click on it.
- REVIEW THIS BLOG POST. Again. http://blog.powerbiz.net.au/security/how-to-detect-and-deal-with-malicious-email-viruses/
Microsoft have finally put up a webpage to document what has been changed in each build of Windows 10 when the operating system is released.
Since the initial release of Windows 10, two updates have occurred. The details of each update have been documented here – http://windows.microsoft.com/en-us/windows-10/update-history-windows-10
Microsoft released a bad patch on 9 December 2015, which caused Outlook 2010 to run only in Safe Mode. The fix for this is to uninstall the patch. Microsoft has already pulled this patch and is likely to release it again at a later time. I would suggest waiting at least a week before reinstalling this patch.
To fix this issue, perform the following steps to uninstall the bad patch.
- Close Outlook and All Microsoft Office Programs
- Open Control Panel
Click on Programs. (Alternatively, you can search for View installed updates in the search bar at the top right corner of the Control Panel)
Click on View Installed Updates
Scroll down to the Microsoft Office 2010 section, and look for Update for Microsoft Outlook 2010 (KB3114409) 32-Bit Edition (or 64-Bit Edition).
Click the Uninstall button
The patch will be uninstalled
When the patch is uninstalled, click OK and close the Control Panel
A “new” feature in the latest cumulative update for WIndows 10 automatically sets the default printer to the last used printer. This setting is turned on by default. This means that every time you use a printer, this printer becomes the default printer for the system.
While this might be a nice feature to have, it can potentially cause a waste of paper and some potentially “difficult” situations when documents are unwittingly printed to the wrong printer. ie, that receipt for the surprise birthday gift, or the 100 page draft document that was supposed to be printed to the paper optimiser print driver.
Fortunately, we can turn off this setting.
- Open up Printers & Scanners. Tip: Click on the Start Menu, and type “Printers & Scanners” in the search box.
- In the Printers & Scanners settings page, turn off the setting “Let Windows manage my default printer“.
The Essentials Server team have released a blog post to highlight which client versions are supported on currently supported Windows Server Essentials and Small Business Server 2011. The blog post can be read here – http://blogs.technet.com/b/sbs/archive/2015/07/23/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os.aspx
Basically, if you need to connect a Windows 10 client to Windows Server Essentials 2012 R2, which is probably the most common scenario, you will need to perform a manual client connector installation. A fix for the server is scheduled to be released on 17 November 2015.
Another common scenario would be the joining of the client connector for a Windows 10 client to Small Business Server 2011. In this case, 2 lines need to be added to the XML file on the server, which is located at C:\Program Files\Windows Small Business Server\Bin\WebApp\ClientDeployment\packageFiles\supportedOS.xml. Add the following 2 lines.
<OS Architecture="9" RequiredProductType="1" RequiredSuite="" ExcludedSuite="512" SPMinor="" SPMajor="" Build="10240" Minor="0" Major="10" Name="Windows 10, AMD64" id="9"/>
<OS Architecture="0" RequiredProductType="1" RequiredSuite="" ExcludedSuite="512" SPMinor="" SPMajor="" Build="10240" Minor="0" Major="10" Name="Windows 10, x86" id="10"/>
Check out the list and remove them off your iPhone or iPad immediately. http://www.redmondpie.com/xcodeghost-malware-list-of-infected-ios-apps-that-you-should-delete-right-now/
- Angry Birds 2 (Chinese App Store only)
- Card Safe
- China Unicom Mobile Office
- CITIC Bank move card space
- Didi Chuxing
- Eyes Wide
- Freedom Battle
- guaji_gangtai en
- Guitar Master
- Hot stock market
- Jane book
- Lazy weekend
- Mara Mara
- Marital bed
- Microblogging camera
- nice dev
- OPlayer Lite
- Pocket billing
- Poor tour
- Railway 12306
- Stocks open class
- Telephone attribution assistant
- The driver drops
- The Kitchen
- Three new board
- Watercress reading
- WinZip Sector
- WinZip Standard