Skip to main content

Dell XPs15 9500 rant - and Killer networking

 well i bought a new laptop.  For most of my career i have been working on the road so had an appropriate laptop for lugging around, with all the RAM/CPU sacrifices that that entails.  The last couple of years I've been more home-based due to my role, so finally decided to pony-up and buy myself an XPS15 9500.

£2500 is not an unsubstantial purchase but i was pretty confident in it.  Reviews were good, 32GB ram means finally Teams isnt eating all my RAM up (thanks MS) and it arrived.


Within 6 weeks it had had a catastrophic failure of the MOBO.  I have full next day support so an engineer arrived and replaced all the inner workings of the machine (!) and all appeared well.  


However since then this machine has been a nightmare.  The network card inside is Killer AX1650 and it "should" be grand.  However:

- it syncs to my network slower than 4-5year old machines (c.100-300Mb/s)

- it drops packets all over the place, which is a real issue when your a home worker (it always seems to happen when i am asked a question on Teams calls too, which is typical!  Like it knows!)

- Bluetooth is also AWFUL - to the point that at times i cannot use a bluetooth keyboard because you end up with wooooooooooooooooooooooooooordsssssssssssssssssssssssssssssssssssssssssssssssssssssss likeeeeeeeeeee tttttttttttttttthis.....................


Just a reminder - £2,500!!!

I had another mobo replacement (wifi chip is soldered on!) to try and fix it with no change whatsoever.


Currently i am on my third support case with Del and am 3 weeks in.  Having been told by Killer to install THEIR drivers and found no improvement, Dell told me i shouldnt do this so we put back their drivers (no change) and Dell then told me to "try the Killer drivers".... 

**screams into the void*


I know what comes next - go through the Killer "diagnostic" document and try all 15 steps on trying to fix it, which include:

- setting preference for either 2.4 or 5ghz - why would i do that??

- messing around with driver config settings

- uninstalling drivers, cleaning them out completely and reinstalling - been there, done that (twice)

I have also been down the Killer "support" route which normally involves

- raising case

- wait a week

- get told to do a clean install of new drivers

- feed back issue still there

- wait a week

get told to do a clean install of new drivers released that week

- and repeat ad infinitum

Between Dell and Killer they have really messed my machine up.  



Comments

Popular posts from this blog

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 ...

SP2 released

Office Project Server 2007 Sp2 has now been released.  see the details here - http://blogs.msdn.com/chrisfie/archive/2009/04/28/announcing-service-pack-2-sp2-for-microsoft-project-2007-and-microsoft-project-server-2007.aspx .  see teh webcast here http://blogs.msdn.com/brismith/archive/2009/04/28/project-server-2007-service-pack-2-sp2-is-now-available.aspx Blogged with the Flock Browser

Reporting from Project Server 2016 - multiple sites and userviews

Just a quickie... I've been interested in how MS have handled the "multiple PWA sites in a Content DB" thing since I read that this was their new approach.  Most of my reporting is via SSRS so i am reliant (still... in 2016) on DB queries rather than OData feeds (tsk) and this "querying a PWA DB with more than one PWA site in it is unsupported" quote was worrying me. So it looks like what is happening is this. When you create the first PWA site in a Content DB it hard-codes the SiteID into the _Userview view design elements.  This means that your first PWA Site is the default.  All the data for subsequent sites are still held in the tables against separate SiteID's but you cannot utilise the OOTB _Userview components (see below) SELECT        ProjectFields.... FROM            pjrep.MSP_TVF_EpmProject('FF19B767-CA6D-4C4C-B123-C0B5AE5354D6') AS MSP_EpmProject  LEFT OUTER JOIN         ...