Archive for SBS – Page 6

SBS is now WSSMB!

imageI have worked with the Microsoft Small Business Server (SBS) product line since 2001. The product itself goes back to the Windows NT era when it was called Microsoft BackOffice Server.

In 2004 I was honored to be designated as a Microsoft MVP (Most Valuable Professional) for the SBS product. This past January, my MVP status was renewed for a 10th straight year. It’s amazing, given the fact that I am one of

But recently Microsoft decided to shake things up a bit, and we were informed that there would be a “technical expertise name change” to our SBS MVP group.

Effective July 17th, 2013, the technical expertise Small Business Server will be renamed to Windows Server for Small and Medium Business. Please note this is a MVP Program expertise change only and has no impact within the product team structure.

And you know what? That’s fine with me.

Many people have been very disappointed over the fact that the SBS product, as we have known it, will not be continued. I’m not one of those people. I see this as an indication that things never remain the same. New things to learn; new skills to develop; new opportunities to do what I like to do – help businesses be more productive.

So, I am officially a WSSMB MVP (at least until my next review period at the end of the year).

Exchange 2010 Forms-Based Authentication Service Doesn’t Start

After installing or migrating to Exchange 2010, one of the first things I check out is Outlook Web Access (OWA). But more often than not, I’m unable to login to OWA.

If you have been working with Exchange 2010 this may be nothing new. But, I am seeing a last minute flurry of activity with installing or migrating to SBS 2011, and thought that a quick post might be beneficial.

The key is to check that all Exchange services that are set to Automatic have in fact started. Quite often you will find that on a reboot of the server that Microsoft Exchange Forms-Based Authentication Service is not running.

Having to remember to start it manually each time you reboot the server is not acceptable!

The solution to this issue is very simple:
Change the startup type for this service from Automatic to Automatic (Delayed Start).
Next time you reboot your server, you will find that this service is running.

image

Scheduling the WSUS Cleanup Wizard

I manage several SBS 2008 and SBS 2011 servers. One of the key maintenance issue is the size of the WSUS database. There are plenty of posts from people bemoaning the fact that suddenly the WSUS Content folder has grown to over 20gb (or more)!

WSUS provides an easy way to run the wizard manually. But doing this requires one to log into the server, and start up the wizard. Why do that, when you can schedule the wizard to run on a weekly basis?

Kudos to my good friend and fellow MVP’er, Kevin Royalty, for this information.

STEP 1 – Run the WSUS Cleanup Wizard manually

Before scheduling the wizard to run automatically, it is important to run the wizard manually first, especially if it has not been run in a long time. Do not be concerned if the wizard takes hours (literally) to run the first time. My fellow MVP’er, Philip Elder, blogged that he had one server required 36 hours to do the initial cleanup!!!

Review  my post for running the wizard manually.

image   image

 

STEP 2 – Create the WSUS Cleanup Batch file

  1. Go to the Codeplex site and download the WSUS Cleanup v2 tool (zip file)
    image     image
  2. Extract the files to your desired folder (C:\Scripts in my case). Three files are extracted.
    image     image
  3. You then need to create your own batch script/command, and documentation to do that is available from the Codeplex site
    – OR –
    Just download my script (WSUSCleanup.txt) and save it to your Scripts directory (be sure to rename it from WSUSCleanup.txt to WSUSCleanup.cmd)
    image

 

STEP 3 –  Schedule to run the batch file automatically

The only thing left is to schedule the task to run on a regular basis (perhaps weekly on Sunday mornings).

  1. Click Start –> Administrative Tools –> Task Scheduler
  2. Click Create Basic Task… from the right hand frame
  3. Type in a name (for example Weekly WSUS Cleanup)
  4. Click to run it weekly
  5. Click to run it every Sunday, and set your time (for example 9:00am)
  6. Click to ‘Start a program’
  7. Browse and locate your script (again, as a reminder, if you downloaded my script, be sure to rename the suffix from .txt to .cmd)
  8. Click to select (enable) the ‘Open the Properties dialog box …’ option, then click Finish.
  9. Click to select (enable) the ‘Run whether user is logged on or not’ option, then click OK
  10. You will be prompted to enter the appropriate user account information for running this task.
  11. I would suggest running the task immediately after creating it and monitor to make sure it runs successfully.
    image

Installing Network Printer to Windows Server 2012 Essentials

These are my abbreviated notes on setting up a network printer on W2012E, with both 32-bit and 64-bit drivers installed. My thanks to a fellow MVP’er, Robert Pearman, who did the real work and has it fully documented on his site (click here).

All steps take place on the Windows Server 2012 Essentials console. In my case, W2012E is running in a guest VM on a Windows Server 2012 Standard Hyper-V parent. I will be installing drivers for an HP LaserJet 4100 printer.

