Using Windows Autopilot to deploy PCs in the middle of a pandemic

This content is 4 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A year ago, who would have thought that so many people would still be working from home because of COVID-19? That a pandemic response would lead to such a huge impact on the way we live? That we’d be having discussions about the future role of the office?

Lots of things changed in 2020. Some of them may never change back.

Changes to PC operating system deployment methods

There is a saying (attributed to the Greek philosopher, Heraclitus) that the one constant in life is change…

Over nearly 30 years working in IT, I’ve worked on a lot of PC rollouts. And the technology keeps on changing:

  • Back in 1994, I was using Laplink software with parallel cables (so much faster than serial connections) to push Windows for Workgroups 3.11 onto PCs for the UK Ministry of Defence.
  • In 2001, Ghost (which by then had been purchased by Norton) was the way to do it. Working with a a Microsoft partner called Conchango, my team at Polo Ralph Lauren rolled out 4000 new and rebuilt PCs. We did this across 8 European countries, supporting languages and PC hardware types with just two images.
  • By 2005, I was working for Conchango and using early versions of the Microsoft Business Desktop Deployment (BDD) solution accelerator to push standard operating environment (SOE) images to PCs for a UK retail and hospitality company.
  • By 2007, BDD had become Microsoft Deployment. Later, that was absorbed into System Center Configuration Manager.

After this, the PC deployment stuff gets a bit fuzzy. My career had moved in a different direction and, these days, I’m less worried about the detail (I have subject matter experts to rely on). My concerns are around the practicalities of meeting business requirements by making appropriate technology selections.

Which brings me back to the current day.

A set of business requirements

Imagine it’s early 2021 and you’re faced with this set of requirements:

  • Must deploy new Windows 10 PCs to a significant proportion of the business’ staff.
  • Must comply with UK restrictions and guidance in relation to the COVID-19 novel coronavirus.
  • Should follow Microsoft’s current recommended practice.
  • Must maintain compliance with all company standards for security and for information management. In particular, must not impact the company’s existing ISO 27001, ISO 9001 or Cyber Essentials Plus certifications.
  • Should not involve significant administrative overhead.

A solution, built around Windows Autopilot

The good news is that this is all possible. And it’s really straightforward to achieve using a combination of Microsoft technologies.

  • Azure Active Directory provides a universal identity platform, including conditional access, multifactor authentication.
  • Windows Autopilot takes a standard Windows 10 image (no need for customised “gold builds”) and applies appropriate policies to configure and secure it in accordance with organisational requirements. It does this by working with other Microsoft Endpoint Manager (MEM) components, like Intune.
  • OneDrive keeps user profile data backed up to the cloud, with common folders redirected so they remain synced, regardless of the PC being used.

What does it look like?

My colleague, Thom McKiernan (@ThomMcK), created a great unboxing video of his experience, opening up and getting started with his Surface Pro 7+:

(I tried to do the same with my Surface Laptop 3 but unboxing videos are clearly not my thing.)

Why does this matter?

The important thing for me is not the tech. It’s the impact that this had on our business. To be clear:

We deployed new PCs to staff, during a national lockdown, without the IT department touching a single PC.

For me, it took around 10 minutes from opening the box to sitting at a usable desktop with Microsoft Teams and Edge. (What else do you need to work in 2021?)

That would have been unthinkable a few years ago.

It seems that, on an almost daily basis, I talk to clients who are struggling with technology to allow staff to work from home. It always seems to come back to legacy VPNs or virtual desktop “solutions” that are holding the IT department back.

So, if you’re looking at how your organisation manages its end user device deployments, I recommend taking a look at Windows Autopilot. Perhaps you’re already licensed for Microsoft 365, in which case you have the tools. And, if you need some help to get it all working, well, you know who to ask…

Featured image created from Microsoft press images.

Setting up a Surface Pen with a new PC

This content is 4 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I’ve been using Microsoft Surface devices for work for years now. Put simply, the company I work for is a Microsoft consulting and services business. So you would expect us to “walk the walk” as well as “talking the talk”, right?

Each time I get a new PC, I seem have challenges setting up the Surface Pen. So, today, after getting my pen up and running with a new Surface Laptop 3, I thought I should write about it (or at least post some links to the information that I used).

I was struggling to pair the Surface Pen in my Windows 10 Bluetooth settings. I pressed and held the top button, but there was no light. I unpaired it from the old PC and tried again. No change. Was it the battery charge? The Surface Pro that I had just unpaired from said the pen had 21% battery charge.

