Archive for Servers – Page 2

MaxFocus RMM Dashboard SHA-2 Security Update Affects XP and Windows 2003 Servers

MaxFocus (formerly GFI) has announced that they will be upgrading all of their SHA-1 SSL certificates to SHA-2. This change may impact XP devices and Windows 2003 servers from connecting to the RMM dashboard, if they are not properly upgraded.

  • XP workstations must have Service Pack 3 installed
  • Windows 2003 Servers must have either KB 2868626 or KB 2918614 installed.

(Please note that Microsoft officially ended support for Windows XP and for Server 2003. As such we are providing this update in an advisory capacity, but cannot offer support with any installation issues of the patches on these endpoint devices.)

Splashtop Slow Screen Refresh to Servers

I stopped using LogMeIn during the past year due to their huge price increases. I have access to Teamviewer through MaxFocus for my managed customers. But I still wanted a remote connection solution for my other customers.

imageI eventually selected Splashtop Business, both for its ease of use and low price. It works great for what I need to do – quick remote access to a computer, supports multiple monitors, and has a built in file transfer capability.

I very rarely use Splashtop on a server, but I had need to do so recently due to an issue while reinstalling Teamviewer on an SBS 2011 server.

I connected fine, but the refresh rate of the video screen was horrible, and almost totally useless. I dug around and discovered that Splashtop requires more video memory than what most servers provide, due to the way Splashtop does it’s video refresh.

The workaround solution is to disable hardware acceleration (see Splashtop support article).

  1. imageRight click on an empty part of the desktop, then click Screen Resolution
  2. Click the Advance settings link
  3. Click the Troubleshoot tab
  4. Click the Change settings button, then move the Hardware accelerator to None
  5. Click OK, and close windows.
  6. NOTE: No reboot of the server is required.

However, there’s one problem: if Splashtop is not refreshing your screen properly, how do you do the above steps?

What I found that worked is that as I did each of the above steps, I immediately closed my Splashtop connection, and then reopened it, and found that the screen was at the next step.

One final note: Splashtop now has a newer solution that does not require turning off hardware acceleration. that involves installing a mirror driver. But this solution also requires you to reboot the server. I will try this out at a later time.

Windows 10 and SBS 2008 Remote Web Workplace RWW

Customer calls me today. One of his employees has Windows 10 at home, but is unable to remote into the SBS 2008 network at the office to access his office computer.

The error message looks something like this:

VBScript Remote Desktop Connection: The wizard cannot configure Remote Desktop Connection settings.  Make sure that the client version of Remote Desktop Protocol (RDP) 6.0 or later is installed on this computer.

Thanks to a post on the Microsoft forum, the resolution is fairly easy. It requires access to the server, but does not require rebooting the server.

Note: On the Windows 10 side, you need to make sure you are using Internet Explorer 11 (IE11) and not the new Microsoft Edge browser.

From the SBS server:

  • Navigate to this folder “C:\Program Files\Windows Small Business Server\Bin\webapp\Remote”
  • Locate and make a backup copy of the file tsweb.aspx
  • Edit tsweb.aspx and comment out the highlighted lined as shown below. (Note: to comment out a line, simply insert a single quote mark)
  • Open up Services (Start –> Run –> services.msc)
  • Locate Terminal Services and click to restart it.
  • It may prompt you that it must also restart an associated service, which you should approve.
  • That’s all that needs to be done on the server

