Ghost Solution Suite

 View Only
  • 1.  GSS 3.1 MP2 and Sysprep modification

    Posted Jul 15, 2016 12:44 PM

    Does anyone know where to modify the default sysprep file generated by GSS so that I can force a network driver that DeployAnywhere doesn't seem to inject correctly? 

     



  • 2.  RE: GSS 3.1 MP2 and Sysprep modification

    Posted Jul 19, 2016 11:12 PM

    Hi there,

    May I ask what OS you are deploying?

    We have noticed some issues with GSS 3.1 MP2 DeployAnywhere.

    We have been deploying our Win10 x64 image (via Win 10 x64 WinPE Automation Folder), but whenever DeployAnywhere runs, it seems to think the OS in the deployed image is X64_WINDOWS8 and will only inject Windows 8.1 x64 drivers, so when SysPrep runs, it doesn't find any drivers it wants to install for Win10.

    We ended up deploying our drivers as a copy file task in the automation environment after it has imaged and then running a script on reboot to install the drivers...

    Cheers,

    Sim.



  • 3.  RE: GSS 3.1 MP2 and Sysprep modification

    Posted Jul 21, 2016 09:14 AM

    We’re currently installing Windows 10 x64 on our computers also. 

    After some frustration, I converted the image I had to a .WIM file and injected most of the drivers I needed using DISM.  Though I still have problems with the network driver which is why I’m wanted to see if could modify the default syspep file to auto logon once to forced the driver to install. 

    Right now I’m testing using the systems task scheduler to test for a disconnected network at boot and reinstall the driver.

     



  • 4.  RE: GSS 3.1 MP2 and Sysprep modification

    Posted Jul 22, 2016 02:35 PM

    I'm glad to see that I'm not the only person having issues with Deploy Anywhere in Ghost 3.1 MP2. Hopefully Symantec finds a solution to this.