I won’t be buying a Seagate product for a long time

I’ve been in the IT business for over 10 years now and for a long time regarded Seagate as brand to be relied on. They seemed to have a high level of design integrity and quality. The FreeAgent Pro external drives were fantastic – fast, quiet, reliable. The 750GB ST3750640NS internal drives were solid and speedy. But things have changed.

I have never been so singularly disappointed with any IT products as I have with the hard drives Seagate has produced this year. Apparently they have shifted their production facility to the far east. Whatever the reason, there is absolutely no excuse for the staggering level of shoddy build quality of their current crop of hard drives.

I would say that in the last year approximately 80% of the PC’s, Servers, and NASes I have re-sold with Seagate hard drives and upgraded with Seagate hard drives have had drive failures. The figure may even be bigger.

To make matters worse, their RMA policy requires they receive the faulty drive before they ship a replacement. This invariably leaves the IT consultant in a precarious situation whilst awaiting the replacement – which may well also fail.

I was recently speaking to the a senior engineer in a highly respected data recovery company who confirmed this annoying situation. His recommendation was to stick to Samsung and Hitachi drives at the present time. I haven’t had a particularly happy experience with Western Digital hard drives so far this year but Seagate drives just take the biscuit.

Save yourself the hassle, don’t buy a Seagate. Not for a long time.

Comments

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more... but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box: \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in: UPDATE tbSingletonData SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Print Management Console Missing

I've encountered a few Windows 11 machines lately, some brand new, that haven't had the Print Management Console installed. Trying to run it from the Run menu using "printmanagement.msc" didn't work either. The fix is to run this from a command prompt: dism /Online /add-Capability /CapabilityName:Print.Management.Console~~~~0.0.1.0

DNS Dynamic Updates & DNS Scavenging

I was encountering an issue at a customer's site where the DNS records of their client PCs often would be behind or out of sync with the records in DHCP. Usually the IP address would be older in DNS and this was causing issues with scripts executing and network tools correctly resolving client PC hostnames to their correct IP addresses. I realised I needed to make some changes to their dynamic DNS updating configuration. After a lot of reading through Microsoft's documentation and various online forums, this is what I ended up configuring. Hopefully this may help someone, some day: - Make the DHCP server a member of the "DnsUpdateProxy" group - Create a new user account, in the "Users" OU, called "dnsdynamicupdates" - This new user only needs to be a member of the "Domain Users" group - no special privileges - Make the password strong and set it to never expire - Set this new user as the credentials used by the DCHP server in IPv4...

Artifact Weblog

Search This Blog