Ghost Solution Suite

 View Only
  • 1.  GSS3.1 post sysprep issue

    Posted Mar 20, 2017 11:43 AM

    Hello All.

    I'm testing GSS3.1 MP5 and having issues with distributing image and need help to some answers.

    Background.

    1. I have used ghost sparingly but process such as ghostcast, USB boot, DVD boot all worked fine when i'm

    in front of the computer.

    2. Current enviroment is all windows 7 Enterprise with the plan to migrate to windows 10. it is in various

    location driving distances.

    3. SCCM is not an option or considered.

    4. 6X different PC models Dell and HP.

    5. Active directory access is limit to OU specific with only admin right to OU and AD object within the OU.

    ADUC access is limit to read only and write access have to be done through NETIQ DRA tool. AD scripting is

    not allowed.

    Setup

    1. GSS3.1 MP5 on Windows 2012R2

    2. Configure = Tools -> Options -> Domain account : with my OU admin account and password.

    3. Configure = Tools -> Options -> Task password ( what is this for? the help file is USELESS explaining)

    4. Installed ADK 1151 and created boot disk wizard from Ghost Console using WINPE10 and Automation folder

    .EXE

    5. Create a Ghost boot ISO and burn onto a CD.

    6. Fresh install windows 10 with drivers and Ghost Aclient (Agent)

    7. Created Unattended file to Accept EULA=True Set Administrator account and Organization name. place file

    in c:\windows\system32\sysprep folder

    8. Run as admin = sysprep /generalize /oobe /shutdown /unattend:unattended.xml

    9. Boot Win10 PC using Ghost CD.

    10. Win10 Client show up in Ghost console -> Right click Win10 client and Create disk Image.

    11. Ghost capture the image successfully and Win10 client boot to sysprep correctly.

    12. Shut down Win10 client.


    Migration Test

    1. Fresh install Windows 7 and join to Domain.

    2. Push install ACLIENT with OU admin account with no issue.

    3. Right click -> Advance -> install automation folder just hang on "Receiving client" on status bar ?????

    4. Work around #3 issue by creating a windows install job using the automation.exe file with a script step
    c:\windows\system32\bcdedit /timeout 0


    Push Windows 10

    1. Fresh install Windows 7 and join to Domain with Aclient and Automation folder installed.

    2. Create Distribute image job.

    3. Select Win10 Gho file

    4. Sysprep is not checked.

    4. Select "Automation perform configuration task after completing this image task"

    5. Select "Boot to production to complete configuration task"

    6. Add Modify configration Step.

    7. Select Microsoft Networking and use %NAME%

    8. Enter Domain name test.local under Microsoft Networking

    9. Start job and Win7 client reboot and go into boot automation and copy file completed.

    10. Ghost push the ghost image successfully and begin the Sysprep process then completed without issue.

    11. The system reboot and join the domain correctly. but Ghost console show error on step "configuring computer".

    " Access is denied" Status code= -2147024891 Win32  ( Any Idea?)

     

     



  • 2.  RE: GSS3.1 post sysprep issue
    Best Answer

    Posted Mar 20, 2017 03:41 PM

    If you are running an additional configuration task then you would not want the below options check on the deploy job. I am not sure what that error is your are receiving but attempt to run the deploy job with these unchecked and then your config task should run  and complete successfully after and join the domain.

     

    Select "Automation perform configuration task after completing this image task"

    Select "Boot to production to complete configuration task"



  • 3.  RE: GSS3.1 post sysprep issue

    Posted Mar 21, 2017 12:09 PM

    My imaging task look like below as one JOB. I will test with both option UNCHECK and will report back.

     

    Thanks

     

    Capture Personality

    Distribute Disk Image

    Modify Configuration

    Install Package (Distribute personality)

     

     

     

     



  • 4.  RE: GSS3.1 post sysprep issue

    Posted Apr 12, 2017 10:24 AM

    Tedy,

    Were you able to get the configuration to work properly?



  • 5.  RE: GSS3.1 post sysprep issue

    Posted Apr 27, 2017 01:19 PM

    Tedy,

    Please mark the most relevant answer as a solution if your issue has been resolved.