Re: Positive support experience on a 600m




"Leythos" <void@xxxxxxxxxxx> wrote in message
news:wXY2f.94787$lI5.9308@xxxxxxxxxxxxxxxxxxxxxxxxx
> In article <0_X2f.7579$ae.4559@xxxxxxxxxxxxxxxxxxxxxxx>,
> tomtoo@xxxxxxxxxxxx says...
>>
>> "Leythos" <void@xxxxxxxxxxx> wrote in message
>> news:4IX2f.31726$tD4.28470@xxxxxxxxxxxxxxxxxxxxxxxxx
>> >I have a client that spent two hours on the phone with Dell Support out
>> > of Panama last night for a laptop that gave an error about missing a C:
>> > \Windows\System32\config folder and would not boot.
>> >
>> > The tech had the user try a repair/reinstall, even though the client
>> > told the tech that the drive was making a clicking sound.....
>> >
>> > This went on for the two hours and it was not resolved - the tech told
>> > the client that they needed to do a wipe/reinstall and to just follow
>> > the instructions in some document...
>> >
>> > Today I came in and booted to the recovery console, did a check-disk
>> > and
>> > found lots of errors (as expected) but it was able to fix enough to
>> > boot
>> > and copy their files to the network.
>> >
>> > I told the client that the drive needed replaced. From past experience,
>> > if the system will boot, Dell support won't replace the drive. The
>> > customer asked me if there was some way to get the drive replaced
>> > without a hassle.....
>> >
>> > I removed the drive from the laptop, booted it - it failed stating that
>> > drive 0 was missing.... Called support, the tech had me do a Diagnostic
>> > test using the F12 option for startup... Found the drive was
>> > defective... Sending new drive over-night - total service call time (on
>> > the phone) was 15 minutes......
>> >
>> > If I had left the drive in the laptop it would have been hours of BS on
>> > the phone (based on my experience) with the tech....
>> >
>> > So, on Wednesday when the new drive arrives - ghost old drive to new
>> > and
>> > we're up and running.
>> >
> [snip]
>>
>>
>> In my experience, Dell has me run diagnostics, which are pretty good, and
>> agrees to replace the drive pretty quickly. CTRL-ALT-D.
>>
>> I've never had to resort to taking the drive out.
>
> But have you had a drive, clicking, but still working for the most part,
> that they replaced BEFORE it completely failed?
>
> On a different note, your Usenet client doesn't snip signatures.
>
> --
>
> spam999free@xxxxxxxxxx
> remove 999 in order to email me


Yep. It did fail the diagnostics.


.



Relevant Pages

  • Re: Positive support experience on a 600m
    ... >I have a client that spent two hours on the phone with Dell Support out ... >told the tech that the drive was making a clicking sound..... ... >found lots of errors but it was able to fix enough to boot ... Dell support won't replace the drive. ...
    (alt.sys.pc-clone.dell)
  • DHCP, dual NIC, DHCP failure
    ... abandon the DHCP protocol about 50% of the time. ... and a Win2003 server that was both boot server and DHCP server. ... It appears to me that the DHCP client runs independent threads to execute this ...
    (microsoft.public.windowsxp.embedded)
  • Re: Jumpstart x86: How not to PXE after jumpstart finishes and reboots ...
    ... :>> PXE and later resets it after the install is complete to booting from ... menu file on the boot server change post-install to boot from the hard drive ... For each client, there ... That symlink is the path that the DHCP server hands to ...
    (comp.unix.solaris)
  • Re: Win2000 diskless client
    ... Did you know you could you use Argon's Client Management Services (CMS) as ... your boot server for diskless or terminal server clients? ... with a PXE boot ROM onboard and your legacy computers can now run more ... The terminal client initiates a PXE network boot using the onboard PXE ...
    (microsoft.public.win2000.setup_deployment)
  • Re: Remote boot server feedback
    ... Files\Windows Embedded\Remote Boot Service\) and change particular client setting to start abortpxe.com boot program for it. ... The security problem, though, could be fixed if you have access to the server share only on the XPe client boot from ... > What is missing is a way to let the remote boot server program know ...
    (microsoft.public.windowsxp.embedded)