From the home Windows 10 computer:

  • Open up Internet Explorer 11
  • Go to the URL you use to remote into the SBS 2008 server (e.g..,
  • Add the URL to Compatibility Settings (IE > Tools > Compatibility Settings > Add > Close)
  • Add the URL you are using to Trusted Sites (IE > Tools > Internet Options > Security > Trusted Sites)
  • Then close and restart IE 11

Give it a try!

Connector for Windows 10 to 2012 R2 Essentials Now Available

This information just came in today:

Windows 10 Client Connector for connecting to Windows Server 2012 R2 is now Released via Download Center

We have now officially released the Windows 10 connector for connecting to Windows Server 2012 R2 via Download Center. It is available from the following URL:

Please note: we do not have the fix for the auto-download and installation released yet. So you have to manually download and install this client connector on the Windows 10 client machine. Then you can run the client deploy to start the connecting.

For the servers in-place upgraded from Windows 7, 8.1 to 10,  you will need to manually download and install this client connector and do the connecting again.

If the machine ID is the same after the upgrade, then everything will be working automatically. However if the machine ID is somehow changed during the upgrade, then it will be treated as a new client, so you have to leave the domain and connect to the Essentials server again. The old client back up data will be in the archive folder on the Essentials server, and you can still use that to do the restore back to the upgraded Windows 10 client.

Client Connector Status of Windows 10 and Server Essentials 2012 R2

IMPORTANT NOTE:  The client connector to connect Windows 10 to Windows Server Essentials 2012 R2 is currently being tested and is not yet available.

Once this updated connector is released, a link to download it manually will be posted. Doing a manual download is a known issue that is expected to be resolved in the October 2015 timeframe.

Over the years Microsoft has released a family of server platforms for the home and small business environments – including Small Business Server (SBS), Windows Home Server (WHS), and Server Essentials.

One of the key parts to these products is the “client connector” which is run from a client workstation to properly connect it to the server, include it in the dashboard, setup appropriate security, and, where appropriate, configure the workstation for daily backup.

In advance of the release of Windows 10, the Microsoft support team has released a blog post with a matrix identifying the availability and any restrictions for the client connector for each server platform, against each supported client operating system (Windows 7, 8, 8.1, and 10).

Client Connector availability with Windows Home Server, Small Business Server and Windows Server Essentials for Supported Client OS

Will there be a Windows Server Essentials 2016?

imageWindows 10 for desktops and mobile devices is just around the corner.

That would be July 29th if you’ve been on vacation! –>

And … the next version of Windows Server will be Windows Server 2016.

The current version is Windows Server 2012, which includes a specific (post-SBS) version called Windows Server 2012 R2 Essentials.

So, it is only fair to have people ask: “Will there be also be a Windows Server 2016 Essentials (W2016E for short) released?”image

The following public Technet article mentions W2016E by name. So it would be a reasonable conclusion to think that they are planning on a W2016E version.

But — given that Server 2016 will not be rolled out until next year, things can always change.


Srv.sys warning on Windows 2012 R2 Best Practices Analyzer

Sometimes we freak out over every warning message that is displayed when we run Microsoft’s Best Practices Analyzer (BPA). In setting up a new Windows 2012 R2 server recently , BPA displayed a single warning:

Srv.sys should be set to start on demand

The BPA simply says that “Client computers will not be able to access file shares …”


The BPA simply says that “Client computers will not be able to access file shares …”

Wow, that sounds more like a major error waiting to happen! Why, then, is it just a warning? 

The answer is that SMB 1.0 protocol is not on by default for Windows Server 2012 R2. SMB 1.0 is required for Windows XP workstations to access file shares.

So you can safely ignore this error.

But, in the chance that you need the SMB 1.0 protocol running, you can do so very easily by opening an elevated command prompt on the server and typing in this command:

sc config srv start=demand

More information is included in this Microsoft Technet article:

Configure Ricoh Aficio MFP to Office 365 for Scan To Email

I recently migrated a customer from SBS 2008/Exchange 2007 to Office 365 with AppRiver and BitTitan’s MigrationWiz tool.

Migration went like a charm … that is, until one of the employees tried to “scan to email” a document from their Ricoh Aficio MP C2500.

A quick search of forums suggested that a lot of people had been down this road before, and with a myriad of possible ways to configure or fix it. Quite often, the suggestion was to use a 3rd party SMTP  service.

I submitted a ticket to AppRiver’s support at 11:57am this morning and received a phone call from their tech support within 15 minutes. A quick remote connect session, and we had everything working within minutes.

Here are my notes for future reference:

First, the solution we followed

Second, gather the following information

  • Your public IP address to your office. You can use if you don’t know it)
  • Your Office 365 MX record. It should look something like this:

Next, setup the Exchange connector within Office 365

  • Login to your O365 Admin Center portal (
  • Click Exchange –> Mail Flow –> Connectors
    • Create a new connector with this information
    • Enter a name for your connector, such as “Ricoh Copier On Prem”
    • From: select Your Organization’s Email Server
    • To: select Office 365
    • Description: enter something like this: This is the connector that will allow traffic from the SMTP services for Ricoh
    • Enable the option Retain Internal Exchange Email Headers
    • IP Address: enter your public IP address

Next, let’s go to the Ricoh web portal to finish things up:

  • Go to your Ricoh’s web portal (local IP address, such as
  • Click to login as the administrator.
    If you don’t know the login/password, here’s a web site that may help you:
  • Click Configuration => E-mail (under Device Settings)
  • Enter the following information as appropriate:
    • Your Admin O365 email address
    • Protocol: SMTP
    • SMTP Server Name: your O365 MX name you looked up previously
      (such as
    • Port: 25
    • SMTP Authentication: OFF
    • SMTP Authentication Email/Username/Password: your O365 Admin email address
    • SMTP Authentication Encryption: DISABLE

That’s all we did. Hope it works for you!

Support for Windows Server 2003 ends today

The end of an era occurs today when Microsoft officially drops extended support for Windows Server 2003.

This means that Microsoft will no longer issue security updates for any version of Windows Server 2003, which includes Small Business Server 2003, and Windows Home Server.


Samsung 850 EVO SSD crashes Windows 2012 R2 Server

I have personally used Samsung’s 850 SSD drives in a few workstations, and they appear to work great.

However, there are several recent posts of Windows 2012 R2 and 2012 R2 Essentials servers crashing. The common denominator? Samsung’s 850 EVO SSD drives.

One person wrote that a 2012 R2 Essentials server will produce 100% crashes. Any other 2012 R2 server will crash if the write cache is disabled, which happens when a server is promoted to a DC. Hopefully, it’s a firmware issue with those drives that Samsung can address. Also, the Samsung 840 SSD drives appear to work just fine, and does NOT cause similar crashes.

Here are some links for your further reading pleasure that identify the issues at hand: