11 October 2007

More on Remote Access

As a follow-on to my post on the remote access tool GoToMyPC, I recently discovered another service called LogMeIn.  This service provides similar functionality, but has a free subscription option (a price most people can live with).  The free subscription does not allow file transfers, remote sound or other bells and whistles found in the premium subscriptions, but does provide basic remote control options.  Here's the service comparison page on the LogMeIn web site, which provides a detailed breakdown of the functionality offered through the free and "pro" versions of their service.

During the past few weeks, I've had the opportunity to use LogMeIn extensively -- remote controlling a client server -- and found it to be reliable and easy-to-use.  In all cases, I had good bandwidth available, so I can't speak to its performance over lower bandwidth connections.  That said, if you're looking for a quick and easy tool to provide basic remote control of either a desktop or a server, you should give LogMeIn a look.

27 September 2007

Interesting Excel 2007 Bug

I came across a blog entry from from Lori Pearce's "All Things SDK" blog regarding an Excel calculation bug. Turns out there is what appears to be a serious flaw in certain calculations in Excel. The actual calculation is irrelevant, it's the result that matters. Calculations with results that should be 65,535 and 65,536, in addition to about 10 other results produce very strange and highly inaccurate results. For example, if you multiple 77.1 x 850, the answer should be 65,525, but instead yields 10,000. However, the real problem, as explained by the Excel team (specifically David Gainer) is the following:

"This is an issue in a function that puts numbers in cells, so the values in Excel's memory are actually correct. Imagine A1 contains =77.1*850 ... Excel actually calculates the correct answer, and you can see that if you use VBA to check the value for A1 - it will be 65535. But in the function that takes that value and formats it to be displayed on the screen, for the values described above, there is a bug. Any calculations based off that cell will be accurate too."

Here's an example of the bug shown in Excel 2007



In all, there appear to be 12 results in 9 quintillion that produce flawed output in Excel.

From what I can tell, Microsoft is working on a patch and this bug does not affect earlier versions of Excel. Here's an entry from the Excel and Excel Services Team Blog with a more in-depth description of the issue and what they're doing to address it (also written by David Gainer).

The original blog entry for Laurie's post can be found here. More background on the generally difficulties in executing math functions in a computer can be found in the following blog entry on Wolfram's blog by Mark Sofroniou "Arithmetic Is Hard--To Get Right."




18 September 2007

SharePoint 2003 SP 3 Released

A new service pack has been released for both SharePoint Portal and Windows SharePoint Services (2003/v2). The KB article on the update can be found here: http://support.microsoft.com/kb/923643.

Thank you to Ian Morrish at WSSDemo for posting a link to the KB article.

27 August 2007

Recycle Equipment to Save Capital

Many small businesses are increasingly pressured to upgrade their systems -- spending money on both hardware and software -- to keep their technological systems running smoothly. Unfortunately, there is also pressure to conserve funding and manage cash. Consejo, like many of our customers, faces this challenge as well. However, we've found one small way to do both -- upgrade our hardware while spending less.

As a consulting firm, we perhaps have more hardware and software demands than the average small business -- technology is literally our business. As a result, we're constantly upgrading, changing and moving hardware and software. However, we do not have always have all of the funding necessary to meet our immediate needs. To balance our need for faster hardware and our ability to "pay for it," we suppliment our new equipment with used and/or refurbished equipment. The sources of this equipement tends to be varied, depending on our needs and expectations, but the cost discounts over the equivalent new equipement help us manage our funds more effectively and give us the needed hardware performance boost.

