Welcome to Kraft Kennedy

I recently had the good fortune to attend the SharePoint Conference 2009 in Las Vegas, which outlined the new features in SharePoint 2010.  Below are some of the things I took away.  I think this will be a huge improvement over the current version, and will offer a lot of very compelling new features, and a lot of good reasons to make the upgrade.

General Comments

The Beta will be released in November.  Final product will be released in the first half of 2010.

Microsoft is focusing on making the upgrade and updates easier.  You can upgrade the back end, while still keeping the master pages (look and feel of sites) the same.  Then you can upgrade the master page at the site level to test and get all of the new features.

Everything is 64 bit.  It requires SQL 2005 / 2008 64-bit, and Windows 2008 64-bit.  The server must have at least 4 GB of RAM.

A level 1 browser is required for users (IE 7 or 8, or FireFox 3) plus SilverLight for the best experience.

WSS is now called Microsoft SharePoint Foundation, and is still free.  SharePoint Designer is still free.  SharePoint Server still has Standard and Enterprise CALs.

There’s a limitation on data storage now if you don’t have SQL… The basic install uses SQL Express now (rather than Windows Internal Database in the old version), which has a 4 GB data limit.  So we should keep this in mind for small projects, and typically recommend SQL Server.

SharePoint has emerged as an entire platform, and Microsoft believes this will bring ECM to the masses, BI to the masses, etc.  Microsoft is also positioning this as a full featured internet-facing platform, as well as an intranet / extranet portal which 2007 was though of.

SharePoint should be evaluated along with Office 2010, since the integration is now extremely tight.  SharePoint can be the access point for all of the firm information.

The most impressive things I saw in 2010 were the workflow enhancements in 2010 and the Office web applications.  In many instances I couldn’t tell whether they were demoing things in the rich Office client or in the Office web app—the user experience is almost identical in either case!
Continue reading…

The legal industry has traditionally been conservative when adopting new OS and software versions.  Law firms need to know that whatever solution they choose to implement has been tried and tested.   This isn’t news to anyone.  Let’s see a show of hands of law firm CIOs who have overseen successful deployments of Windows Vista.   *crickets*.    Yep, that’s pretty much what I figured.

The landscape has changed though with the release of Windows 7.  There are a few reasons why Kraft Kennedy is advising our customers to deploy Windows 7 now:

• Still 6.x:  Since the build of Windows 7 is actually 6.1 (Vista is 6.0), most applications that were designed to be compatible with Vista will be compatible with Windows 7.   When Microsoft made the jump from 5.1 (XP) to 6.0 (Vista), it took software vendors months to re-write their products to be Vista-compatible.  We’ve seen these compatibility issues become more sparse with Windows 7.
• Better than Vista:  Simply speaking, Windows 7 is the OS that Microsoft wanted Vista to be.  It looks slick, performs well, and has a lot of useful features that firms will likely take advantage of.
• From Beta to Omega: Kraft Kennedy started using Windows 7 with our application set as soon as the first Beta was available.  Nearly all our staff was using Windows 7 fully before the RTM was released on October 22.  In addition, we’ve already developed processes for a completely automated and zero-touch deployment of Windows 7 using Microsoft technologies.

For reasons similar to this, Kraft Kennedy is also advising our Worldox DMS customers to upgrade the latest version, GX2, when implementing the new Windows 7 desktop.   GX2 is already supported on Windows 7, and like Windows 7, is using similar (but much improved) code to its previous version, Worldox GX.   Kraft Kennedy has had betas running in it’s research lab, and now has the final released version running as well.   The new features of GX2 were described in a previous blog post.

This week, Kraft Kennedy will be completing its first 64-bit Windows 7 deployment and Worldox GX2 rollout at a client site.  Initial pilot and lab testing has been successful, and the performance of launching Microsoft Word 2007 on 64-bit Windows 7 is a sight to behold!   Look for myself and other Kraft Kennedy bloggers to report on the success of this deployment in the coming weeks.

It’s time to start implementing the future today.

