Ghost Solution Suite

 View Only
  • 1.  Sysprep - Machine not getting joined to Domain

    Posted Mar 02, 2007 10:21 AM
    I am having an issue with GSS Sysprep. I've added my sysprep.inf to the Sysprep Configurations in GSS. Everything works except it doesn't join or AD domain.

    In my sysprep.inf, I've added

    JoinDomain=AD
    DomainAdmin=******
    DomainAdminPassword=******

    In this file the passwords are correct and work if I run sysprep separately, but don't seem to have an effect.

    Any ideas?


  • 2.  RE: Sysprep - Machine not getting joined to Domain

    Posted Mar 04, 2007 03:44 PM
    Hi Bill,

    What GSS version do you use? I'd guess you've used console task to push an image? If so, how do you set up the task and what steps does it include? Please post your task's detail in here. If you use GSS 2.0, you can get all steps that the task has included by right click the task and choose "Task Scenario". Also after the task has been executed, can you export the task logs and post them here as well?

    Regards,
    Jenny


  • 3.  RE: Sysprep - Machine not getting joined to Domain

    Posted Mar 19, 2007 11:45 AM
    Jenny,

    Thanks...I'm using GSS 2.0. Here's the Task Scenario

    Task : New Image Task

    Task steps :
    User Migration: Capture
    Clone
    SID change
    Configuration
    User Migration: Restore

    Number of client machines: 1

    Machine names:
    ORLANDTST7-6552 - 71AACR3F

    Network Information:
    Data transfer mode: Not set
    Data throughput limit: Not set

    User Migration: Capture

    Apply Profile to : All Users
    Package name generated automatically from machine name
    Selected Migration Templates :-
    New Migration Template

    Clone

    Image definition: Images\T42 Orlando Image
    Image file location: C:\Documents and Settings\leahy\Desktop\orlando.GHO

    Target drive: 1

    Image info:
    1 - NTFS - 76316.1 - 6119.1
    Image file preserved: No
    Files and directories preserved: 0

    Configuration

    Configuration change type: Default
    Configuration changes per machine:

    ORLANDTST7-6552 - 71AACR3F

    Computer Name orlandtst7-6552 (Default)
    NetBIOS computer name ORLANDTST7-6552 (Default)
    User (No change)
    Computer Description (No change)
    Member of Domain AD (Default)
    Add to Active Directory containerTIAA-CREF Workstations/Production (Default)
    Move if currently in a containerYES (Default)
    IP Address DHCP (Default)
    Default Gateway (No change)
    DNS Domain (No change)
    DNS Server (No change)
    WINS Server (No change)
    Novell Netware Client (No change)

    User Migration: Restore

    Restore using most recent User Migration Package of same machine name

    Not sure how to copy the log.....but it fails at To Target Operating System. I believe I solved that problem...caused by me NOT installing GSS client on target machine first.

    Any help would be appreciated.

    Bill


  • 4.  RE: Sysprep - Machine not getting joined to Domain

    Posted Mar 19, 2007 11:56 AM
    Jenny,

    Here's the log.....

    Task Name: New Image Task
    User: leahy
    Execution Time: 3/13/2007 4:55:25 PM
    Number of client machines: 1
    Clients finished OK: 0

    Task warnings:1

    Task process listing
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Client file missing - copying from server now 3/13/2007 4:55:38 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Client file missing - copying from server now 3/13/2007 4:55:39 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Update DOS system files 3/13/2007 4:55:39 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Update DOS Network Drivers 3/13/2007 4:55:39 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Changing Logon Settings 3/13/2007 4:55:39 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 To target operating system 3/13/2007 4:57:57 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Send user migration options 3/13/2007 4:57:57 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Make user migration package 3/13/2007 4:58:57 PM WARNING
    Details for: Make user migration package
    To view the migration log file select "Error File" from the "View" menu in the event log.
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Retrieve user migration package 3/13/2007 4:58:58 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Changing Logon Settings 3/13/2007 4:58:58 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Create machine account 3/13/2007 4:59:03 PM Success
    Details for: Create machine account
    ORLANDTST4-6552, LDAP://addc06-nyc.ad.tiaa-cref.org//DC=ad,DC=tiaa-cref,DC=org
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Prepare configuration 3/13/2007 4:59:17 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 To Virtual Partition 3/13/2007 5:00:31 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Clone 3/13/2007 5:13:34 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 SID change 3/13/2007 5:14:42 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 Configuration 3/13/2007 5:15:07 PM Success
    ORLANDTST4-6552 - 71aacr3f 00-16-41-14-0C-B2 To target operating system 3/13/2007 6:00:13 PM Failed
    Details for: To target operating system
    Client timed out
    --------------------------------------------------------------------------------


  • 5.  RE: Sysprep - Machine not getting joined to Domain

    Posted Mar 19, 2007 05:01 PM
    Jenny,

    Found out the problem......of course human error......I didn't create a configuration set. Once question though, if you leave the "Apply Computer Name" field, blank, will it use the default one or will it assign something generic?

    Important since we use serial #s for our computer names.

    Thanks,

    Bill