Here’s an excerpt:

About 55,000 tourists visit Liechtenstein every year. This blog was viewed about 240,000 times in 2012. If it were Liechtenstein, it would take about 4 years for that many people to see it. Your blog had more visits than a small country in Europe!

Click here to see the complete report.

I’ve loved LG equipment for years. Every time I’ve replaced an optical drive its been with an LG drive, I’m on to my second LG washing machine and I’m on to my 4th Generation of LG monitors.

The Blu-Ray player in the lounge is LG and after a major fallout with Sky, who are no longer going to be receiving £50 of my money every month, I decided to go down the Freeview route.

My love of LG I didn’t even look anywhere else, I knew what I wanted and that seemed to be presented in the form of the LG HR650 which is a dual tuner Freeview player with 500GB hard disk and a 3D Blu-Ray player. But not only that. It has built in wifi which gives access to web based video resources as well. Sounds awesome…..I bought one.

That was Thursday. It’s now Monday and it’s going back tomorrow. It would be going back today if it hadn’t been a bank holiday!

It’s awful! It jumps, so if you are watching someone running they pretty much skip across the screen because of the missed frames.

When someone is talking it looks like its been badly edited with pixels around the edge of their mouth.

Sounds like a signal problem? That’s what I thought….unfortunately not…Jonny English DVD was even worse….and I don’t mean the film!

And then…to make matters even worse….if they weren’t bad already….I setup to do some recording. It fails. I suspect because it pops up with a message asking you to confirm you actually want to record it. OF COURSE I DO! I ASKED YOU TO!

Sadly, this is not the end of my breakup with LG, it continues….it has crashed 3 or 4 times to the point where it’s needed to be starved of power to regain any sort of usability.

This is one very upset LG fan. Such is my fallout I haven’t even considered a replacement unit. It’s going back for a refund. I’ve ordered a Panasonic instead.

One of the things I’d like to be able to offer the students and teachers is the ability to select between a Mac or Windows desktop. More for educational purposes than anything else.

For some reason Apple have decided that I can only run OSx Virtual Desktops on Mac hardware.

VMware have on their supported hardware list the XServer 3.1 which is no longer available.

I have a 6 cluster HP DL380 ESX setup, I don’t want a Mac server. But I want the ability to use Mac Virtual Machines.

I think this is very short sighted of Apple and is closing the door on a whole host of future Apple users.

Unless of course…there is information out there that isn’t readily available that explains how to achieve this? I reserve the right to be wrong

If I’m not wrong, and you are also looking for this functionality then lets vote here, post this page wherever you can and see if we can get noticed!

It’s a win win for Apple and us. They receive revenue for the licensing, a whole host of future apple users (I have 1800 students at the school where this would be used) and we get to show the students another OS, benefit from being able to use Apple only products and features.

What’s not to like?! Come on Apple!!! sort it out!!

When migrating from SBS2008 to SBS2011 I have come across this issue a number of times now and each time I seem to get caught up in the moment and try to find another way of resolving this issue.

Lot’s of posts about this being a 3rd party connector that has been setup for a photocopier or mail service of some sort etc etc.  None of which is correct.

It’s plain and simple, this is a foreign connector in SBS 2008, and contrary to other posts, it does seem to be there by default, I have checked vanilla SBS 2008 installs and those that have been migrated. I even installed a fresh SBS 2008 in to a virtual machine and it was there too.

This can be confirmed by launching the Exchange Management Shell and running Get-ForeignConnector and if you want more details run Get-ForeignConnector | fl

It’s also part of the Migration guide from SBS 2008 to SBS 2008.

It’s purpose…to receive email addressed to companyweb.  If you check the Exchange Management Console on an SBS 2008 server you will see it listed under Organisation Configuration > Hub Transport > Remote Domains you will see the Windows SBS Company Web Domain.  This is the matching address space.

The purpose…to drop any emails destined for companyweb to a folder ready for pickup by Sharepoint.  By Default this will be C:\Inetpub\mailroot\drop

This functionality is not available in SBS 2011 (or isn’t as far as I can tell) therefore before migration you will need to remove the foreign connector.

To do this, run the following command Remove-ForeignConnector –Identity “Windows SBS Company Web Connector SERVER2008” and then select Y at the confirmation prompt.

Without really giving it too much thought I had convinced myself I could simply connect to the server remotely using RWW.

Unfortunately I hadn’t yet got around to installing a 3^rd party trusted certificate, which kind of complicated the issue somewhat.  Upon connecting to RWW and clicking the connect button underneath the SBS server name I was rudely presented with this error.