My last post Citrix Provisioning Services Part 1 – What Is It? served an introduction to what exactly Citrix Provisioning Services is capable of. Below I hope to open people’s eyes to using PVS for something other than VDI, as it is often thought of as a part of the XenDesktop suite. However PVS is actually independent of XD or VDI, and can be utilized in combination with XenApp to bring single-image benefits to the Terminal Services world.

Provisioning Services allows for server consistency, easier maintenance, dynamic servers, and aids in disaster recovery.

• Consistency – As a best practice every XenApp server delivering the same applications should be 100% identical to the rest of the farm. However, obtaining this is easier said than done.  By streaming the same image to every server, each server is inherently and 100% the same as the rest.
• Maintenance – Updating and patching large farms can be a very time consuming task, and anything done to one server must be repeated for the entire farm to maintain consistency. With PVS, patches and software installations are applied once to the master image and on next reboot, each XenApp server boots the new updated image. In addition to software patching and installation, Terminal Servers need to be completely refreshed periodically to keep them clean and performing optimally; they are used by dozens of different users, reducing performance and resulting in inconsistent servers. A typical server refresh requires the server to be re-imaged and the software redeployed, a time consuming process that can be prone to error, leaving a server in an unusable or inconsistent state. Operating system streaming with PVS results in a completely fresh and optimized server on every reboot.
• Dynamic – PVS allows for a dynamic XenApp farm instead of a static one. As load rises and additional servers are needed, they can be quickly brought online in seconds instead of hours. Conversely, as load drops, un-needed servers can be powered off or repurposed as needed. A server becomes a vessel for different workloads and can be a XenApp server one day and an IIS server another if need be. Since Provisioning Services is capable of streaming to both physical and virtual servers, administrators have the ability to utilize different types of resources all from the same master image(s).
• Disaster Recovery – Creating a disaster recovery plan for the XenApp environment often requires complex processes, scripts and configurations. Assuming a PVS server has been built in the DR site, and that the master image has been replicated as well, quickly bringing an entire farm of XenApp servers online becomes a simple task.

Creating a XenApp environment that is more dynamic and easier to maintain is a goal for many XenApp administrators. The addition of Provisioning Services to a XenApp implementation can go a long way to achieving those goals. By leveraging the single-image management capabilities of PVS, administrators can dramatically reduce the costs involved with deploying and maintaining their XenApp farms. While at the same time, guaranteeing consistency between and ensuring peak performance of each server in the farm. All while being capable of quickly adapting to changes in load and disaster scenarios.

Microsoft has announced that Exchange 2010 has been released to manufacturing with expected general availability and launch to be announced at TechEd Europe 2009 in early November.  More information on Microsoft’s official announcement of Exchange 2010 can be found at the MS Exchange Team blog here.  Exchange 2010 marks a significant milestone in the development of Exchange Server.  Some of the most important features have been summarized below but many more exist that make this a compelling upgrade for all firms. 

Please note that Exchange 2007 SP2 and/or Exchange 2003 SP2 are required for coexistence with Exchange 2010 in the same Active Directory site.

• Dramatically Improved Storage Footprint and Large Mailbox Support – Changes in the underlying storage architecture allow for a 70% reduction in I/O over Exchange 2007 and a 90% reduction over Exchange 2003. This allows for more efficient usage of storage and results in the ability to store Exchange databases on slower/lower-cost disk such as SATA.  This makes Exchange not only better performing for larger mailboxes but also more cost effective.
• Native E-mail Archiving – With Exchange 2010, basic archiving features are now included natively, allowing firms to reduce the footprint of production mailboxes and improve client-side Outlook performance.  While this functionality may not be as feature-rich as third-party solutions and even though it requires a to-be-released Outlook 2010 client to support it (or OWA 2010), it does present a much needed piece of functionality that many firms have desired natively for years.
• Database Availability Groups – All of the Exchange 2007 high availability and disaster recovery methods (Local Continuous Replication, Single Copy Clustering, Cluster Continuous Replication, and Standby Continuous Replication) have been deprecated and replaced with a single concept: Database Availability Groups (DAGs).  DAGs unify the concepts of high availability and disaster recovery into a single deployment and management process, thereby simplifying it dramatically over previous versions of Exchange.
• Native eDiscovery and Compliance Features – Multi-mailbox search, legal holds, and improved retention policies all combine to increase the native capabilities of Exchange to assist with compliance processes and discovery requests.
• MailTips – Exchange can now notify users if a message violates an aspect of IT or corporate policy (sending to unauthorized third-parties or exceeding a maximum allowed message size) or if the result of sending the message may be unexpected (recipient is out of the office or a distribution list contains a large number of recipients).  This can enable users to better understand the results of sending a message and potentially reduce confusion and calls to IT.

