Using partition variable in task sequence

I need to configure a piece of software as part of a task sequence to direct some of its files to a specific partition.  I have the ts creating 3 partitions and I'm specifying variables for each: DataDisk = 10GB, UsersDisk = 100GB, OSDisk = 100% remaining
free space.
The 100GB partition is the one I need the software to use. In the "Custom Tasks" section of the ts "Dump MDT Variables" step dumps all MDT variables to a text file on the local machine so I can see at that time UsersDisk = D:\, DataDisk
= C:\ and OSDisk = V:\, but after the deployment finishes UsersDisk = E:\.  Also in the "Custom Tasks" section I'm running the "Configure Data Igloo" to configure the program.  Is there a way to set UsersDisk = E:\ before I run
the "Configure Data Igloo" step when there's also an internal DVD drive likely using E:\?
Edit: I should add that it's all working properly at the moment but the "Configure Data Igloo" step is referencing E:\, not %UsersDisk% and I see this causing problems latter.  Does anyone know how the drive letters are assigned?  That is,
why does %DataDisk% = D:\ and %UsersDisk%= E:\ after deployment, why not the reverse?

Thanks for the reply Keith.  I'm not thrilled about having to customize the partition structure either but because we use Deep Freeze we need use Data Igloo to cache user profiles on a partition other than C:\.
What I've ended up doing is using the 'Set Task Sequence Variable' tasks to set DataDisk = D:\ and UsersDisk = E:\ and then I can reference these variables for the task that configures Data Igloo.  To be clear for anyone trying to follow this, I'm not
actually changing the letter assigned to the partitions, I'm just assigning a value to a variable which is then referenced in later task sequence steps.
The thing that I'm not sure about is how the partition letters are assigned.  In my case the DataDisk partition is always assigned D:\ and UsersDisk is always assigned E:\.  I thought it might be alphabetical but I changed the 'Format and Partition
Disk' step to rename UsersDisk to ADisk and it still gets letter E:\. 
This isn't a big deal but if anyone knows how the letters are assigned please let me know.