For those of you who might interested in some of the places you can find refurbished and/or used equipment, I have provided a list the categories below. In each category, I have tried to provide an example. Please understand that any vendor listed in this blog entry does not imply a specific endorsement. In addition, you should absolutely do you own research to ensure you find the right vendor for you firm.

  • Off Lease Equipment
    Lots of medium and large organizations lease their equipment to help them manage both cash and keep their infrastructure current. Once the equipment comes off lease, the financing companies that held the note will auction off the equipment. Occassionally this is done through the equipment manufacturer or sometimes through a used equipment dealer. Either way, smaller firms can acquire this equipment, which is typically 2 to 3 years old, for 50% to 70% off the original pricing (sometimes more). On example of an "owned" (owned by a financing company) reseller of off lease equipment is 2nd-Byte.
  • Vendor "Factory Outlet"
    Major hardware manufacturers often have a refurbishment program. Refurbished machines ("refurbs") come in two varieties: a) equipment that was damaged or flawed during the manufacturing process and repaired or b) equipment that was purchased by a customer and returned (once the equipment is unboxed, it can not be sold as new). Typically, refurb customers can save 20% or more off the cost of similarly configured new equipment. Also, this type of equipment tends to be more technological current when compared with other sources of "not new" equipment. One example of a factory outlet is Dell's Factory Outlet.
  • Used Equipment Dealers
    The name says it all -- previously used equipment being resold. Used equipment dealers market all sorts of used equipment and their sources for this equipment are varied (unlike the off lease companies). However, they tend to be a good source of "quality" used equipment, meaning that they tend to ensure the equipment is operational prior to being shipped to their customers. Further, some vendors offer warranties on the equipment of varying lengths -- sometimes as long as new. One example of a used equipment dealer is Stallard Technologies.
  • EBay
    Good old EBay. What can't you find there? Ebay tends to host a lot of used equipment "stores" as well as being a source for individual sellers of used equipment. Obviously you should check the seller feedback scores before buying, but you can find some great deals on equipment. In most cases, the sellers offer a DOA ("dead on arrival") warranty, but that is usually it. As a side note, Dell officially sells some used and/or off lease equipment through EBay through the member ID dell.computers.
While keeping up with the technological Jones' can be difficult, judicious purchasing of used or refurbished equipment can lessen the investment, but provide most or all of the value of new equipment. The next time your firm needs to upgrade equipment, you should consider these or other sources before you buy new immediately. As an additional benefit, buying used or refurbished equipment will keep that machine out of a landfill that much longer and help reduce the global landfill footprint for old computer equipment.

13 August 2007

REVIEW: Remote Access with GoToMyPC