I decided to pop the battery out and test it. My battery tester’s needle didn’t move. 21% was clearly not enough. So, I popped in a new AAAA battery. Bingo! The pen’s light was illuminated and pairing was successful.

Partial screenshot showing the Surface Pen paired in Windows with full battery power.

So, my advice would be:

  • Press/hold the top button for a few seconds to put the pen into pairing mode. Look for a light.
  • If this doesn’t work, suspect the battery. Even if it’s already working with another PC!
  • If you’re still having trouble pairing after changing the battery, unpair from any other devices.
  • The device name will be Surface Pen (I have a randomly-named device within Bluetooth range that I have no idea what it is, but it wasn’t the Surface Pen!).
  • I have an older post which may help if you don’t have any AAAA batteries (and they don’t tend to be in the local shops).

Links

Here’s some links to the information I used:

Smart lighting: Part 2 (adding Innr and IKEA Trådfri bulbs to my Philips Hue installation)

This content is 4 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

My blog posts are like buses. You wait years for one to come along, and then two arrive at once. The only problem is that they are four years late.

In part 1 of this series, I wrote about getting started with Zigbee lighting, in the form of Philips Hue. Unfortunately, although it’s widely supported, Hue can be expensive so I quickly started to add compatible devices to my network. Here’s what I found.

Coloured bulbs

Whilst I use white lights in communal areas, I have some coloured lamps in some of the bedrooms and in the home offices. I also have one on the landing outside my office, which can be linked to my Teams presence information to show if I’m busy, using Isaac Levin (@isaacrlevin)’s PresenceLight solution).

Rather than shelling out £50 for a coloured Philips Hue bulb, I used Innr smart bulbs (both B22 and GU10 formats). These are also Zigbee-based but are not Apple HomeKit certified. That means that they work with the Hue app, but not natively in iOS. I decided that I can live without that (even more so since I switched to Android).

Innr supports connecting its smart bulbs to a Philips Hue bridge (but not for Hue Sync).

Low cost GU10s

I mentioned in my first post that I have some low-voltage MR16 bulbs in the house, for which I can’t find Zigbee replacements. Newer parts of the house (like the loft extension) have mains voltage GU10 fittings. For these, I used inexpensive IKEA Trådfri bulbs.

At the time, getting Trådfri working with Hue was a bit hit and miss but newer firmware seemed to improve this. The IKEA website even states that the Trådfri products can be used with Hue:

Do the IKEA smart lighting products work with the Philips Hue Bridge?

Yes, you can use the IKEA smart lighting products together with the Philips Hue Bridge.

How do I connect my IKEA smart lighting products to a Philips Hue Bridge?

If the software version of your IKEA smart lighting products is 1.2.x or later, you can connect them directly to a Philips Hue Bridge. Simply follow these steps: – First, make sure that the light sources that you want to connect have an updated software version (1.2.x or later).

– Keep the light sources close to the Philips Hue Bridge.

– Search for new devices with the Philips Hue app.

– Do a factory reset of the light sources by toggling the main switch six times.

[…] If the software version of your products is not 1.2.x or later, you need to update it by using a TRÅDFRI gateway and the IKEA Home smart app.”

IKEA Smart Lighting product support

A few things I found:

  1. Trådfri bulbs do seem to need to be physically close to the Hue Bridge in order to pair (as noted above).
  2. Some early firmware versions didn’t work so well with non-IKEA gateways (as noted above). I’ve had no real issues with my 2017 Week 44/46 and 2018 week 01 bulbs. You can find the version number on the packaging before purchase. According to the Hue software, these are all running software version 1.2.214.
  3. I couldn’t make IKEA Trådfri accessories (switches, etc.) work with the bulbs whilst the bulbs were paired with Hue. Your mileage may vary. I returned my Trådfri gateway to the store.
  4. Sometimes, the Trådfri bulbs will stop responding (remain on or off, regardless of control). This can usually be fixed by removing them from their fitting and then reconnecting them (basically rebooting the bulb). Later firmware may help.

Mixed messages

One side effect of the mixed system is that the Philips Hue software can only update its own equipment. It recognises the other equipment and will even tell me the software versions but updates would need the corresponding Innr or IKEA gateways and apps to be used. That’s a cost and level of complexity that I decided to manage without.

