USB Boot not working for E5491 with symentec Ghost 11.5

I did create an USB Boot for E5491 but I am getting following error
when i tried to boot with it Error:
Unable to locate the PCI LAN Adapter/ The following are possible causes:
1. The system may not support the PCI bus.
2. The PCI adapter may not be properly installed in a slot.
3. Some of the PCI adapter resources in configuration space may be invalid. Check for possible errors listed above and run adapter diagnostics.
Failure: Driver did not load, NDIS environment invalid.

I did download the driver for MS-DOS from intel ® Ethernet Connection I219-LM , PRODOS.exe 23.5.2 I made following changes on to the USB boot but still i am getting the same error any help very much appreciated as we have an bulk order for E5491
Autoexec.bat
@echo off
prompt $p$g
\net\netbind.com
MOUSE.COM
cd \ghost
echo Loading..
GHOST.EXE -fni

Also remember to add the driver name to the protocol.inf, so it looks like this:

[protman]
drivername=PROTMAN$

[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66

[nic]
drivername = e1000$

Hi there,

DAgent was working, discovering Ghost Server via multicasting, tested imaging, all working for some days.

All of a sudden, DAgent is not able to discover the Ghost Server anymore! No change in setup.

When I configure DAgent on the client to use the current IP-Adress of the server, it works...
But I need multicast discovery to work.

- Ghost Server v. 3.2. RU7
- Windows 10 1803 on Server and Client

Thanks in advance!

DAgent Logfile:

[03/04/2019 14:19:47.537 8120 1] AgentLog.cpp:615 ***** InitializeFileLog *****
[03/04/2019 14:19:47.537 8120 2] main.cpp:670 - DAgent Version: 6.9.3655 (64 bit)
[03/04/2019 14:19:47.537 8120 2] main.cpp:686 - argv[0] =  C:\Program Files\Altiris\Dagent\dagent.exe
[03/04/2019 14:19:47.537 3248 1] DsaServiceEntry.cpp:113 - Entering DsaServiceMain()
[03/04/2019 14:19:47.552 3248 1] DsaServiceEntry.cpp:118 - Registering the ServiceControl proc
[03/04/2019 14:19:47.552 3248 1] DsaServiceEntry.cpp:126 - Tell ServiceControl SERVICE_START_PENDING
[03/04/2019 14:19:47.552 3248 1] DsaServiceEntry.cpp:131 - Start the Bootstrap thread
[03/04/2019 14:19:47.552 3248 1] DsaServiceEntry.cpp:136 - Tell ServiceControl SERVICE_RUNNING
[03/04/2019 14:19:47.552 1528 1] bootstrap.cpp:306 CBootstrap::Run - throw/catch from DebugWaitEnabled value! err=6, syserr=87
[03/04/2019 14:19:47.552 3248 1] DsaServiceEntry.cpp:140 - Exit DsaServiceMain()
[03/04/2019 14:19:47.552 1528 0] bootstrap.cpp:1131 - Error reading input file.
[03/04/2019 14:19:47.568 1528 1] bootstrap.cpp:1212 - Deleting BDCInfo.cfg file
[03/04/2019 14:19:47.568 1528 1] bootstrap.cpp : 363 Calling CConfigBootwork::EnableBootworksPartition(False).
[03/04/2019 14:19:47.599 1528 1] bootstrap.cpp:368 Checking for sysprep
[03/04/2019 14:19:47.599 1528 2] DsAgent.cpp:900 CDSAgent::NewMessage()
[03/04/2019 14:19:47.599 1528 2] DsAgent.cpp:805 InvokeHandler called - Internal=WaitForSysPrep
[03/04/2019 14:19:47.599 1528 2] TbxDispatch.cpp:40  - Attempting to load default.dll
[03/04/2019 14:19:47.599 1528 1] TbxDispatch.cpp:72 HandleMessage() - calling default.dll Version(6.9.3655)
[03/04/2019 14:19:47.599 1528 1] Toolbox-Main.cpp:80 Toolbox::DoMagic - Finding handler for Internal=WaitForSysPrep
[03/04/2019 14:19:47.599 1528 1] WaitForSysPrep.cpp:26 - Internal WaitForSysPrep
[03/04/2019 14:19:47.599 1528 1] WaitForSysPrep.cpp:37 - Checking on Microsoft key for Sysprep
[03/04/2019 14:19:47.599 1528 1] WaitForSysPrep.cpp:44 - Image state is IMAGE_STATE_COMPLETE
[03/04/2019 14:19:47.599 1528 1] WaitForSysPrep.cpp:88 - CWaitForSysPrep::DeleteRandomUser()
[03/04/2019 14:19:47.599 1528 1] WaitForSysPrep.cpp:111 - No Random user found!
[03/04/2019 14:19:47.615 1528 1] TbxDispatch.cpp:107 HandleMessage() - default.dll returned TBX_FAILED
[03/04/2019 14:19:47.615 1528 1] bootstrap.cpp:1407 CBootstrap::CheckForHpNics - no registry value found, returning.
[03/04/2019 14:19:47.615 1528 1] bootstrap.cpp:378 Waiting for network
[03/04/2019 14:19:47.615 1528 2] DsAgent.cpp:900 CDSAgent::NewMessage()
[03/04/2019 14:19:47.615 1528 2] DsAgent.cpp:805 InvokeHandler called - Internal=WaitForIP
[03/04/2019 14:19:47.615 1528 2] TbxDispatch.cpp:40  - Attempting to load default.dll
[03/04/2019 14:19:47.615 1528 1] TbxDispatch.cpp:72 HandleMessage() - calling default.dll Version(6.9.3655)
[03/04/2019 14:19:47.615 1528 1] Toolbox-Main.cpp:80 Toolbox::DoMagic - Finding handler for Internal=WaitForIP
[03/04/2019 14:19:47.615 1528 1] CWaitForIP::HandleMessage
[03/04/2019 14:19:47.615 1528 1] TbxDispatch.cpp:107 HandleMessage() - default.dll returned TBX_SUCCESS
[03/04/2019 14:19:47.615 1528 1] bootstrap.cpp:385 Waiting for network complete
[03/04/2019 14:19:47.630 1528 1] bootstrap.cpp:390 Checking Initial Config
[03/04/2019 14:19:47.630 1528 2] DsAgent.cpp:900 CDSAgent::NewMessage()
[03/04/2019 14:19:47.630 1528 2] DsAgent.cpp:805 InvokeHandler called - Internal=OSInfo
[03/04/2019 14:19:47.630 1528 2] TbxDispatch.cpp:40  - Attempting to load default.dll
[03/04/2019 14:19:47.630 1528 1] TbxDispatch.cpp:72 HandleMessage() - calling default.dll Version(6.9.3655)
[03/04/2019 14:19:47.630 1528 1] Toolbox-Main.cpp:80 Toolbox::DoMagic - Finding handler for Internal=OSInfo
[03/04/2019 14:19:47.630 1528 1] OsInfo.cpp:94 - Internal OSInfo Entered
[03/04/2019 14:19:47.630 1528 2] common\sys\Wmi.cpp:1797 Checking for existing WMI on this thread
[03/04/2019 14:19:47.630 1528 2] common\sys\Wmi.cpp:48 Wmi() created for Thread 1528
[03/04/2019 14:19:47.630 1528 2] sys/BasicCom.cpp:26 Init()
[03/04/2019 14:19:47.630 1528 2] common\sys\Wmi.cpp:75 Wmi::_init()
[03/04/2019 14:19:47.630 1528 2] common\sys\Wmi.cpp:120 Wmi::_init() was successful
[03/04/2019 14:19:47.646 1528 1] TbxDispatch.cpp:107 HandleMessage() - default.dll returned TBX_SUCCESS
[03/04/2019 14:19:47.646 1528 0] bootstrap.cpp:467 GetCfgFilename(): strName = C:
[03/04/2019 14:19:47.646 1528 1] bootstrap.cpp:537 The config file is not there, we’re done.
[03/04/2019 14:19:47.646 1528 1] bootstrap.cpp:399 Calling Agent Startup
[03/04/2019 14:19:47.646 1528 2] bootstrap.cpp:806 - Resetting Logging Parameters
[03/04/2019 14:19:47.646 1528 2] bootstrap.cpp:853 - New Log Params
    errors=1, info=1, debug=1
    filename=C:\Program Files\DAgentLogs\DAgent.log, size=512000
[03/04/2019 14:19:47.646 1528 1] bootstrap.cpp:628 ---Agent startup code being called. Welcome!---
[03/04/2019 14:19:47.646 1528 2] DsAgent.cpp:900 CDSAgent::NewMessage()
[03/04/2019 14:19:47.661 1528 1] bootstrap.cpp:918 - Using Multicast to connect to server.
[03/04/2019 14:19:47.661 1528 2] DsAgent.cpp:805 InvokeHandler called - Internal=MulticastIpDiscovery
[03/04/2019 14:19:47.661 1528 2] TbxDispatch.cpp:40  - Attempting to load default.dll
[03/04/2019 14:19:47.661 1528 1] TbxDispatch.cpp:72 HandleMessage() - calling default.dll Version(6.9.3655)
[03/04/2019 14:19:47.661 1528 1] Toolbox-Main.cpp:80 Toolbox::DoMagic - Finding handler for Internal=MulticastIpDiscovery
[03/04/2019 14:19:47.661 1528 1] MulticastIpDiscovery.cpp:44 - CMulticastIpDiscovery::HandleMessage
[03/04/2019 14:19:47.661 1528 1] MulticastIpDiscovery.cpp:108 - CMulticastIpDiscovery::CreateMulticastSocket : Creating Multicast socket
[03/04/2019 14:19:47.661 1528 1] MulticastIpDiscovery.cpp:116 - CMulticastIpDiscovery::BroadcastRequest : Broadcasting Request=GetServer
[03/04/2019 14:19:47.661 1528 1] MulticastIpDiscovery.cpp:141 - CMulticastIpDiscovery::GetBroadcastReply : Getting Broadcast Reply
[03/04/2019 14:20:2.671 1528 2] DsAgent.cpp:900 CDSAgent::NewMessage()
[03/04/2019 14:20:2.671 1528 1] MulticastIpDiscovery.cpp:102 - CMulticastIpDiscovery::HandleMessage returning.
[03/04/2019 14:20:2.671 1528 1] TbxDispatch.cpp:107 HandleMessage() - default.dll returned TBX_SUCCESS
[03/04/2019 14:20:2.671 1528 1] bootstrap.cpp:947 - Server  = , Port =
[03/04/2019 14:20:2.671 1528 0] bootstrap.cpp:677 unhandled exception thrown from startup code
    bootstrap.cpp:969 - Unknown Error discovering IP address of DS.
    Value=1, SystemError=0x000000B7
[03/04/2019 14:20:2.671 1528 1] bootstrap.cpp:407 Destroying Agent
[03/04/2019 14:20:2.687 1528 2] DsAgent.cpp:289 CDSAgent::Destroy()
[03/04/2019 14:20:2.687 1528 2] DsAgent.cpp:295 CDSAgent::Destroy() - Closing socket connection
[03/04/2019 14:20:2.687 1528 2] DsAgent.cpp:306 About to serialize data
[03/04/2019 14:20:2.687 1528 0] DsAgent.cpp:490 About to serialize objects
[03/04/2019 14:20:2.687 1528 2] DsAgent.cpp:309 Deleting queues

USB Boot not working for E5491 with symentec Ghost 11.5

I did create an USB Boot for E5491 but I am getting following error
when i tried to boot with it Error:
Unable to locate the PCI LAN Adapter/ The following are possible causes:
1. The system may not support the PCI bus.
2. The PCI adapter may not be properly installed in a slot.
3. Some of the PCI adapter resources in configuration space may be invalid. Check for possible errors listed above and run adapter diagnostics.
Failure: Driver did not load, NDIS environment invalid.

I did download the driver for MS-DOS from intel ® Ethernet Connection I219-LM , PRODOS.exe 23.5.2 I made following changes on to the USB boot but still i am getting the same error any help very much appreciated as we have an bulk order for E5491
Autoexec.bat
@echo off
prompt $p$g
\net\netbind.com
MOUSE.COM
cd \ghost
echo Loading..
GHOST.EXE -fni

Also remember to add the driver name to the protocol.inf, so it looks like this:

[protman]
drivername=PROTMAN$

[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66

[nic]
drivername = e1000$

I have created boot environments for PXE and USB stick, and have been connecting EliteDesk 800 G3 without any issues to GSS v3.3 (Build 2508). Pulling my hair out trying to connect Elitedesk 800 G4. Both G3 and G4 have i219LM onboard ethernet, so I'm not sure what's different about G4 ether. I've tried quite a few versions of the i219 driver to add to the device driver list. But every time I try adding, I get a message saying "Boot Disk Creator could not add driver". I need a solution quickly, or else I won't have any hair left :-(

Fyi, GSS is installed on Server2016 Datacenter (the O/S drop down list doesn't have this option)

Thanks in advance.

I am trying to image a new system or empty HD by booting to it using a boot disk.  However when it boots I receive a "Please remove the Boot Media and Click OK" message.  Behind it I can see Symantec DAgent Service Status: Client Record Updated and the server details.

I have seen in some videos the PC will pop up in GSS and the user can deploy that way or use GhostCast Server.  What could I be missing?

This is a weird one. If I install windows 10 on a laptop and immediately attempt to image it using ghost64.exe version 12.0.0.10514 I can create an image without issue.

However, if I do the same thing but I also let the computer get all of its windows updates, ghost will fail. It appears that Microsoft is pushing out an update that is causing Ghost to fail. The error is Application Error 31002 - Unable to access Linux partition 3.

This is very recent like within the last two weeks or so. Anyone else seeing this? Any fix from symantec yet?

I need to install the agent manually as we have yet to join to the network. I wanted to know if this can be down as I only see the remote agent via the console and was not sure "C:\Program Files (x86)\Altiris\eXpress\Deployment Server\Agents" is where it install it from and which one to choose as there are three. AClient, ADLAgent and CEAgent. Thanks for any help you can give.

Kuroo

So I managed to implement iPXE on our Ghost server that is running 3.3 RU2.

It can boot into the PE environment in under 30 seconds!  However, that is only with Secure Boot disabled.  When Secure Boot is enabled you get a BSOD type screen.

I see the issue is already logged under this Tech article, https://support.symantec.com/en_US/article.TECH252464.html

It says the cause is unknown, but it is because of secure boot.  It makes sense the Secure Boot doesn't allow it, but is there any known fix or can there even be a fix without disabling secure boot?

iPXE supports wireless (SSID/PSK) as long as the drivers are included.

I know that Symantec does not officially support wireless for iPXE, but has anyone been able to sucessfully modify the PE for thier iPXE boot to include wireless settings for thier network(s)?

Hi all,

I have all tutorials and all videos read and watch but I don't have a solution for my problem. I have no idea what to do in my case.

I have GSS Suite on a Server 2012R2 in a VM ESXI and on the same VM machina a windows 7 prof. Client. If I want to boot PXE

I become the following screen and after this my Win7 boot normaly but don't boot PXE. Is there anyone who have the same problem?

Thanks for your help

OptiPlex 7460 AIO

    Processor - Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz

    RAM - 16GB

    OS - Windows 10 Pro

Latitude 5400   

    Processor - Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz

    RAM - 16GB

    OS - Windows 10 Pro

Symantec Ghost 12.0.0.8023

Trying to image new Dell OptiPlex 7460 All-in-ones as well as some Dell Latitude 5400s. All updates for windows as well as drivers and firmware are up to date, there are no driver conflicts. When trying to map the images to a network drive (I have no information about the specs or build of the server, sorry) I am met with "System error 1231" saying the network location cannot be reached. I am able to ping the server via windows command prompt but not through ghosts command prompt. All pings other than the loop-back address are returning a transmit failed, general failure. 

I am able to ping the server though other PCs i have available in ghost, just not these specific computers.

Any help is appreciated! Thanks.

Hi!

I´m in the Process of migrating from W7 to W10. To do so, among a lot of other things, I rolled out GSS-Client to all my Machines (~230)  and change Bootorder to place Network-Boot first on every Machine. For Clients known to the GSS-Console (all my Clients) "Next Device" is default in PXE, so my Clients boot their local OS after 5 Seconds waiting when no job is assigned (what is the default case)

So during PXE-boot, every Client aks my DHCP for an IP-Address, which the Client normally needs only for the above mentioned 5 Seconds. After that the local OS boots where I have configured staticIP´s on every Client.

In this configuration I need a reltivly big IP-Range (in the past I had a Range of only about 20 IPs for special things) in DHCP.
What should I use as Lease-Time in this configuration?
How do you "solve" this Problem in your Environments?

Thanks in Advance!

TJ

The DAgent Service doesn't not retain the manually entered GSS console address when you got into DAgent configuration and alway swithces to multicast.  What setting or file do I need to clear on the system so the address will stick?

James Trice

Hi Everyone,

I have nearly 200 machines inside of my Ghost console. For some reason over the last few weeks maybe...10 of them, actually show as active. The rest are greyed out; however, they do come alive if and only if a user is signed into the computer. But, even that doesn't seem to be universal as there are a few that show inactive no matter what I do.

I've read that sometimes there can be issues with Dagent if the "encrypt sessions" options are enabled, but I've checked and that option is turned off both in Dagent on the clients and inside the "Configuation" window of the Ghost console.

I checked the settings of the Dagent service and it's set for automatic and to log on as a Local Systems Account.

This did start roughly after I had to reinstall Windows, but it was a fresh installation of everything including GSS and Windows 10.

If it helps I'm running GSS 3.2 on Windows 10 v1809 (I'm aware that Ghost prefers a server OS, but it's always been successful on W10).

My company has the licenses for GSS 3.3, but I've held off updating since we're close to renewal and I don't want to deal with Symantec's convoluted licensing process any more than I have to. However, is it possible that this is some kind of compatibility issue I'm looking at? At the moment I'm at a complete loss to explain this, much less fix it.

I appreciate any helpful suggestions you can offer!

Thanks,

--Frank

Hello,

I am a store manager of an independent Hallmark retail location.  We have 2 of their previous Fujitsu registers running on Windows XP.  These registers are no longer covered by Hallmark's tech support line or I would reach out to the company.  Unfortunately during a power outage they restarted and from what I can see, the backup server register had a Blue Screen of Death with the "Unmountable Boot Drive" error.  I am trying to run the POSX recovery cd that was provided with the systems in 2010.  When I get to the Ghost 8.2 screen, I get an error message "Output error file to the following locations A:\GHOSTERR.TXT" When I click ok to close that window I get the following: "Application error 29004.  Read sector failure, result=1, drive=0, sectors 19647236 to 19647300" with the link to http://service.symantec.com.  Clicking ok to exit that window prompts me to remove the recovery cd and restart the computer (which without the cd in the drive, results in the endless boot loop since the hard drive seems to be compromised).  Any suggestions would be much appreciated since I have no tech support for this matter. 

Thanks,

Sara

Has anyone had any luck booting these Dell 5400s from a USB drive?  Since legacy mode is dead, I've reformatted my Ghost Boot Disk to GPT with UEFI and the PC does NOT recognize the USB disk.  I've tried two different disks and in the boot menu I don't see a USB device.  I've disabled Secure Boot and made sure USB support was enabled.  I tested my USB disk and it boots with my Surface (which is what I originally used this specific boot disk for).  I've tried all three USB ports on the PC.  HD is set to RAID on.

Thanks!

Hi guys,

Ive being doing some research but believe I cant figure this thing out. I need to deploy almost 300 machines, these machines are new so not connected to the ghost server.

I configured a initial deployment with a deploy image but everytime a start a new machine I have to go the wizard the select disk and then select the image I want to deploy, I need to deploy these images automatically without any user intervention.

Am I missing something??

I was stuck in "calling custom actions" then I added these lines (cd ghost ghost64.exe) to the startup.bat but still I have to choose the image and follow a wizard, I know is not that long but I consider I have to do it 300 times.

Hello all, 

We currently started purchasing Dell XPS 9570s and 9370s. We are running GSS 3 in a test VM before we put it into production and I am running into an issue that I cant figure out. I have pushed automation folders to the client PCs that I am trying to capture a backup image from. I can get them to boot into automation using a wait job and they are getting an IP from the DHCP server and they are mapping to the M: which is where we want the images to save. The issue is if I run an image job I cannot get ghost to launch, the PC will reboot back to windows. I even tried manually running a command to launch it by doing the following: M:\ cd ghost, and then ghost\ghost64.exe. When I do this 1 of 2 things happens, it will either reboot into windows 10 and take me to the login screen or it will sit there and do nothing. I been working with a gentlemen from Symantec and even he has run out of ideas. Just to bring everyone up to speed, Ive installed a clean copy of windows 10 pro on this machine and deleted all the factory Dell partitions. I would really like to get this into production soon, so any help is highly appreciated.

How does licensing work if the principle use of Ghost is using a Ghost created WinPE bootable USB to clone a hard drive for backup?

Is it the same as any other license?  Meaning, in this case, one license per backup created?

Hi guys,

I already configured ghost solution suite, I can take images from pxe, deploy images to one machine. So I decided to deploy to several machines but for some reason for example if I run 5 machines Im getting this error "Restarting DHCP clilent service:  retry 1..." in 4 computers and only one runs after this one completes if I connect a new one same error "Restarting DHCP clilent service:  retry 1..." so I have to reboot the ghost server but still only one runs

The ghost server is a windows 2012 and is a virtual machine, the DCHP server is other virtual machine and the computers I want to deploy to are physical.

What am I missing?