Dell Latitude 7400

I need a solution

Anyone had luck using standalone ghost instances with a USB boot stick on Dell Latitude 7400? My WinPE instance hangs up and freezes when trying to load. I don’t even get as far as launching ghost. Just see a Windows logo, a loading circle at the bottom, then a flash and the machine freezes.

At first I was getting just a black screen so I loaded the graphics drivers for this model into my boot ISO. Now it shows display but freezes. Have I put too many drivers in and am just burning up all the ram before I get to the ghost app? 

0

Related:

  • No Related Posts

Computer stuck at “bootguard”

I need a solution

Upon startup, one Win7 computer just gets stuck at the black screen with “bootguard _” on it. I’ve looked at several solutions online and so far none of them work. I do have a WinPE UFD with the encryption stuff on it, but any WinPE environment won’t even recognize there’s an internal hard drive at all. I can boot up with a GParted live CD and that will see the disk just fine. I can even browse its contents with the GParted live CD (between that and the SEE snap-in), so I know the disk is not encrypted.

I’ve tried using diskpart, but of course, the internal HDD is not recognized as even being connected by the Windows PE environment
I’ve tried using Bootrec.exe /FixMbr, but of course, the internal HDD is not…. you get the picture. Anything I’ve tried won’t work without the WinPE environment realizing that there’s a disk attached. Only live linux distros see the internal HDD.

Any suggestions would be greatly appreciated. Thanks!

0

Related:

  • No Related Posts

Injecting 802.1x cert into Symantec’s Automation Folder boot.wim

I need a solution

The original problem we are experience at the present time is “DHCP Service Retry” repeated error messages.  Yes we updated the NIC driver (I-219LM) and this did not resolve the error messages.  We have isolated it to the point where we need to insert 802.1x protocol into the WinPE Automation Folder.  This means we need to properly place our  802.1x pfx file onto the Notification Server and Re-create the Preboot Configuration ( BootWiz)  so that we get an 802.1x boot.wim file that can be distributed to the client.  To Date no one knows where to place this fix and/or perform the command sequencing to get this imported or inserted into the bootwiz process ultimately the boot.wim file.

We currently are using Rel 8.5 RU2, and running out of time.   So if anyone has performed a similar task please contact me with the steps you have taken and.or provide the instructions to successfully complete this challenge.

Thanks Steve

0

Related:

Can’t boot to PXE

I need a solution

Have 3 site servers running DS. Recently recreated the PXE files and now cannot PXE boot on 2 of them. Get:

File: BootBCD

Status: 0xc000000f

Info: The Boot Configuration Data for your PS is missing or contains errors.

Found this article: https://www.symantec.com/connect/forums/winpe-10-preboot-dont-work which seems to apply that has a link to another article but that link is dead for. It also refers to running a script but have no idea what that is.

The one DS that does work is Windows Server 2012 and the 2 that don’t are Windows server 2008 r2. About 3 months ago I updated to ADK 1803 on the NS. I am very afraid of doing any of this without clear instructions as the one that is working is high volume and I do not want to mess that one up.

Thanks in advance for any support you can provide.

0

Related:

  • No Related Posts

Need NIC driver for HP Elitedesk 800 G4

I need a solution

I’m trying to create a build for an HP Elitedesk 800 G4.  I can’t find the correct WinPE 10 driver for the NIC.  It is an Intel I219-LM with driver e1d65x64.sys (12.17.10.7). 

I’ve tried the HP WinPE driver packs, the HP web site drivers for this device, the Intel drivers from their website but none of them work.  Has anyone had any success getting this device to build with this NIC?  

Any help would be appreciated?

0

Related:

WinPE 1803/1809 on DS 8.0?

I need a solution

We’ve received some new PCs with Coffee Lake processors and they will not boot to WINPE. Our current ADK version is 8.59. It appears we need to upgrade our ADK to at least Win10 1709. I’m thinking to go ahead with 1803 or 1809 to reduce the chances of this happening again soon. I’ve found this article to upgrade: https://support.symantec.com/en_US/article.INFO3561.html. I just want to verify this is supported on DS 8.0. We are in a major laptop replacement project right now and cannot afford a lot of down time.

Thaks in advance for any advise or recommendations.

-Greg

0

Related:

  • No Related Posts

iPXE – WinPE – Driveletters

I need a solution

Hi

We have enabled iPXE and it is working great and the speed is great compared to standard PXE/TFTP.

But, when we boot into Winpe with iPXE the driveletters to local disk on the destination computer is not the same at with standard PXE.

In standard PXE we see local drive as C: but with iPXE it is D:  – Our challenge and problem is that we have many scripts, tasks and jobs that expect the local drive to be C: 

Is there any way to change this or is this by design? Does anyone have a clue why this is happening?

0

Related:

  • No Related Posts

Windows crashed – Trying to recover data

I need a solution

Hi Everyone, 

We are using SEE 11 and one of our users has some Windows curruption on her hard drive. We are trying to recover her data, but we have ran intoa road block. We are booting to a WinPE boot disk, and we are trying to running the following command:

eedAdminCli — status –au username –ap password 

However, I’m wondering what the username would be for this command. A local admin? The user we configured SEE with? 

Thanks, 

Mike

0

1547749232

Related: