Preparing for a demo room install of IUM

The first and most important consideration, is when you will need to have IUM (or any other application FWIW) ready to demo.  Then plan to complete that installation and configuration well in advance of that date.  

While this seems fairly obvious, there are a few very good reasons to ensure that you do leave yourself plenty of time:
1) Your demoing the application, not how to troubleshoot it, you want the application up and running properly, and more to the point, you want to have time to familiarize yourself with the features and capabilities of the application before the questions start coming from your customer.  Yes you always have support available, but as a customer, I get a warm fuzzy feeling when my dealer is demoing to me, not talking to application support.
2) Focus on what you need to demo on the short term.  If you are demoing rules based printing, you would concentrate on having a functional server, a functional client, Rules in place that you've tested, etc.  Don't squander time on an embedded client if the customer isn't interested in an embedded, we can always come back to your demo server after the Rules demo to get embedded running.  (Embedded clients don't uphold rules, you can't demonstrate Rules on an embedded client, so if Rules are what the customer is interested in...)
2) Obtaining support is always at the mercy of the queue, if we're busy, this may impact your ability to get assistance in a timely fashion.

The next consideration should be the environment.  The task at hand is demo the application, not the support for that application.  Use clean machines for demo room installs.  This is particularly important with web-based applications like IUM.  Webservers are powerfully flexible platforms capable of supporting many applications.  But those applications may have conflicting requirements, and some may configure IIS such that applications like IUM encounter issues that they would not encounter in a clean environment.  Resolving such environmental issues is often part and parcel of an install in a customers environment, but that's a very different case than a demo room.

Virtual Machine hosting applications can be indispensable tools for this purpose.  You can checkpoint a VM right after installation, and revert to that checkpoint whenever you are installing a new application to demo.  After installing the demo software, and ensuring it is functional, you can then again checkpoint the VM so you can return to that configuration whenever you need it. Similarly when demoing embedded clients, factory reset those machines and try to return them as close as possible to the state that they were delivered in before proceeding with the embedded install.

Having a clean environment and planning to complete the work well in advance will help to ensure demo room setups run smoothly and the resulting demo's also run smoothly.



How did we do with this article?