Please refer to my three-part blog post series on Exchange 2010’s specific benefits for law firms (Part 1 can be found at http://blogs.kraftkennedy.com/index.php/2009/08/19/exchange-2010-benefits-for-law-firms-part-1-of-3/).  Check back often for additional blog posts about the new features of Exchange 2010. 

Windows SharePoint Services (WSS) doesn’t come with a whole lot of web parts out of the box, but here’s a few handy ones we’ve found to spice up some of the home pages we’ve built.  These are all free and work with WSS.

• Tim Heuer’s RSS Feed Reader
  http://feedreader.codeplex.com/

Only MOSS comes with an RSS reader, and even that one can display only one feed.  This web part is invaluable if you’re using WSS.  This is the best free RSS feed web part that I’ve found, and it allows you to neatly pull multiple feeds next to each other.

• Bamboo World Clock and Weather
  http://store.bamboosolutions.com/pc-55-1-world-clock-and-weather-web-part.aspx

This web part neatly displays the weather in 3 cities side-by-side and can optionally display the time if they are in different time zones.  This is a nice looking web part and tends to fit nicely on the right-hand side of a home page for a firm with multiple offices.

• Amrein MSN Money Stock Quote
  http://www.amrein.com/apps/page.asp?Q=5731

This web part displays stock quotes, company names, changes, and percent changes pulled from MSN Money.  It’s the best free web part I’ve seen to do this, and will save a lot of time over trying to follow one of the examples online for doing this with a data view.

• Matt Jimison’s Twitter Search Web Part
  http://www.mattjimison.com/blog/2009/03/04/twitter-search-webpart/

This uses the twitter search API to search twitter based on the parameters you specify in the web part, and you can download the wsp or the source code from the web page.

• Kraft & Kennedy Google Search Box
  (Code below)

We’ve had a few instances where we were asked to put a Google search box on a SharePoint page.  This can easily be accomplished by just inserting a content editor web part on the page and editing the HTML directly.  You can paste in the following code, which includes JavaScript, to open a Google results page after the person enters a search term and presses enter or clicks a button.  This is of course a simple approach–you could also federate search results in your search center to include Google–but this simple html code works well in many cases.

<P align=left>Search Google: <INPUT id=Google name=Google onkeydown="javascript:if (event.which || event.keyCode){if ((event.which == 13) || (event.keyCode == 13)) {
window.open('http://www.google.com/search?hl=en&amp;q=' + this.value + '&amp;btnG=Google+Search','_blank','');
return false;}};"> <IMG alt="Go" id="btnGo" name="btnGo" src="/images1/icongo.gif" onclick="window.open('http://www.google.com/search?hl=en&amp;q=' + document.all.Google.value + '&amp;btnG=Google+Search','_blank','')"  onmouseover="this.style.cursor='hand'">
</P>

One of the great features of desktop virtualization (VDI) being touted by the industry is the ability to manage and update all of your desktops from a single central master image.

Citrix’s solution to the single image process is accomplished by a product called Provisioning Services (PVS). This software is the result of their purchase of a company called Ardence back in 2007. Provisioning Services is an often misunderstood piece of software, and its great benefits and potential are not necessarily apparent to everyone.

PVS works by streaming a master (read-only) image from the server to a target server or workstation. Any subsequent writes are then sent back to the PVS server and written to a cache file. The reads and writes are sent back and forth between the PVS server and target in a constant stream over the network. The easiest way to grasp this is to imagine that the cable connecting the hard disk inside of the server to the motherboard (and thus the CPU and RAM) is replaced by a network cable running back to the PVS server. The operating system sees the PVS disk as though it were a normal hard disk, and everything is done entirely transparent to the OS. The magic happens when the server is powered up; instead of booting from a local disk it is instead set to boot to the network card (PXE, BOOTP) which talks to a service on the PVS server, which streams the assigned operating system image to the target. The target device starts up immediately, as though it was booting from a local disk.

