Task Sequence - Moving computer to new OU

I have a SCCM 2012 SP1 Cumulative Update 3 environment and I am trying to build a step into my Win7 x64 task sequence that will query registry keys to get username and workstation type (laptop vs. desktop).
The user information is obtained at the beginning of the process, put into n TS variable, and written to the registry. After the OS, drivers, and basic software is installed, I would restart into OS and would like to query the registry, move the computer
OU based off user's domain id location, and rename computer via a powershell script.
I have the following steps built into the task sequence.
1. Install .Net Framework 4.5
2. Install WMF 4.0
3. Enable RSAT and Import AD Module
4. Move and Rename Computer
I am running into issues with the powershell script that runs on step 4. The script is running with an ID account that has privileges to query AD and move computers. All steps (1-4) run without any issues if I target the computer that already has an
OS installed.
Here is the command that I am running in the step 4: 
powershell.exe -ExecutionPolicy Bypass -File SHI_Computer-New.ps1
It fails on the first line that queries the registry with an error that states “Get-ITemProperty is not recognized as a cmdlet, function, operable program, or script file.
$Name = (Get-ItemProperty -Path HKLM:\SYSTEM\Setup\SCCMOSD -Name User).User
Has anyone seen this type of issue?
If I hit F8 and run the script as local system from the Packages folder that contains the script I can run the script without any issues.
Any feedback is greatly appreciated!