Annoyed with myself for not doing enough so that I could complete this job and completely forgetting to install the CA certificate I searched for a way to resolve this.

Thankfully, I didn’t have to look too far.

When connecting to RWW, listed under Shared Folders is the default Public Share as illustrated below.  Click this link, in the new window that opens select Public and then Downloads.  Under here you will see Install Certificate Package.zip put a check box next to this and then select download.

Once downloaded, extract the zip file and then launch the InstallCertificate.exe file.  Select Install Certificate on my computer and click install.

Once done, close and re-launch internet explorer and re-connect to RWW.  You will now find you can successfully connect to remote computers.

The other alternative is to purchase a 3rd party trusted certificate from http://www.exchangecertificates.com that will remove these certificate errors completely.

One such company that I have come across recently is UK iPod Repairs. With the growing number of isomething devices in the home and business these days, it’s very often a week doesn’t go by when someone says “do you know a good place where I can get this fixed?” Well, the answer is yes, I cannot recommend this company more.

I placed an order online for the repair of a cracked iPhone 3GS screen. I’d seen the replacement screens you can buy online and fit yourself, but UK iPod Repairs were offering this service for £40 including return postage and packaging. They were boasting same day repairs and next day return delivery, of course, with any such claims there is always reticense as to whether they can deliver.

Well, I am very pleased to announce that they did deliver on every aspact of their service. The timeline is illustrated below.

• Saturday, I posted my iPhone, special delivery guaranteed before 1pm on Monday, I wanted it insured having had some bad experiences with damaged goods recently.
• Monday morning at 10:02 I receive an email confirming my phone had been received by UK iPod Repairs
• Monday afternoon at 13:27 I received an email confirming my iPhone screen had been repaired and that I will be informed when it has been dispatched.
• Monday afternoon at 17:02 I received a final email confirming my iPhone had been dispatched
• Tuesday morning the postman knocks on the door with my iPhone, screen fully replaced with a very high standard of workmanship and fully working.

UK iPod Repairs, I thank you, for delivering a service that is lacking these days, and the service we all crave. Speedy, well communicated, and cost effective. I will certainly, no doubt, use you again in the future, especially as we have at least 5 idevices in our household and my customers have numerous themselves.

UK iPod Repairs full list of services can be found at http://www.ukipodrepairs.co.uk

My first tip Migration Tip #1 – Source Server Health can be found here: http://demazter.wordpress.com/2011/06/12/migration-tip-1-source-server-health/

My second tip Migration Tip #2 – The Practice Run can be found here: http://demazter.wordpress.com/2011/06/14/migration-tip-2-%e2%80%93-the-practice-run/

My third tip Migration Tip #3 – Preparing for Live Migration can be found here: http://demazter.wordpress.com/2011/06/15/migration-tip-3-preparing-for-live-migration/

My fourth top Migration Tip #4 – The Migration can be found here: http://demazter.wordpress.com/2011/06/16/migration-tip-4-the-migration/

My fifth tip is based around testing and clearing up after the migration.  You’ve done all the hardwork, it would be a real shame to get this far and to encounter problems when you start to remove the old system.

Check over your work, do some test shutdowns of the old system.  Making sure that all users, data and systems are all operational during the shutdown.  Even go as far as to turn the system off for a week before you actually remove it from the network.  Making sure you tell your users that you are doing this and that any glitches you want to know about.  Believe me, all too often they will put up with a glitch and won’t tell you about it, until it’s too late.  You need to make it very clear that no matter how small you need to know about it during this “down” time.  It’s easier to resolve when the system is available than it is when it’s no longer part of your network.

There may be additional tasks you will need to perform once the old system is decomissioned.  These could include (but are not limited to):

• Backups, check you are backing up the data/system in it’s new location.
• Data flow, check that any dataflow in, out and around your network/systems have been updated to accomodate the changes you have made.  for example if it’s an Exchange migration, make sure that the firewall rules that control mailflow have been updated.  If it’s a SQL Database, make sure that any scripts/log shipping/etc have been modified. 
• Check any internal/external DNS entries have been modified if required.  If migrating to the cloud these will be external changes, if internal migrations then they will be internal changes.
• Check that any systems that interact with what has been migrated are still functioning, MFD’s, Fax Machines, NAS  devices etc etc.  The list is endless and only you will know what devices/systems you have in place.  Check them all.
• Check with your users that they are happy that all of what they need access to is working and functioning as they expect it to.
• Update your network documentation, do this now, whilst it’s still fresh in your mind.

