I spent far too much of yesterday fighting with SharePoint workflows… including trying to cancel some that have run away on a list with almost 400 items in it…
Some idiot (initials MW) created a workflow to auto-populate a column based when a record was created or updated. Then, thinking that was successful, he created another one to update a different column. He was so pleased with himself that he didn’t stop to think of the consequences of one workflow updating an item, which would then trigger another workflow because the item had been updated… the resulting event from which would then trigger another workflow… and so on…
The long and short of it, is that I found SharePoint 2007 doesn’t have the ability to bulk remove errant (or otherwise) workflow tasks. Not from the user interface, at least – and I didn’t want to do it, twice, for each one of 377 items (there weren’t quite that many runaway workflows but it was well into three figures). I found some code on a blog post from SharePoint MVP Brian Farnhill (@BrianFarnhill) to cancel a workflow programmatically but I’ll need to put the code into an app and I’m not really sure how to do that (my limit is probably opening Visual Studio). Besides which, I figure that the administrators of our SharePoint platform, who have probably spent the last 3 weeks wondering why it was running out of memory (or running more processes, or something similar) won’t appreciate me running unsupported code against their servers – even if it is client side…
Although it would be gratifying to create the app, in the end I settled for removing the workflow from the list, which has the side effect of ending all running workflows (unless you select the “no new instances” option). Unfortunately I still have a bunch of items that generate an error message when I try to open them – goodness knows why.
I decided to fight fire with fire and given that I’m clearly some sort of SharePoint Destroyer Designer workflow deity (not), I created another workflow to nuke all the column settings I’d created with the first two workflows (since neutered).
The logic goes like this:
Condition: If columnname is not empty
Action: Set columnname to null
Unfortunately it’s not possible to leave a null/blank value when setting field values but, like so many things in SharePoint, there is a workaround. That workaround is to set a workflow initiation parameter (imaginatively, I called mine Blank) of type single line of text, with an empty default value.
Now, the workflow action can use the value Initiation: Blank (i.e. null) to clear the contents of a column.
Unfortunately, it still hasn’t fixed the problem with the items that will not open. And, in case my manager is reading this post (which I doubt), hopefully this now puts to bed the running joke whether it’s he or I that is our team’s “SharePoint guru”. Clearly my infrastructure background does not lend itself to being a “guru” in an application platform (as I have always maintained!)…
Every now and again, I get asked to review a technology book. My response is usually something along the lines of “sure, send me a copy and I’ll take a look”. Experience suggests that dead tree editions are more likely to get read than a PDF but sometimes I’m just busy and it takes a while. That’s not because I’m lazy – it’s because if I review a book I want to take the time to review it properly and write a considered response – not just bang out a blog post because the publisher is nagging me for a review…
Unfortunately, this particular publisher was chasing me just 48 hours after they ordered me a copy (and several days before I’d received the book!) and, just a month later (in the middle of the summer holiday season) they are still pushing…
As I’d expect from a book written by a couple of MVPs, this book covers all of the basics of implementing the Exchange Online elements of Office 365. Importantly, it doesn’t just concentrate on the enterprise elements, including information for those getting started with the Office 365 plans for small business and professionals, highlighting some important limitations (although not all – as I found recently, the P1 plans don’t include two factor authentication, which is something that users on competing platforms are being encouraged to use). The book continues to take a logical approach, working through the administration portal and on to integration options – even considering the practicalities involved when the available options from Microsoft are less than desirable, recommending some alternatives to consider. Unfortunately the space given to working from the command line in PowerShell (a useful tool in the Office 365 administrator’s arsenal) is very limited.
Moving on through enterprise integration options, preparing for, and performing both simple and hybrid migrations (including supporting infrastructure, such as Active Directory Federation Services), it seems that the authors have covered a variety of scenarios, with many screen shots and diagrams provided to illustrate key points in the process. One criticism is that the screen shots can, in places, feel as though they are being used to pad out the text – presumably the target audience consists of experienced administrators and they shouldn’t really need screen shots of EULA dialogues – after all, this is not “Office 365 migration for dummies”! Finally, the book examines some important post-migration considerations and highlights additional resources.
When I previously reviewed a book from the same publisher, I remarked on the high cover price. Well, I’m pleased to say that this one is a much more reasonable £24.99 ($39.99) and that there are online discounts and free shipping, as well as reasonably-priced eBook options. Indeed, very sensibly, the print and eBook bundle only costs a little more than the print copy on its own.
If you get the chance to read the book properly and you have some comments (perhaps even based on experience of following its advice, as I would have like to have done), then please leave a comment below. Maybe, together, we can crowdsource its review!
Much as I like the rawness (is that a word?) of the naked Raspberry Pi, it does feel like it would be very easy for me to break and, with huge waiting lists to get a replacement as demand massively outstrips supply, I really don’t want to break mine. Consequently, I decided that a some sort of case would be appropriate (a punnet?).
Punnet v1.0 (or maybe it was v0.1) was the brainchild of freind and neighbour Jon Cowell, who took a plastic box that had originally been used as packaging for a set of business cards (I’m told that Graze boxes work well too) and used a Dremel multitool to cut out holes for connectors. I also had a few spare business card boxes so, after an evening in Jon’s garage, I had a case for my Pi – and very happy with it I was too!
Alternatively, for those with a flat-screen monitor that’s not fixed to the wall, SK Pang’s VESA mount for Raspberry Pi looks interesting. Who needs an iMac when you can fix a Raspberry Pi to the back of a cheap monitor, eh?!
I use Adobe Lightroom for most of my digital photography workflow but as our family takes more and more pictures on a variety of cameras, other family members need to process images – and I’m not letting them near my Lightroom catalogue!
As we tend to use iPhoto every year to product yearbooks, calendars, etc., the solution we decided on was for me to copy unprocessed images over onto an old Mac Mini, which is running OS X 10.6 (Snow Leopard) with iPhoto (still version 6, part of the iLife suite shipped with OS X 10.4, which was what originally installed on the Mini).
I refuse to buy a new Mac for this – the whole point of the exercise was to provide a fit-for-purpose solution using the kit we already have – and a new machine doesn’t come into that (heck, I might as well just put Photoshop Elements on my wife’s Windows laptop), so it was back to the drawing board.
If my combination of OS X and iPhoto won’t read my raw files, I’ll just need to batch convert them to something else first…
First up, I installed Apple’s developer tools – XCode. These are found on the operating system DVD for OS X 10.6 (in the Optional Installs folder) but are a free load from the Mac App Store for 10.7 and later. I did register for a developer account and started downloading version 3.2.6 but then realised that it was a 4.1GB download and retrieving the DVD from the loft was easier. After installing XCode from the DVD, I updated to 3.2.6 using the OS X Software Update utility although other versions of OS X might have a slightly different XCode upgrade process.
The Unix Command Line tools are an install option on XCode 3.2.6 (they can be downloaded from inside XCode from version 4 onwards) but, once these were installed, the next step was to download and install MacPorts. Again, there are different versions according to the release of OS X in use but I downloaded the .DMG for OS X 10.6 and then kicked off a Terminal session.
Once in Terminal, I entered the following commands:
su admin sudo port install dcraw
following which MacPorts did all of the work to download and install dcraw and all of its dependencies.
Batch converting raw images on the Mac
With dcraw installed, there are many options for processing images but the basic syntax may be found by opening Terminal and typing:
One final tweak before import the files to iPhoto was to set the file dates to match the camera timestamp (without this, iPhoto seemed to think that the images were taken on the day they were imported):
dcraw -z *.tiff
The resulting files were ready to import to iPhoto for family use, with no risk to the master copies that are stored on my MacBook.
“It’s all to easy to forget that, although the current version of the Pi was intended for developers in preparation for a broader educational release, it’s been massively popular with 350,000 boards shipped (and on target for a million by the end of the year!). Add to that, the Raspberry Pi foundation is 20 guys and girls who don’t get paid and who have day jobs – that’s a very limited resource pool to support an awful lot of people! Even so, the Raspberry Pi is not necessarily the most user-friendly experience for those who are not used to hacking around in a command line interface […]”
With that in mind, this blog post is intended as a basic guide for those who don’t have 20 years of experience working in IT, or are not bedroom coders, but do fancy getting stuck in to creating new and exciting things with a small and inexpensive computer. Regular readers may find that I explain things in more detail than usual but I’m assuming the audience are complete beginners when it comes to using a Raspberry Pi and that they do not spend their time geeking out with bits of hardware or bytes of software. If I’ve missed anything – or made some invalid assumptions – please leave a comment on this blog post, or tweet me (@markwilsonit) but please bear in mind that I have a day job too (so my response might not be immediate) and I can’t answer every single question about getting started with a Raspberry Pi!
What’s in the box – and what else do I need?
At its most basic level, the Raspberry Pi is a single board computer. Some distributors may sell bundles with mice, keyboards, etc. but many people will just get a board like the one shown here:
That means there are some essentials to buy:
A 5V power adapter with a micro-USB type B connection (I use the one that came with my mobile phone but not all phones have these):
A USB keyboard – i.e. a keyboard with a USB type A connection like the one below:
A USB mouse (if you want to run a graphical user environment – i.e. one that is not just text-based)
An SD card with an operating system. I recommend that beginners start out with one that comes pre loaded, for example with Raspbian Linux. If you are going to “roll-your own” then that can be more complex and my earlier post based on Debian “Squeeze” might help but that’s a lot more technical and certainly outside the scope of this basic guide.
A television or digital computer monitor with either an RCA component, DVI, or HDMI input. VGA will not work. See below for details of what these connections look like.
A cable to connect to the Raspberry Pi to the television or computer monitor. The type of cable will depend on the type of connection.
RCA cables look like this (normally red and white are used for audio and yellow is used for video, but it doesn’t really matter – the cables are identical):
DVI cables look like this (the picture shows the “male” format, with the pins sticking out – the “female” version has holes and is normally found on the back of a computer):
VGA connectors look like this (these are very common on both old and new monitors but the Raspberry Pi does not have a VGA output):
An Ethernet cable with an RJ45 connection to connect to your home broadband router/modem (Wi-Fi on the Raspberry Pi can be tricky – a cabled connection is often easiest to start with) – often these are supplied by your ISP with the router/modem:
Some headphones or speakers with a 3.5mm stereo TRS connection (if you want to hear any sound from your Raspberry Pi):
You might also want to buy a case for your Raspberry Pi but that is by no means essential. Many people will already have the components listed above but if you need to buy them, they shouldn’t be too expensive. Probably the most expensive parts are the keyboard and mouse but I picked up a wireless mini keyboard and mouse from Maplin today for £14.99 and they worked out of the box with my Pi. You might also want to get a powered USB hub if you plan to use more than two USB devices (for example if you want to plug in a webcam, a USB flash drive, or a hard disk).
Putting it together
All of these components are different sizes and shapes so should be pretty easy to plug in. It doesn’t matter which of the two USB plugs are used for the keyboard and the mouse but this diagram (from the Raspberry Pi Foundation’s quick start guide) should help:
Just make sure that the power is coming directly from a 5V supply plugged into the mains and don’t be tempted to run a cable from a USB socket on a PC!
The operating system
Remember that I said I wasn’t going to show you how to prepare your Raspberry Pi with an operating system? There are other guides on the Internet (the Raspberry Pi website is a good place to start) but I strongly recommend you buy an SD card with Raspbian pre-loaded.
If you don’t know what an operating system is, don’t worry – it’s the software that runs on a computer when you turn it on and performs basic functions like driving the screen, keyboard, etc. (like Microsoft Windows on most PCs or Mac OS X on Apple Macintosh computers). Modern operating systems tend to include other functions, like web browsers and media players. Other applications can then be installed on top of the operating system to carry out more specialised tasks (like a word processor, an image editing package, or communications software like Skype).
Raspbian is a Linux operating system – that means that it is freely available (although some organisations might charge for supporting Linux distributions) and that the operating system is similar in many ways to a system called Unix that has been around for over 40 years and is used on many computer systems all over the world.
Logging in and getting going
After all of the “peripherals” (screen, keyboard, etc.) have been plugged in and the power has been switched on, you should see some characters appear on the screen and a prompt to login.
At the login prompt (which will say something like raspberrypi login: followed by a flashing _ cursor) type the username pi and press the Enter key, then type raspberry and press Enter at the password: prompt.
Once you are logged in, the prompt will change to pi@raspberrypi:~$ followed by a flashing _ cursor. This is username@machinename so you can see that your user is pi and the computername is raspberrypi.
These are the default username and password settings but you really should change the password to something that only you know (I’ll tell you how to do this in a moment).
The first time you start your Raspberry Pi (the first “boot”, as us geeks like to say), your Pi will prompt you for some setup information. It’s important to select the options to expand_rootfs (expand the operating system to use the whole of the memory card) and change_pass (change password).
If you ever need to run this setup programme again, then the command to type is:
Press the Enter key after typing the command (and for any other commands in this blog post). Then, just follow the instructions on screen.
Many people will find the command line interface (text-only, also called a CLI) unfriendly, so you can load a graphical user interface (GUI) to see something a little more familiar, driven by a mouse, and with applications in windows. To do this, the command is:
This will slow down the Raspberry Pi a bit but it should be OK. There is a status indicator towards the bottom right of the screen (a green/black bar graph) that shows how busy the Raspberry Pi is. There are many applications pre-installed on the Raspberry Pi, accessible via the start menu (just like on Windows) and you can download others from the Internet (I’ll leave that for now – there’s plenty to get started already pre-loaded in Raspbian). Here are just a few ideas to get going with your Raspberry Pi:
You could try some programming in Scratch, or Python.
Or if that sounds a bit much for now, just browse the Internet (the browser is called Midori).
And, if you need to run any more commands from the CLI, then you can launch an application called LXTerminal.
Updating your Raspberry Pi
Before I sign off, it’s probably worth mentioning some commands that might be necessary to update the software on your Pi. Before I do that, I’ll explain something else – remember the command to run the Raspberry Pi Configuration Utility?
The sudo part of this is worth remembering. Your username on the Raspberry Pi (pi) is what we call a standard user. It runs with a lower level of permissions to prevent any unintended consequences from running applications that might change the configuration of your system. When we want to make deliberate changes, we use sudo to run a command as a super user (like an administrator in Windows or Mac OS X).
So, to update the software on the Raspberry Pi, run:
sudo apt-get update sudo apt-get upgrade
APT is the Advanced Packaging Tool – so apt-get is getting details of available software. update downloads details of the available packages (a “resync”). upgrade is updating the operating system.
Finally, there is a tool called rpi-update that can be used to update the firmware (that’s the really low-level code that drives the components on the Raspberry Pi board, underneath the operating system). This isn’t installed by default and is written by a programmer called Hexxeh. You can find more details on Hexxeh’s blog and download rpi-update with these commands:
This will download the rpi-update program and then change the permissions so that it can be executed (run) on the local computer. I found that I also needed to install git before I could use rpi-update:
sudo apt-get install git-core
to update the firmware on your Raspberry Pi. Generally you will only need to do this if you are having problems getting something to work.
So, we’ve seen:
What you need to buy/find to get your Raspberry Pi working.
How to logon to a Raspberry Pi running Raspbian and how to get past the command line and into a more familiar (graphical) environment.
Some basic commands to keep your Raspberry Pi up to date.
If you want to learn more, check out the Raspberry Pi Foundation website and there are also other resources available on the Internet. You could also read a book like Meet the Raspberry Pi by Gareth Halfacree and Eben Upton.
Much of the information in this post is from a talk given by Peter Onion (@PeterOnion) at the Milton Keynes Raspberry Jam, with additional input from Rob Bishop (@Rob_Bishop) of the Raspberry Pi Foundation.
The illustrations used are taken from Wikipedia and elsewhere as follows:
I booked onto the event and then noticed that it was on a Sunday morning. Evenings are generally not a problem for me but weekends are sacred family time so I thought I might have to pull out, until I realised my family would be away and I was home alone. Time to geek out!
This morning’s Raspberry Jam, organised by Peter Onion (@PeterOnion) did not disappoint. With around 30 enthusiasts of varying abilities and even representation from the Raspberry Pi Foundation, in the form of Rob Bishop (@Rob_Bishop), there were talks on a variety of topics, followed up with a tour of The National Museum of Computing (I’ll save that for a separate blog post).
Next, Brian Hogan demonstrated RISC OS on a Raspberry Pi. This is something I’d also seen at the London jam and the basic premise is that, as the ARM CPU on the Pi is a development of the CPU used in the BBC Micro and later Acorn computers, why not port the Acorn RISC OS operating system to run on a Raspberry Pi? RISC OS dates back to the 1980s and has many user interface features that are commonplace today (and a few that are less so – like the three-button mouse controls that replace menu bars). Currently available as an alpha release, it’s hoped that RISC OS Open (which comes in at less than 6MB and runs pretty quickly on modern hardware!) will be stable in time for the upcoming Raspberry Pi educational launch, providing opportunities for a BBC BASIC renaissance as well as access to commercial and open source RISC OS software packages.
The final session was a basic introduction to getting started with the Raspberry Pi. It’s all to easy to forget that, although the current version of the Pi was intended for developers in preparation for a broader educational release, it’s been massively popular with 350,000 boards shipped (and on target for a million by the end of the year!). Add to that, the Raspberry Pi foundation is 20 guys and girls who don’t get paid and who have day jobs – that’s a very limited resource pool to support an awful lot of people! Even so, the Raspberry Pi is not necessarily the most user-friendly experience for those who are not used to hacking around in a command line interface, so I’ll be writing a follow-up post this eveningI’ve written a follow-up post to help those of a less technical background to get going with their Pi.
Peter hopes to run future Raspberry Pi events at Bletchley Park on a monthly basis. I’m not sure if I’ll be able to attend every time but I hope to take the elder of my two sons along with me to learn some geek skills (“it’s time you learned about programming, son”), as well as picking up a few tips myself (like using the GPIO to control some electronics…). Watch this space for more Raspberry Pi adventures!
Much of the music I play these days comes from Spotify but there are times when I’d really like to stream my music to some speakers on the other side of the house that are plugged into an Apple Airport Express.
When adjusting the volume/pause/play etc. there is a short delay before the changes take effect (due to latency in the network) – so this is unlikely to work for live DJing (it was fine for my 40th birthday party a few months ago though!).
Now that I’ve taken the test, I just wanted to share some more experiences that might help people looking to do the same. I won’t say anything about the test content as there are strict disclaimers about that sort of thing – my post earlier today outlined my study/revision approach though (and it obviously worked as I passed the test) but here are a few extra pointers that might be useful:
The 4-hour time slot includes registration, pre-post exam questionnaires etc. (on this occaision, those weren’t offered to me) and the actual exam is 150 minutes long (as the courseware tells us – I believe there are slightly longer sessions for those who don’t speak English natively).
I found that I completed part 1 (40 questions, with a required pass mark of 55%) in about half the 60 minutes that are allocated but that didn’t give me extra time to use for part 2 (it’s still 90 minutes).
All of the responses are multiple choice, and you can mark questions to go back review them at the end, before moving on.
Confusingly, at the end of part 1, the only option is to “end” the exam – don’t worry, it does continue to part 2, even though it’s not clear that it will do so.
Part 2 is only 8 questions (for which the required pass mark is 60%), of the scenario-type with graded scoring (5 points for best answer, 3 for next, 1 for the least-best answer, and 0 for the distractor). I needed all of that time with some questions requiring reference to the TOGAF manual (provided electronically, more on that in a moment). If you allow 5 minutes per question to fully read the scenario and understand what is being asked of you, that doesn’t leave a lot of time to search the TOGAF reference, so it’s better not to rely on it too much and to save that for when you really need it!
I didn’t expect to get a score for part 2 immediately (at least not based on the advice from The Open Group) so wasn’t sure if I would get my part 1 score today either. Needless to say I was pleasantly surprised to find that scores were given for both parts 1 and 2 at the end of the test (a combined score on screen, and individual part 1 and part 2 scores on the test result certificate).
Prometric test centres have been dire since I first started taking Microsoft exams in the late 1990s (later I took some VMware ones too) but it seems nothing has changed. The test booking site feels like it was specified by the same user experience designers as the London Olympics ticketing site, with no ability to search for centres based on post code (I had to scroll through 5 pages of test centres, looking at each one to see if it was near me and had availability to book a test on the date I required). The centre I visited today had newer PCs than I’ve experienced in the past – even a widescreen monitor – but the software still looks like something from Windows 3.1 and the resolution was still 1024×768 (stretched, and spilling over the edge of the visible display!). That caused some challenges with the scenario-based questions (scenario on the left, answers on the right) – thankfully the keyboard allowed me to scroll as the on-screen controls were not visible…
Add to that the fact that I couldn’t even take a bottle of water in with me (some earplugs would have been nice too) and that the reference lookup of the TOGAF manual in the open book part of the test ran in an awful PDF browser that has terrible search facilities (and which crashed on me, requiring the test centre to restart the PC running my exam – thankfully back to the same state it was in before the crash!) – in all it’s not a very good user experience.
Hopefully all of this helps those who are less familiar with Prometric tests to prepare for their exam. Good luck!
After many years designing and implementing technology infrastructure, I’ve been trying to move “up the stack” out of the (multiple) domain architect space, towards solutions architecture and onwards to develop as an enterprise architect. That involves a mindset change to progress from the role of a designer to that of an architect but I’m on my way… and I currently manage roadmaps, portfolios (standards) and reference architectures (amongst other duties), so it might be useful to know a bit about Enterprise Architecture…
I thought it might help to get certified in The Open Group Architecture Framework (TOGAF) and I spent a week on a TOGAF 9 training course last year following which I received a voucher to sit the combined part 1 and 2 exam. At the time of writing I don’t know how successful I’ve been – in fact, this post is timed to go live at the moment when I’ll be sitting at a Prometric testing station, no doubt getting frustrated with a single monitor and limited screen resolution as I try to search a PDF of the TOGAF manual at the same time as answering questions… but, even so, I thought I’d share my revision experience for the benefit of others.
For reasons that I won’t go into here, there was a gap between my course and my exam voucher being released so I wasn’t able to take it whilst the content was still fresh in my mind. Several months later, I set aside a week to spend four days revising the content, and reading around the topic, before taking the exam at the end of the week but I found it hard to revise – my main strategy was to going over the course content again, along with a variety of other resources – all of which were highly textual (even the diagrams are unattractive) and, above all, excruciatingly dull.
The first and last two minutes are, understandably, an advert for the training that Knotion provides but then Craig gets into a really easy to understand overview of TOGAF and broader enterprise architecture concepts, even diving into service oriented architecture (SOA) at one point. These are freely available on YouTube but, based on watching them, I would suggest that Craig could package up some training content for remote delivery and it would be a worthwhile investment for people in the same situation as me. In fairness, I did start to get lost towards the end, and the overview doesn’t seem to strictly follow the TOGAF materials (that may be seen as a good thing!) but the first hour was really useful – there is definitely a market for high quality subscription-based training in this space. Remote delivery ought to drive down the costs and it would certainly be better than the Architecting The Enterprise course that I attended (of course, that’s a personal view and your mileage may vary – I’m sure many people enjoy hours and hours of very dull PowerPoint content mixed with some group exercises and squeezed into 4 days when 5 would be more appropriate…).
Of course, Craig’s 90 minute introduction isn’t everything I need to pass the exam but it has helped to cement a lot of concepts in my mind. After watching the videos, I stopped working through the course materials in detail, and concentrated on a more general understanding of the Architecture Development Model (ADM) and the related TOGAF concepts. The TOGAF Version 9 Pocket Guide (which was provided on my training course) helped here, as did the Practice Test Papers (also from the course but available online for a fee). Other potentially useful resources include:
I’m still not sure I have enough knowledge to pass the exam (we’ll see – my scores in the practice tests were OK but not outstanding) but I do feel better prepared and, if anyone finds some useful, modern, engaging aids to learning about enterprise architecture in general and TOGAF specifically, then please do leave a comment!