Monday, October 22, 2012

SBS2011 Changing your default website from remote.domain


Open the Server Console and on the Home screen select “Set up your internet address”:


“I already have a domain name I want to use”:



“I want to manage the domain name myself”:



Enter in your domain name and Select “Advanced Settings” below the domain name to open up the following:


In my example below I changed it to mail.


Select OK and Configure

Then confirm the wizard completes with no errors

Thursday, October 18, 2012

Brother MFC Get the most out of your Toner!


Here are the basics to get the most out of your toner:

Warning some of these settings and tips may void your warranty so “if you break it you bought it”

1) Replacement toner that is not new or a new official original replacement toner unit cannot reset the toner alert on the LCD. (if anyone knows a trick I don’t please post it)

2) Clean the corona wire whenever you replace the toner (green slide on the drum slide it back and forth a few times) (CAREFUL: only touch the outer plastic surfaces, oil from your skin can cause problems if you make contact with the toner and printer drum) (if you do make contact clean with a dry soft cloth immediately)

3) The toner alert will stop ALL printing if not set to “continue mode”. Always use Toner in the (Continue Mode) to use ALL of your toner. Each model’s menu may be a little different but you are probably looking for a “General Setup” “Replace Toner” setting in the menu. Option is usually “Stop” by default. “Continue” will let it keep printing. You’ll know when its time to replace when you don’t have full coverage.

4) Give it a gently rocking shake when it starts looking low. If any toner falls out clean it up with a soft dry cloth. If toner is dumping out do NOT install back in your printer.

5) If printer has an eco mode for printing. Unless you need the extra darkness of printing leave that on.

6) If you replace the drum with a NEW one reset it on the printer by opening the front cover, press clear with the cover open, and when the menu displays “new drum” select YES or NO as necessary. If you do this on an old Drum you can extend it’s life, however be careful as extra toner not fused to the paper floating around will cost more than a drum to clean up and repair.

7) Older toner cartridges have a clear cover on the left and right that is used by a sensor to determine if light passes through and thus indicating toner is low. This can be overridden by covering the senor with tape or filing in the clear cover with a black Sharpie.

Monday, October 15, 2012

SBS2011 Moving Data Paths and Logs


Open the SBS 2011 Server Console

Select Backup and Server Storage

Select Server Storage

Select the data you want to move using the tasks listed on the right as shown below:


WSUS the rest of the story….

After Moving WSUS using the menu above you will notice the C:\WSUS\SUSDB folder does not move.

You have to move this via SQL Management Studio

Login to server as an administrator.

Click Start/Programs/Microsoft SQL Server 2005

Right Click on /SQL Server Management Studio Express and select

Run As Administrator

Fill in the following information and then click Connect

  • Server type: Database Engine
  • Servername: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
  • Authentication: Windows Authentication

Note: If you didn’t “run as administrator” above you may see:

 "login failed" (Error 18456) error messages in SQL Server 2005

Expand Databases and right-click on SUSDB and select Tasks > Detach…

Select theDrop Connectioncheckbox and click OK.

Move C:\WSUS\SUSDB folder to the same location you moved your WSUS directory to above. for example:


To reattach the database, right-click on Database and select Attach

On the Attach Databases page select the Add button.

Browse to the new location of the SUSDB for example:


click OK twice to complete task

Moving IIS Logs: 

Open IIS7

Open each site and double click on the logging Icon


Create a new folder on the data drive or a drive with a lot more space.  Create a Logs\logfile folder

Change the path of the logfiles


Caution: The next step will take your web server offline for a minute or so

Once done right click and open a command prompt as administrator

type in and run “iisreset”    

It will restart IIS and update the paths and you can clean out the existing folders on drive C.

Credit: Michael Patrick

Friday, October 12, 2012

SBS2011 SharePoint 2010 Patch Installation follow up

In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:

1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

Note: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.

SBS2011 DistributedCOM 10016 System Event Fix

  1. Click Start, click Run, type Regedit on the Open box, and then click OK.
  2. Navigate to the following registry key: HKEY_CLASSES_ROOT\AppID\{61738644-F196-11D0-9953-00C04FD919C1}
  3. Right click on the key {61738644-F196-11D0-9953-00C04FD919C1} and choose permissions
  4. Click Advanced button
  5. Change to the Owner Tab
  6. Change the Owner to the Administrators Group be sure to check the box labeled “Replace owner on subcontainers and objects
  7. Once the Owner is changed, go back to the security tab and Grant the Administrators group Full Control
  8. Close Regedit

Use the following steps to grant the SPFARM account the local activation right.

  1. Click Start, click Run, type dcomcnfg in the Open box, and then click OK
  2. Expand Component Services, expand Computers, expand My Computer, and then click DCOM Config
  3. Right-click IIS WAMREG admin Service, and then click Properties
  4. Click the Security tab. 
  5. Under Launch and Activation Permissions, click Edit
  6. Click on the SharePoint Farm Account and check the box for Local Activation.
  7. Click OK and close out of the Component Services Utility.

SBS2011 Cleaning up Event Logs of False Alerts


Credit- Damian Leibaschoff and Justin Crosby

This process is actually quite easy to complete and will reduce the “what do you mean the error is normal” conversations with clients.

Installation and Usage

  1. Download and extract the SBSAlertsCleanup package which is hosted on the SBS Support Team’s SkyDrive.  (Kevin’s Note: When you extract it you will want to copy the files or rename the path with a shorter name (no spaces…) to make directory access easier in Powershell later in the steps)
  2. Open the location of the extracted files and then the properties of SBSAlertsCleanup.ps1 file.
  3. Unblock the file if the option is shown. Note: you do not need to do this to the .sql files.
  4. Launch an elevated PowerShell prompt.
  5. From PowerShell, browse to the folder where you extracted the files.
  6. From PowerShell, run:
    .\SBSAlertsCleanup.ps1 –Action install [enter]

You will see “Changed database context to ‘SBSMonitoring’

Listing current Exclusions

.\SBSAlertsCleanup.ps1 –Action ListExclusions

ID Event Source
-- ----- ------
1 129 WinRM
2 142 WinRM
3 4107 Microsoft-Windows-CAPI2
4 10016 DCOM
5 10009 DCOM
6 5586 SharePoint Foundation
7 6772 SharePoint Foundation
8 6398 SharePoint Foundation
9 8 MSExchange CmdletLogs
10 6 MSExchange CmdletLogs

Removing an Exclusion

This is a 2 part process, first you have to list the current exclusions, and then we can pick which one to remove.

.\SBSAlertsCleanup.ps1 –Action ListExclusions

ID Event Source
-- ----- ------
1 129 WinRM
2 142 WinRM
3 4107 Microsoft-Windows-CAPI2
4 10016 DCOM
5 10009 DCOM
6 5586 SharePoint Foundation
7 6772 SharePoint Foundation
8 6398 SharePoint Foundation
9 8 MSExchange CmdletLogs
10 6 MSExchange CmdletLogs

.\SBSAlertsCleanup.ps1 –Action RemoveExclusion –ID 1
Removing Exclusion for Source: WinRM, EventID: 129

To confirm:

.\SBSAlertsCleanup.ps1 –Action ListExclusions

ID Event Source
-- ----- ------
2 142 WinRM
3 4107 Microsoft-Windows-CAPI2
4 10016 DCOM
5 10009 DCOM
6 5586 SharePoint Foundation
7 6772 SharePoint Foundation
8 6398 SharePoint Foundation
9 8 MSExchange CmdletLogs
10 6 MSExchange CmdletLogs

Adding an Exclusion

This is a 2 part process, first you have to list the available instances of events that have already been collected, and then we can pick which one to exclude.

.\SBSAlertsCleanup.ps1 –Action ListEvents

