Deployment Solution

 View Only
  • 1.  Cant create Win10 image with Ghost solution suite 3.0

    Posted May 30, 2017 03:38 AM

    Hi.

    I want to create an image of a windows 10 professional x64 with Ghost solution suite 3.0.

    But when i run the task to create the image,It fail and reboot the client normally and i obtain this log file:

    [05/30/2017 07:03:21.962 3936 0] InputThread.cpp:323 - Exiting Input Thread
    [05/30/2017 07:03:21.976 4928 0] UiInitialConnectThread.cpp:97 - CUIError error, CUiInitialConnect::ReadConnectPacket() - Shutting down. - 0
    [05/30/2017 07:03:21.976 4928 0] UiInitialConnectThread.cpp:138 - CUiInitialConnect::Run RETURNING...
    [05/30/2017 07:03:22.007 1340 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
        
    [05/30/2017 07:03:22.007 2244 0] DsAgent.cpp:488 About to serialize objects
    [05/30/2017 07:03:22.023 1912 0] main.cpp:786 - Leaving Main()
    [05/30/2017 07:03:22.023 1912 0] main.cpp:787 - =============================================================

     

     

    [05/30/2017 07:03:24.608 3956 0] bootstrap.cpp:1129 - Error reading input file.
    [05/30/2017 07:03:24.838 3956 0] bootstrap.cpp:465 GetCfgFilename(): strName = C:
    [05/30/2017 07:03:31.133 5552 0] ReplyUpdateComputer.cpp:190 - Error removing registry value.
    [05/30/2017 07:03:31.148 5552 0] ReplyUpdateComputer.cpp:296 - Error reading logevent status from registry.
    [05/30/2017 07:04:40.290 5540 0] InputThread.cpp:323 - Exiting Input Thread
    [05/30/2017 07:04:40.306 3644 0] UiInitialConnectThread.cpp:97 - CUIError error, CUiInitialConnect::ReadConnectPacket() - Shutting down. - 0
    [05/30/2017 07:04:40.306 3644 0] UiInitialConnectThread.cpp:138 - CUiInitialConnect::Run RETURNING...
    [05/30/2017 07:04:40.353 4720 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
        
    [05/30/2017 07:04:40.353 3956 0] DsAgent.cpp:488 About to serialize objects
    [05/30/2017 07:04:41.375 3956 0] bootstrap.cpp:1129 - Error reading input file.
    [05/30/2017 07:04:41.550 3956 0] bootstrap.cpp:465 GetCfgFilename(): strName = C:
    [05/30/2017 07:04:45.525 2268 0] ReplyUpdateComputer.cpp:190 - Error removing registry value.
    [05/30/2017 07:04:45.537 2268 0] ReplyUpdateComputer.cpp:296 - Error reading logevent status from registry.
    [05/30/2017 07:05:27.982 1456 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
    [05/30/2017 07:05:32.971 1456 0]     33 is invalid event type
    [05/30/2017 07:05:35.507 1456 0] internal/Configure.cpp:824 - Configuration task was successful. Deleted 'config-failed' value from registry.
    [05/30/2017 07:05:35.507 1456 0] PrepForImage.cpp:74 - Error removing 'config-failed' registry value.
    [05/30/2017 07:05:35.523 1456 0] DsAgent.cpp:488 About to serialize objects
    [05/30/2017 07:05:35.523 2732 0] InputThread.cpp:323 - Exiting Input Thread
    [05/30/2017 07:05:35.554 4080 0] UiInitialConnectThread.cpp:97 - CUIError error, CUiInitialConnect::ReadConnectPacket() - Shutting down. - 0
    [05/30/2017 07:05:35.554 4080 0] UiInitialConnectThread.cpp:138 - CUiInitialConnect::Run RETURNING...
    [05/30/2017 07:05:35.601 2152 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
        
    [05/30/2017 07:05:35.601 3956 0] DsAgent.cpp:488 About to serialize objects
    [05/30/2017 07:05:41.905 5272 0] main.cpp:786 - Leaving Main()
    [05/30/2017 07:05:41.905 5272 0] main.cpp:787 - =============================================================

     

     

    [05/30/2017 07:06:12.831 2152 0] bootstrap.cpp:1129 - Error reading input file.
    [05/30/2017 07:06:14.708 2152 0] bootstrap.cpp:465 GetCfgFilename(): strName = C:
    [05/30/2017 07:06:14.724 2152 0] internal/Configure.cpp:266 Networking was disabled see if we need to go to wrk grp
    [05/30/2017 07:06:14.724 2152 0] internal/Configure.cpp:276 Looks we are coming after create image, No need to go to wrk grp
    [05/30/2017 07:06:14.739 2152 0]     33 is invalid event type
    [05/30/2017 07:06:24.008 2152 0] internal/Configure.cpp:824 - Configuration task was successful. Deleted 'config-failed' value from registry.
    [05/30/2017 07:06:24.023 2152 0] DsAgent.cpp:488 About to serialize objects
    [05/30/2017 07:06:30.368 4728 0] ReplyUpdateComputer.cpp:190 - Error removing registry value.
    [05/30/2017 07:06:30.383 4728 0] ReplyUpdateComputer.cpp:296 - Error reading logevent status from registry.

     

    I'm a trainee in an internship so I don't understand all the file.

    did someone know how to resolve this issue ?

     



  • 2.  RE: Cant create Win10 image with Ghost solution suite 3.0

    Posted May 31, 2017 11:10 AM

    what process are you following to create an image?

    Is your pxe environment setup correctly (see below article) ?
    https://www.symantec.com/connect/articles/quick-start-guide-pxe-configuration

    Can you boot the client into pxe?

    What is your WinPE version?



  • 3.  RE: Cant create Win10 image with Ghost solution suite 3.0

    Posted May 31, 2017 06:43 PM

    If you can provide details I may be able to help walk you thru. I have successfully created a Windows 10 x64 image and deploy it with Ghost.



  • 4.  RE: Cant create Win10 image with Ghost solution suite 3.0

    Posted Jun 01, 2017 03:18 AM

    I Process like in this video :

    https://www.youtube.com/watch?v=vB_5IjiAdII&feature=youtu.be

     I can boot the client into PXE but my Internship tutor tell me that is not the solution

    the server is a windows 2012 server x64 and the client is a windows10 x64

    I'm sorry If I do not answer your question correctly but like i said i'm in an internship so my skills are limited



  • 5.  RE: Cant create Win10 image with Ghost solution suite 3.0

    Posted Jun 01, 2017 11:25 AM

    Prenom,

    You would follow the below video for deployment. Partition deployment is definitely not what you would need.

    https://www.youtube.com/watch?v=XepDYp9NtiU&feature=youtu.be



  • 6.  RE: Cant create Win10 image with Ghost solution suite 3.0

    Posted Jun 02, 2017 02:54 AM

    Thx for the link but my issue is not the deployement task, it's the create image task i can't create an image of my win10 computer



  • 7.  RE: Cant create Win10 image with Ghost solution suite 3.0

    Posted Jun 05, 2017 12:38 PM

    Prenom,

     

    Here is the link for creation.

    https://www.youtube.com/watch?v=b7kI7A_aOjg&t=22s



  • 8.  RE: Cant create Win10 image with Ghost solution suite 3.0

    Posted Jun 06, 2017 04:50 AM

    BrycenM,

    I have tried to use thi method but it's doesn't work.

    my Win10 computer dont reboot in automation mode so ghost can't capture the image, that's why i'm trying to tell you since 1 week.

    I can't find a solutionand my training period finish in a cupple of time so i hope i'm gonna find how to make it.



  • 9.  RE: Cant create Win10 image with Ghost solution suite 3.0
    Best Answer

    Posted Jun 06, 2017 10:26 AM

    Prenom,

    If your client machine will not boot into automation that is likely a bios issue. Make boot to lan or boot to network is set as the first boot option in your bios.

    The steps in that video are exactly the steps you would perform to capture and deploy a Windows 7 image.

     

    Additionally, the forums are a great place for information and collaboration. But they do not replace a phone call with support. If your issue is time sensitive, I would recommend calling into Symantec Support and creating a ticket.