The beauty here is that this single read-only image can be simultaneously streamed to multiple diskless targets, both physical and virtual. This central image can now be maintained in one place. This makes tasks such as installing updates or new software quick and easy. After installing an update into the master image, all machines running that image will boot up into the updated image on next restart. To put that in perspective, think of the time and effort required to push out something such as a service pack to Windows or Microsoft Office to your entire firm. Now imagine simply installing that update once and having every machine in your environment receive that update on next reboot, without any additional effort.

Look for a follow-up post discussing the benefits that Provisioning Services can bring to a XenApp implementation.

High availability and site resiliency have evolved a great deal from early versions of Exchange through Exchange 2007.  While Exchange 2007 introduced the concepts of Single Copy Clustering (SCC) and Cluster Continuous Replication (CCR) for high availability and Standby Continuous Replication (SCR) for site resiliency, each had very specific benefits and drawbacks.  CCR gradually became Microsoft’s and the industry’s preferred solution for high availability because of its robust availability capabilities but concerns about manageability, scalability, and associated storage cost were all factors when settling on a design.  SCR extended CCR technology to provide a robust and cost effective solution for site resiliency but many firms were frustrated by the configuration and database activation processes and that all administration must be completed via cmdlets.
Continue reading…

With Server Based Computing and consolidation becoming increasing prevalent along with the enormous buzz of VDI, I think it is worth debunking some of common myths of XenApp and Terminal Server.  Below are the most common misconceptions that I continue to hear from IT folks today on the limitations of XenApp/Terminal servers that I have debunked from real world experience supporting and working with different terminal server environments.

Myth 1: Application compatibility is a huge problem on Terminal Servers.
There might have been some truth to this myth a decade ago, but in reality this is just not a big problem in the 2003/2008 world.  From my first hand experience, I can say that an application that works on XP will work on 2003, what works on Vista, will work on 2008, etc.  Are there some exceptions?  Of course.  However, these applications are few and far between, yet the “application compatibility” myth continues to circulate. This myth was probably true in the NT/2000 OS where applications did not do a good job of differentiating between “user” and “computer” parts of an installation.  Since Windows XP, application developers have done a better job writing “user” specific information in the user profile and “machine” specific information in Program Files, or HKLM.  I would probably attributed to the “Fast User Switching” feature introduced in XP.  Whatever the reason, this is just not a problem anymore.

Continue reading…

Move over H1N1; recent months have seen an uptick in a particularly sinister breed of virus, commonly called scareware.

This form of malware disguises itself to appear as though it is an anti-virus or anti-spyware program, when, in fact, it is exactly what it claims to prevent. Often, the rogue software will appear as a red shield in the system tray very similar to the yellow windows update icon, or in a web browser window designed to look just like Symantec or a similar anti-virus program interface. It will alarm the user that the computer has already been affected with spyware or malware, and urge them to click to scan the computer or clean the viruses off the hard drive. Of course, this will only download further malware, or require the user to purchase a registration key and refuse to remove the infection until that is done.

Continue reading…

With the release of VMware vSphere 4, VMware has released a very powerful management tool called Fault Tolerance (FT).  At a basic level, FT allows you to keep two virtual machines (a Primary VM and a Secondary VM) running in lockstep on two different physical ESX hosts.  If one of the ESX hosts were to experience a hardware failure, the VM protected with FT would remain running on the second host without any downtime.  This can greatly reduce downtime due to hardware failures and provide increased service levels for important applications.

FT is often compared to Microsoft Windows Failover Clusters, formerly Microsoft Cluster Server (MSCS), and in fact many have talked about how FT can replace Microsoft clustering altogether.  Rather than jump to conclusions like this, it is important to understand the use cases for both technologies.  In addition, there are several limitations to FT that need to be considered. Here are some important points to remember about FT:

Continue reading…