Ghost Solution Suite

 View Only
  • 1.  IP address not configured after deploy

    Posted Jul 07, 2017 04:01 AM

    GSS 3.1 MP6, Windows 10 1703 x64 image destination 

    Hello,

    I'm facing a problem after deploying an image : IP adress is not configured in the configuration process after deploy. Computer name is configured, but not the IP. So multiple PC have the same IP, so conflict and domain joining fail. In fact only one PC of the job is doing the full process well, the one who success to join the network.

    I suspect the option : Boot to production to complete configuration task to be the cause of my problem, so I uncheck it. But after the task begin (or after complete), if I edit the task the option is checked again... Is that a bug???

     

    So it drive me to this question : my source image have a static IP. If I set it to DHCP, will the configuration task be able too set static IP from computer configuration?

    Is there a best practice of configuration for the source image?

    Thanks,

    best regards



  • 2.  RE: IP address not configured after deploy

    Posted Jul 07, 2017 05:51 AM

    Is there any specific error?



  • 3.  RE: IP address not configured after deploy

    Posted Jul 07, 2017 05:51 AM

    Is there any specific error?



  • 4.  RE: IP address not configured after deploy

    Posted Jul 07, 2017 07:37 AM

    I'm going to try DHCP configured source image to see if the problem occur.

    If not, I need to activate Altiris client log file (I miss this)

    The probleme is that I have 2 hours each time between tests sessions....

    May be that Altiris client need full network with GSS server for the configuration task go well. The strange thing is that the computer name is well configured, but IP is not, so domain not.

    On the target computer, after deploy, the aclient.cfg  file have the good IP in, but Altiris client don't apply it...

     

    Question : what is the process of deploy+configuration, who configure the computer after ghost deploy? The WinPe boot environement? Or the Altiris client, after first boot?

     



  • 5.  RE: IP address not configured after deploy
    Best Answer

    Posted Jul 07, 2017 10:11 AM

    My comment disappear...

    So, trying with DHCP configured source image in progress.

    What in the process of configuring task after deploy? What is configuring Windows? The WinPe environement or the Altiris client on first boot?

    On the failed computers, name of the coomputer is set, but not the IP. May be Altiris client need full network connectivity on first boot to process configuration...

    The strange thing is that the file aclient.cfg have the good IP in, but Altiris client did not applied it...

     

    EDIT : All went well with DHCP configured source image, configuration is done, static IP is set.