Section 1 – Prerequisites

  1. Go to your vendor’s web site and download the appropriate x86 and x64 print drivers. For my needs, I downloaded the drivers for Windows 7 (32bit) and Windows 2012 (64 bit).
  2. Next, extract the driver files to subfolders. In my case, the HP files I downloaded are self-extracting files. But be sure you uncheck the option to run the install immediately after extracting the files.
  3. Finally, before proceeding, make sure you know the IP address of your network printer.

Section 2 – Add the Network Printer

  1. Go to Control Panel –> View Devices and Printers (under Hardware)
  2. Click on Add a Printer. It will scan for new printers, and we should expect that it will not find any. 
  3. Click on The printer that I want isn’t listed link.
  4. On the next screen, click on the Add a local or network printer as an administrator link.
  5. The scan will run again, and (again) we will click on The printer that I want isn’t listed link.
  6. Select the Add a printer using a TCP/IP address or hostname option, then click Next.    
  7. On the next screen, enter the printer’s IP address in the Hostname or IP address field, and click Next.
    image
  8. Wait while Windows looks for the printer. If the printer has a built in network adapter, you should see an appropriate Printer Class Driver selected.
  9. However, in my case, the Laserjet 4100 is connected to the network via a D-Link print server adapter. Windows lists it as a generic network port and ask that I confirm that I had entered the correct IP address. Let’s click Next and it will rescan that IP address again.
  10. This time it will ask me to identify the type of printer. I scroll through and locate the HP Laserjet 4100 Class Driver
  11. Be sure to select Do not share this printer for now and click Next. We can share the printer later on.
  12. Press Finish.

Section 3 – Install the required Print Drivers

  1. Open up the Devices and Printers window, select your printer, and then click on Print server properties
  2. Click on the Drivers tab, and then click on Change Driver Settings. The window will refresh.
    == Install the x64 (64 bit) print driver ==
  3. Select the Printer we are installing, and then click Add.
  4. This will start the Add Printer Driver Wizard. Click Next.
  5. Select the x64 box (leaving the x86 box unchecked) and click Next
  6. Click Have Disk… and then click Browse… and locate the x64 print driver folder. For this HP printer, there was a list of .inf files available I followed Robert’s suggestion, and selected the first one in the list (immediately below the Drivers folder)
  7. I then select the HP Universal Printing PCL 6 driver, click Next and then Finish.
  8. But wait, we still have to install the 32 bit driver in a similar fashion!
    === Install the x85 (32-bit) print driver ===
  9. So repeat steps 3-7, but check the x86 box and install the x86 driver.

Section 4 – Change the Selected Print Drivers

  1. Return back to the Devices and Printers window
  2. Double click on your printer, and then double click on Customize your printer
  3. Click on the Advanced tab, and change the print driver to the one we just installed.
  4. If you wish, you can also click on the Sharing tab, and make the printer available.

SBSMonitoring Database is nearing maximum size

Chances are, if you have an SBS 2008 server, it is running very well. But this may lead you to become complacent in managing the server. For example, it is important that you run the SBS 2008 Best Practices Analyzer on your server on a regular basis. Whether that is monthly, or quarterly, run it!

On a recent SBS 2008 server that has been chugging along quite nicely, I discovered that BPA had not been run in quite awhile. When I did, I was greeted with this warning:

The SBSMonitoring database is nearing maximum size
The SBSMonitoring database is currently 3762487296 bytes in size

image

Wow, that’s nice … except for the fact that the warning message doesn’t tell you what to do to fix it or clean it up. It doesn’t even point you to a KB article.

The rest of this blog post identifies three different solutions to this problem.

 

Solution 1: KB 981939

If you do your due diligence in searching the web, you will come across Microsoft KB 981939. You can read through the KB article for the details, and you may want to give it a try.

When you run their PowerShell script, you may get an error about the execution of scripts. If so, simply type the following command at the PS> prompt:

Set-executionpolicy remotesigned and press Enter

But, wait — there’s a second solution!

 

Solution 2: Replace SBSMonitoring Database

If solution 1 fails, and you go back to search the Internet, you will discover a blog post from Third Tier titled: SBS 2008 Monitoring Database Fills to Capacity.

This solution has you replacing the current SBSMonitoring database with a new clean one. Only one problem: how many people keep a clean copy of their Monitoring database around???

No problem, there’s a third solution, which is the best!

 

Solution 3: Recreate the SBSMonitoring Database

Check out the SBS Blog site for How to Recreate the SBSMonitoring Database.

Simply download the provided zip file, extract the PowerShell script, start up an administrative PowerShell session, and run the script. Voila! It’s finished almost immediately.

image

All that is left is to rerun the BPA and verify that the warning message no longer appears!

Cheers!

Install Exchange 2010 SP3 on SBS 2011

Carl Gray (“Oxford SBS Guy”) has a very good, step by step blog on installing Exchange 2010 SP3 on SBS2011, including screen shots. So, there’s no need for me to replicate what he has already posted.

However, there are two critical steps he did not include:

    1. Before you start the SP3 upgrade, please go into Services and stop the Windows SBS Manager service.
    2. Please make sure that you DO NOT have Windows Management Framework (WMF) 3.0 installed on the server. Look for KB2506143. You will need to uninstall this patch and then reboot the server before you install the SP3 upgrade.

