Yeah… sure

yeahright

Amy brought this up in tonight’s Ransomware webcast.  Never download an update to a flash player if you are on a site that alerts you to an update.

A follow up article that folks might be interested in — but with a more consumer slant — is here http://windowssecrets.com/top-story/how-to-defend-yourself-from-ransomware/

2015 Microsoft MVP Virtual Conference

MVP15_MicrosoftMVP_VC_WebTile_Speaker_160x160px

Coming up in May I’ll be talking about two topics on security.  The first is about….

Understanding Windows updating

Every month the largest cloud service in the world updates and services the largest number of Systems. Find out how Windows update works, how to understand its cryptic error messages, how to prevent failures and learn about upcoming changes in Windows 10 and how it handles Windows updates

 

I’ll also be talking about

Ransomware – Key tools for prevention and recovery

I’ll be discussing ways you can prevent, defend, and minimize the damage of the various infections that want to hold you and your data hostage.

To sign up for this free conference – click here:  http://mvp.microsoft.com/en-us/VirtualConference.aspx

Registration opens up April 6th.

Windows Server Backup doesn’t start after you perform a BMR in Windows Server 2012:

To   Windows Server Backup doesn’t start after you perform a BMR in Windows Server 2012: https://support2.microsoft.com/default.aspx?scid=kb;en-us;2961238 Consider the following scenario:

  • You have a computer that’s running Windows Server 2012 or Windows Server 2012 R2.
  • You’re using a UEFI system with two hard disks, and you have EFI System Partition on your system disk.
  • You use Windows Server Backup to perform a complete backup.
  • You then use the backup data to perform a bare metal recovery (BMR).

However, after the recovery operation is completed, the Windows Server Backup service cannot be started. To resolve this issue, Windows Backup must rebuild the catalog to reflect the latest disk configurations. To trigger this action, follow these steps:

  1. Open an administrative command prompt.
  2. Run the following command:
    wbadmin delete catalog
  3. Restart the Windows Server Backup service, or restart the computer.

The Windows Server Backup service should now run normally. Someone in the past year has hit this and I remember them telling me about this issue.

New puppy in the family

RemiFullSizeRender

This is a image of my new baby, he’s called Remi.  He’s about another pound in size now from when this photo was taken :-)

 

MS15-010 and it’s impact on Essentials

essentials

http://blogs.technet.com/b/sbs/archive/2015/03/13/the-ms15-10-security-update-for-windows-server-2012-r2-essentials-and-the-client-restore-functionality.aspx

Just a heads up – it looks like the eta for this fix will be in the May time frame.

Until then bare metal restore still works, or you will need to uninstall those security updates noted.

Essentials Server 2012 R2 issue with restore console after March updates

First reported last month due to the other font patch KB..

The MS15-10 Security Update for Windows Server 2012/R2 Essentials and the Client Restore Functionality – The Windows Server Essentials and Small Business Server Blog – Site Home – TechNet Blogs:
http://blogs.technet…ctionality.aspx <http://blogs.technet.com/b/sbs/archive/2015/03/13/the-ms15-10-security-update-for-windows-server-2012-r2-essentials-and-the-client-restore-functionality.aspx>

Now it’s repro’ing again with this month’s updates.  Obviously the code that the Essentials doesn’t like is now in core windows updates.

“Just as an additional data point I can confirm that on both of my Windows 8.1 Pro systems (one 64-bit and one 32-bit) it is necessary to uninstall 3023562, and only 3023562, in order to eliminate the crash whilst running the Windows Server 2012 R2 Essentials client restore wizard. I only have the one Windows 7 Pro system and on that I need to remove all four of the updates (3023562, 30135131, 3033929 and 3046049) in order for the client restore to work, irrespective of what various knowledge base entries say about one update replacing another. All of the systems involved are domain joined.”

http://homeservershow.com/forums/index.php?/topic/8906-problems-restoring-files-from-client-backup

PDFs keeping you folders locked from editing?

We’ve been suffering from an issue where PDF files will ‘hold’ the folder open and we can’t rename folders when we want to.  In googling up the problem, we aren’t alone.

This appears to be the fix at this time — mind you — we’ve seen this on any version of servers and any version of workstations so it doesn’t appear to be related to any particular SMB version.

Turn this off by going to ORGANIZE > FOLDER AND SEARCH OPTIONS >VIEW (tab) … and then tick “Always show icons, never thumbnails“. Click Apply/OK and you’re done.

 

 

Fixing up WSUS on SBS 2011-

If you have Windows 8.1 or server 2012 R2 machines behind a WSUS 3.0 (SBS 2011) you’ll need to do two things to ‘fix’ it up.

Thing one.  Run a SQL script to make the machines not be listed as Windows 6.

The key steps are here:

http://community.spiceworks.com/topic/405248-windows-8-1-shows-as-windows-6-3-in-wsus?page=1

Launch SQL manager with a run as command.

Enter \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query to get into the WSUS SQL database.

Now open a SQL query window and cut and paste the following:

UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]
SET [OSDescription] = ‘Windows 8.1′
WHERE [OSMajorVersion] = ‘6’
AND [OSMinorVersion] = ‘3’
AND [OldProductType] = ‘1’
AND ([OSDescription] <> ‘Windows 8.1′ or [OSDescription] IS NULL)

Choose the SUS database and click on execute.  It should say that it worked on 2 rows.

Now do the same for the following commands:

UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]
SET [OSDescription] = ‘Windows Server 2012 R2′
WHERE [OSMajorVersion] = ‘6’
AND [OSMinorVersion] = ‘3’
AND [OldProductType] <> ‘1’
AND ([OSDescription] <> ‘Windows Server 2012 R2′ or [OSDescription] IS NULL)

Next ensure you have the following hotfix installed:

http://www.microsoft.com/downloads/details.aspx?FamilyID=ea69c31b-d53d-456f-9385-84b02127632f

You’ll need to reboot the server.

Now got to the Windows 8.1 and 2012 r2 machines that may be having difficulty checking in with the server and delete the software distribution folder (it’s located under c:\windows).  You may need to reboot the Win8’s or turn off the Windows update service.

Now your 8.1 should list themselves as 8.1’s in the WSUS gui.

Helping out Handy Andy

I keep forgetting to post this, and it’s also a reminder to myself to go get my credit card out and donate.

http://www.gofundme.com/mc64ns I remember the first time I met Handy Andy in person, it was back in Charlotte, North Carolina and he happed to be at the North Carolina Microsoft office for Exchange training.  We happened to know that like a day later he would officially be a SBS MVP so we convinced him to ditch the Exchange training and come with us for SBS training.

Andy is one of those guys that is everywhere and into everything.  He may not be up front in front of the crowd, but he’s in the background organizing everything.

So here’s to beating this thing and helping him beat not only the disease but the financial worry as well.

So I’m going to donate right after I post this, I’ll urge you to do so as well!

Heads up on issue with client backup on Essentials r2

http://homeservershow.com/forums/index.php?/topic/8906-problems-restoring-files-from-client-backup/

After installing KB3023562 [MS15-010 – the OTHER font update in this month’s kernel update bundle] update on the clients, Essentials R2 fails on restoring a client backup.

Alerting Microsoft/in the process of opening up a support case, but if you are running Essentials or Essentials role on 2012 R2 – be aware with a reported side effect with KB3023562 installed on the clients.  Removing that update from the clients (currently reported on 7 and 8.1) will make the client restore work again.

Remember that the OTHER font update – 3013455 is causing font corruption issues with Vista/Server 2008/Windows 2003 and obviously XP POS systems.  Microsoft knows about that issue and is investigating a better solution for those platforms.