Ghost Solution Suite

 View Only
Expand all | Collapse all

Windows 7 - Push Configuration

  • 1.  Windows 7 - Push Configuration

    Posted Jan 23, 2012 02:46 PM

    Hello everyone,

    I'm having a little headache with my ghost solution suite and Windows 7. I have a task deploy without ghostwalker of Windows 7 Enterprise. After the ghost is deployed, sysprep is ran. After sysprep, the computer auto-logon then install various software, ending with ghost agent. After, the computer reboot and ghost does it thing.

    When looking at the task log, everything is fine; no warning, no error. But when going to the computer, it's not into the domain although the configuration say to put him into the domain. I have to send another push configuration task and then it's working. I never had this problem before and I can't find why it's doing that now.

    Thanks



  • 2.  RE: Windows 7 - Push Configuration

    Posted Jan 23, 2012 04:19 PM

    Are you running sysprep manually or using the sysprep option in the console?

    Are you running the configuration task along with the image deploy task?

     

    If running sysprep from the console have you specified the answer file to join to the domain?

     

    Provide details on the tasks being executed



  • 3.  RE: Windows 7 - Push Configuration

    Posted Jan 23, 2012 04:50 PM

    The sysprep is ran manually. I have an image called audit and another sysprep. The sysprep is ran manually cause I have a lot of script that run before the sysprep (a vbs I made). It used to work but I don't know why, on 8 labs I deployed, 3 didn't join the domain at first run.

     

    The configuration task is ran successfuly in the deploy task, that's my biggest issue. If it would at least give me a warning but no, all computer are renamed but they don't join the domain.

    It happen to computer regardless of past state to domain (new or already present).

     

    thanks



  • 4.  RE: Windows 7 - Push Configuration

    Posted Jan 24, 2012 03:16 AM

    Can you put a "pause" before the domain joining code, and check whether the NIC drivers are loaded?

    It could be that specific machines are not mounting the correct drivers and cannot therefore connect to the network to join the domain.

    Is the issue hardware specific?



  • 5.  RE: Windows 7 - Push Configuration

    Posted Jan 24, 2012 01:08 PM

    Hmmm. how do I put a pause?

    But I know it's not an NIC problem because if it was, ghost would report a failed task since it can't reach the computer. I know the drivers a good too because it used to worked and I didn't changed the drivers. Also, I have 5 labs with the same machine and they don't have all the same problem.

    I get a successful configuration task in ghost, although it doesn't do it. That's really weird.



  • 6.  RE: Windows 7 - Push Configuration

    Posted Feb 17, 2012 09:16 AM

    Update on the situation:

    I tried a new sysprep script. Now, instead of having an autoreboot after all my task in the first autologin, if ghost client is installed, it will stop and wait for ghost console task. This worked in 2 labs.

     

    But then, I got a new problem which is really a headache now. I had a lab fully working that after sysprep and ghost configuration task (everything is successful and the configuration are ok, I've been using it for the last 6 years), the computer didn't join the domain.

    I then run the task again (push configuration) and about 5 out of 21 joined the domain but they all reported successful on the configuration task.

    What's the issue here? I'm not in the sysprep phase anymore, windows is on the login screen, computer has been rebooted many time, the ghost client is running and I see the task running and applying configuration, but the computer remain out of domain. I have to manually join them.

     

    Thanks



  • 7.  RE: Windows 7 - Push Configuration

    Posted Feb 17, 2012 11:15 AM

    Can we check that you are running Ghost 11.5.1 at build 2266?. This revision is essential for Windows 7 environments.



  • 8.  RE: Windows 7 - Push Configuration

    Posted Feb 17, 2012 11:50 AM

    Yup it's that version. It worked well for the past year in Windows 7, I don't get why suddently, it stop working



  • 9.  RE: Windows 7 - Push Configuration



  • 10.  RE: Windows 7 - Push Configuration

    Posted Feb 17, 2012 03:43 PM

    Nope, nothing change (well, windows update and change in the sysprep order just to prevent an autoreboot, which I though was the cause).

     

    Sysprep isn't the problem (both link you provide talk 'bout sysprep and I don't use sysprep to join domain).

    I just tried again on the computer that is ghosted 2 days ago and again, it didn't join the domain although it's reported that it was successful.



  • 11.  RE: Windows 7 - Push Configuration

    Posted Feb 20, 2012 04:45 AM

    Running a configuration task along with deploying the image and running sysprep after that could be a possible cause for this issue.

     

    Please try running sysprep without the option to join a domain or skip the configuration task and then restore the image and run sysprep with settings to join domain.

     

    I have observed this issue to occur when joining the domain has been set in both sysprep and configuration task.

     

    Do try the above mentioned steps and update the status



  • 12.  RE: Windows 7 - Push Configuration

    Posted Feb 20, 2012 01:49 PM

    Hello,

    sysprep doesn't join the computer to the domain. Sysprep does only the following: generalize, sid gerenation, run script to install video card, install drivers, install various program (window security essential), configure keyboard because microsoft never understood what is French Canada => French Canada keyboard and always put English Canada => French Canada without removing all other keyboard, install ghost agent. It also generate a computer name, which is randomly generated from sysprep.

    Then, configuration task give the computer name and domain join, but only after the sysprep process. Everything is working well on my other images, just this one that started doing that problem.

     

    But then, It got worst. Here's the situation:

    I deploy the computer, sysprep is ran, computer is logged as administrator, installation script execue, ghost client is installed then the computer wait for further information from ghost. The, the configuration task is run, computer reboot in winPE, it receive his name, reboot and join domain (from task log). But in reality, the computer only changed name, no configuration task.

    Since that, the computer has rebooted many time (from users trying to login). 24 hours later, I try a new configuration task from cold boot. It does all the task as it suppose but no domain join (although log says it did). Another day after, tried again, same problem. I then proceed to connect myself as administrator and join the computer to the domain manually and it work.

    I'm currently deploying the images on another computer in another network to see if the same problem exist.