Software update in the Philips Hue app (Hue bulbs)
Software update in the Philips Hue app (Ikea Trådfri bulbs)
Software update in the Philips Hue app (Innr smart bulbs)

Smart Assistants

I mentioned that my cheaper bulbs are not compatible with Apple HomeKit, but I’ve had no problems working with Amazon Alexa via the Philips Hue skill. In truth, my home automation is a rats nest of Samsung SmartThings, TP-Link Kasa, SmartLife, Apple HomeKit and Amazon Alexa. I really need to look at sorting that out (maybe with Home Assistant). Watch out for a future blog post… hopefully it won’t be four years in the making).

Wrap-up

My experience with Zigbee smart bulbs from a variety of manufacturers has largely been positive. I still occasionally ask Alexa to turn on a light and find it doesn’t work because someone has switched off the circuit but that’s what us IT folks refer to as a “layer 8 problem” or an issue with the “wetware”. Whilst mixing manufacturers may present some challenges with updates, a Hue hub at the centre of a mixed network seems to work pretty well for me. After all, the likelihood of someone hacking my unpatched IKEA lightbulbs seems pretty minimal…

Acknowledgements

Featured image by soynanii from Pixabay.

Smart lighting: Part 1 (getting started with Philips Hue/Zigbee)

This content is 4 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Earlier today, I spotted a tweet from Karan Chadda (@kchadda) that reminded me of an unfinished blog post from 2017…

So, here’s part one of the story that never got posted…

A new Hue

Around four years ago, I began an experiment. Hot on the heels of success with a Wi-Fi activated smart socket (a TP Link HS-110), I thought I’d expand on my home’s Internet of Things (IoT) credentials with some smart lighting.

I should explain that my house is a fairly typical UK house: a 1990s-built, detached property, with some pretty uninspiring pendant lights in most rooms. The kitchen/dining room is a little different, as it has low-voltage MR16 spotlights. These were recommended by the electrician who worked on our extension in 2009.

I did some research, and decided that I wouldn’t go down the Wi-Fi route. Not only were the bulbs expensive but it’s not a great use for Wi-Fi (and at the time my home Wi-Fi performance was pretty flaky). Instead, I went for a Zigbee-based solution, with Philips Hue at its heart.

The Hue gateway is pretty easy to set up – it just needs a wired connection to the network. Most home routers have a few of these; my setup is a little more extensive, with PowerEthernet running to my office and other locations that are away from the Internet connection but have a need for wired network connections. With a gateway in place, it was just a case of strategic lightbulb swap-outs, taking out traditional bayonet-fit (B22) bulbs and replacing them with smart equivalents.

Smart lighting, not so smart users…

At this point I should explain, all the smart technology is useless if the circuits aren’t left powered on. And this has been the major flaw in my plan. Our family is divided between the geeks (myself and my eldest son), and the “normal” tech users (my wife and my youngest son). If I was being less charitable, I might put my wife into the laggards category but, to be fair, she’s happy to adopt technology when she can see its value.

For me, part of that value was the ability to set up routines so that lights turn on/off when we’re away from the home. I also have one that turns all the lights off after everyone has gone to work/school (because physical switches appear to only work in one direction for my family – they can all turn lights on, but seemingly not off – I believe this is a common complaint for Fathers up and down the land, walking around houses turning lights off in empty rooms, even during daylight hours).

The biggest drawback I found was that I’ve yet to identify suitable Zigbee switches for the UK market. That means that, when the circuit is switched off (usually when leaving the house or going to bed), the lights are no longer controllable in software. On the flip side, the less-technically-inclined family members can operate the lights as normal, with the only minor inconvenience being, if the light has been turned off in software, they need to flick the switch off and on again to turn on the light “manually”.

Those in other parts of the world may have more luck – have a listen to these podcast episodes or watch some of the videos on this channel:

Form factors and accessories

Over time, I’ve expanded the system and I now have smart bulbs in the communal areas (hall, stairs, landing, etc.) as well as in the home offices and some of the bedrooms.

Unfortunately, there are no suitable MR16 Hue-compatible bulbs, so the rooms with those lights still have traditional halogen (for dimmer-controlled rooms) or LED spotlights. I’ve also stuck with “normal” bulbs in the bathrooms.

I’ve added a Hue sensor in the garage storeroom (so the light comes on when we open the door) and a couple of Hue dimmers, one of which has moved between various rooms over the last couple of years but is currently in our loft room. For the dimmer, I bought a Samotech adapter that covers the original light switch (left switched on), whilst still allowing the Hue dimmer to attach magnetically.

Samotech adapter in use with a Philips Hue dimmer and a standard UK light switch

The verdict?

All in all, things are working well. After nearly four years I’ve only had one failed bulb (replaced under warranty after about a year). The Philips Hue system seems to be a widely supported platform, with plenty of integrations (e.g. to smart home assistants) and the use of third-party bulbs in places has helped me to keep costs down to a reasonable level (I’ll write about these in my next post).

Acknowledgements

Featured image by HeikoAL from Pixabay.

What’s the future of the office?

This content is 4 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

2020 saw huge changes in the way that we work. The COVID-19 novel coronavirus forced home working for millions of people, and left office blocks empty for weeks or months at a time. As we enter 2021, will that change? And will we ever go back to our previous work patterns?

I don’t have a crystal ball, but I’d have to answer that with a “yes” to the question of change and a “no” to the return to 2019 working patterns.

Unfortunately for commercial landlords (and so for large chunks of our pension funds), the genie is out of the bottle. Remote and flexible working is now normal. Physical distancing requirements mean that offices can’t operate at their previous capacity. We simply cannot go back to a world whether offices squeeze people into banks of hot desks based on a 6 desks for every 10 people model. And as for lifts – pah! You’d better get used to climbing the stairs.

Even my rather poor fortune-telling skills come to the conclusion that we have to find a new way to use office space. And conversation with others more intellectual than I has led me to the conclusion that, rather than offices being the place for people to meet and come together to do work, they will be the places of safety for those who cannot work at home.

Offices as a meeting space

In April 2020, I’d probably have said that we still need somewhere to go and meet. Humans need contact, and some of our best work is done together. I’m itching to go back into an office, grab some pens and write on the walls, as I get increasingly excited by a concept and thrash out the details with my colleagues.

As 2020 continued, we got used to doing everything on a small screen. Whilst I seem to hear nothing but universal hatred for Microsoft Whiteboard (personally, I can’t see the problem) and tools like Miro are lauded as the latest and greatest, we are getting used to working as remote teams.

The problem comes when we have a hybrid approach with groups of people “in the room” and groups outside, as Matt Ballantine (@ballantine70) has noted on multiple occasions, including the Twitter thread below:

Offices as a place of security

Some work needs to be performed in a secure environment. Arguably that could still be remote (digitally secure) but if analogue paperwork is involved then that could be a challenge.

And not everyone has a place at home in which to work, securely. For some, a kitchen counter, shared with children for their homework, may not be the best place for work. Similarly those who live with parents or in a shared house with friends may only have a bedroom in which to work. If your work is harrowing (e.g. social work), do you really want to sleep in the same room?

We need to provide a place for people to work who don’t have the option of remote work. Offices will continue to function for that purpose and it’s entirely possible that making these spaces COVID-secure will see “hot desks” return to single-person occupation.

The rise of localism

Many people are concerned about the impact of reduced office working on local businesses. What about the cleaners (if anything, they have more to do)? What about the sandwich shops? What will this mean for the country’s future transport needs?

Whilst I have genuine sympathy for the independents that are no-doubt struggling with reduced footfall and enforced closures, or partial closures, that sympathy does not extend to the Pret a Mangers and Wetherspoons of our identikit town centres. I am concerned for the people that work in these businesses but not for the corporates that own them.

But, for every pound that’s not spent in big towns and cities, there’s another that’s spent in a local economy somewhere else. The small town where I live appears to be thriving – people who previously commuted and simply weren’t in the town during weekdays now use the Thursday market and the local shops. The local coffee shop has even opened new branches.

We’ve also seen banks, for example, starting to bring spaces above branches into use as local touchdown centres, rather than encouraging workers to commute to large offices in major towns and cities.

This rise of the local economy is good for society in general and good for finding a work-life balance.

Helping people to do their best work

Perhaps the real purpose of the office is to help people to do their best work. That may take a variety of forms but it’s also where technology can help. We need to provide the safe working environment. We need to provide the collaboration spaces, whilst remaining physically distanced. We need to keep people communicating.

  • The way we work has changed and we cannot rely on being co-located.
  • “Working out loud” has to be the operating model, supported by flexible technology and processes that encourage collaboration.
  • And services provided across the Internet are now at the heart of this transformation.

Some Business Transformation may be required, to make sure the processes can keep up with new ways of working – but, whatever the future of the office is, we can be sure of continued change over the coming months and years.

Acknowledgements

Large parts of this post are based on conversations with Matt Ballantine and others on the WB-40 Podcast WhatsApp group. Thanks to Matt and to Chris Weston for the inspiration and for providing this community where we often work out loud, in digital safety.

Featured image by MichaelGaida from Pixabay.

Installing Google Play on an Amazon Kindle Fire tablet

This content is 4 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Amazon’s Kindle Fire tablets are excellent value but they run their own version of Android (Fire OS). Fire OS doesn’t include Google’s app store (Google Play) and the Amazon store has fewer apps.

This is not the first time I’ve blogged on this topic but both Android and the Fire OS have moved on considerably, so I thought it was time for an update.

Over the years, I’ve had a few Kindles: first I bought one of the eInk devices; then I bought a Fire HD in 2016, and another in 2018 because my first one was lacking in memory. Then, after an accident with a water glass by my bedside, my 7th generation (2018) Fire HD was fried (I don’t think it was water damage – I think an electrical surge damaged it) and I needed to replace it. Luckily, it was close to “Amazon Prime Day” and so my 2020 Kindle Fire HD was not too big a hit on the wallet…

That means that, every couple of years, I’ve needed to go back around the loop of installing Google Play on my Kindle. On this most recent occasion, I was pleased to find that the process is just as simple as last time. It just needed me to download and install four APK files, making sure they were from a reliable source and in the right order.

Some good advice

The advice I followed this time was from Corbin Davenport (@corbindavenport)’s Android Police article. As I write this, I’ve found it was updated a few days ago to help with any Christmas 2020 purchases. You can find the details at The ultimate guide for installing the Google Play Store on Amazon Fire tablets.

For my 10th generation Kindle Fire HD 8, I needed:

  • Google Account Manager 7.1.2 (com.google.gsf.login).
  • Google Services Framework v9-4832352 (com.google.android.gsf).
  • Google Play Services (64-it ARM,nodpi, Android 9.0+) (com.google.android.gms).
  • Google Play Store (universal, nodpi) (com.android.vending).

To find which generation of tablet you have, either check on the device (in Settings, Device Options, About Fire Tablet) or in your Amazon account (Manage Your Content and Devices). Then, use the Android Police article I mentioned above to download the appropriate APK files.

That sounds a bit technical…

If it all sounds a bit “geek”, yes, it is. But all you are really doing is installing some Android modules that Amazon does not provide. The installation process is simple, as long as you:

  1. Are familiar with downloading files on an Android device and know how to find them.
  2. Have removed any SD card that may be installed (to make sure the apps go onto internal storage).
  3. Have allowed the installation of apps from unknown sources, for the Silk browser – which you will use to download the APK files.
  4. Install in the order listed above (files ending login, gsf, gsm, vending) and install them all before opening any of them.

Once you’re done and have restarted the device, you should see the familiar Play store icon and will be ready to install your favourite Android apps.

The end result

My Kindle is now fully loaded with a stack of Android apps. I use:

  • All the British TV on-demand apps (BBC iPlayer, ITV Hub, All 4, My5).
  • HDHomeRun for live TV streaming.
  • Spotify, YouTube, Plex, Sonos, VLC for most of my music and video needs.
  • TV Guide.
  • Some smart home stuff (like Philips Hue and, of course, Amazon Alexa).
  • Microsoft Office Apps and the Microsoft Remote Desktop Client.
  • Google Chrome (and Microsoft Edge) because the Amazon Silk browser is pretty poor – I only used it to download the APKs to install Google Play!
A selection of Android apps and the Google Play Store on an Amazon Kindle Fire tablet

Some of these apps are available from the Kindle store but I generally install from Google Play to get the latest versions and to simplify update management.

Invalid/missing request nonce when connecting WordPress to Google Photos

This content is 4 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I’ve wanted to make my blog posts more visual for a while but selecting good stock images takes time. Creating them takes even more time!

Anyway, I decided to include an image from Pixabay (with credit) in yesterday’s post as well as in the one that I’ve scheduled for after my return to work in January.

I could quickly fill up my web space with images and I didn’t really want to expand my WordPress database with images either (they are currently hosted in a folder structure) but there is an option in WordPress to include media stored in Google Photos.

Unfortunately, my attempts to authorise access were met with a message about an “invalid/missing request nonce” (whatever that is). I tried another computer, in case the problem was related to cookies, or to restrictions on my work PC, but that was no help.

Then I tried another route…

Logging into wordpress.com (even though my blog is self-hosted with wordpress.org) and managing the marketing connections gave me an alternative interface to authorise WordPress with Google Photos. That then jumped into life:

WordPress.com Marketing and Integrations page, showing succesful connection to Google Photos.

After this, I could easily insert images from Google Photos into my blog posts.

And seriously, whoever decided that WordPress has something called a “nonce” should look it up in colloquial English

Featured image by Kevin Phillips from Pixabay.

What does it mean to work flexibly?

This content is 4 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

2020 has brought many things – not all of them welcome – but for many office workers one of the more significant changes has been the acceptance of working from home.

Of course, there are many jobs that can’t be carried out remotely but, for a lot of people, the increased flexibility that comes with home working is a benefit. For others, it may be less welcome – for example those who do not have a regular place to work from, or who share a house with family who are also competing for the same resources. That means that offices continue to have a role but we’re not quite sure what that is yet. One thing does seem certain: it will continue to evolve over the coming months.

Outputs, not inputs

I’ve been fortunate to have worked from home for some of the time for many years. I’ve been contractually based from home since 2005 but even before then I tried to work from home when I could. What I’ve seen in 2020 is organisations where managers previously wouldn’t allow their teams to work from home being forced to accept change. Very quickly. A culture of “presenteeism” was often rife and sometimes still is. Some organisations have transferred poor office-based culture to a poor online culture but others have embraced the change.

Moving to remote work means providing flexibility. That certainly means flexibility in where work takes place, but it may also mean flexibility in when the work happens.

My own work is contractually 30 hours over a 4 day working week. In reality, it’s not based on hours, it’s based on outputs – and I put in what is needed in order to deliver what is expected of me. That will almost always take more hours – and sometimes there’s a fine balance. Sometimes, I have to say “enough”. I’ve learned that modern work is never “done”, just that priorities change over time. And, as a manager, I have to look for the signs in my own team’s workload and be ready to reassign work or adjust priorities if someone is overloaded whilst a colleague has gaps.

Crucially, I don’t need my team to be in front of me to manage them.

“Working hours”

Similarly, many of us no longer need to be tied to the “9 to 5”. Some roles may require staffing at particular times but, for many office workers, meetings can be scheduled within a set of core hours. For organisations that work across time zones, that challenge of following the sun has been there for a while. Avoiding the temptation to work extended days over multiple time zones can be difficult – but, conversely, working in bursts over an extended period may work for you.

I’m mostly UK-based and nominally work on UK time. For many years, I’ve had an unwritten rule that I don’t arrange meetings first- or last-thing in the day, or over lunch. If that means that all of my meetings are between 09:30 and 12:00 or between 14:00 and 16:30, that’s fine. A solid day meetings is not good. Especially when they are all online!

Before 09:30 people with chlldren may be on the school run. Those with other dependents may have other responsibilities. Everyone is entitled to a lunch break. At the end of the day there may be other commitments, or maybe another meeting is just not going to get the best out of people who have already been in back-to-back Microsoft Teams calls.

Often, I’ll return to work in the evening to catch up on things. That’s not to say I expect others to. I actually have a disclaimer on my email which says:

“My working hours may not be your working hours.  Please do not feel any pressure to reply outside of your normal work schedule. Also, please note that I do not normally work on Fridays. Another member of the risual team will be happy to assist in my absence.”

It’s about setting expectations. In a previous role, I wrote about my email SLA but people shouldn’t feel pressured to respond immediately to email. As a former manager once told me:

“Email is an asynchronous communication mechanism over an unreliable transport.”

[Mark Locke, Fujitsu, approx 2010]

When working across time zones, that’s particularly important but we should also be empowered to work when it works for us.

For me, I’m not great at getting up in the morning. I often get into flow in the late afternoon and work into the evening.

So, whilst I’m sure messages like this one in Microsoft Outlook from My Analytics are well-intentioned, I don’t find them helpful because they are based on the concept of “working hours”. Yes, I could delay send, but what if that person likes to start their day early?

My Anaytics prompt in Microsoft Outlook to consider delaying an email until working hours.

On the basis that email should not be time-sensitive (use a chat-based medium for that – maybe even a phone), it shouldn’t matter when it’s sent, or received. The workplace culture needs to evolve to prevent the “I sent you an email” response from being acceptable. “Ah, thank you. I haven’t seen that yet but I’ll make sure I watch out for it and respond at an appropriate moment.”.

Time to adjust our expectations?

So, in a world of increased flexibility, with colleagues working at a time and place that works for them, we all need to adjust our expectations. I suggest thinking not about when a message is sent but instead about whether email is actually the right medium. And, as for whether we need a meeting or not… that’s a whole blog post in itself…

Featured image by congerdesign from Pixabay.

Investigating my not-so-superfast broadband

This content is 4 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I’m constantly frustrated by my broadband speeds. They are not bad, but not as good as they should be either, especially not when marketed as “superfast broadband”. And the real-world speeds seemed to drop about 10% when I switched ISPs from PlusNet to Vodafone a couple of years ago. I think I’m out of contract now, so it’s a good opportunity to take a look at what is possible.

For reference, I’m on a Vodafone Superfast 1 business broadband package, which should give up to 38Mbps, with a claimed average of 35Mbps and 73% of customers able to achieve those speeds:

Vodafone's estimated broadband speed for my phone line.

In the real world, I get around 22Mbps down and 7Mbps up, according to various speed checkers. The most I’ve ever seen on a speed test is around 25-26Mbps, with my previous ISP.

Step 1: Check basic broadband availability.

The Kitz Broadband Checker helps here, using BT Wholesale and SamKnows data to check what is available for a given phone number/postcode. There are basic details of the local telephone exchange and there is a rough indicator of how far away it is. It may be 618m as the crow flies, but I can tell you it’s more like 1500m by road/cable (assuming it follows the route I would expect around the local streets and doesn’t run along the alleyway behind my house). I don’t understand all of the acronyms and abbreviations but it seems to me that the site doesn’t (yet) understand whether Fibre To The Premises (FTTP) is available, or just Fibre To The Cabinet (FTTC) and earlier broadband options.

Step 2: A few more details from BT Wholesale

The BT Wholesale Broadband Checker was my next port of call. This tells me all sorts of things about my line, like that: I should be able to get around 42.5Mbps down (instead of my 22) – which is probably where the real-world claimed up to 38Mbps comes from; that FTTP is available (along with several other products); and that my current FTTC cabinet is Cabinet 10. I’ve spotted this cabinet on my walks around town and so I know it’s not particularly close to home – probably around 1000m by road, though it could be as little as 350m if the cable runs through the alleyway I mentioned earlier.

BT Broadband Availability Checker results for my phone line

Step 3: Check the modem stats

I stopped using my ISP-provided modem a couple of years ago and switched to a DrayTek Vigor 130 modem (since discontinued by the manufacturer) with a Ubiquiti AmpliFi router.

Logging on to the router’s web interface told me that I was syncing at around 27Mbps down and 7 up and on VDSL Profile 17A with a signal to noise ratio (SNR) around 6:

DrayTek Vigor 130 modem online status

That fits with my real-world performance in speed tests of around 22Mbps. Digging a little deeper via a telnet session gave me a whole load of stats:

> adsl status
  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          : 27400000 bps   US Actual Rate       :  7265000 bps
   DS Attainable Rate      : 28950732 bps   US Attainable Rate   :  7265000 bps
   DS Path Mode            :        Fast    US Path Mode         :        Fast
   DS Interleave Depth     :        1       US Interleave Depth  :        1
   NE Current Attenuation  :       25 dB    Cur SNR Margin       :        7  dB
   DS actual PSD           :     4. 3 dB    US actual PSD        :    11. 7  dB
   NE CRC Count            :      935       FE CRC Count         :    13805
   NE ES Count             :      261       FE  ES Count         :     7519
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        7
   ITU Version[0]          : fe004452       ITU Version[1]       : 41590000
   VDSL Firmware Version   : 05-07-06-0D-01-07   [with Vectoring support]
   Power Management Mode   : DSL_G997_PMS_L0
   Test Mode               : DISABLE
  -------------------------------- ATU-C Info ---------------------------------
   Far Current Attenuation :       28 dB    Far SNR Margin       :        6  dB
   CO ITU Version[0]       : b5004244       CO ITU Version[1]    : 434da4a1
   DSLAM CHIPSET VENDOR    : < BDCM >

Comparing that sync speed of 27.4Mpbs with the BT Wholesale test in step 2, and my connection is running as quickly as it ever has (though I’m not sure what period the BT Wholesale test ran over for its maximum observed speed).

(It also tells me that my cabinet has a Broadcom chipset, so it’s most likely to contain Huawei equipment).

So, why is my “Superfast broadband” not so… superfast?

So, I have lots of metrics, what’s the analysis?

  1. Possibly: my connection. Several years ago (pre-broadband) we had a second phone line put in the house (since disconnected) and I seem to recall that some jiggery-pokery was required at the exchange to accommodate that, possibly even running two phone numbers over one copper connection. I thought that might explain why I get about half the theoretical maximum bandwidth (and my neighbour three doors down gets the whole lot).
  2. Possibly: internal wiring on-premises. My modem is connected directly to a line into the house but it’s not the BT master socket – it’s connected by some other external route that I don’t understand. I’ve tried moving previous modem/routers to connect directly to the master socket and it’s not made any noticeable difference to sync speeds.
  3. Most likely: physics. Whilst researching this post, I found information about FTTC speed vs. distance from the cabinet (repeated on various forums). At 1km from the cabinet, the most I will get, even on a 17A (80Mbps) profile, is 28Mpbs and I’m syncing at around 27 (this table at ThinkBroadband suggests even lower). So what about my neighbour who gets 38? Maybe he’s just lucky, or perhaps his line takes a different route around town…

Assuming my analysis is correct, this is probably about as good as it gets, without an FTTP upgrade. And, as the service is cheap (around £28/month including a home phone calling package and with no line rental), we might just stay put for now – after all my Teams calls work in the day and my Netflix and YouTube work in the evening/at the weekend!

SamKnows?

As a little addendum (and there is nothing in this for me), if you’re trying to work out what’s going on with your broadband, I’d recommend checking out SamKnows. I have one of their “white boxes” on my network and have had for several years (ever since the late Jack Schofield pointed me in their direction). In exchange for some real-world performance monitoring, which is aggregated to assess ISPs, I get reliable stats on the state of my connection.

SamKnows stats for my connection

Getting started with Markdown

This content is 4 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

The problem

One of my recent projects has been to build out a repository of architecture artefacts for my team to use in delivery of our engagements. I wanted something quick, simple to use, and my budget was… zero. I probably could have used Github or Azure DevOps but I wanted to integrate with an existing SharePoint site, so I simply created a new document library and started uploading files.

Some more requirements

I didn’t want a folder structure – ideally I will use the metadata on the files to allow searching – but I did want some simple release notes to act as an entry point/index of what’s here.

I wanted to avoid Office file formats. They are good for many things, but I wanted something lightweight that would render easily in a browser or a text editor. And I wanted something a bit more than a text file. Which led me to Markdown – something I’ve been meaning to get to grips with for a while now*.

A solution

Markdown is not new, but it is beautifully simple. And in a world of wall-to-wall Microsoft productivity tools, it turned out to be incredibly elegant.

Getting started with Markdown is simple. Open a text editor and write some words – as set out in John Gruber’s original post. This guide tells a bit more though – or try a tutorial.

I actually started writing my Markdown (.md) files with the Dillinger Markdown Editor. Once I had the basics, I switched to editing in the SharePoint text file editor, or in Visual Studio Code:

As can be seen from the screenshot in the tweet above, the syntax is pretty straightforward but I just use Adam Pritchard’s Markdown cheatsheet to help with any syntax stuff I can’t remember. And the Markdown files render pretty well in Edge (presumably in other modern browsers too). There’s no need to worry about special tools to render to HTML.

Markdown FTW

So that’s got me started with using Markdown. The learning curve is so gentle that I can’t see me using anything more heavyweight now (like a Teams Wiki or a shared OneNote) when a few .md files will do the job quite nicely…

* I have a dream. A dream that one day, we will no longer write our design documents in Microsoft Word but will select sections of standard text from a website, enter the design decisions in a form, and hit “generate”. Documents will be created for Consultants, rather than by Consultants – and I can avoid what sometimes feels like a life of constant copy-editing (good techies that can write well seem to be a rare breed). That day is still a long way away… or is at least a side project that I haven’t worked out how to get started on…