William Rendell

My 1st Swarm

admin — Thu, 10 May 2012 10:05:33 +0000

I have now only had my Bee’s for one week and I have already been asked to collect a swarm. The swarm had made its home inside a bird box that was outside, next to the kitchen window of a friend of mines parents. I waited until early evening before going to remove the bird box with the swarm in it. Everything went fine, you can see in the below photo, that I am just about to wrap up the bird box in a sheet to transfer the bee’s via a car to a hive owned by a friend of mine.

Collecting my first Bee swarm

The next photo is the Bee swarm in its new hive, there are in the hive on the left.

The hive on the left holds the swarm

I’ve been stung

admin — Sun, 06 May 2012 16:52:01 +0000

Today I got my 1st Bee sting, thankfully it did not hurt that much! In the photo below, you can see the little balls of pollen on the bee’s legs.

Below again is Olivia ready to take a look at the Bee’s with me

The Bee’s Day 2

admin — Fri, 04 May 2012 07:19:30 +0000

I have now transferred the Bee’s out of their traveling box and they are now in their own hive. The photos below were taken during the transfer process.

The Bee's in their traveling box

Me transferring a frame of bee's to their new hive

remaining frames left in travelling brood chamber

Bee's on front of hive

Max with a smoker at the front of the new hive

Ex2010 – Ex2003

admin — Thu, 03 May 2012 12:18:50 +0000

During as SBS2003 migration to SBS2011, while decommissioning the source server (SBS2003) before Exchange 2003 can be removed you will have to remove the routing group connector from Exchange 2003 and Exchange 2010. You can use the Exchange System Manager to remove the 2003 to 2010 connector. To remove the connector from the destination server 2010 to 2003 you will use the Exchange Management Shell using the below command.

Remove-RoutingGroupConnector -Identity “Exchange Administrative Group (FYDIBOHF23SPDLT)\Exchange Routing Group (DWBGZMFD01QNBJR)\DestinationServer to SourceServer” -DomainController DestinationServer.LocalDomain.local

Make sure you change the following first;

DestinationServer = name of new SBS 2011 Server

SourceServer = name of old SBS 2003 Server

LocalDomain.local = name of the local domain

The use of this code is done at your own risk.

the received certificate has expired

admin — Wed, 02 May 2012 10:28:03 +0000

When migrating a SBS 2003 server to SBS 2011 you may receive the error “The received certificate has expired” whilst migrating the public folders from Exchange 2003 to Exchange 2010, if you do follow the steps below.

To remove the SSL binding to an incorrectly published certificate

Navigate to the virtual root Exadmin in IIS.
Right-click Exadmin, click Properties, and then click Directory Security.
In the Secure Communications section, click Edit.
Clear the Require secure channel (SSL) checkbox.
If the Require 128-bit encryption checkbox is selected and is greyed out, perform these steps:
1. Select Require secure channel (SSL).
2. Clear Require 128-bit encryption.
3. Clear Require secure channel (SSL).
Launch the ADSI Edit tool from the Windows Support Tools. For more information about using the ADSI tool, see ADSI Edit (adsiedit.msc).
In the left pane, click Configuration, and then click each of the following to expand:CN=ConfigurationCN=ServicesCN=Microsoft ExchangeCN=
CN=Administrative Groups

CN=First Administrative Group

CN=Servers

CN=Protocols

CN=HTTP

CN=1

CN=Exadmin
Right-click CN=Exadmin, and then click Properties.
In the list of attributes, scroll down to msExchSecureBindings, select it, and then click Edit.
Select the entry :443:, click Remove, and then click OK.
Click Apply, then click OK.
Exit ADSI Edit.
Close and reopen Exchange System Manager.

This article is given as is and I will not be held liable for anything that happens to your system.

Day 1 with the Bee’s

admin — Tue, 01 May 2012 21:59:39 +0000

I got the Bee’s last night and transported them back to my house. The photo below shows the roof and stand from my hive. The grey box is a brood chamber that was used to transport the Bee’s in. This contains 7 brood frames, I may this evening transfer the Bee’s on the frames into my hive and add some additional empty frames to give the Bee’s some more room. There are some additional photos below of me putting together the additional frames (in the kitchen, sorry Elaine)

The Bee's first night in their new home

Frame Construction

Frame Construction part 2

A complete frame

Three complete brood frames for a national bee hive

The start of a journey

admin — Tue, 01 May 2012 21:46:46 +0000

I have always been interested in keeping bee’s more specifically the honey bee. After keeping chickens succsessfully over the last three years, I decided that i was at the right place in my life to start learning the art of bee keeping.

In the Autum of 2011, I took part in a day course, kind of like a taster session in keeping bees, with a theory based session in the morning, and a hands on session in the Aipary during the afternoon. The course was ran by Oaktree Cottage Apiary in a village called Flaxey in the Forest of Dean, Gloucestershire.

Following on from the day course I joind the Gloucestershire Bee Keepers Association – Cheltenham and Gloucester branch. I enrolled in their classroom based Winter course. The course is now complete, I now need a bee hive, a smoker, a hive tool, a bee suit and oh yes I almost forgot the most important thing, the Bees.

Batch file needs UAC

admin — Mon, 30 Apr 2012 14:28:09 +0000

I have a few batch files that run on a schedule, I have found though that they are not running properly? If I right click the batch file and run as administrator it works fine, after some research I came up with this.

set __COMPAT_LAYER=RunAsInvoker

I add this as the start of my batch files and now they run fine via the schedule. This seems to work on Windows 7 and server 2008, I will not take responsibility if this dopes not work for you.

Evenit ID 210

admin — Sun, 29 Apr 2012 16:26:44 +0000

You can increase the message size limit but I would strongly suggest you make sure you have the horsepower to do this or you WILL have performance issues trying to transfer large mail.

That being said, from the Exchange Powershell run the following

This command will display the current size

Get-ReceiveConnector | select identity, maxmessagesize

This will set the size to 50mb and the timout to 9 min.

Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 50mb -ConnectionInactivityTimeout 00:09:00

Then restart transport…

This will set all receive to 50 mb, use with caution!

Getting to Work

admin — Thu, 19 Apr 2012 08:50:33 +0000

Driving from Tewkesbury to Cheltenham is not so bad, a lot easier than these guys have to do to get to work!!