Similar Messages

  • Using computer variables in task sequence "Run Command Line"

    I am attempting to deploy VMs through VMware's vRealize Automation tool using CM. The process creates a CM computer object then creates a direct rule on a CM collection for the new computer object. During the creation of the computer object vRA creates computer
    variables provided by me on the computer object. I see the computer object built and i see the custom variables on the computer object:
    Name Value
    dns1 10.10.10.10
    dns2 10.10.10.11
    gateway 10.10.10.1
    ipAddress 10.10.10.2
    netMask 255.255.255.0
    In the task sequence the last step is to "Run Command Line":
    cmd /c netsh int ip set address name="Ethernet0" static %ipAddress% %netMask% %gateway% & cmd /c netsh int ip set dns name="Ethernet0" static %dns1% & cmd /c netsh int ip set dns name="Ethernet0" static %dns2% index=2
    When the TS gets to that step it doesn't substitute the variables in the command with the computer variables listed above. Looking at the smsts logs after the deployment is complete I see lines stating:
    Set Command Line:...
    Start executing command line:...
    Executing command line:...
    ProgramName = ...
    All of those lines show the command exactly as it is above with the %variables% intact.
    The command immediately fails with the error:
    Invalid address parameter (%ipAddress%). It should be a valid IPv4 address.
    Does anyone have a suggestion on why the TS isn't using the variables? I found this article https://technet.microsoft.com/en-us/library/bb693541.aspx but its for 2007 not 2012. I wasn't able to find something comparable for 2012.

    I don't know why anyone here thinks you *need* sccm osd to achieve fully automated customizations.
    Customer selects base image (2008 r2 core, 2008r2 gui, 2012 r2 core, 2012 r2 gui), which should be thin and with zero customizations anyway,
    vaai accelerated clone creates vm,
    ip addr/gateway/dns config is injected with powercli,
    customers config management engine agent of choice is installed via powercli script injection/execution (we have puppet users, ConfigMgr users, saltstack users, IEM users, Cheff users),
    the clone completes in ~2 minutes and a VM is presented to the customer in less than 5 minutes 
    Deploying windows VMs via SCCM OSD is not only slow, but requires dev work on the customer side to get things rolling which wastes everyone's cycles including your own

  • When to use unattend.xml in task sequence - best practice?

    Hi, I've tried researching this but not found an answer to my specific query.
    We have ConfigMgr 2012 R2 with MDT 2013 although I don't think this is an MDT specific question.
    I'm trying to create a Build and Capture task sequence for our Windows Server 2008 R2 and Server 2012 /2012R2 server builds utilising an UNATTEND.XML file to make some customisations that can be deployed for every build afterwards in a Deployment Task Sequence.
    Specifically the addition of some Windows Features like SNMP and it's configuration and the addition of the Telnet Client. There are other bits like language settings and configuration items but I'm specifically interested in the Features part for my question.
    In CM 2012R2 you now have the option under the "Apply Operating System" to use a captured image or an original installation source. However they work differently if you specify the use of the same unattended answer file.
    The "image" deployment ignores all of the "add features" sections of the XML file and the "installation source" loses the  configuration options from SNMP from the XML file. When you then deploy the captured image using
    the same unattend.xml again the one from the "installer" now has all the SNMP features required and the one from the "image" is still missing everything.
    So my question is as follows.
    What is best practice for specifying an unattend.xml file in a task sequence. Is it in the build and capture TS or in the Deployment TS ?
    or
    Do I need multiple XML files, one for build and capture with some bits in and another for deployment with the rest in?
    or
    Should I be doing something else?
    Although this is specifically asking about Server O/S we will be using the same methodology for Windows 7 deployment.

    In this case DISM is only used to add the actual features... for configuration you could use a simple script that runs afterwards. Sample registry file:
    SAMPLE REG FILE - HKLM-SNMP.reg
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters]
    "NameResolutionRetries"=dword:00000010
    "EnableAuthenticationTraps"=dword:00000001
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\RFC1156Agent]
    "sysServices"=dword:0000004f
    "sysLocation"=""
    "sysContact"=""
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\TrapConfiguration]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\TrapConfiguration\public]
    "1"="127.0.0.1"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\ValidCommunities]
    "public"=dword:00000004
    Sample batch file:
    SAMPLE SCRIPT FILE - ConfigureSNMPService.bat
    @ECHO OFF
    net stop "SNMP Service"
    regedit /s HKLM-SNMP.reg
    net start "SNMP Service"
    Also some settings for SNMP can be controlled through group policy:
    http://serverfault.com/questions/285762/group-policy-for-multiple-snmp-permitted-managers

  • What determines whether an application gets a green check or a yellow warning sign in the deployment summary screen when using an MDT/UDI task sequence?

    I am trying to get Office 2010 to install using a UDI task sequence, and it IS installing, but it has a yellow exclamation point next to it at the summary screen after the task sequence completes, as does another app I am trying to install.
    The apps that use an .MSI are fine, and get the green check, but the two apps that use .exe for their installers get the yellow warning sign.  I assume this has to do with exit codes or detection rules, but I am very new to SCCM (using 2012 and MDT
    2012 Update 1), so I need some help.
    Thank you! 
    EDIT: This probably has to do with the fact that SuccessOrFailureCode being blank.  I have been pouring over .vbs scripts and logs, but they all seem to indicate that my application installs just fine, with an exit code of 0. Where does this screen
    get the SuccessOrFailureCode?
    Like
    This
    Quote
    MultiQuote
    Edit

    I have some updated info on this problem.
    I am trying to install Symantec Endpoint Protection with a custom wrapped .EXE file, and I have created detection rules for the install.
    According to AppEnforce.log, SEP is installing and returning an Exit code of '1', and that is being handled with my custom return code handling, which I've defined as a 'success'.  However, the deployment summary is still showing a yellow exclamation point
    next to the SEP install, and the SuccessOrFailureCode is blank.
    Why isn't the SuccessOrFailureCode equal to '1'?  Where is the disconnect between the AppEnforce.log and the deployment summary.

  • Cannot use sqlplus variable in create sequence statement

    Hello!
    I would like to create a sequence object starting with a number retrieved from a select statement:
    var max_resp_no number;
    begin
    select max(substr(resp_no,2)) into :max_resp_no from brc_mast
    where substr(resp_no,1,1)='Z';
    end;
    print max_resp_no;
    drop sequence p659_resp;
    create sequence p659_resp start with :max_resp_no;
    It tells me that :max_resp_no is an 'invalid number';
    TIA,
    habeeb

    You need to do this entirely in PL/SQL. You can either create a procedure, or use an anonymous block. The procedure version is below. Just change the CREATE to a DECLARE to get an anonymous block.
    CREATE OR REPLACE PROCEDURE new_seq IS
    max_resp_no NUMBER;
    BEGIN
    SELECT to_number(MAX(SUBSTR(resp_no,2)))
    INTO max_resp_no
    FROM brc_mast
    WHERE SUBSTR(resp_no,1,1)='Z';
    EXECUTE IMMEDIATE 'DROP SEQUENCE p659_resp';
    EXECUTE IMMEDIATE 'CREATE SEQUENCE p659_resp START WITH '|| max_resp_no;
    END;
    SQL> CREATE SEQUENCE p659_resp START WITH 1;
    Sequence created.
    SQL> SELECT p659_resp.nextval from dual;
       NEXTVAL
             1
    SQL> SELECT * FROM brc_mast;
    RESP_
    Z001
    Z002
    Z003
    Z075
    SQL> exec new_seq;
    PL/SQL procedure successfully completed.
    SQL> select p659_resp.nextval from dual;
       NEXTVAL
            75Note that the user creating this procedure will need to have CREATE SEQUENCE granted explicitly for the procedure to work. The anonymous block version should work if CREATE SEQUENCE is granted through a role.
    John

  • Has anyone used NiNite in there task sequence?

    Hey everyone. 
    At my company we have a basic image standard applications that are on my WIM image (  java, flash, itunes, foxit reader, chrome, skype ) 
    whats happening is that I have to update my WIM all the time to keep up with the applicaiton updates so I was curious if I use NiNite as part of my applicaiton install.   ( rigt I only have office 2010 and our AV in the applications to install ) 
    what if I use the NiNite installer, it will download all the new updated applications versus getting pop up windows for software updates. 
    any help pointing me in the right direction would be appreciated 
    thanks 

    This will be a bare metal machine getting its first image / reimaged. 
    So it will be getting a base image and I would need to install all the essential applications ( java, flash, itunes,
    foxit reader, chrome, skype )  since those are updated on a weekly bases it seems like, I would like them to get the most up to date application during the time of the imaging. 
    does that make sense?  

  • Deploying the SCCM 2012 Client to WES 7 devices that are locked down with the FBWF using 2007 task sequence via WEDM.

    I'm wondering how people are migrating their embedded devices that are using the FBWF. I've done some googling and it seems like most people are just re-imaging the devices and after migrating a single device i see why. Its not a pretty process. This will
    be a long description but ultimately my question stems more from trying to find a better way to execute the device migration from 2007 to 2012.
    Some back ground on my situation might be in order here. I'm in the process of wrapping up our 2007 to 2012 migration. We have a 2007 infrastructure that was a central server with 2 primaries and 286 secondary site servers. I've consolidated that to a single
    2012 primary site server that hosts all the main roles. There are 2 more servers in the data centers both operating solely as push distribution points I'll refer to them as 2012 01 02 and 03. I'm over half way through the migration and so far haven't needed
    to offload any site roles. There are almost 10,000 clients now reporting to the 2012 site server and almost a 100 field servers pulling content from 2012 02 as their source dp as pull dp is the only way forward for this many devices. I've read the horror stories
    of trying spin up 200 plus push dps. We are running PKI. I'm at the point now where i need to start migrating the Windows Embedded Seven Standard clients that have the 2007 sccm client on them with WEDM for write filter handling.
    What i'm wondering is if anyone has any pointers for me regarding migrating the WES 7 devices. My plan that i've come up with is to somehow script the process using a 2007 WEDM Task Sequence to try and migrate them over to 2012. Things are complicated as
    I need to somehow script the install, the policy checkin, hardware inventory, software inventory, and validate the SCEP client installs before I reboot the device one last time to enable the FBWF. How I handled the SCCM 2007 client install on these devices
    when they were provisioned was to just create a batch file that would sleep for ten minutes then check to see if the inventoryagent.log file had been created yet. I realize now that is inefficient as i can kick off the inventory using a WMI method once the
    client has installed. Also I need to make sure the machine gets its first policy as that is how it creates the communication using PKI through that first policy transfer and that also finalizes the client install. The biggest piece i'm uncertain about in this
    regard is the SCEP client.
    I had to change the SCEP client install from yes to no in the default client settings as we have some Mcaffee servers that can't have the SCEP client on them. I have incremental updates enabled on the collection that has the policy that installs the SCEP
    client but this will take an unknown amount of time unless i force the environment to update as the device starts in 2012 install, or if I could kick off the SCEP isntall... IDK. I'm also wondering if i should keep the device in the migration process until
    i validate it has its proper scep policy applied which I believe can be validated by a registry key somewhere.
    Once the 2012 client gets installed will that cause it to lose its place within the 2007 Task Sequence? Considering its going to take a minimum of 2 reboots I'd normally use the task sequence to handle its progression through the process.
    I'm also considering trying to use an Orchestrator runbook, as that would be a good way to keep track of the migration process as each device migrates. Especially since this might take several seperate scripts.
    I'm going to take a stab at scripting the migration process, but if anyone has any pointers that might make this a less complicated I'd really appreciate it as I've got about 3000 of these devices that need to be migrated over. The other things i've learned
    the hard way is any time you have something this complicated over the course of 3000 devices you will run into unknowns and the failure rate increases. I'm in the precarious position of having to not only build this process out but in some situations have
    it complete in the shortest amount of time possible as we have sites running 24x7. I know the end users behavior all to well and they will just keep hitting the power button sometimes even though their not supposed to so they can get their device functional
    again. In those situations i'd end up, if i'm lucky with a device that no longer has a healthy SCCM client in either environment and the write filter disabled.
    So like i said any pointers anyone could throw my way i'd really appreciate. I manually went through the migration process on a single device for proof of concept and ended up with almost 2 pages of pseudo code for my migration script/scripts.
    Thanks,
    -K.R.

    Hi,
    In R2 there are some new variables you can use to solve this,
    http://ccmexec.com/2014/12/smstsmplistrequesttimeout-value-in-milliseconds/
    In Sp1 though adding a step to sleep for 2-5 minuter after reboot and before the application install step is a common workaround.. a powershell command with "Start-Sleep
    -s 120" should do it. 
    /Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • SCCM 2012 SP1 and MDT 2012 Task Sequence Templates, MDT File/Settings Packages

    We're setting up SCCM 2012 integrated with MDT 2012 for our OSD. My main issue is finding actual reference material for the MDT task sequence templates when integrated with SCCM. The MDT documentation has a lot of information on variables and task sequences
    outside of SCCM integration. 
    One thing I'd love to find information on is what's actually going on during an MDT Client Task Sequence template. I found this http://social.technet.microsoft.com/Forums/en-US/645a77b2-5be6-431d-818c-57d24b1435cc/understanding-mdt-task-sequence?forum=configmgrosd but
    it doesn't delve into the kind of detail I'm looking for. I can dig up information through the MDT reference material on some things, but I just can't find anything out there that actually walks you through an SCCM/MDT task sequence template. For instance,
    under State Restore what is being referenced in Install Software with base variable name PACKAGES, vs Install Applications and base variable name COALESCED APPS. And, where are you supposed to put these applications? That's just a specific example, I'm hoping
    to find some kind of walkthrough.
    Two things I'm hazy on are the MDT packages. What exactly are the MDT Settings Package, and the MDT Files Package? What are they used for? What benefits do you get out of using them? And, how exactly do you use them? I know one of them has something to do
    with customsettings.ini, but what's the point of using SCCM with MDT if you still have to muck around in the customsettings.ini file?
    Either way, it seems like there are a lot of references to SCCM task sequences, and a lot of references to MDT task sequences. But, not together. Which is a bit annoying since the MDT-integrated task sequence templates are very obviously different than either
    SCCM or MDT by itself. Any help would be appreciated, even just information on where to look. Maybe I'm just really bad at finding reference material for SCCM/MDT. Thanks. 

    When MDT integrated with SCCM, We need the following MDT components to be created:
    MDT Boot image
    MDT Toolkit Files
    MDT Settings
    The MDT boot image (for example) gives you extra abilities over the standard ConfigMgr boot image such as the ability to display a HTA Refer here:
    http://www.windows-noob.com/forums/index.php?/forum/98-frontends-and-web-services/
    MDT Files once created, you will find UDIWizard_Config.Xml file in which you can start User driven Installation OSD using UDI designer.
    Refer these links for better understanding:
    http://www.windows-noob.com/forums/index.php?/topic/5131-using-sccm-2012-rc-in-a-lab-part-16-integrating-mdt-2012-rc1-with-configuration-manager-2012/
    http://www.windows-noob.com/forums/index.php?/topic/5221-using-sccm-2012-rc-in-a-lab-part-17-using-mdt-2012-rc1-within-configuration-manager-2012/
    http://www.windows-noob.com/forums/index.php?/topic/5250-using-sccm-2012-rc-in-a-lab-part-18-deploying-a-udi-client-task-sequence-with-mdt-2012-rc1-integrated-in-configuration-manager-2012/
    Thanks, Prabha G
    Thanks for the quick reply. But, what about the MDT Settings Package? Also, both have a pretty big folder structure for each package. Surely it does more than just provide a couple xml and ini files? I'm not looking for anyone to spoon-feed me the information,
    but at least a pointer in the right direction for finding the reference material. It seems for SCCM/MDT integration you have to go all over the place finding scraps of information to put together. 
    Also, any info on the SCCM/MDT task sequence templates? Thanks. 

  • Image creation with MDT task sequence- "Windows has recovered from an unexpected shutdown"

    I'm using MDT 2012 U1 to build and capture a Windows 7 x86 image for deployment with ConfigMgr 2012 SP1.  I'm using the standard client task sequence in MDT.
    The MDT task sequence consistently fails after the reboot in the "Postinstall" group.  The install OS, Copy Scripts, Configure, Inject Drivers, Next Phase, and Restart Computer tasks all execute successfully, then the MDT-initiated reboot
    completes successfully.  There is nothing else helpful in the SMSTS.LOG, these are the last entries in the log:
    Successfully complete the action (Restart Computer) with the exit win32 code 0
    Sending status message
    Executing in non SMS standalone mode.  Ignoring send a task execution status message request
    Set a global environment variable _SMSTSLastActionRetCode=0
    Set a global environment variable _SMSTSLastActionSucceeded=true
    Expand a string %_SMSTSMDataPath%\Logs
    Deleting file without retrying
    The error message on the reference computer says, "Windows has recovered from an unexpected shutdown" along with "An existing in-progress deployment was found but is not in an expected state.  Would you like to ignore this in-progress
    deployment and start a new one?"
    I have found one post that suggested modifying customsettings.ini with  HideShell=Yes, which I tried.  It didn't help.
    I am not sure why MDT thinks the reboot was unexpected?  Has anybody run into this?  What steps can I take to narrow down the problem?
    Any help/suggestions are appreciated.
    Thanks,
    FP

    Thanks for your reply Phil.
    Setuperr.log is empty, zero bytes.  Setupact.log looks good to me, it has these entries at the end:
    OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE] --> [Image_State_Complete]
    OOBELdr.exe exiting with code [0x0]...
    Process exited with exit code [0x0]
    c:\windows\panther\SetupInfo succeeded.
    c:\windows\panther\setupinfo.
    Windeploy.exe exiting with code [0x0]
    SetupSQM Started
    Panther path is C:\windows\Panther
    SQM not opted in
    SetupSQM is finished
    Our image environment was created during an MCS Engagement, so we have the solution pack and there are many variables in customsettings.ini.  I will need to find out how to narrow this down but I'm not finding a log file that tells me where it's choking... 
    Any suggestions are appreciated.
    Thanks,
    FP

  • MDT 2013 - Different settings per task sequence

    Hi,
    I'm trying to create different settings for different TaskSequenceIDs. For one TS I wanted to join the pc to a workgroup and do SkipApplications=YES and for the other TS I wanted to join a domain and do SkipApplications=NO. But I can't get it to work for
    some strange reason.
    I've tried and tested this solution https://gallery.technet.microsoft.com/scriptcenter/Different-settings-per-4faa55e9#content but it doesn't work.
    I tried this too : http://www.the-d-spot.org/wordpress/2012/07/20/how-to-use-different-settings-per-task-sequence-with-mdt-2012/ but it doesn't work.
    Perhaps MDT 2013 acts different then 2012 and 2010???? It would be nice if you could help me out on this one. :-)
    Paul

    @fapw, we use the database for a few years now and we're quite familiar with it. But we're going to install MDT for a client and they don't have SQL and they don't want to have it installed on one of their servers. So that's why I'm playing with the customsettings.ini.
    The first I made was for a plain and simple capture, then I added Make&Model and I'm making it more and more complex. The idea is to have a final customsettings.ini that imitates - or gets as close as possible to - what we have already accomplished with
    the database.
    In the meantime I've read that the skip-panels-stuff is something that stands above everything and thus it's not possible to control that using properties, like f.ex. MACaddress. Well, that's alright then.
    But I've got GOOD news for you all : selecting values for variables based on TaskSequenceID DOES WORK in MDT 2013 and ADK 8.1. This is what I did :
    https://gallery.technet.microsoft.com/scriptcenter/Different-settings-per-4faa55e9#content
    So I've downloaded the vbs, created an "external" tasksequenceid.ini which is read at the beginning of my Task Sequence and booted up the pc. When you select the tasksequence of your choice the parameters get filled in correctly ! OSDComputername
    was the variable that I used to show me if the other tasksequenceid.ini file was read or not. If yes, the computername would have to be my value, if not it would be MININT-randomnumber.
    Only downside of this fantastic wizard is that going back to change one of your options is not possible anymore. The moment a variable has a value, it doesn't change anymore! That particular behaviour was messing up my tests yesterday.

  • SCCM 2007 - task sequence - prestaged media - self-signed certificates - error message 'Certificate has expired for this media'

    Hi there
    Quick scenario.
    We have created a task sequence prestaged media .wim file (SCCM 2007, client OS is Windows XP).
    Recently some of these swap-out machinses, on delivery and start up, have started showing this message:
    'Certificate has expired for this media'.
    This is because the self-signed certificate created during the prestaged media creation process has expired.
    My question is: is it possible to mount the image using dism or imagex and then inject an updated sertificate?
    Best regards
    John

    the disk that has the prestaged media applied must be the boot partition.
    create a task sequence to stage the prestaged media. In this task run a format and partition step which configures both the system disk and the os disk, though make the os disk the active boot partition. Then apply the prestage wim.
    On your deploy task, somewhere after the OS has applied create a group that runs only if the media is OEM (from memory  _SMSTSMedia =
    OEMMedia)
    in this group run the command bcdboot C:\Windows /s F: /f ALL where f: is the drive letter assigned to the system disk, then run another step that removes the drive letter and reboots. The deploy task will now continue and you will be booting to the system
    partition.
    So I wanted to get back to working on this issue.  I noticed that when I said it Worked that it was actually still booting from C drive instead of the reserved partition.  For the past few days I have been trying to get the prestaged to work like
    a network deploy but fail every time.  I cannot get the prestaged to boot from any other partition other then the partition where windows was imaged too.
    So where I am at today.  When I do as suggest above the D drive (The reserved Boot volume) return on reboot. it will not stay hidden.  also the OS is till booting from C and does not change to the D drive or no drive letter drive with the above
    commands.  I think there is some other command missing that tells it to boot from a new location that is not bcdboot.
    Has anyone seen any guides for how to use prestaged and bitlocker enabled task sequence?  I think that would help me figure out my current issues as with bitlocker you must have this other partition.

  • MDT 2012 Replace computer task sequence

    Hello all,
    I am using MDT 2012 Update 1 for upgrading over 200 machines from Windows XP to Windows 7.
    Some of these machines are going to be REFRESH scenario. I have the task sequence for REFRESH scenario and it is working as expected.
    However, I do not know how to create REPLACE scenario task sequence. From what I understand, I need to create two tasks sequences. I have created a task sequence that capture user's data and upload it to a share.
    But how do I create a restore task sequence that restores that data to another computer after installing OS? What do I need to in the restore task sequence that either prompts me to select where to restore the data from or knows where the data is?
    In SCCM there is computer association, but I have not been able to figure out how to do it purely using MDT. 
    Any expert help is greatly appreciated.
    Thanks in advance,
    SinghP80

    Right, you will need 2 task sequences in a replace scenario.  The REPLACE task sequence captures the user state from the running OS.  Then you use a NEW COMPUTER task sequence (I called mine RESTORE) that restores the user state back after installing
    the OS, which will boot from media or PXE.  RESTORE gets all of its values from the Default and Jackson sections. My apologies, my customsettings.ini is butchered and has comments and junk in it that I should remove to clean it up.  And you will
    have to edit the code as described in the settings per task sequence thread for my cs.ini to work.  And, I set my OSDComputerName=%assettag%.  I set my Dell asset tags in the BIOS with the Dell CCTK tool.
    http://social.technet.microsoft.com/Forums/en-US/e17a1952-d1f7-41ef-8231-0d6fcc41882e/mdt-2012-settings-per-task-sequence?forum=mdt
    [Settings]
    Priority=ByLaptopType, ByDesktopType, ByIsVM, DefaultGateway, TaskSequenceID, Default
    Properties=MyCustomProperty
    [DefaultGateway]
    192.168.122.1=Jackson
    [Jackson]
    DeployRoot=\\192.168.122.6\FDO_Offices
    SkipComputerBackup=NO
    BackupDir=Captures
    BackupShare=\\192.168.122.2\f$
    UDShare=\\192.168.122.2\f$\usmtstorage
    OSDComputerName=%AssetTag%
    UDDir=%OSDComputerName%
    SLSShareDynamicLogging=%DeployRoot%\Logs\%OSDComputerName%
    SLSHARE=\\192.168.122.2\F$\Logs
    MachineObjectOU=OU=Computers,OU=Jackson,OU=Branches,DC=xxxxxxxx,DC=xxxxxxxx,DC=xxxxxxxxxx
    UserDataLocation=\\192.168.122.2\f$\usmtstorage\%OSDComputerName%
    ComputerBackupLocation=\\192.168.122.2\f$\captures
    UserID=xxxxxxxxxx
    UserDomain=xxxxxxxxxx
    UserPassword=xxxxxxxxxxxx
    [ByLaptopType]
    Subsection=Laptop-%IsLaptop%
    [ByDesktopType]
    Subsection=Desktop-%IsDesktop%
    [ByIsVM]
    Subsection=IsVM-%IsVM%
    [Laptop-True]
    SkipBitLocker=NO
    BDEInstall=TPM
    BDEInstallSuppress=NO
    BDEWaitForEncryption=FALSE
    BDEDriveSize=512
    BDEDriveLetter=S:
    BDERecoveryKey=AD
    ;BDEKeyLocation=\\192.168.122.2\f$\bitlocker_keys
    BDEAllowAlphaNumericPin=Yes
    [Desktop-True]
    SkipBitLocker=YES
    [IsVM-True]
    SkipBitLocker=YES
    [Laptop-False]
    [Desktop-False]
    [IsVM-False]
    [Default]
    XResolution=1
    YResolution=1
    BitsPerPel=32
    ApplyGPOPack=NO
    HIDESHELL=NO
    DISABLETASKMGR=YES
    ;BackupDrive=ALL
    SkipProductKey=YES
    SkipLocaleSelection=YES
    UserLocale=en-US
    UILanguage=en-US
    SkipTimeZone=YES
    TimeZoneName=Central Standard Time
    KeyboardLocale=en-US
    _SMSTSOrgName=Office of xxxxxxxxxxxx
    SkipAdminPassword=YES
    AdminPassword=xxxxxxxxxxxxx
    SkipApplications=YES
    SkipAppsOnUpgrade=YES
    SkipDeploymentType=YES
    SkipSummary=Yes
    MandatoryApplications001={aa888a5e-849a-4522-a4e4-57b39dfa29c2} ;you'll want to remove this
    [NEWCOMPUTER]
    SkipUserData=YES
    DeploymentType=NEWCOMPUTER
    OSInstall=Y
    ;OSDComputerName=
    SkipComputerName=NO
    SkipFinalSummary=Yes
    FinishAction=LOGOFF
    SkipTaskSequence=NO
    SkipDomainMembership=YES
    JoinDomain=xxxxxxxx
    DomainAdmin=xxxxxxxxxxxxxx
    DomainAdminDomain=xxxxxxxxxxx
    DomainAdminPassword=xxxxxxxxxxxxx
    SkipCapture=YES
    DoNotCreateExtraPartition=NO
    [CAPTURE]
    SkipUserData=YES
    TaskSequenceID=CAPTURE
    DeploymentType=CUSTOM
    BackupFile=MASTERCAPTURE.wim
    SkipAdminPassword=YES
    AdminPassword=xxxxxxxxxx
    SkipCapture=NO
    DoCapture=YES
    [REFRESH]
    SkipUserData=NO
    TaskSequenceID=REFRESH
    DeploymentType=REFRESH
    DoCapture=NO
    USMTMigFiles001=MigApp.xml
    USMTMigFiles002=MigUser.xml
    USMTMigFiles003=MigDocs.xml
    USMTMigFiles004=migexcludexternaldrives.xml ;you'll want to remove this 
    USMTMigFiles005=migmydocs.xml ;and this
    ;USMTMigFiles006=migwallpaper.xml 
    ;USMTMigFiles006=MigNetPrinters.xml
    ; USMTMigFiles007=config.xml
    ;ScanStateArgs=/v:5 /o /c /vsc /all /localonly
    ScanStateArgs /v:5 /o /c /ue:%computername%\*
    LoadStateArgs=/v:5 /c 
    ;BackupDrive=ALL
    ;OSDComputerName=%OSDComputerName%
    SkipComputerName=NO
    OSInstall=Y
    SkipFinalSummary=Yes
    FinishAction=LOGOFF
    SkipTaskSequence=NO
    SkipCapture=YES
    DoNotCreateExtraPartition=NO
    SkipDomainMembership=YES
    JoinDomain=xxxxxxxxxxxx
    DomainAdmin=xxxxxxxxxxxxx
    DomainAdminDomain=xxxxxxxxxxx
    DomainAdminPassword=xxxxxxxxxxxxxx
    BackupFile=%OSDComputerName%.wim
    [REPLACE]
    TaskSequenceID=REPLACE
    DeploymentType=REPLACE
    SkipComputerName=NO
    DoCapture=NO
    USMTMigFiles001=MigApp.xml
    USMTMigFiles002=MigUser.xml
    USMTMigFiles003=MigDocs.xml
    USMTMigFiles004=migexcludexternaldrives.xml ;remove this
    USMTMigFiles005=migmydocs.xml ;and this
    ;USMTMigFiles006=migwallpaper.xml
    ;USMTMigFiles006=MigNetPrinters.xml
    ; USMTMigFiles007=config.xml
    ;ScanStateArgs=/v:5 /o /c /vsc /all /localonly
    ScanStateArgs /v:5 /o /c /ue:%computername%\* /ue:xxxxxxxxxxxx\administrator
    LoadStateArgs=/v:5 /c 
    ;BackupDrive=ALL
    SkipUserData=NO
    SkipAdminPassword=YES
    AdminPassword=xxxxxxxxxxx
    SkipCapture=YES
    DoCapture=NO
    SkipComputerBackup=NO
    BackupFile=%OSDComputerName%.wim
    [RESTORE]
    TaskSequenceID=RESTORE
    DeploymentType=NEWCOMPUTER
    DoCapture=NO
    USMTMigFiles001=MigApp.xml
    USMTMigFiles002=MigUser.xml
    USMTMigFiles003=MigDocs.xml
    USMTMigFiles004=migexcludexternaldrives.xml
    USMTMigFiles005=migmydocs.xml
    ;USMTMigFiles006=migwallpaper.xml
    ScanStateArgs /v:5 /o /c /ue:%computername%\*
    LoadStateArgs=/v:5 /c /ue:%computername%\* /ue:xxxxxxxx\xxxxxxxx
    SkipComputerName=NO
    SkipUserData=NO
    SkipDomainMembership=YES
    JoinDomain=MSS
    DomainAdmin=xxxxxxxxxxxx
    DomainAdminDomain=xxxxxxxxxxx
    DomainAdminPassword=xxxxxxxxxxxxx
    DoNotCreateExtraPartition=NO
    SkipFinalSummary=Yes
    FinishAction=LOGOFF
    SkipComputerBackup=NO
    Bootstrap.ini:
    [Settings]
    Priority=Default
    [Default]
    DeployRoot=\\192.168.122.6\FDO_Offices
    UserID=xxxxxxxxxx
    UserDomain=xxxxxxx
    UserPassword=xxxxxxxxxxxx
    SkipBDDWelcome=YES

  • OSD Task Sequence - Network boot capture of modified OS reference VM, but without MDT?

    Hi All
    Guess the Title of the question sums it up really.
    Is it possible to do a network-boot (aka PXE) capture of an OS that has been modified, so that its WIM is created for use within other deployment Task Sequences?
    I know that this is possible via MDT's "Sysprep and Capture" Task Sequence, but this integration has not been done yet, and from time-scales is not possible.  Just curious if others have found a work around via custom Task Sequence(s) of some
    kind?  If not will have to go with the SCCM's more manual 'Capture Media' option.
    Any help much appreciated.
    Kind Regards
    Andrew

    Hello,
    It is possible to capture image without MDT integration
    http://www.windows-noob.com/forums/index.php?/topic/4468-using-sccm-2012-rc-in-a-lab-part-7-build-and-capture-windows-7-x64/
    You can also do this manually.
    You need sysprep the reference image first, then boot into win PE with either PXE or USB bootable device. Run ImageX or DISM tool to capture the image. Check this:
    https://technet.microsoft.com/en-in/library/dd799291%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Running a Task Sequence within a Task Sequence

    We are running an SCCM 2012 R2 setup for OSD, WSUS, App Deployment and Endpoint Protection.
    To simplify the management of drivers across several OSD task sequences, I'd like to have one "master" task sequence containing only Apply Device Drivers with model specific targeting that is referenced from the OSD task sequences.
    Why would I want this? With every new computer model that is being added to the environment (We are currently supporting 20 different computer models, and the list keeps growing), I have to update one task sequence with model specific targeting for a driver
    package, then copy all the changes to several other task sequences. To try to simplify the administration and reduce the chance of human error and ensure consistency across the board, this would probably be the best way to ensure this.

    Out-of-the-box you can't start one task sequence within another task sequence. A few workarounds:
    You can make your task sequence put your computer object in a new collection which has a new task sequence targeted, but that probably won't perform that well;
    You can target multiple task sequences to the same collection and try to use PowerShell to trigger a new task sequence. For example something like this (I have never tried to use this from a task sequence):
    http://powersheller.wordpress.com/2012/05/24/sccm-2012-execute-task-sequence-with-powershell/
    You can try to merge your current task sequences.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude
    Since what I'd like to do is to "pause" the current task sequence until the second task sequence has run and then resume the current task sequence (Just the apply drivers step) I don't think either would be great options. I guess the copy paste
    option is what is left for me.
    Thanks for replying and your suggestions

  • Operating System Package Section Window is blank for Task Sequence

    Trying to create a capture and build sequence. I have added Win7 x64 to the 'Operating System Installers' section. But when going into 'Create Task Sequence' I dont have any operating systems to select. (see screenshot).
    Only info I found on the web references to beta versions of SCCM 2012. I added server is SCCM 2012 R2 Update 1. (version 5.00.7958.1000).
    Any Suggestions?

    During the Create Task Sequence Wizard, this step requires to use a
    Operating System Image (a WIM file) and not a Operating System Installer.
    An Operating System Installer can only be used by editing the task sequence after the wizard.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

Maybe you are looking for