Post by: Eric Fontaine
Posted on: 8/21/2014 8:30:00 PM
Recently, we've had the opportunity to help several clients migrate their legacy physical or virtual infrastructure environments to converged infrastructure that consolidates the compute (server) tier and the storage tier into a single integrated appliance. Nutanix is a market leader in converged infrastructure and has provided our client's with the ability to significantly reduce their physical infrastructure footprint and scale linearly. Many clients are seeing the value in modernizing their infrastructure and removing reliance on a SAN as well as seeing significant reductions in energy, rack space & power requirements. One client managed to reduce 22U of Rack space into a single 2U Appliance! The Nutanix differentiator resides in it's ability to combine standard enterprise grade hardware with it's proprietary tiered Storage Control technology allowing for linear scale-out and ground breaking storage performance all at a reasonable price point. Each Nutanix node has a combination of Solid State Flash Storage & Traditional Hard Drive drives. The Storage controllers pool together all of the storage available and present it as either NFS or SMB 3.0 and is Hypervisor agnostic. How does it perform?One of the key benefits of the Nutanix infrastructure is removing the reliance on an underlying storage network, allowing the flash tier to be placed as close as possible to the compute tier.We were recently migrating a client from Hardware that was approximately 5 years oldFrom 3 Node Hyper-V 2008 R2 ClusterMid-tier SAN with 28 Disks Capable of roughly 4000 IOPS To3 Node Hyper-V 2012R2 Nutanix Cluster comprised of 6020 Model Nodes.Performance was benchmarked using inside a Windows Server 2008 R2 test VM before and after migration and the performance increase was astounding. Tests performed using SQLIO - 25GB Test File, 8 Threads, 8 Outstanding requests, 120 second duration as follows sqlio -kW -t8 -s120 -o8 -frandom -b8 -BH -LS C\TestFile.dat sqlio -kR -t8 -s120 -o8 -frandom -b8 -BH -LS C\TestFile.dat sqlio -kW -t8 -s120 -o8 -fsequential -b64 -BH -LS C\TestFile.dat sqlio -kR -t8 -s120 -o8 -fsequential -b64 -BH -LS C\TestFile.dat TEST-VM on Old HardwareMBPSIOPSAvg Latency (ms)Random 8 KB Writes11.161429.544Random 8 KB Reads12.181559.140Sequential 64 KB Writes195.673130.8719Sequential 64 KB Reads247.453959.2515 TEST-VM on NutanixMBPS IOPSAvg Latency (ms)Random 8 KB Writes189.5224259.22Random 8 KB Reads733.8393930.450Sequential 64 KB Writes1392.5622281.112Sequential 64 KB Reads3792.7260683.590 Performance IncreaseLatency Decrease Random 8 KB Writes1698%2200% Random 8 KB Reads6025%4000% Sequential 64 KB Writes712%950% Sequential 64 KB Reads1533%1500% While in-guest performance testing is never fully representative of real-world workloads, running identical tests within the same Virtual Machine on different hardware definitely shows how much progress has been made in 5 years!Post by: Bryant Gofsky
Posted on: 8/19/2014 5:58:00 PM
A customer that I'm currently working with began to have issues with the 'Connect To Office' functionality that is offered in SharePoint after installing Lync 2013 on computers that also have Office 2010.Symptoms There were two different symptoms that we began to see. First, some users would click 'Connect to Office' and then 'Add to SharePoint Sites'. SharePoint would indicate that the site had been added, but a link would never appear in the 'SharePoint Sites' explorer shortcutSecond, some users were completely missing the 'SharePoint Sites' shortcut in Windows explorer.Solution The solution for both issues required some edits and additions to the registry.The following registry key is crucial to the proper functioning of the 'Connect to Office' feature. The registry key is created as part of a normal Office installation.HKEY_CURRENT_USER\Software\AppDataLow\Microsoft\Office\15.0\Common\PortalNotice the reference to '15.0' in the registry key. This indicates a reference to Office 2013. This key would have been created after Lync 2013 was installed. However, we also have Office 2010 installed along with Lync 2013. Office 2010 would be designated by '14.0' (e.g. HKEY_CURRENT_USER\Software\AppDataLow\Microsoft\Office\14.0\Common\Portal). Since there is no reference to '14.0' in the registry key listed above, the 'Connect to Office' functionality will not work when you are using Excel 2010, Word 2010, PowerPoint 2010 etc.. Installing Lync 2013 seems to have removed(or changed) the version of the registry key that referenced '14.0'. I was able to fix this by manually creating the required keys. Create a new string value called 'PersonalSiteFallbackURL' in the following pathHKEY_CURRENT_USER\Software\AppDataLow\Microsoft\Office\14.0\Common\PortalFor the data value add the URL to your mysite host (e.g. http//mysite.contoso.com)*The LinkPublishingTimestamp key is created automatically when you start adding sites via 'Connect To Office' in SharePoint.I found that I did not have to delete the '15.0' registry hierarchyThis fix addressed both of the symptoms indicated above. It allowed the 'SharePoint Sites' explorer shortcut to be created for people who were missing it, and also enabled sites that are added via the 'Connect to Office' option to appear in the 'SharePoint Sites' explorer shortcut. Note that you won't see the newly added sites until you open Word, Excel, PowerPoint etc. and select 'Save As'.By default, sites that are added via 'Connect to Office' will not be added to the 'SharePoint Sites' shortcut for 24 hours. You can bypass this limit by manually restarting the Web Client service on your computer. If the links still aren't populating then you can delete the LinkPublishingTimestamp registry key (located here HKEY_CURRENT_USER\Software\AppDataLow\Microsoft\Office\14.0\Common\Portal), which will trigger a refresh the next time that you open Excel, Word, PowerPoint etc. and select 'Save As'. Alternatively, you can just wait 24 hours and then the links will populate on their own.