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
My fellow MVP, Robert Crane, is offering a free 23 part SharePoint Online training course via email. The link to get this free training is here – https://investable.leadpages.net/gs-spo/
Here’s a great resource – powershell.office.com
Are you an Office 365 IT administrator who is new to PowerShell? Are you looking for an Office 365 admin tool to automate repetitive administrative tasks? Or perhaps you are looking to access additional capabilities that aren’t available in the Office 365 Admin Center? Then PowerShell for Office 365 is for you.
For those using Exchange on-premises (including SBS 2011), here are some best practice recommendations from the Exchange Team.
In a nutshell,
- Deploy supported operating systems, clients, browsers, and exchange versions
- Test everything by disabling SSL 3.0 on Internet Explorer
- Disable support for SSL 3.0 on the client
- Disable support for SSL 3.0 on the server
- Prioritize TLS 1.2 ciphers, and AES/3DES above others
- Strongly consider disabling RC4 ciphers
- Do NOT use MD5/MD2 certificate hashing anywhere in the chain
- Use RSA-2048 when creating new certificate keys
- When renewing or creating new requests, request SHA 256-bit or better
- Know what your version of Exchange supports
- Use tools to test and verify
- Do NOT get confused by explicit TLS vs. implicit TLS
- (For now) Wait to disable TLS 1.0 on the Exchange server
The Essentials Server team have just published a blog post which gives you an at-a-glance look at what features are supported and not supported with the six current (and recently past) SBS and Essentials SKUs.
Read the blog post 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
One of the most popular posts on this blog has been the blog on setting up an Internal SMTP Service for SMBs that need to send server reports and support emailing from Internal devices that have move to cloud based email services.
One of the issues with this service is that is occasionally stops. There does not appear to be any reason why it stops, but it does. Restarting the SMTPSVS service does not restart the service, because it is based on IIS6.
Good news! You can use powershell to script the restart of this service.
Open an Administrative PowerShell window.
To Start the SMTP Virtual Server, type the following:
$SMTP.ServerState = 2
To Stop the SMTP Virtual Server, type the following:
$SMTP.ServerState = 4