Susan Bradley has previously posted on both of these issues (see Stop SBS Manager and Uninstall WMF 3.0)

I also offer some additional advice to add to his process, which you may find helpful:

  1. When downloading the Exchange2010-SP3-x64.exe file, put it into an empty temp folder (say ..\Downloads\E2010SP3temp). Then when you double click on the .exe to extract all the files, it will extract the files to this same temp folder. Once the SP3 upgrade is completed, all you need to do for cleanup is to delete this one temp folder.
  2. I highly recommend that you make sure that you have a full, recent backup of your server before you start.
  3. I also recommend that you reboot the server BEFORE starting the upgrade process.
  4. If you are installing SP3 remotely (using RWA), be aware that you will lose your remote connection during this process. DO NOT PANIC. The SP3 upgrade will stop the RDP/Gateway service. Just be patient. Give the upgrade about 30-40 minutes to complete. Eventually you will be able to connect back in via RWA, and when you do, you should find that the upgrade has completed.
  5. If SP3 has been installed successfully, I would suggest rebooting the server again. It doesn’t hurt, and in some cases, it may help!
  6. Finally, Carl says to check that the version of Exchange is correct. Here is how I perform that step:
    1. Open up Exchange Management Shell
    2. Type the following: get-exchangeserver | fl name,edition,admindisplayversion
      image
    3. The build number for Exchange 2010 SP3 is: 14.3.123.4

SBS and Essentials Build Docs

For several years the SBS MVP’s have been maintaining several Wiki-type “build” documents for the SBS and Essential server platforms, including SBS 2008, SBS 2011 Standard/Essentials, Windows 2012 Essentials and Storage Server 2008 R2 Essentials!

image

These documents contain a wealth of real-world and time-tested hints and recommendations, collected from MVPs around the world. They contain information you need to know before, during, and after installing SBS or Essentials.

This link below will take you to the main page with links to each individual build document.

http://social.technet.microsoft.com/wiki/contents/articles/1710.small-business-server-documentation.aspx

Enjoy!

DISM for Windows Server 2008 R2 (64 Bit)

DISM is a command-line Microsoft tool for Windows 7/8/2008/2012. DISM stands for ‘Deployment Image Servicing and Management’. If you do a search for dism.exe you will find many posts of people using it to reduce the size of their WinSxS folder, especially after installing SP1. There is a 32-bit and a 64-bit version of this tool.

The actual command to do this cleanup is: dism.exe /online /cleanup-image /spsuperseded

So, you are sitting at the console of a Windows 2008 R2 x64 server, and you want to run this utility. Chances are, you will try to use the dism.exe that is listed inside the c:\Windows\SysWow64 folder.

However, if you do so, you may encounter the following error message: Error: 11 You cannot service a running 64-bit operating system with a 32-bit version of DISM. Please use the version of DISM that corresponds to your computer’s architecture.

image

In order to run this properly, you need to go directly to the native system folder to run this tool on a 64 bit system. Here are the steps:

  • Open command prompt window as administrator (‘Run as’).
  • Change directory by typing: cd \windows\system32
  • Run the command: dism.exe /online /cleanup-image /spsuperseded

This will take about ten minutes to run. Please note that even after the progress bar reaches 100.0%, the tool has not finished running. Do NOT close the command prompt window until you get the message “The operation completed successfully”.

image

What is the result of running this tool? I ran this on a Windows 2008 R2/SBS 2011 server, and it reduced the size of the WinSxS folder from 10.8GB to 7.37GB.

image   image

Not very drastic if you ask me. Not with today’s disk sizes. However, if you are running out of disk space on your server system drive, this might buy you some needed room!

Fix IE10 and SBS 2008 RWW error

You just upgraded your workstation to Internet Explorer 10. But when you try to remote into your SBS 2008 server, you get a “VBScript: Remote Desktop Connection” error message, like this:

image

The detail error message reads: 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.

 

Solution:

The solution is so easy, you probably will miss it. After clicking OK on the error window, click on the Compatibility switch icon image at the top of your IE10 window.

image

Your RWW login screen will refresh. Log back in and try connecting to the remote computer, and it should be working as expected.

N.B. It probably is incorrect to call this a “solution”, as it is more of a “workaround”. It’s not a bug with IE10, it’s that the decision was made that it’s acceptable to have a “workaround” rather than to fix IIS to flag compat mode from the server.

Case Study–Windows Server 2012 Essentials

My good friend and MVP buddy, Wayne Small of Australia, was the focus of a recent Microsoft case study on the features and benefits of implementing a mixed cloud/on-premise solution to customers.

The article details Wayne’s approach, using Windows Server 2012 Essentials (the follow-on product to the highly successful Small Business Server) and Office 365.

He explains how this winning combination helps to address the needs of many of his customers, and discusses the benefits of deploying Windows Server 2012 Essentials.

image

Congratulations, Wayne!