Skip to main content

Slightly off topic... choosing a new laptop

** Update ** decided to plump for the ThinkPad Yoga on an i7 and 8GB RAM.  I wish there was a 16GB option, and I will miss Quad Core but my back will be much happier! The final deciders were 

1) ability to use it on a train
2) "good enough" screen res (not this stupid high res fad thats going around) 
3) its an i7, even if its only dual core.  
4) It's a nicely made machine.  

Hoping to get it in a couple of weeks



My trusty (not) Lenovo W520 is approaching three years old now, and the heft of this machine is really starting to get to me, or should I say get to my ageing back.  So I reckon it's time to look at replacing her.

When I chose this beast back in 2011, things we're very different.  If I needed to demo SharePoint, I would have to bring along a Windows Server laptop running Hyper-V with some serious RAM and SSD add-ons, which meant my laptop options were limited.  The main contenders were some nameless HP thing, a Dell Precision and the Lenovo W520.

Now this lappy is 6lb or 2.8KG which is bad enough but the power cable weighs about as much as I do, and I think this has contributed to a rather nasty shoulder complaint!

Fast forward to 2014 and we have SharePoint Online, Project Online and decent enough upload speeds on cable to support RDP to my home server, all of which - assuming the customer has a wifi/guest network access point - mean the need for a workstation has dropped significantly.  Even without a network access point i can usually fall back on 3/4G and get "good enough" results.

So... the window of opportunity now presents itself for an "80% of the time" machine for doing the everyday stuff (docs, browsing, customer support and some BI stuff), whilst the Lenovo can sit at home to be called upon for the 20% that needs more grunt.

A colleague recently went for the Lenovo Yoga 2 Pro which is an ok machine but not really what I want.  I cant see me making use of Tent Mode et al, and it looks a bit plasticky (sic!) for me.  

Dell XPS13 - Well, its a Dell so it's dull dull dull.  Sounds like there's some issues around the cooling system (fan noise) which wouldn't be cool.  I find it hard to get excited about it

Lenovo X1 Carbon - Expensive.  Crappy keyboard

Yoga2Pro / Thinkpad Yoga - Could be the best of an average bunch. Thinkpad Yoga gets very expensive with a decent screen, and I am not sure of the necessity for the "mad resolution" of the Y2P.

Samsung Series 9 - seems impossible to buy, and i dont like buying computers from companies that sell Hoovers.  It's a bit shiny for my liking too (not picky, much!)

Macbook Pro 13 / Macbook Air - well I would have to run windows 8.1 on these machines which is a horrible thing to do to a Mac.  Potential for driver/software issues too.  MBA is a little behind the times on screen resolution now too.  The MBP is still a possible though.... 

Surface Pro 3 - I am worries about the typing position, which I suppose could be resolved by a keyboard when at home.  Docking station seems difficult to buy in the UK (I think I'd want something) and I am not 100% on hooking this up to multiple monitors, although it appears possible (USB hub or DP Daisychain)


I think my heart wants a Surface Pro 2 but the costs on purchase including keyboard, dock, etc do rocket up quite quickly.  It'd need to be a 256GB min on i5 (£1100) although I would prefer an i7 for those BI moments (£1339-1649) but those prices are way steep, the base i7 taking me to £1493 (including portable mouse as that trackpad won't cut it).  

well as we dont get the SP3 until the end of August 2014 over here in the UK, I guess it's a waiting game for now.








Comments

Popular posts from this blog

TPG Apps Highlights - Risk Matrix #projectonline #projectserver #risk

This post is the first of a series to highlight the apps available for Project Server and Project Online from the SharePoint store  ( https://store.office.com/search.aspx?productgroup=SharePoint&qu=tpg ) and direct via your local TPG office. The first of this series will look at the s imple plug-and-play apps that all users of Project Online can make use of quickly and easily.   T hese are: Risk Matrix  Milestone Trend Analysis (MTA) WBS Chart viewer Next we will focus on the challenge of  Resource Request Supply and Demand by demonstrating our more recent TeamLink and TeamManager apps. Team Manager App is a Resource Manager/Owner app for allocating resource supply to Projects and BAU activities and monitoring demands against commitments Team Link App is a PM tool for monitoring Project demands vs the supply provided by the Resource Managers  Finally I will highlight some of the benefits of our integration tools when used in the context of Project Online

Restoring PWA Site to another Web App in the same Farm

The scenario is this: SharePoint 2016 Farm with Project Server Two Web Apps Development UAT One PWA on Development Web App. I want to copy the PWA Site on Development web app to UAT to support a testing cycle. As far as I knew there were two options: 1) Content Database Restore and Attach Process would be backup your Dev Content Database, Restore to a new Content Database for QA, then mount the database on the appropriate web app and your off.... Problem:  Although you can do this with the -AssignNewDatabaseID switch in Powershell (to avoid two content db's having the same database id) the Site Collection (PWA) in the db still retains its SiteID which means there is a duplicate SiteID in the Configuration Database.  This stops the PWA site being created and alllocated correctly and becomes essentially orphaned. This method is only any good for MOVING not COPYING Back to the drawing board... 2) Backup-SPSite / Restore-SPSite I didn't believe this w

Migration Project Server (2010 to 2019) Issue 1 - Upgrading from 2013 to 2016 - Error encountered while migrating project data in Content database. The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users

I was intending to write a set of posts on the topic of migrating SharePoint and Project Server from 2010 on premise through 2013, 2016 to 2019 Azure, using SQL Managed Instance as the backend SQL Service.  This set of posts are still getting drafted and updated as we move through this cycle, but I came across a huge blocker this week that I wanted to post on, whilst it was fresh. Our Azure migration machines (2013 and 2016) are: - dual core 2.3ghz - 28GB Ram 2013 server is Windows Server 2012 R2 running SQL 2012 SP1 2016 server is Windows Server 2016 running SQL 2014 SP1 The Project Server dataset we are dealing with here is c.100GB (50% archive data). The uplift from SP/PS 2010 to 2013 went without a hitch over a 2.5hr period which was a huge win.  However when attempting to upgrade to 2016 we hit a hitch. Firstly some background:  When you perform the Migrate-SPProjectDatabase command, the following will happen (well it certainly did to us) - the ProjectWebApp DB fro