none
MDT 2013 REFRESH TS RRS feed

  • Question

  • I am working on trying to get the REFRESH (user backup) scenario working, but I am at a loss right now on exactly how it is supposed to be ran (while logged on or PXE)?

    I have no issues deploying an image while PXE booting, but I would really like to get the REFRESH (user backup) portion working. This will allow me a quicker imaging turn around, due to having to manually backing up each users data. Also is it possible to define user(s) or last logged on for the user backup?

    Thank you for all the help in advance!

    Thursday, October 1, 2015 5:26 PM

Answers

All replies

  • Isn't "user backup" called the "Replace" scenario?

    The clientreplace.xml task sequence template is executed from within the full OS. Just run \\server\deploymentshare$\scripts\litetouch.vbs and select your "Replace" task sequence.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Thursday, October 1, 2015 7:32 PM
    Moderator
  • Hello,

    the refresh task sequence should be launched from the old OS. you log in with an account that has admin rights, connect to the deployment share and launch litetouch.vbs. then you can select the task sequence in the wizard or you can automate this by using the customsettings.ini.

    regarding the user backup, you can specify which user is backed up by using several techniques, the easiest one is to filter accounts that haven't logged in in XX days. you can define that using the SCANSTATEARGS MDT variable (see https://technet.microsoft.com/en-us/library/dn781091.aspx for reference) and the /UEL scanstate switch (https://technet.microsoft.com/en-us/library/hh825093.aspx). you can also choose to exclude certain accounts using /UE (all local accounts or several accounts using a wildcard, etc.)

    if you want to only migrate one profile in particular dynamically based on the last logged on user, I think you will have to script that and set the UDPRofiles MDT variable


    David Sebban | Nelite North America | My Blog : http://dsebban.wordpress.com | Follow me on twitter : http://twitter.com/davidsebban


    Thursday, October 1, 2015 7:33 PM
  • The replace scenario is the one that includes replacing the computer and is broken down into 2 TS, one for data backup on the old machine and one for OS install and data restore on the new machine.

    the refresh scenario does data backup, os install and data restore on the same machine with only one task sequence

    the upgrade scenario preserves data and settings and only upgrade the OS


    David Sebban | Nelite North America | My Blog : http://dsebban.wordpress.com | Follow me on twitter : http://twitter.com/davidsebban

    Thursday, October 1, 2015 7:46 PM
  • @David - It was a rhetorical question for MBriles

    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Thursday, October 1, 2015 8:04 PM
    Moderator
  • Thank you for the responses.

    I understand the concept, but do I use a standard Client TS or a Standard Client Replace TS. I am unsure how to exactly setup up everything in the TS itself in order for it to run as a REFRESH and not a brand new install.

    Fro example in the Standard Client TS I see that there is a Stat Capture and a State Restore, which does the backup and restore of the user data and when ran it starts over as a new deployment. I know that there are REFRESH items that come as default inside that TS, but how exactly do I get those portions to run before I does a Disk Part and OS install?

    Below is what my CS has in it.

    [Settings]
    Priority=ByLaptopType, ByDesktopType, TaskSequenceID, ByDeploymentType, Default
    Properties=SavedJoinDomain,StagingOU, OUPath,

    [ByDesktopType] 
    Subsection=Desktop-%IsDesktop% 

    [ByLaptopType] 
    Subsection=Laptop-%IsLaptop%  

    [Desktop-True] 
    OSDComputerName=WK-#Right("%SerialNumber%",8)# 

    [Laptop-True] 
    OSDComputerName=NB-#Right("%SerialNumber%",8)#

    [Desktop-False] 
    Properties=MyCustomProperty

    [Laptop-False] 
    Properties=MyCustomProperty

    [ByDeploymentType]
    Subsection=%DeploymentType%

    [Default]
    SkipTaskSequence=YES
    SkipFinalSummary=YES
    SkipDomainMembership=YES
    SkipComputerName=YES
    SkipComputerBackup=YES
    ComputerBackupLocation=NETWORK
    SkipAppsOnUpgrade=YES
    SkipCapture=YES
    SkipProductKey=YES
    SkipBitLocker=YES
    SkipBitLockerDetails=YES
    SkipSummary=YES
    SkipDeploymentType=YES
    SkipBDDWelcome=YES
    HideShell=NO
    SkipTimeZone=YES
    SkipAdminPassword=YES
    SkipUserData=YES
    SkipApplications=YES

    TaskSequenceID=REFRESH

    OSInstall=YES
    DoNotCreateExtraPartition=YES
    DeployRoot=\\x.x.x.x\DeploymentShare$
    DriverGroup001=Windows 7\%Make%\%Model%

    UserDataLocation=\\x.x.x.x\Deploymentbuild$\UserBackup
    UDShare=\\x.x.x.x\Deploymentbuild$\UserBackup
    UDDir=%OSDComputerName%
    'UserDataShare=\\x.x.x.x\Deploymentshare$\MigUserFiles
    'UserDataDirectory=%SerialNumber%
    ScanStateArgs=/o /c /uel:30 /ui:* /efs:skip
    LoadStateArgs=/v:5 /c /uel:30

    UserID=domain user
    UserDomain=user domain
    UserPassword=domain password

    SkipLocaleSelection=YES
    KeyboardLocale=en-US
    UserLocale=en-US
    UILanguage=en-US

    TimeZoneName=Central Standard Time

    SLShare=\\x.x.x.x\Deploymentshare1$\Logs
    SLShareDynamicLogging=\\x.x.x.x\Deploymentshare1$\Logs\%ComputerName%
    EventService=http://x.x.x.x:xxxx

    With my CS set this way should the backup and restore work properly without it imaging as a new box?

    Thanks again!

    Thursday, October 1, 2015 8:30 PM