Often being involved in or running a small business requires you to be in many places at once. You need to take a meeting with a customer, but you're meeting at their location, not yours. However, you still have to access data that may not be portable, simply not loaded on the laptop you have with you or you don't have your own machine immediately accessible. Alternatively, what if you're home (not actually working) and need to access a file on your computer in the office? What do you do? If you're like many customers I meet, you either have to anticipate your need (loading that valuable data on your laptop or a USB thumb drive) or you do without (in many cases this really isn't an option, but more a consequence). You could also turn to a "corporate" solution of a Virtual Private Network (VPN) that allows you to remotely connect to your businesses network to retrieve your data. Certainly a VPN is the ideal solution for true remote network connectivity, but it also comes with the burden of being somewhat complex to setup/configure and requires you to spend more money on equipment and/or support. Further, VPN-type connections are frequently blocked by corporate networks and, sometimes, your local coffee shop's WiFi network. So what can you do? The answer could be a web-based technology like GoToMyPC.


GoToMyPC is a technology that was aquired by a Citrix a few years ago, but has been around for quite some time. Essentially, it enables a user to remote control a PC using a web-based Java application. What does this really mean? Well, no matter where you are, if you have an Internet-connected computer and a web browser, you can access that machine at home or work or somewhere entirely different. GoToMyPC allows you not only to control the machine, but also transfer files between the "guest" (the machine that is controlling) and the "host" (the machine being controlled). Having tested this service under a number of different circumstances (and connection speeds), I can attest to the utility of the service. The following is just a partial list of some of the ways I've used the service:


  • Remote access to files stored on my office desktop
    I travel a great deal and occassionally will put something on my desktop while I'm in the office, but forget to pull it off of that machine before I leave. With GoToMyPC, I just connect to that machine and transfer the data I need.

  • Accessing applications not loaded on my laptop
    I have been using QuickBooks to manage my business since Consejo started. While I've recently started using the Online version of QuickBooks, I had previously used the Professional version. Since the data can only realistically exist in one place, I needed a way to access the application when I wasn't in the office. I could have loaded it on my laptop, but I also didn't necessarily want sensitive financial data "out in the world" where something bad could happen. Using GoToMyPC, I was simply able to "dial in" to my office desktop, do what I needed to do in Quickbooks and get out.

  • Remote Support
    When you're the "technical" guy in the family, you tend to get a lot of "help desk" calls from relatives. In my case, I get these kinds of calls frequently enough to warrant a solution where I didn't necessarily have to step my relatives through a troubleshooting process. It's often much easier for them to simply call, tell me they're having a problem and I remotely connect to their machine. Once I've connected to their machine, I have the option of "showing them" how to correct their problem, simply fixing the problem for them or scheduling a time when I can connect later to do some more investigation.

This list is obviously not exhaustive, but it is a realistic picture of what I've used the service to accomplish. I can honestly say that I use the service a few times a day for almost all of the applications in my list. While it is clearly targeted at controlling a single machine, once you're connected to that single machine, you have the option of using a Windows-included technology like Remote Desktop to control other machines within the remote network (this is good for remote network administration of servers or other machines connected to the same network as the host). For me it has been well worth the $179/year subscription fee (you also have the option of paying around $20 monthly).

In short, GoToMyPC is an excellent technology for providing secure and relatively reliable (as reliable as the Internet connection you have) remote access.

25 July 2007

Access Denied when trying to Schedule a Crawl in SharePoint

While I'm not a huge fan of simply re-posting content originating on other individual's blog, this particular re-post is warranted, if for no other reason that it was a bear to find the solution. My hope is that more references to the posting will increase the likelyhood that someone else will spend less time finding the answer in the future.

Now, effectively the problem I encountered was an "Access is Denied" message when trying to schedule a search crawl in Office SharePoint Server 2007 (RTM). While, I could manually start a crawl and it would successfully complete, I was not able to create a schedule for either an incremental or a full crawl. Apparently, the trouble was missing permissions on the Tasks folder in the Windows directory; the "WSS_WPG" group (created by SharePoint during installation) needed read and write access to the folder.

It totally makes sense that SharePoint would leverage scheduled tasks to kick off scheduled crawls, but I would have hoped that the installation process set this for you. In my case, the server I dedicated to the index function was a "recycle" and was never reloaded with the OS -- the prior implementation of SharePoint was uninstalled and I re-installed the new implementation over top. In hindsight, this may not have been such a good idea, but we live and learn.

Here's the article that saved me the trouble of rebuilding my machines (yes I was that frustrated): http://www.folin.se/index.php/category/microsoft-office-sharepoint-server-2007/

Many thanks to Michael Folin for posting such a great tip!

08 July 2007

Effective Project Management in Small Organizations

I've had the good fortune to work in a number of different organization sizes, in addition to working with a wide array of individuals, project types and technologies. In large part due to this broad experience, I've seen my share of successful, mostly successful (in spite of team member actions to the contrary) and failed projects. In all cases, I've learned a good deal about what makes project successful and not so successful. Particularly in small organizations (either in terms of employees or revenue), making projects successful proves to be challenging, since mistakes can't simply be brushed aside by adding more money, resources or both. As a result, smaller organizations need to be especially careful how they manage their IT projects. Unfortunately, these are the very same organizations that have little or no discipline around managing projects and, generally, think a bunch of really smart people simply "get it done."


Most recently, as Consejo was completing a series of projects for a medium-sized customer, I found myself helping them think a bit differently about managing projects -- gathering requirements, deciding what functionality "get in" to what phase, how to assign resources, how to perform solid on-going management and how to test and deploy the project once complete. While Consejo won't be involved in this next project phase, the information we shared with them is relevant for a great number of companies. As such, I thought it would be worth sharing what I shared with them. To that end, here are some general best practices we have developed at Consejo to help us and our customers manage projects to a successful conclusion.



  • Make sure you understand what you want to build
    Another way of saying this is "make sure you document, review and validate requirements." I suppose this goes without saying, but Consejo has done work for more than one customer who felt that the business users (the folks who create requirements for applications or IT projects) simply needed to "tell" the IT group what they want. Often words and/or phrases like "simple," "shouldn't be hard," and "this isn't rocket science" creep in to those descriptions. Unfortunately, these customers often give requirements like "needs to be easy to use." While this is truly a requirement, what's missing are the details like: what is "easy" in the context of this requirement, what metrics do we use to measure successfully meeting this requirement and, most importantly, who's the audience for this "easy" application? Don't get me wrong, a reasonable person could arrive at approximations of "easy" on their own, but as the project starts to get close to finishing up and folks are rushing to meet deadlines, both IT and the business tend to get pretty picky about requirements; (over generalization coming) business users want to continuously tweak the application and IT simply wants to establish that they've met a particular requirement and move on. So, be sure to document, review and validate requirements up front -- before the coding or development begins.

  • Establish a good change control system
    Almost no one can argue that requirements are fixed once they've documented, reviewed and validated. Even in the best case scenario, requirements change -- the business climate changes, the audience changes, new insight emerges or the Earth starts spinning in the opposite direction. Ultimately, something always changes. However, the difference between a well-run project and one that will spin out of control, is how the collective team developing this solution manages changes. Consejo recommends having a well-established and formalized process for defining, submitting, validating and approving changes to an in-process project. Project teams must understand precisely what the new requirements is, how it fits with the existing requirements (e.g. what changes and what doesn't), the impact to the project effort and/or duration and, if applicable, the cost of the change (which is usually tied to increases or decreases in effort -- but not always). More often than not, a bad project is the result of an unending set of changes, mid-project, that no one (including the folks providing the requirements) keep track of well enough to be able to establish whether the new application meets the modified requirements. This situation usually results in a very heated back-and-forth discussion at the end of the project, where no one is happy with the final outcome.

  • Set project scopes so that you can meet requirements quickly
    Very long projects tend to yield the most defects and the most dissatisfied end users. Especially in IT, where the underlying technology changes rapidly, long projects simply aren't practical. Consejo recommends that customers define project scopes that can be accomplished (start to finish) in three months or less. This may seem unreasonably short, but consider that projects that take six months or longer suffer greatly due to changes in business climate (e.g. external to the organization) and organization needs (e.g. internally driven requirements). Having personally worked for organizations that had a "13 week year," a three month project allows organizations to quickly realize benefit without being unreasonably sidetracked by either internal or external forces. In addition, having such a tight project delivery schedule forces both IT and the business to focus on the highest value requirements and/or features, pushing other features or requirements out until later phases. To illustrate this problem, consider projects that take six months or longer. Businesses typically make changes to any number of aspects of approach in the market -- be it advertising, new product launches or competitive advantages. Making the business wait for a six to twelve month project to complete, just so that business changes can be integrated into this new application is an unreasonable expectation (especially if IT doesn't want to get a flood of change requests). A three month time line is much easier to manage and provides more immediate opportunities to improve the application once the development cycle has been completed.

  • Use the "metrics for success" to test the project outcome
    Testing anything seems to be counter to corporate culture. This statement may seem overly dramatic, but I've been involved in more than one project where the customer expected less than a week's worth of testing for a project that took three months to complete (I've also worked for firms that understood testing to be the period immediately after the application was completed and place into production -- when real customers were using the tool). Further, these same customers are the ones that tend to "tell you" the requirements, without documenting and validating them. If an organization truly wants to be successful, it takes the time to document requirements and indicates what success means in terms of satisfying a requirement. They then use this documentation to craft a testing strategy to ensure success. For example, if "easy" to the customer means that a user can get to or access a particular function within two clicks, then there should be a corresponding test scenario that allows a tester to validate the application has met this metric. If there isn't a formalized approach to testing, you end up with developer-test solutions and developers inherently know where not to go to break their own code.

  • Find the right people, not the convenient people
    In today's market, it's tough to find qualified candidates, get them involved in your project and/or find a candidate willing to work for what you can afford. Most often, the best resources are busy, stretched to thin and/or asking too much. If anyone has recently tried to find a good SharePoint resource, you understand what I'm describing. However, finding the right resource to lead, manage or participate in your project is critical. When describing the "right" resources, I want to be clear: the right resource isn't necessarily the most technically savvy, but the best well-rounded individual. The right resource, beyond being technically qualified to participate in the project, should understand and adhere to good project management practices (even if they're not a project manager), they need to be a good team player (I've met many "smart" and technically superior resources who were terrible team players) and, most importantly, they need to be able to find the answer if they don't have it themselves. In short, they need to be flexible, resourceful and have good "people skills." Some companies make the mistake of reallocating resources who are underutilized to projects when their short of team members -- either out of convenience or ignorance. This was common in the mid-nineties, when administrative assistants were made into "web masters" because they were enthusiastic and the web was thought of as a "toy" (this was especially true when companies were starting to create intranets). These admins may have understood HTML, but they didn't understand what the impact was to the organization or how to make the intranet work for the organization. In addition, However, consider this: the better resources in the market can often find faster ways to get your project done -- even if their per unit cost is higher, the project will likely cost you the same. In addition, these resource also understand how to make this new application "real" for your organization by being able to interact with the business and, potentially, end-customers.
This list is certainly not exhaustive, but it covers the points that are often overlooked by organizations taking on IT projects. I hope it's useful to you and I would certainly appreciate any feedback you may have.