Ghost Solution Suite

Hi,

When i wan't to create a image, i am able to start it automatically from PXE. It makes a succesfull connection with the client and  i can see the status "Uploading image" in the console. But after a few seconds it fails. 

What am i doing wrong? 

HF3

==========

[12/08/2015 14:02:14.648 3440 0] bootstrap.cpp:1128 - Error reading input file.
[12/08/2015 14:02:14.835 3440 0] bootstrap.cpp:464 GetCfgFilename(): strName = C: 
[12/08/2015 14:02:25.666 4144 0] ReplyUpdateComputer.cpp:190 - Error removing registry value.
[12/08/2015 14:02:25.668 4144 0] ReplyUpdateComputer.cpp:296 - Error reading logevent status from registry.
[12/08/2015 14:10:12.215 4340 0] apps\dsagent\toolbox\default\handlers\internal\SetOneTimePXEBoot.cpp:201 CSetOneTimePxeBoot::HandleMessage(): caught exception
    apps\dsagent\toolbox\default\handlers\internal\SetOneTimePXEBoot.cpp:193 - One time Pxe boot is not available
    Value=0, SystemError=0x00000000
[12/08/2015 14:10:13.969 4340 0] internal/Configure.cpp:824 - Configuration task was successful. Deleted 'config-failed' value from registry.
[12/08/2015 14:10:13.971 4340 0] PrepForImage.cpp:74 - Error removing 'config-failed' registry value.
[12/08/2015 14:10:14.736 4340 0] DsAgent.cpp:488 About to serialize objects
[12/08/2015 14:10:14.737 3560 0] InputThread.cpp:323 - Exiting Input Thread
[12/08/2015 14:10:14.744 3544 0] UiInitialConnectThread.cpp:97 - CUIError error, CUiInitialConnect::ReadConnectPacket() - Shutting down. - 0
[12/08/2015 14:10:14.745 3544 0] UiInitialConnectThread.cpp:138 - CUiInitialConnect::Run RETURNING...
[12/08/2015 14:10:14.749 3552 0] apps\dsagent\agent\LogEventThread.cpp:57 - CLogEventThread::Run CLogEventError
    Thrown from apps\dsagent\agent\LogEventThread.cpp:113 -message = CLogEventThread::ReadLogEvent() - Shutting down.
    SystemError Value = 0x00000000
    
[12/08/2015 14:10:14.750 3440 0] DsAgent.cpp:488 About to serialize objects
[12/08/2015 14:10:24.109 2220 0] main.cpp:786 - Leaving Main()
[12/08/2015 14:10:24.109 2220 0] main.cpp:787 - =============================================================

Hello,

I reviewed the log entry there and I found an article that may help:

Unable to connect with DAgent for status updates

The specific item to check is #2 in the article, and for Ghost the path should be Control Panel > Ghost > Options > Connections > Allow reject agents based on IP, instead of the path it states there. Check and see if that helps.

Thank you,

Randall Newnham

The change brings me further then it used to be. The Dagent does now update the status (Client Record Updated), but right after a couple min its starts getting black and  I get a message Connection Closed - Session terminated.

Here is the logs:

12/16/2015 14:36:9.922 2968 0] bootstrap.cpp:1128 - Error reading input file.
[12/16/2015 14:36:10.530 2968 0] bootstrap.cpp:464 GetCfgFilename(): strName = C: 
[12/16/2015 14:36:10.577 2968 0] internal/Configure.cpp:266 Networking was disabled see if we need to go to wrk grp
[12/16/2015 14:36:10.577 2968 0] internal/Configure.cpp:276 Looks we are coming after create image, No need to go to wrk grp
[12/16/2015 14:36:19.499 2968 0] internal/Configure.cpp:824 - Configuration task was successful. Deleted 'config-failed' value from registry.
[12/16/2015 14:36:19.521 2968 0] DsAgent.cpp:488 About to serialize objects
[12/16/2015 14:36:26.293 4260 0] ReplyUpdateComputer.cpp:190 - Error removing registry value.
[12/16/2015 14:36:26.295 4260 0] ReplyUpdateComputer.cpp:296 - Error reading logevent status from registry.

Any idea?

Strange is that sometimes it cannot create the F: drivemapping says device mapping is in use and it switches over to x:. The share folder looks ok and security settings is for everbody full permission (for now).

If it is using F: as the drive mapping, that means that you have none of the hotfixes applied to Ghost. The default drive mapping changed to M; in the first hotfix. unfortunately, that letter is low enough it might already be in use by the machine itself. I recommend updating to the latest hotfix (HF4 is available now, and can be downloaded from Fileconnect). Just to clarify, X: is not a drive mapping; X: is WinPE's virtual drive running in RAM.

I forgot to mention that after the hotfix is applied, you wil need to recreate boot media and regenerate PXE boot images.

Oke i will install the HF4. But what is the cause of my problem and should that be fixed with the new update? As i told i think problem is not the drivemapping, my client is updating with the Dagent.

Hi,

Error -99 occurs when the DAgent is unable to locate the resources on the eXpress share. This is either because,

1) The eXpress share cannot be mapped.
2) A custom startup script in WinPE has altered the current path

An F:\ drive mapping is a sure-fire way though to get and "Error -99" scenario. In automation, fixed disks, CD/DVD drives and USB media will all take first grabs of the available drive letters. This will mean that the F:\ will not be mapped and render the express share unavailable.

To resolve, ammend the automation configuration in Bootdidisk creator and set the mapping there to M:\ 

Kind Regards,
Ian./