Finally, once all that has been completed and you are happy that everything is working, decomission the old system.  Making sure of course you take a final backup before you do so.  Make sure you follow the correct procedure for removing the system you are migrating away from.  Don’t just turn it off and take it away.  Not following the correct procedure, can and will effect your network and any future migrations.

This is my final migration tip, I hope you have found them useful.  Please watch out for my next migration guide which will be available in the next few weeks which is Migrating Small Business Server 2008 to Small Business Server 2011.

If you are planning on a migration and are not comfortable with the process then Demazter IT Services can assist you. Please contact me on glen@demazter.co.uk.

All versions of Microsoft Exchange and Small Business Server require the use of an SSL Certificate. Whilst they will quite happily use a self-signed certificate a commercial certificate can save a lot of time and hassle, purchase Exchange/SBS SSL Certificates at an excellent price from: http://www.exchangecertificates.com

My first tip Migration Tip #1 – Source Server Health can be found here: http://demazter.wordpress.com/2011/06/12/migration-tip-1-source-server-health/

My second tip Migration Tip #2 – The Practice Run can be found here: http://demazter.wordpress.com/2011/06/14/migration-tip-2-%e2%80%93-the-practice-run/

My third tip Migration Tip #3 – Preparing for Live Migration can be found here: http://demazter.wordpress.com/2011/06/15/migration-tip-3-preparing-for-live-migration/

My fourth tip is about the actual migration itself, you’ve done all the preparation, you have practiced and you’ve spoken to everyone with a vested interest.  Now it’s time to do the deed.  The actual migration.

My advice here, is to take your time, nobody will actually get affected by the migration until you move data.  If you are following a guide, then do so religiously.  I made the mistake on my very first migration of skipping a few steps because I thought I knew better.  Even if you think they don’t need doing, do them.  There is a reason these steps are in the guide.

Test each step as you go along, read it, read it again, then perform the step, then double check it.  Make sure you are happy with that the step is completed before you move on to the next one.

If you come across a problem or something you are not sure of, stop.  Don’t continue and think “it’s OK, I will sort that out later”.  Fix it now.  If you can’t fix it find someone who can help you before you move on.  There are some great Q&A sites out there where volunteer experts will help you. http://www.experts-exchange.com being my favourite and where I tend to hang out.  But it’s easier for the experts to help you if you haven’t continued past the problem.  Often continuing will cause you to create a bigger problem which will be more costly in terms of time and possibly money to resolve.

More importantly, if you encounter a problem that means you have to stop the migration then communicate this to the people using the system.  Make sure they know that what was your final deadline may now shift.  This makes sure you are not under any unnecessary pressure, and again, manages their expectation.

Performing a migration can be a stressful tasks, and lots of blue line watching.  So make sure you get away from the system whilst the installations are being performed.  The blue lines will still move if you don’t watch them.  And watching them will make the migration seem like it’s taking all that much longer.

Watch out for tip Migration Tip #5 – The Aftermath

If you are planning on a migration and are not comfortable with the process then Demazter IT Services can assist you. Please contact me on glen@demazter.co.uk.

All versions of Microsoft Exchange and Small Business Server require the use of an SSL Certificate. Whilst they will quite happily use a self-signed certificate a commercial certificate can save a lot of time and hassle, purchase Exchange/SBS SSL Certificates at an excellent price from: http://www.exchangecertificates.com

My first tip Migration Tip #1 – Source Server Health can be found here: http://demazter.wordpress.com/2011/06/12/migration-tip-1-source-server-health/

My second tip Migration Tip #2 – The Practice Run can be found here: http://demazter.wordpress.com/2011/06/14/migration-tip-2-%e2%80%93-the-practice-run/

So, we now have a healthy source server and you have practice until the match sticks snap what next?

My third tip is about making sure you are prepared for the task ahead. Any type of migration needs to be taken seriously, it is a business critical operation you are about to embark on. If you are in any doubt about it at all, now is the time to say so, and if necessary call in help.

If you are happy with the process and confident you are able to complete the steps to achieve your goal then the next thing we need to do is plan a time to do it.

Most migrations are not time limited other than SBS to SBS migrations that have a limit of 21 days where both SBS servers can co-exist at the same time.

Make people aware of what you are doing, involve them, explain that you are expecting to have teething problems but would prefer if they collated them and then passed them to you when you ask for them. The last thing you want is to try trouble shooting whilst trying to complete a migration.

Find out if there is anything business critical happening (a big bid/contract etc that needs to be out just when you take the mail system offline) that could be delayed by the work you are carrying out, and if so, delay your migration. Talk to absolutely every member of staff. Manage Expectation.

In reality, if you get it bang on, the end users shouldn’t even notice and I would say 99% of the migrations I have done this has been the case. But there is always the odd one.

Have a recovery plan, know how to back out of what you are doing if it does go pear shaped. If you need to lock and migrate huge amounts of data then make sure you plan this stage of the migration for when people aren’t going to be using the system as heavily.

Document what you are doing, make notes of which stage you have got to and what action you have just taken.  This might seem like a waste of time, but take it from someone who has picked up a few failed migrations from people just like yourself, it’s not.  Knowing exactly what stage you are at will help a consultant very quickly get to grips with the situation and this means a faster resolution.

And, most importantly of all, make sure you have backups! Take more than one, take one off-site, and do it different ways. I like to have a backup on either removable storage so I can access it quickly but also on tape just to be sure.

Watch out for tip Migration Tip #4 – The Migration

If you are planning on a migration and are not comfortable with the process then Demazter IT Services can assist you. Please contact me on glen@demazter.co.uk.

All versions of Microsoft Exchange and Small Business Server require the use of an SSL Certificate. Whilst they will quite happily use a self-signed certificate a commercial certificate can save a lot of time and hassle, purchase Exchange/SBS SSL Certificates at an excellent price from: http://www.exchangecertificates.com/

My first tip Migration Tip #1 – Source Server Health can be found here: http://demazter.wordpress.com/2011/06/12/migration-tip-1-source-server-health/

My second tip is about making sure you are familiar with the technology you are migrating to.

For many people, migrating to a new technology will be the first and only time they perform this task. So, it’s always a good idea to familiarise yourself with the setup process before you do it for real.  With the use of virtualisation technologies we can install and test new products without the need for new hardware and without the possible impact on our live environment.

There are a number of virtualisation products that will allow you to do this on your desktop/laptop computer. You need to consider that most new products (if not all) will be based on x64 bit architecture. This does limit the virtualisation technologies that you can use on the desktop. Some of my favourites are listed below.

VMWare Workstation, this is a paid product but worth its weight in gold: http://store.vmware.com/store/vmwde/en_IE/pd/productID.166452200/Currency.GBP/?src=PaidSearch_Google_PersonalDesktop_WKSN_EMEA_UK_EN_Brand
VMWare Server, this is free for use and technically should only be used on a Server Operating System, but it does work on Desktop OS for testing purposes: http://www.vmware.com/products/server/overview.html
Virtual Box: http://www.sun.com/software/products/virtualbox/get.jsp

Whichever technology you use, virtualisation will allow you to install the new software in a test environment, and keep installing it until you are happy with the process. Run through it 2, 3 even 4 times. Make sure you are familiar with the screens and what answers you are going to provide to the wizards. Take notes, even write a step-by-step of what you encountered and when you encountered it. Remember, the more you do now when you are in a safe “sandbox” environment, the easier and less pressurised the real thing will be. Don’t pay too much attention to the actual data you are entering as some of this will change when you do a migration as opposed to a new installation.

For the actual Migration Pick a migration guide for your technologies, it’s always best to use one that’s recommended by others and they have had good success with.  You will find my migration guides here: http://demazter.wordpress.com/category/migration-guides/ I use my guides in my own migrations and update them with any changes as often as possible.  Read the guide thoroughly before you start the migration.   It’s easier to get answers when you are not under pressure to fix things.

If you have the time and the inclination I would also suggest that you convert your physical source server to a virtual one. This will allow you to do a test migration with your actual source server. There are many tools for performing the capture and they depend on the virtualisation technology you are using and whether you want a free or paid product. Some examples of methods that can be used to convert physical machines to virtual ones can be found here: http://4sysops.com/archives/p2v-for-vmware-six-ways-to-convert-physical-to-virtual/

Doing a virtual migration with a virtual copy of your actual source server is a great way to identify any problems you may encounter during the real live migration. You then have the opportunity to rectify these issues and then try the migration again. Once you are happy the migration has worked you are then in a position to do the live backup. I would be doing 3 to 4 virtual migrations just to be absolutely sure.

Watch out for tip Migration Tip #3 – Preparing for Live Migration in the next day or two.

If you are planning on a migration and are not comfortable with the process then Demazter IT Services can assist you. Please contact me on glen@demazter.co.uk.

All versions of Microsoft Exchange and Small Business Server require the use of an SSL Certificate. Whilst they will quite happily use a self-signed certificate a commercial certificate can save a lot of time and hassle, purchase Exchange/SBS SSL Certificates at an excellent price from: http://www.exchangecertificates.com/