I decided I would take the Get-ItemProperty out of the mix and use the task sequence variables in the command line, but still encounter the same issue.
Here is the command line that I am now using:
powershell.exe -ExecutionPolicy Bypass -File SHI_Computer.ps1 -Name %USER% -Desktop %ISLAPTOP%
It is able to resolve my arguments without any issue, but now errors on the Get-AdUser logic.
param(
  [string]$Name,
  [string]$Desktop
$Name
$Desktop
$UserID = Get-AdUser $Name | FT SamAccountName
Here is the error:
GetAdUser: The term 'Get-AdUser' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Am I missing something in my powershell script or is this not possible in a task sequence?
Is anyone else using the Active Directory module in a task sequence? 

Similar Messages

  • Moved computer to new desk; now can't connect to internet or network

    I moved a computer to another office down the hall and now it won't connect to the internet or office network. Two other computers connected using the same ethernet plug and wire. Repaired permissions. Tried manually entering IP and using DHCP. What else should I try?

    I'm no expert but maybe try adding a new location.
    Network preferances -> location drop down -> new location
    Then try manually entering all the information required.
    Just a wild guess...
    -Ollie

  • Cannot open any of my music on itunes...moved computer to new area in house

    itunes was created originally on computer A with an added external drive as backup.... have new computer now(B) ... hooked external drive to (B)...... computer (A) moved to secondary position on wired router......can see my itunes library but cannot access any tunes!!!! Do I need to refer back to external drive? Tunes should be available here on (A) and accessible from (B) and other laptops/ipad connected to this Wifi....what am I doing wrong?

    Your music will only be where you put it.
    It has always been very basic to always maintain a backup copy.  Have you failed to do this?
    If for some reason you have failed to back up, then you can redownload some itunes purchases in some countries:
    Downloading past purchases from the App Store, iBookstore, and iTunes Store

  • Custom Image Capture that Auto Imports the OS WIM and Creates a New Task Sequence

    We just finished a consulting project where our customer requested an easy solution to capture thick images.  After hearing their reasoning it made sense for their circumstances.  The people that
    will be managing the system will be non-technical and all they wanted was a very, very simple method of capturing and deploying images with no learning curve.   They wanted the ability to Deploy the images via PXE.  
    This quickly became both our easiest scope project but making MDT simple for non-technical users can be challenging.   The MDT capture and staging steps are pretty easy for tech savvy person but for non-technical people it presented a learning
    curve that the customer wanted simplified. They didn’t want to understand sysprep, capture, importing an OS and then creating a Task Sequence to reference that new image.        
    So we changed the scope of our project to automate MDT to perform additional steps following the capture that would:
    Automatically Import the Captured OS into the MDT Deployment Share
    Automatically Create a new Task Sequence that references the newly imported image
    Auto Name the Task Sequence with the Model Name, Date and Time of Capture
    The Final Solution:
    Customer will setup a Windows PC Thick Image (All software and drivers)
    The customer will Kick-off the Sysprep and Capture Task Sequence
    The customized Task Sequence will capture, import the new image, and create a new TS with the new image
    Customer can then PXE boot a new computer and Deploy the image or stage to media and deploy the image
    We were able to remove the import OS and create new task sequence steps and this simplified it for our customer considerably.  If anyone is interested in this functionality
    let me know and I can send you instructions.  We used Vbscript, Powershell and PSExec.exe from PowerShell.  It seems to being working pretty good so far
    MDT Task Sequence Duplicator https://panaconsulting.egnyte.com/h-s/20130614/61707be809944999 Application Bundle Duplicator https://panaconsulting.egnyte.com/h-s/20130614/405e7d64e5d54610

    We just finished a consulting project where our customer requested an easy solution to capture thick images.  After hearing their reasoning it made sense for their circumstances.  The people that
    will be managing the system will be non-technical and all they wanted was a very, very simple method of capturing and deploying images with no learning curve.   They wanted the ability to Deploy the images via PXE.  
    This quickly became both our easiest scope project but making MDT simple for non-technical users can be challenging.   The MDT capture and staging steps are pretty easy for tech savvy person but for non-technical people it presented a learning
    curve that the customer wanted simplified. They didn’t want to understand sysprep, capture, importing an OS and then creating a Task Sequence to reference that new image.        
    So we changed the scope of our project to automate MDT to perform additional steps following the capture that would:
    Automatically Import the Captured OS into the MDT Deployment Share
    Automatically Create a new Task Sequence that references the newly imported image
    Auto Name the Task Sequence with the Model Name, Date and Time of Capture
    The Final Solution:
    Customer will setup a Windows PC Thick Image (All software and drivers)
    The customer will Kick-off the Sysprep and Capture Task Sequence
    The customized Task Sequence will capture, import the new image, and create a new TS with the new image
    Customer can then PXE boot a new computer and Deploy the image or stage to media and deploy the image
    We were able to remove the import OS and create new task sequence steps and this simplified it for our customer considerably.  If anyone is interested in this functionality
    let me know and I can send you instructions.  We used Vbscript, Powershell and PSExec.exe from PowerShell.  It seems to being working pretty good so far
    MDT Task Sequence Duplicator https://panaconsulting.egnyte.com/h-s/20130614/61707be809944999 Application Bundle Duplicator https://panaconsulting.egnyte.com/h-s/20130614/405e7d64e5d54610
    I would love to get the instructions to this process, as I have a simular client.

  • Trying to use Variables with the Unknown Computer collection to prompt Task Sequence for Domain, Join Account, Join Password, and Join Location.

    I want to use SCCM 2012 R2 and OSD, to boot a bare metal machine, install and OS, and bind it to Active Directory. The catch is that I want the deployment process in SCCM to prompt for the following pieces of information, and then use that information to
    bind the computer to Active Directory (W/O using MDT) instead of supply the data in the task sequence.
    Computer Name
    Domain
    Domain OU
    Domain Join Account
    I am approaching this in a similar fashion as stated in this blog.
    http://osdblog.com/2013/06/26/add-a-prompt-for-a-computer-name-in-your-sccm-deployment/
    I have added the following collection variables to the unknown computers collection:
    When I launch the task sequence, I am prompted as I would expect. I input the desired information, the deployment competes, but it does not bind to the domain.  Here is what my TS looks like. I intentally disabbled  the apply Network Settings step
    because it forces you to enter specific information if it enabled. I don't want to that, thus why I am trying to use the variables.
    My SMSTS log does not have a whole lot of meaningfull data, but I can post it if someone wants to see it. The only possible thing I could think of would be drivers, their are some driver errors in the log. However, if I turn on the Apply Networking setting
    process in the task sequence and turn off the variables, the machines bind fine. With that in mind, I would not think my problem would be driver related. Anyone out there have expertise in using a process like this, that could assist?
    --Tony

    Awesome! Thanks. One more thing, how should I supply the OSDJoinPassword variable? Should I just enter %OSDJoinPassword%
    for Password and Confirm Password? I can not tell if it will actually read it as a variable or try to use "%OSDJoinPassword%" for
    the actual password.
    --Tony

  • Powershell commands to change operating system image in task sequence

    Hello,
    I am looking for a way to script changing a task sequence to use a different OS image file. So far the only thing I can find using the powershell MDT module is the "import-mdttasksequence" command, but it looks like that can only create a whole
    new task sequence.
    My end goal is to automate our master image builds  and the last step is to take the captured master wim file, import it into the Operating Systems folder, and then update the associated custom image task sequence to use that new OS image. With
    "import-mdttasksequence" I have to create a new task sequence with a new ID, when I already have one present that would be easier to just update to point to a different OS image. I do not see anyway to edit task sequence steps using the powershell
    module.
    Is this possible? Maybe using Get-Item to get the OS GUID and then editing the task sequence XML file directly?
    MDT 2013
    Server 2008 R2
    Regards,
    Darren

    Hi Darren,
    If I understand correctly, you can use the same name for the captured WIM file? Then you can just copy it to the operating systems and it will be picked up by your TS.
    I've found this
    thread on the forums that probably has your solution in it.
    From that thread:
    I now capture to the Captures folder and name the WIM file after the task sequence ID. So for example, my "Update Windows 8 General Purpose" task sequence with ID "8_GP" now creates "\\server\DeploymentShare$\Captures\8_GP.wim"
    In the Scripts folder on the deployment share I created "Relocate.cmd" with the following contents:
    MOVE /Y "%DEPLOYDRIVE%\Captures\%1.wim" "%DEPLOYDRIVE%\Operating Systems\%1"
    And finally, I added a step at the end of my task sequences that runs this custom command (no
    Start in value defined):
    cmd /c %SCRIPTROOT%\relocate.cmd %TaskSequenceID%
    This works great and MDT does in fact recognize the changed .wim file in Operating Systems and copies it to linked deployment shares, so no worries there.
    Hope this helps.

  • 2012R2 Application installation steps after deploying OS from Task sequence is slow after applying hotfix 2910552

    We are currently using CM2012r2 for Endpoint protection, and in trying to save licensing costs, I have been given the task of doing imaging and application deployment through CM as well... everything started off well... noticed that imaging took a lot longer
    than I remembered when I used CM2007 at my previous employer. Found we needed hotfix 2910522 and what took an hour to download now only takes 5 minutes (yay!) Then started other strange issues.  Mostly the fact that in the task sequence, the install application
    blocks (we have 3 with 4-8 apps each) suddenly got really slow to execute. (boo!)  The application blocks eventually finish, but take about 5 hours and only the last block actually installs.    For example: 7zip takes 15 minutes to "install"
    but since it isn't in the last block, it doesn't in fact install on the system.
    so here is what I know so far:
    Updated the boot image after applying the hotfix
    Added the hotfix to the Windows and configmgr setup step command line to install the patch
    Verified that all applications install correctly outside of the task sequence.
    Created a new task sequence just in case the hotfix messed something up.
    here is what I've noticed:
    Only happens on workstations that have been imaged previously by CM (even if I remove the machine from AD and CM)
    New machines image just dandy
    not hardware specific (tested on 5 different laptop models and 3 desktop models)
    workstations that have the issue, when finished, only installed the applications from the last block (4 apps) and none from the previous 2 blocks (16 applications)
    If imaged new (not previously known) it installs the client correctly and it checks in, ones with the issue are in internet only mode and don't see the PKI cert for the machine, and will not check in.
    Things I've checked, double checked, verified, and done:
    All applications have the box for "allow this application to be installed from the Install Application task sequence action..."
    applications are on all distribution points
    Distribution points are healthy
    One MP/DP was complaining about how it couldn't access a SMS folder.  uninstalled the roles, let it sit over the weekend, reinstalled this morning
    Verified that the servers were on 10Gb full and were not throwing error on the line
    Antivirus scanning was not scanning the store (used the built in template for scep)
    Next steps that I am going to try:
    create a new task sequence and split up install application blocks to only have single applications in them
    recreate the boot wim for the media
     Thanks in advance

    So this issue of yours is in B&C -task sequence? You're using capture CD for capturing, why? Why not automate the build entirely.
    I'd suggest you add this:
    http://support.microsoft.com/kb/2775511/en-us to your BUILD image (either online of offline, in the WinPE -phase), it fixes many WMI related problems.
    After you've done your golden .wim, deploy it to your clients.
    We don't do a build and capture because certain applications require handling on our part. Management has said it needs to be a certain way, therefore this is how we have to build it.  (mostly settings, and views that can't be controlled through registry,
    Group Policy, etc.)  There are users that if they have to click on an accept button or it isn't the right color, or they want a different icon in their lab, then they go to the top and it comes back down to us, and our lives become miserable.
    We create the image in audit mode, capture it using boot media, and sequence in things that are updated constantly (flash, shockwave, java, etc.) through the task sequence.
    in relation to that KB, why would it work on new machines but not ones that have been touched before?

  • Driver Utility Task Sequence Process/Examines all the driver Packages in the T/s, Although it actually should install only 2-3 Drivers for a particular Computer Model

    Hi,
    Although the Driver Utility Task Sequence is working fine as expected, i have noticed that after initiating the Driver Utility from from the Software Center it takes quite a long time to start the installation of the drivers and few Apps which are in chain
    I have pasted the log from a Computer which shows that it checks/Processes all the packages which are in the T/s and that is where it spends the time, although for this model it has to install just 3-4 drivers
    Can we do something about this, to make the installation process just checks/Examines the drivers which are associated under its Specific Model Tree and saves time.  ( Fyi there are around 14 Different Models of Laptops/Desktops which are separated
    by folder and a WQL Query to identify the Model.
    could not paste the log file as its too long
    Thank you,
    Tanoj
    OSLM ENGINEER - SCCM 2007 & 2012

    Is there a specific need that you need to update the already installed drivers or is this just something that someone
    has always done and it will always be done? Give it a thought for a moment.
    We dont upgrade the already installed Drivers, its just installed when a machine is newly imaged / reimaged 
    so whenever a new image is being engineered, simultaneously we create a new T/s with updated drivers and that goes to production along with the new image release
    Thank you all for your replies, looks like the only option at this point is to workaround with splitting the T/s
    Regards
    Tanoj
    OSLM ENGINEER - SCCM 2007 & 2012

  • 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

  • OSD Task Sequence fails with "There are no task sequences available for this computer"

    Let me preface this by saying that I have read at least 100 forum posts with people having similar issues. However, none of the solutions in those
    posts have worked for me.
    The Problem: SCCM 2012 R2 will not image unknown computers.
    The task sequence gives the error "There are no task sequences available for this computer." As soon as that error occurs, SCCM places an Unknown entry into the All Systems collection. I have been imaging unknown computers, without fail, for
    4 months and no environmental changes have been made. NOTE: I am using USB media, not PXE.
    What I've Tried:
    Checked for duplicate SMSBIOS GUIDS in the console, none.
    Checked for duplicate MAC Addresses in the console, none.
    Checked for expired certificates, none.
    Recreated Boot Media, twice.
    Deleted the Unknown entry and retried, SCCM just recreates the Unknown entry.
    Deleted all of my task sequence deployments, and then redeployed them each to All Systems (Only Boot Media and PXE) and to Unknown Systems (Only Boot Media and PXE)
    I have also ran the following in the SQL Server Management Studio;
    SELECT
    * FROM
    ResPolicyMap WHERE
    machineid = 0 and
    PADBID IN
    (SELECT
    PADBID FROM PolicyAssignment
    WHERE BodyHash
    IS NULL)
    No result
    Select
    * From
    vMacAddresses Where
    MacAddresses = '00:00:00:00:00:00'
    This displays an entry for every time that I have tried to image the unknown machine attached to the MAC Address with a different ItemKey and SMS_Unique_Identifier for each entry.
    Added the machine manually using Import Computer Information, immediately recognized the Task Sequences that I have advertised to the All Systems collection.
    Any and all assistance is welcome, I am going on the third straight day of dead ends. Below I have tried my best to post the entire SMSTS Log;

    LOGGING: Finalize process ID set to 744
    ==============================[ TSBootShell.exe ]==============================
    Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
    Debug shell is enabled
    Waiting for PNP initialization...
    RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM
    WinPE boot path: C:\SOURCES\BOOT.WIM
    Booted from removable device
    Found config path C:\
    Booting from removable media, not restoring bootloaders on hard drive
    C:\WinPE does not exist.
    C:\_SmsTsWinPE\WinPE does not exist.
    Executing command line: wpeinit.exe -winpe
    The command completed successfully.
    Starting DNS client service.
    Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\
    The command completed successfully.
    ==============================[ TSMBootStrap.exe ]==============================
    Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\
    Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
    Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL'
    Current OS version is 6.2.9200.0
    Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH
    Failed to open PXE registry key. Not a PXE boot.
    Media Root = C:\
    WinPE boot type: 'Ramdisk:SourceIdentified'
    Failed to find the source drive where WinPE was booted from
    Executing from Media in WinPE
    Verifying Media Layout.
    MediaType = BootMedia
    PasswordRequired = false
    Found network adapter "Intel(R) Ethernet Connection I217-LM" with IP Address XXX.XX.XXX.XXX.
    Running Wizard in Interactive mode
    Loading Media Variables from "C:\sms\data\variables.dat"
    no password for vars file
    Activating Welcome Page.
    Loading bitmap
    WelcomePage::OnWizardNext()
    Loading Media Variables from "C:\sms\data\variables.dat"
    no password for vars file
    Spawned thread 1008 to download policy.
    Entering TSMediaWizardControl::GetPolicy.
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'
    Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'
    Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}
    Setting LogMaxSize to 1000000
    Setting LogMaxHistory to 1
    Setting LogLevel to 0
    Setting LogEnabled to 1
    Setting LogDebug to 1
    UEFI: false
    Loading variables from the Task Sequencing Removable Media.
    Loading Media Variables from "C:\sms\data\variables.dat"
    Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
    Setting SMSTSMP TS environment variable
    Setting _SMSMediaGuid TS environment variable
    Setting _SMSTSBootMediaPackageID TS environment variable
    Setting _SMSTSBootMediaSourceVersion TS environment variable
    Setting _SMSTSBrandingTitle TS environment variable
    Setting _SMSTSCertSelection TS environment variable
    Setting _SMSTSCertStoreName TS environment variable
    Setting _SMSTSDiskLabel1 TS environment variable
    Setting _SMSTSHTTPPort TS environment variable
    Setting _SMSTSHTTPSPort TS environment variable
    Setting _SMSTSIISSSLState TS environment variable
    Setting _SMSTSMediaCreatedOnCAS TS environment variable
    Setting _SMSTSMediaPFX TS environment variable
    Setting _SMSTSMediaSetID TS environment variable
    Setting _SMSTSMediaType TS environment variable
    Setting _SMSTSPublicRootKey TS environment variable
    Setting _SMSTSRootCACerts TS environment variable
    Setting _SMSTSSiteCode TS environment variable
    Setting _SMSTSSiteSigningCertificate TS environment variable
    Setting _SMSTSStandAloneMedia TS environment variable
    Setting _SMSTSSupportUnknownMachines TS environment variable
    Setting _SMSTSTimezone TS environment variable
    Setting _SMSTSUseFirstCert TS environment variable
    Setting _SMSTSx64UnknownMachineGUID TS environment variable
    Setting _SMSTSx86UnknownMachineGUID TS environment variable
    Root CA Public Certs=
    Missing root CA environment variable from variables file
    Support Unknown Machines: 1
    Custom hook from X:\\TSConfig.INI is
    No hook is found to be executed before downloading policy
    Authenticator from the environment is empty.
    Need to create Authenticator Info using PFX
    Initialized CStringStream object with string: 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A;2014-07-16T18:15:39Z.
    Set media certificate in transport
    Set authenticator in transport
    CLibSMSMessageWinHttpTransport::Send: URL: XXXXXXXXX.XXXXXX.com:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA
    Request was successful.
    Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider
    Default CSP Type is 24
    New settings:
        site=XXX,XXX, MP=http://XXXX.XXXX.com, ports: http=80,https=443
        certificates are received from MP.
    Unknown machine GUIDs: 774b17a2-6eeb-44bc-9c94-ce9081f5fe4c 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
        MP specific X86 unknown machine GUID is received at run time
        MP specific X64 unknown machine GUID is received at run time
    Getting MP time information
    Set authenticator in transport
    Requesting client identity
    Setting message signatures.
    Setting the authenticator.
    CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80  CCM_POST /ccm_system/request
    Request was successful.
    ::DecompressBuffer(65536)
    Decompression (zlib) succeeded: original size 406, uncompressed size 2460.
    -120
    Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
    Client Identity:
    Netbios name:
    Current time: 2014-07-16 18:15:39.787 TZ:Pacific Standard Time Bias:0480
    Current time zone info: 480, Pacific Standard Time, [0 0 0 0 0 0 0 0], 0, , [0 0 0 0 0 0 0 0], 0
    Adjusting the system time: -14400.551 seconds
    Time zone info set to: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
    New time: 2014-07-16 14:15:39.235
    Current time: 2014-07-16 14:15:39.231 TZ: Bias:0300
    Downloading policy from http://XXXX.XXXX.com.
    Initializing HTTP transport.
       Setting URL = http://XXXX.XXXX.com.
       Setting Ports = 80,443.
       Setting CRL = false.
       Setting Server Certificates.
    Set authenticator in transport
       Setting Media Certificate.
    Preparing Client Identity Request.
        Setting transport.
        Setting SourceID = 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A.
        Setting site code = XXX.
    Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.
        Setting SMBIOS GUID = XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
        Adding MAC Address XX:XX:XX:XX:XX:XX.
    Executing Client Identity Request.
    Requesting client identity
    Setting message signatures.
    Setting the authenticator.
    CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80  CCM_POST /ccm_system/request
    Request was successful.
    ::DecompressBuffer(65536)
    Decompression (zlib) succeeded: original size 415, uncompressed size 2460.
    -120
    Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
    Client Identity:
    Netbios name:
    Client GUID = , Netbios name = , State = Known
    Using unknown machine GUID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
    GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=TRUE
    Hash computed from CSP: Microsoft Enhanced RSA and AES Cryptographic Provider, AlgID: 32772, HashSize: 20
    Computed HardwareID=2:4AC96CD5003991BC201B7AC01FBC88E592C3E2BE
    Hardware ID: 2:4AC96CD5003991BC201B7AC01FBC88E592C3E2BE
    Preparing the Client DDR Message
        Setting SourceID = 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A.
    Sending the Client DDR message.
    Sending Report
    <Report><ReportHeader><Identification><Machine><ClientInstalled>0</ClientInstalled><ClientType>1</ClientType><Unknown>1</Unknown><ClientID>GUID:26717327-194f-4cd6-90ba-309998c058f2</ClientID><ClientVersion>5.00.0000.0000</ClientVersion><NetBIOSName>Unknown</NetBIOSName><CodePage>437</CodePage><SystemDefaultLCID>1033</SystemDefaultLCID></Machine></Identification><ReportDetails><ReportContent>Inventory
    Data</ReportContent><ReportType>Full</ReportType><Date>20140716141539.000000+000</Date><Version>1.0</Version><Format>1.1</Format></ReportDetails><InventoryAction ActionType="Predefined"><InventoryActionID>{00000000-0000-0000-0000-000000000003}</InventoryActionID><Description>Discovery</Description><InventoryAc
    Setting message signatures.
    Setting the authenticator.
    CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80  CCM_POST /ccm_system/request
    Request was successful.
    Submitted new client identity: GUID:26717327-194f-4cd6-90ba-309998c058f2
    Preparing Policy Assignment Request.
        Setting transport.
        Setting site code = XXX.
        Setting client ID = 74f16942-dd75-437f-8c4b-2a5de4d0e5e5.
       Setting site signing Certificate.
    Setting SiteSigningCertificateContext
    Executing Policy Assignment Request.
    Sending RequestAssignments
    Setting message signatures.
    Setting the authenticator.
    CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80  CCM_POST /ccm_system/request
    Request was successful.
    ::DecompressBuffer(65536)
    Decompression (zlib) succeeded: original size 274, uncompressed size 662.
    Request client ID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
    Response client ID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
    Retrieving Policy Assignments:
    Successfully read 0 policy assignments.
    Retrieving collection variable policy.
    Found 0 collection variables.
    Retrieving machine variable policy.
    Found 0 machine variables.
    Setting collection variables in the task sequencing environment.
    Setting machine variables in the task sequencing environment.
    Exiting TSMediaWizardControl::GetPolicy.
    WelcomePage::OnWizardNext()
    Loading Media Variables from "C:\sms\data\variables.dat"
    no password for vars file
    No assigned task sequence.
    Setting wizard error: There are no task sequences available for this computer.
    Skipping Confirmation Page.
    Skipping Task Sequence Selection Page.
    Skipping Variables Selection Page.
    Skipping Resolve Progress Page.
    Activating Finish Page.
    Loading bitmap
    Executing command line: X:\windows\system32\cmd.exe /k
    The command completed successfully.
    Successfully launched command shell.

  • Upgrading & moving LR to new computer

    Hello! I would love some help.
    I have a question with a few question in it!
    I have been using LR3 for 2 years and have one catalogue that has been on the same computer the whole time.
    I just bought a new mac and want to do 3 things:
    1. Get LR on to my new computer (yes I still have the cd and #)
    2. Upgrade to the newest LR (5 I think)
    3. Get my catalogue that I have been using for 2 years on to the new computer  and have it work with LR 5
    I want all these things to work together, I am hoping that I will be able to upgrade to LR5 and still be able to use my old catalogue.
    So my question is what should I do first? Get LR on new computer, then upgrade, then transfer catalogue and will it all work like that.
    I would love any and all help!  -- thank you - Alibaba

    Separate the two tasks.
    Upgrade on the same computer, once you are sure everything is working, then move everything to the new computer; OR
    Move eveything to the new computer in LR3, once you are sure everything is working, upgrade to LR5.
    It probably doesn't matter which order you this.
    Instructions on moving to a new computer
    http://www.lightroomqueen.com/2009/02/28/how-do-i-move-lightroom-to-a-new-computer/
    Also, throughout this entire process, do not use this as an opportunity to rearrange files and folders for any reason, do not try to "clean up" your folders or make the more logical. Move them to a new computer yes, but other than that, no rearranging or moving files or folders from here to there.

  • Task Sequence failed to restore captured data from USB drive onto a new machine using UDI task requence

    Hi,
    Environment ConfigMgr 2012 R2
    Replace Scenario: Capture data to a USB external drive and Restore it from USB external drive.
    Steps taken:
    1) Created Computer Association with New computer and Source computer
    2) Deployed UDI replace Task Sequence to Source computer and captured data to a USB external drive
    3) Run UDI Task Sequence from Boot Media to Restore data from USB External drive which had the captured data.
    Issue:
    My task sequence failed to restore data from USB external drive.
    Is there a fix
    Any help is greatly appreciated it. 

    I created a query to see the deployment logs in real time. I see the TS fails when running "Request State Store" task. Here are the logs.
    Severity Type Site code Date / Time System Component Message ID Description
    Error Milestone POK 7/22/2014 4:13:15 PM MININT-P6E4T6G Task Sequence Engine 11141 The task sequence execution engine failed execution of a task sequence. The operating system reported error 1: Incorrect function.
    Error Milestone POK 7/22/2014 4:13:15 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Error in the task sequence) in the group (Gather Logs and StateStore on Failure)
    with the error code 1  Action output: [ smsswd.exe ] PackageID = '' BaseVar = '', ContinueOnError='' ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' SwdAction = '0001' Set command line: Run command line Working dir 'not
    set' Executing command line: Run command line Process completed with exit code 1 Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved.  Microsoft Deployment Toolkit version: 6.2.5019.0 The task sequencer
    log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTI deployment failed, Return Code = 1 Command line returned 1. The operating system reported error 1: Incorrect function.
    Information Milestone POK 7/22/2014 4:13:14 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Copy Logs) in the group (Gather Logs and StateStore on Failure)
    with exit code 0  Action output: ... 扴捡杫潲湵⹤潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就瑺獩瑥慢正牧畯摮氮杯潃祰湩⁧㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯穜楴慴潴⹯潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散�潌獧䍜剏ⵐ䠳䑗塐就潃祰湩⁧㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯作䑓敓畴坰穩牡⹤潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就协卄瑥灵楗慺摲氮杯潃祰湩⁧㩃坜义佄南停湡桴�潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就慐瑮敨屲湕瑡整摮䍇潃祰湩⁧潬⁧㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯䉜䑄氮杯挠湯整瑮⁳潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌�Console
    > Successfully resized the shadow copy storage association Return code from command = 0 Cleaning up default wallpaper registry keys Process completed with exit code 0 zticopylogs processing completed successfully. Command line returned 0.
    Information Milestone POK 7/22/2014 4:13:07 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Move State Store) in the group (Gather Logs and StateStore on Failure)
    with exit code 0  Action output: [ smsswd.exe ] PackageID = '' BaseVar = '', ContinueOnError='' ProgramName = 'cscript.exe "C:\_SMSTaskSequence\WDPackage\scripts\ztimovestatestore.wsf"' SwdAction = '0001' Command line for extension .exe is "%1" %* Set
    command line: Run command lineWorking dir 'not set' Executing command line: Run command line Process completed with exit code 0 Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved.  Microsoft Deployment
    Toolkit version: 6.2.5019.0 The task sequencer log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ztimovestatestore processing completed successfully. Command line returned 0.
    Information Milestone POK 7/22/2014 4:13:07 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Gather) in the group (Gather Logs and StateStore on Failure) with
    exit code 0  Action output: ... (BIOS is 'DELL   - 1072009'). Property IsVM is now = False Finished getting virtualization info Connection succeeded to MicrosoftVolumeEncryption There are no encrypted drives Property IsBDE is now = False Processing
    the  phase. Determining theINI file to use. Using COMMAND LINE ARG: Ini file = CustomSettings.ini Finished determining the INI file to use. Added new custom property MYCUSTOMPROPERTY Using from [Settings]: Rule Priority = DEFAULT ------ Processing the
    [DEFAULT] section ------Process completed with exit code 0 ------ Done processing CustomSettings.ini ------ Remapping variables. Property TaskSequenceID is now =  Property DeploymentType is now = NEWCOMPUTER Finished remapping variables. ZTIGather processing
    completed successfully. Command line returned 0 ReleaseSource() for C:\_SMSTaskSequence\Packages\POK0000F. reference count 1 for the source C:\_SMSTaskSequence\Packages\POK0000F before releasing Released the resolved source C:\_SMSTaskSequence\Packages\POK0000F.
    Information Milestone POK 7/22/2014 4:13:03 PM MININT-P6E4T6G Task Sequence Engine 11130 The task sequence execution engine skipped the action (Use Toolkit Package) in the group (Gather Logs and StateStore on Failure) because
    the condition was evaluated to be false.
    Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Set Error Code) in the group (Gather Logs and StateStore on Failure)
    with exit code 0  Action output: Finished with error code 0.
    Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11124 The task sequence execution engine started the group (Gather Logs and StateStore on Failure).
    Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11122 The task sequence execution engine skipped the group (Cancelled Wizard Group) because the condition was evaluated to be false.
    Error Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Connect to State Store) in the group (State Restore) with the error code 1 
    Action output: ... ( 0x80070035 ) , trying to connect without username.  The network path was not found.  Unable to connect to
    \\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f.  Sleeping for 15 seconds. Unable to connect to share: The network path was notfound. ( 0x80070035 ) , trying to
    connect without username.  The network path was not found.  Unable to connect to
    \\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f.  Sleeping for 20 seconds. Unable to connect to share: The network path wasnot found. ( 0x80070035 ) , trying to
    connect without username.  The network path was not found.  Unable to connect to
    \\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f.  Sleeping for 25 seconds. Process completed with exit code 1 ERROR - Unable to map a network drive to
    \\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f. Unable to connect to 563807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f ZTI ERROR - Non-zero return code by ZTIConnect,
    rc = 1 Command line returned 1. The operating system reported error 1: Incorrect function.
    Warning Milestone POK 7/22/2014 4:11:46 PM MININT-P6E4T6G Task Sequence Engine 11138 The task sequence execution engine ignored execution failure of the action (Request State Store) in the group (State Restore).
    Error Milestone POK 7/22/2014 4:11:46 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Request State Store) in the group (State Restore) with the error code 16389 
    Action output: ... etting Media Certificate. Sending request to MP
    http://abcdefg.xyx.xyz.local. Setting message signatures. Setting the authenticator. CLibSMSMessageWinHttpTransport::Send: URL: abcdefg.xyx.xyz.local:80  CCM_POST /ccm_system/requestRequest was successful. migInfoRequestMessage.DoRequest (m_sResponse,true),
    HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1098) pClientRequestToMP->DoRequest(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2778) ExecuteRestoreRequestToMP(migInfoFromMP),
    HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2903) ExecuteRestoreRequest(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\main.cpp,84) OSDSMPClient finished: 0x00004005 reply from server
    is 'NoReply' ClientRequestToMP::DoRequest failed (0x80004005). ExecuteRestoreRequestToMP failed (0x80004005). ExecuteRestoreRequest failed (0x80004005).. The operating system reported error 1: Incorrect function.

  • OSD don't continue after reboot(restart computer task sequence)

    I create a restart computer task sequence(reboot into"currently installed default operating system") after install some softwares
    but I found the OSD will stop after reboot. why it will stop? how to fix it?
    the The following is log files.
    smsts-20140530-095634
    Successfully completed the action (Patch IE9_Patches_1405) with the exit win32 code 0 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    MP server http://PRI1.ABC.COM. Ports 80,443. CRL=false. TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Setting authenticator TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set authenticator in transport TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Sending StatusMessage TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Setting message signatures. TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Setting the authenticator. TSManager 2014/5/30 9:56:34 1808 (0x0710)
    CLibSMSMessageWinHttpTransport::Send: URL: PRI1.ABC.COM:80 CCM_POST /ccm_system/request TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Request was successful. TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Clear local default environment TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Updated security on object C:\_SMSTaskSequence. TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a global environment variable _SMSTSNextInstructionPointer=44 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=44 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a global environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a TS execution environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Save the current environment block TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Successfully save execution state and environment to local hard disk TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Start executing an instruction. Instruction name: Reboot. Instruction pointer: 44 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a global environment variable _SMSTSCurrentActionName=Reboot TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a global environment variable _SMSTSNextInstructionPointer=44 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a local default variable SMSRebootMessage TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a local default variable SMSRebootTimeout TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a global environment variable _SMSTSLogPath=C:\WINDOWS\CCM\Logs\SMSTSLog TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Expand a string: smsboot.exe /target:HD TSManager 2014/5/30 9:56:34 1808 (0x0710)
    smsts
    Expand a string: TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Command line for extension .exe is "%1" %* TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set command line: smsboot.exe /target:HD TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Start executing the command line: smsboot.exe /target:HD TSManager 2014/5/30 9:56:34 1808 (0x0710)
    !--------------------------------------------------------------------------------------------! TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Expand a string: WinPEandFullOS TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Executing command line: smsboot.exe /target:HD TSManager 2014/5/30 9:56:34 1808 (0x0710)
    ========================= [ smsboot.exe ] ========================= Reboot 2014/5/30 9:56:34 2572 (0x0A0C)
    Command line: '"smsboot.exe" /target:HD' Reboot 2014/5/30 9:56:34 2572 (0x0A0C)
    SMSTSRebootDelay=3 Reboot 2014/5/30 9:56:34 2572 (0x0A0C)
    SMSTSRebootMessage=正在安装新的 Microsoft Windows 操作系统。必须重新启动计算机才能继续。 Reboot 2014/5/30 9:56:34 2572 (0x0A0C)
    SMSTSRebootRequested=HD Reboot 2014/5/30 9:56:34 2572 (0x0A0C)
    Process completed with exit code 0 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    !--------------------------------------------------------------------------------------------! TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Successfully completed the action (Reboot) with the exit win32 code 0 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    MP server http://PRI1.ABC.COM. Ports 80,443. CRL=false. TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Setting authenticator TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set authenticator in transport TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Sending StatusMessage TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Setting message signatures. TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Setting the authenticator. TSManager 2014/5/30 9:56:34 1808 (0x0710)
    CLibSMSMessageWinHttpTransport::Send: URL: PRI1.ABC.COM:80 CCM_POST /ccm_system/request TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Request was successful. TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Clear local default environment TSManager 2014/5/30 9:56:34 1808 (0x0710)
    Updated security on object C:\_SMSTaskSequence. TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Set a global environment variable _SMSTSNextInstructionPointer=45 TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=45 TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Set a global environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Set a TS execution environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Save the current environment block TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Successfully save execution state and environment to local hard disk TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Reboot to local harddisk TSManager 2014/5/30 9:56:35 1808 (0x0710)
    _OSDGinaIsConfigured variable set to TRUE TSManager 2014/5/30 9:56:35 1808 (0x0710)
    _SMSTSServiceStartType variable set to TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Command line for extension .exe is "%1" %* TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Set command line: "bcdedit.exe" TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Executing command line: "bcdedit.exe" TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Process completed with exit code 0 TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Calling RebootSystem() TSManager 2014/5/30 9:56:35 1808 (0x0710)
    OSD type of task sequence. ignore the service window setting TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Path variable OSDrive converted from C: to CE0B39280000100000000000: TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Updated security on object C:\_SMSTaskSequence. TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Set a global environment variable _SMSTSNextInstructionPointer=45 TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=45 TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Set a global environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Set a TS execution environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Save the current environment block TSManager 2014/5/30 9:56:35 1808 (0x0710)
    Expand a string: %_SMSTSMDataPath%\Logs TSManager 2014/5/30 9:56:35 1808 (0x0710)
    ==============================[ OSDSetupHook.exe ]============================== OSDSetupHook 2014/5/30 9:57:59 908 (0x038C)
    Executing task sequence OSDSetupHook 2014/5/30 9:57:59 908 (0x038C)
    Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". OSDSetupHook 2014/5/30 9:57:59 908 (0x038C)
    Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} OSDSetupHook 2014/5/30 9:57:59 908 (0x038C)
    Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} OSDSetupHook 2014/5/30 9:57:59 908 (0x038C)
    Debug shell is enabled OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
    Successfully enabled debug command shell support. OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
    Configuring local administrator account OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
    Re-assign all drive letters... OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
    The drive information which has no drive letter can not be found. No need to re-assign driver letters. OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
    Installing SMS client OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
    Client already installed. OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
    Moving logs to SMS client directory OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)

    Hi,
    I suspect the IE require reboot and TS cannot catch this. So the TS cannot resume its state.
    Also, see the KB below.
    http://support.microsoft.com/kb/2894518
    Juke Chou
    TechNet Community Support

  • SCCM 2012 R2 task sequence: Move a computer object to different OU

    Hi,
    We migrate from Windows XP to 7.
    During task sequence, we need to be sure the object is moved from one OU to another (XP to Vista OU/policies).
    What is the best way to do this?
    Could be wrong, but it seems that a default task sequence does not move the object although there is a step which explicitely says to put the computer object in a certain OU ("apply network settings").
    Please advise.
    J.
    Jan Hoedt

    Hi you can check this article:
    http://myitforum.com/cs2/blogs/maikkoster/archive/2010/04/08/moving-computers-in-active-directory-during-mdt-deployments-step-by-step.aspx
    Hope this helps.
    Note: This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights. Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and
    recognises useful contributions.

  • 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

Maybe you are looking for