ID Event Source
-- ----- ------
346141 11 Disk
349778 13 Server Infrastructure Licensing
349779 14 Server Infrastructure Licensing
349781 15 Server Infrastructure Licensing
349552 25 WindowsUpdateClient
349832 54 MSExchange OWA
349827 135 WinRM
349795 502 Windows Small Business Server 2011 Standard
349809 1000 Application Error
343153 1016 DhcpServer
342822 2002 ESENT
348341 2007 ESE
342823 2007 ESENT

Let’s say that the administrator was been receiving several events for WindowsUpdateClient 25 on a regular basis. The admin has investigated this event and determined that it is not cause for concern on their network and they would no longer like to be notified about this event. The admin can do the following to exclude this event from the report:

.\SBSAlertsCleanup.ps1 –Action AddExclusion –ID 349552

Adding Exclusion for Source: WindowsUpdateClient, EventID: 25

To confirm:

.\SBSAlertsCleanup.ps1 –Action ListExclusions

ID Event Source
-- ----- ------
2 142 WinRM
3 4107 Microsoft-Windows-CAPI2
4 10016 DCOM
5 10009 DCOM
6 5586 SharePoint Foundation
7 6772 SharePoint Foundation
8 6398 SharePoint Foundation
9 8 MSExchange CmdletLogs
10 6 MSExchange CmdletLogs
11 25 WindowsUpdateClient


Upon removing an exclusion or uninstalling the product, the process of collecting all events will resume and only after the event is experienced again it will then be collected and will appear on the report.

.\SBSAlertsCleanup.ps1 –Action Uninstall

Default set of exclusions

We install a set of common exclusions for known events that are generally considered as ignorable. This may not be the case for each and every server so you might have to tweak the list of exclusions, removing and adding as needed as to make your reports show relevant errors that could be of interest for someone administering the health of the server.

SBS 2008

  • 10016 DCOM
  • 10009 DCOM

SBS 2011 Standard

  • 129 WinRM
  • 142 WinRM
  • 4107 Microsoft-Windows-CAPI2
  • 10016 DCOM
  • 10009 DCOM
  • 5586 SharePoint Foundation
  • 6772 SharePoint Foundation
  • 6398 SharePoint Foundation
  • 8 MSExchange CmdletLogs

    6 MSExchange CmdletLogs

  • Wednesday, October 10, 2012

    Windows 8 using VSphere client unable to access console

    Windows 8 does not appear to be able to use ESX5.0 VSphere client to access the console. I received the error:

    “The VMRC Console has disconnected… attempting to reconnect”

    I tried reloading client…, but no joy. It appears from the articles I found it is related to IE 10. I ended up using the following to gain console access:

    You will however still want to use the VSphere Client for most, if not all, other administrative needs.

    Monday, October 8, 2012

    VMWare View 5.1 Certificate Installation Guide


    Most of what you need to know can be found here:

    This is the rest you need to know:

    I would recommend using a wildcard certificate for your servers otherwise you will need a separate certificate for each server.

    Here is an example of a 2048 key wildcard for’s


    Signature="$Windows NT$"
    Subject = "CN=*,, O=Oppihle, L=Louisville, S=Kentucky, C=US" ; replace with the FQDN
    KeySpec = 1
    KeyLength = 2048
    ; Can be 1024, 2048, 4096, 8192, or 16384.
    ; Larger key sizes are more secure, but have
    ; a greater impact on performance.
    Exportable = TRUE
    MachineKeySet = TRUE
    SMIME = False
    PrivateKeyArchive = FALSE
    UserProtected = FALSE
    UseExistingKeySet = FALSE
    ProviderName = "Microsoft RSA SChannel Cryptographic Provider"
    ProviderType = 12
    RequestType = PKCS10
    KeyUsage = 0xa0
    OID= ; this is for Server Authentication
    ; SAN="dns=FQDN_you_require&dns=other_FQDN_you_require"

    Note: SAN listed above is DNS SAN (Subject Alternative Name) not storage SAN

    When you import your certificate onto your servers into the personal certificates you need to change the general name properties to “vdm” if you have an existing already named “vdm” rename it “oldvdm”

    Then restart view services and confirm it is working properly