Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Task sequence that will not join domain MDT 2010

Proposed Task sequence that will not join domain MDT 2010

  • Monday, August 13, 2012 1:38 PM
     
     
    Sign In to Vote
    0

    Using MDT 2010 to roll out Windows 7. I've been asked if we can put together basically a copy of our Windows 7 task sequence for roll out, only with a different naming convention and without having the machines join AD in the process.

    The problem I see is that both of those things are set to happen in our deployment rules in the deployment share properties. I am wondering if there is a way to have a task sequence under that share that will not join AD and will just use a generic computername that our techs can change on boot. I'm hoping that I don't have to add a 2nd deployment share that mirrors the first just to have 2 different settings, and can be done in the task sequence somewhere.

    Thanks

     

All Replies

  • Monday, August 13, 2012 7:40 PM
     
     
    Sign In to Vote
    0

    You can have different settings per task sequence in the customsettings.ini file. Take a look at this:

    http://www.deployvista.com/home/tabid/36/entryid/139/language/en-us/default.aspx

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

     
  • Monday, August 13, 2012 9:43 PM
     
     
    Sign In to Vote
    0

    You can have different settings per task sequence in the customsettings.ini file. Take a look at this:

    http://www.deployvista.com/home/tabid/36/entryid/139/language/en-us/default.aspx

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    Maybe I am not comprehending this but it seems to me that the customsettings.ini applies to ALL task sequences in the deployment share. Every deployment we have already uses that. What I'm not seeing is a way to differentiate on a per-task basis.

    what I tried was to make a copy and name it "customsettings2.ini" with joining AD stripped out and the naming change, then in the GatherLocalOnly section I pointed it to that file. After running that Task Sequence nothing changed. The system pulled the settings from the other file and joined AD and did our production naming for the workstation.

    So how exactly do I have a customsettings.ini for different task sequences?

     
  • Monday, August 13, 2012 10:37 PM
     
     Proposed
    Sign In to Vote
    0

    If you take a look at the link that I provided you can see that you can have multiple settings in cs.ini for different task sequences. Take a look at the example Johan has below. Johan set the priority level to be by Task Sequence ID first and then the Default. Below that he has the default settings, and then below that he has the Task Sequence ID with the settings for that particular TS. He has one TS joining a domain and another TS joining a workgroup. Follow the instructions in the link and you should be ok.

    [Settings]
    Priority=TaskSequenceID, Default

    [Default]
    OSInstall=Y
    SkipAppsOnUpgrade=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipBDDWelcome=YES
    SkipComputerName=YES
    SkipDomainMembership=YES
    SkipUserData=YES
    SkipCapture=YES
    DoCapture=NO
    SkipLocaleSelection=YES
    SkipTaskSequence=NO
    SkipTimeZone=YES
    SkipApplications=YES
    SkipBitLocker=YES
    SkipSummary=YES
    SkipBDDWelcome=YES
    TimeZone=004
    TimeZoneName=Pacific Standard Time

    [W7-X86-001]
    JoinDomain=TSLAB
    DomainAdmin=TSLAB\JoinAccount
    DomainAdminPassword=P@ssw0rd
    MachineObjectOU=ou=Workstations,dc=tslab,dc=net
    Applications001={785633b7-283b-420e-a4a3-2557377d204c}
    Applications002={c47087e9-220e-4191-930e-819cf03e7cfe}

    [W7-X86-002]
    JoinWorkgroup=WORKGROUP
    Applications001={5e731fe1-ef93-44f9-bb17-8f7a5734cec8}
    Applications002={c47087e9-220e-4191-930e-819cf03e7cfe}

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”


    • Edited by Frank Trout Monday, August 13, 2012 10:39 PM
    • Proposed As Answer by ssonal Tuesday, August 14, 2012 8:27 AM
    •  
     
  • Tuesday, August 14, 2012 1:02 PM
     
     
    Sign In to Vote
    0
    Ok so I would only add the differential settings under the different task sequences then? Sounds perfect.
     
  • Tuesday, August 14, 2012 2:16 PM
     
     
    Sign In to Vote
    0

    Just make sure you follow the first step in that post. I forgot to do it once and it drove me nuts.

    Configure the two Task Sequence's to run Gather local data and process rules (Rules file: customsettings.ini)

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

     
  • Tuesday, August 14, 2012 8:16 PM
     
     
    Sign In to Vote
    0

    Just make sure you follow the first step in that post. I forgot to do it once and it drove me nuts.

    Configure the two Task Sequence's to run Gather local data and process rules (Rules file: customsettings.ini)

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    I have been messing with it all day and I can't seem to get it to work. It seems to be all or nothing and will not differentiate between deployment task settings. I have definitely followed the first step.

    Here is my customsettings.ini file. Do you see anything that is off? (I modified any sensitive info)

    Essentially all I did for the first 3 tasks was take out the settings from [default] and added them under [%sequence name%] instead. Then for the VM one I set the 2 settings I want that are different from the rest. It seems to be only looking at [default] still because none of the machines are joining the domain and the VM ones are not getting the proper computer name. When I add anything to [default] (all the domain join stuff) the machines all join the domain, even the VM task. It's been driving me nuts all day.

    [Settings]
    Priority=TaskSequenceID, Default
    Properties=MyCustomProperty

    [Default]
    OSInstall=Y
    _SMSTSOrgName=Windows 7 Deployment
    AdminPassword=password
    AreaCode=215
    BuildID=Windows 7 Professional x64
    ComputerBackupLocation=\\server\DeploymentShare$\Captures
    CountryCode=1
    DeploymentType=NEWCOMPUTER
    FullName=companyname
    KeyboardLocale=en-us
    OrgName=companyname
    DoCapture=NO
    SkipAdminPassword=YES
    SkipApplications=YES
    SkipAppsOnUpgrade=YES
    SkipBitLocker=YES
    SkipBuild=NO
    SkipCapture=YES
    SkipComputerName=YES
    SkipDeploymentType=NO
    SkipDomainMembership=YES
    SkipFinalSummary=YES
    SkipLocaleSelection=YES
    SkipPackageDisplay=NO
    SkipProductKey=YES
    SkipSummary=YES
    SkipTimeZone=YES
    SkipUserData=YES
    SLShare=\\server\DeploymentShare$\Logs
    TimeZoneName=Eastern Standard Time
    UILanguage=en-us
    UserDataLocation=NONE
    UserLocale=en-us
    DoNotCreateExtraPartition=YES
    FinishAction=RESTART

    [Install Company Windows 7 Professional Image]
    ComputerName=%SERIALNUMBER%-Win7
    JoinDomain=domain.net
    DomainAdmin=adminID
    DomainAdminDomain=domain.net
    DomainAdminPassword=password
    MachineObjectOU=OU=Workstations Win7,DC=company,DC=net

    [Out of Box Windows 7 Install]
    ComputerName=%SERIALNUMBER%-Win7
    JoinDomain=domain.net
    DomainAdmin=adminID
    DomainAdminDomain=company.net
    DomainAdminPassword=password
    MachineObjectOU=OU=Workstations Win7,DC=company,DC=net

    [Windows 7 Development & QA Image]
    ComputerName=%SERIALNUMBER%-Win7
    JoinDomain=domain.net
    DomainAdmin=adminID
    DomainAdminDomain=domain.net
    DomainAdminPassword=password
    MachineObjectOU=OU=Workstations Win7,DC=company,DC=net

    [Image for Virtual Machines]
    ComputerName=W7VM
    JoinWorkgroup=WORKGROUP

     
  • Tuesday, August 14, 2012 8:23 PM
     
     
    Sign In to Vote
    0

    Make sure you are putting the Task Sequence ID in the brackets, not the description.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

     
  • Thursday, August 16, 2012 8:19 PM
     
     
    Sign In to Vote
    0
    Changed that, same results. It seems to be ignoring anything under the task sequence ID sections. If I take out the domain settings from default and add them under those, it just doesn't join the domain. When I add them back it joins fine. On the system I don't want to join, it is in the workgroup but not being named as I directed, it's just a MININT-XXXXX name. This has be pulling my hair out.
     
  • Friday, August 17, 2012 11:12 AM
     
     
    Sign In to Vote
    0
    Just out of curiosity, flip flop the priority level to Default, TaskSequenceID.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

     
  • Friday, August 17, 2012 3:24 PM
     
     
    Sign In to Vote
    0

    You have to put the task sequence ID in the brackets in UPPERCASE