Missing create MDT task sequence
I have been put in charge of the imaging/task sequence creating of SCCM for my company. I had the sysadmin here set up the MDT integration with SCCM but i still don't see a "Create MDT Task Sequence" in the sccm console. If he logs into the server
he can see it, but if him or i do it through the admin console there is nothing.
thanks
You need to install MDT locally on the same system as the console you are using and then integrate MDT with your console as these options are local console extensions. Make sure you run the integrate task elevated also.
Jason | http://blog.configmgrftw.com | @jasonsandys
Similar Messages
-
2 questions - missing boot image, create mdt task sequence button missing
I'm learning SCCM 2012. I am watching a training video and the instructor shows a "Create MDT Task Sequence" button at the top of his ribbon bar when going into Task Sequence. I do not have this button - where did it go? I am
using 2012 SP1.
All I see is "Create Task Sequence" and "Create Task Sequence Media" but not "Create MDT Task Sequence".
Also - I only have an x86 boot image, and no x64. How do I get this into my inventory?
Thank you
Nathan"Create MDT Task Sequence" will be visible after you install MDT and integrate it to SCCM.
MDT is different product and not part of default SCCM installation.
You can integrate MDT to SCCM to create advanced Task Sequence if the default is not suitable for your needs.
Integrate MDT to SCCM.
MDT latest version is 2013:
http://www.microsoft.com/en-us/download/details.aspx?id=40796
For creating x64 boot image:
http://social.technet.microsoft.com/Forums/en-US/a3877a66-d35c-49ca-95c5-1c02d1611f2f/default-x64-boot-image-not-created-during-sccm-2012-setup
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks. -
MDT Task Sequence with standard "Create Task Sequence Media" image capture?
Hello,
After much research and a lot of exhausted attempts/hours between two of us we have broken down and decided to ask a very direct question. Is it possible to run an MDT Task Sequence with an image captured within SCCM and not MDT?
Reason for asking is the sequence fails every time with the error:
“Task Sequence: NAME has failed with the error code (0x80070490).”
I should note that there is no smsts log because it fails during the install and comes back with "no OS available" and there is no sccm client on the machine either. From what I could gather the error code is related to the HDD and I have tried
every setting within the task sequence I know of in different combinations to no avail. Which led us to wondering if maybe the whole process isn't even possible since we are using an MDT task sequence with an sccm image capture.
The standard task sequences work fine with the sccm image capture, but as soon as we try to the MDT sequence it fails. ANy advice/information/help on this is much appreciated.I can't thank you enough, that was exactly it. I should have known that it would be something so simple, I've been going crazy looking through the task sequence properties trying to figure out what I could be missing.
No problem at all, happy to help! I was in the same boat driving myself crazy looking at the task sequence properties. I just happened to stumble upon that setting and decided to give it a shot since I had exhausted seemingly every other avenue.
Also, to answer your other question, in a standard task sequence, you can name the computer by using the collection variable "OSDComputerName". Just right click the collection you have your task sequence deployed to, choose properties, and then the collection
variables tab. Click the starburst, enter the variable name OSDComputerName, uncheck the box for "do not display" (I think that's the setting) and apply your changes. When you run your task sequence again, you'll choose your TS from the list, click next, double
click OSDComputerName (just clicking next will skip it and begin the TS), enter the computer name, click OK, and kick off your TS.
I'm still finding my way around SCCM since it was thrown into my lap with no prior experience so I'm happy to help when someone is stuck. I've been there more times than I can count and others have helped me. -
How to install Office 365 Pro Plus Ms office 2013 Offline through MDT Task Sequence
Hi
How can i deploy the Office 365 pro Plus Ms Office 2013 (that come with Office 365 E3 License) offline to Client Machines through MDT Task Sequence?
Shailendra DevThere is a wealth of information on Office 365 deployments at:
http://technet.microsoft.com/en-us/library/gg715562(v=office.15).aspx
Overview:
Download the office deployment tool
configure your config.xml file
download the bits locally to your server.
create a package for MDT.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com -
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,
FPThanks 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 -
How to exceute some commands to Laptops only through MDT Task sequence
Hi
I just created one commands below in batch file for Add wifi profile , and I add a Command line Step in Task sequence
that batch file run successfully but I need to execute such batch file only on laptops. please guide how can I do this -- I need to change batch file or I need to set some logic in Command line steps in MDT Task sequence.
command in my batch file
netsh wlan add profile filename="sockmonkey.xml" user=all
ScreenShot of my TShi
Thanksfor your quick reply , I will check and let you know..
I am getting error code 1618 while deploying multiple Application (.exe and .msi both) through MDT Task Sequence, can you please provide me a sample script to install below Applications through MDT TS.
Intel IPPRODIFX-- iProDifX.exe
Intel Pro Wireless 16.7 --- msiexec /i "WiFi.msi" /qb /norestart ADDLOCAL=all REMOVE=WIFI_Admin_Toolkit,WIFI_PROSet,WIFI_MWT_Software
Juniper junos 3.1 -- Junos64.exe /q
Lenovo HotKey -- SETUP.EXE /s
CCM :- ccmsetup.exe
MBAM client 2.0 --- msiexec /q /i MBAMClient.msi
Shailendra Dev -
Hi,
Please see titlte. When I try to apply an CM captured WIM via an MDT task sequence, it starts, applies but stops after 15 minutes.
Logfile says it "cannot find the file specified".
Full error: "Installation of image 3 in package mypackage failed to complete. . The system cannot find the file specified. (Error: 80070002, Source: Windows).
Though the image IS there, redistributed it (if it wouldn't be there the task sequence would not start).
Please advise.
J
Update: could it be the fact I'm using an old (SCCM 2012) MDT wim? If I need to recreate the WIM boot image, where do I get the SCCM 2012 R2 boot wims?
Jan HoedtSee how to manually re-create your boot images
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson -
Hyper-v Virtual machine creation as part of MDT task sequence
Hello,
I have an existing MDT 2013 environment where I deploy Server 2008 R2 core with Hyper V role to HP Microservers.
The next step is to use hyper v manager and remotely configure the network and build VMs.
I would like to try and bring this together, and am sure I have seen similar powershell scripts online, but have not been able to find them despite an afternoon/evening of searching.
Ideally what I would like to happen is run a powershell script as part of MDT task to do the following.
1) create switch on hyper v host
2) build two VMs with fixed hard discs
3) VMs to automatically start and either PXE boot, which will connect to my existing automated MDT environment, or load the MDT iso image to initiate OS install.
Is anyone aware of existing scripts which can do this?
Or have any links which could help me achieve this?
Please note i am only using server 2008 r2 OS at present.
Many ThanksBasically this has a little to nothing to do with MDT.
It's more about having the powershell scripts to do it, here's a good start:
http://blogs.technet.com/b/heyscriptingguy/archive/2013/10/16/powertip-create-a-virtual-switch-in-hyper-v-with-windows-powershell.aspx
http://technet.microsoft.com/en-us/magazine/jj933287.aspx
Once you have the script's tested and working, you can try to incorporate them into your MDT task sequence. Just add an "Run PowerShell Script" and refer to the script as: %DeployRoot%\Applications\Name Of Script\createVM.ps1 or something like that.
Good luck!
If this post is helpful please click "Mark for answer", thanks! Kind regards -
Lenovo Power Manager Software - MDT Task Sequence
I'm working in an environment which does Operating System Deployment via SCCM 2007 SP2 R2 with MDT 2010 Update 1 Integration. I have an MDT Task Sequence that deploys my captured Windows 7 WIM file to predominantly Lenovo laptops (98% Lenovo fleet too). Part of this Task Sequence uses rules to specifically target drivers and applications to individual models. I'm am having GREAT difficulty in getting the Lenono Power Manager software (V3.31) to install as part of the Task Sequence.
The summary of the story is as follows:
Lenovo Bluetooth software is installing OK (msiexec /i Win32\BTW.msi /t 1033.mst /qb-)
Lenovo Hotkey software is installing OK (SETUP.EXE /S)
I've put logs for the Power Manager installation, and there are no errors i.e. it "seems" to install OK (SETUP.EXE /S)
I can advertise the Power Manager software POST image and it installs and works OK
Applications in the Task Sequence run in the order of Power Manager, Bluetooth, Hotkeys.
That hopefully provides the information for someone to maybe shed some light. It's a little frustrating given that the package actually will successfully install. I'm almost to the point where I want to try and create a collection with rules to populate it with Lenovo laptops and then mandatory install it. It's not a critical application - it would just be nice to have.
Solved!
Go to Solution.I did some more searching and found this method to do it - http://www.windows-noob.com/forums/index.php?/topic/1231-os-deployment-and-lenovo-computers/. I used the idea of creating a Task Sequence step to copy the files locally, followed by a step to install it from the local files. It worked fine for this. If anyone has a "cleaner" method though, let me know.
-
Is it possible to edit a MDT Task Sequence after starting a deployment, between Hyper-V snapshots?
Using a Hyper-V VM, I take snapshots of my base image build between major sections (automatic updates, application installation, scripts and extras, etc.) with the intention of being able to go back to that area and look at it for troubleshooting's sake.
Each of these snapshots is manually taken during a pause in my MDT task sequence (using LTISuspend). I would like to be able to roll back to these snaphots make edits to the task sequence (obviously to sections that haven't yet run), then resume and
see the changes implemented - but I don't know where the task sequence file(s) resides on VM being imaged, or if that can be changed after kicking it off at the very start of the build.
Is it possible to replace the task sequence file (and any other necessary files) that are cached locally on the VM during the imaging process? Where are those files located? Or any other way to implement changes to my task sequence so I wouldn't
have to start the image build completely from scratch?
This build takes about 6 hours. Having to make even the slightest modification causes me to lose an entire day, so this would be golden even if I have to manually edit certain files!Hi,
Based on my known, you cannot edit the task sequence after starting the deployment.
However, I suggest you ask this issue in MDT forum for more professional solution:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn
from your interaction with us. Thank you for your understanding.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Hi ,
Am getting Error code 1603 (fatal error during installation) while deploying the SEP through MDT task sequence . am not getting such issue regularly but some time am getting and need to be fixed.
Shailendra
Shailendra DevHi,
I am Chetan Savade from Symantec Technical Support Team.
Logs can provide more detail info, as said earlier by MrBrooks provide SEP_Inst.log from the affected machine.
Adding Windows defender related articles if they can help you:
Keeping Windows Defender Enabled when Deploying and Installing Symantec Endpoint Protection Client package.
http://www.symantec.com/docs/TECH168501
Windows Defender startup type registry value is Manual instead of Disabled after installing Symantec Endpoint Protection
http://www.symantec.com/docs/TECH206793
How to prepare a Symantec Endpoint Protection 12.1.x client for cloning
http://www.symantec.com/docs/HOWTO54706
Best Regards,
Chetan -
Hi,
When I try to import the MDT boot image X86, I get the following error:
Started processing.
Creating boot image.
Copying WIM file.
Mounting WIM file.
WIM file mounted.
Setting Windows PE system root.
Set Windows PE system root.
Set Windows PE scratch space.
Adding standard components.
Adding component: winpe-mdac
Adding extra content from: C:\Users\ADMINI~1.afO\AppData\Local\Temp\3\sfup2yp2.0rt
Unmounting WIM.
Copying WIM to the package source directory.
Creating boot image package.
Error while importing Microsoft Deployment Toolkit Task Sequence.
Failed to insert OSD binaries into the WIM file
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.Put(PutOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
--- End of inner exception stack trace ---
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
Note: previous x86 image was deleted some time ago.
Please advise.
J.
Jan HoedtThis is the error in smsprov.log
*********** WBEM Missing property TransformAnalysisDate SMS Provider 16/04/2014 15:11:00 7856 (0x1EB0)
************ WBEM Missing property TransformReadiness SMS Provider 16/04/2014 15:11:00 7856 (0x1EB0)
Image language ID 1033 and en-US SMS Provider 16/04/2014 15:11:00 7856 (0x1EB0)
Image language ID 1033 and en-US SMS Provider 16/04/2014 15:11:10 7856 (0x1EB0)
Image language ID 1033 and en-US SMS Provider 16/04/2014 15:11:19 7856 (0x1EB0)
ERROR> Error -1073741502 returned to execute the command line: "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\windows\TEMP\BootImages\{8AEF81AB-4B11-4AEF-96D3-E90D84D3DA94}\mount" /Add-Package
/PackagePath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-Scripting.cab" SMS Provider 16/04/2014 15:11:19 7856 (0x1EB0)
Failed to install required components into the boot image C:\windows\TEMP\BootImages\{8AEF81AB-4B11-4AEF-96D3-E90D84D3DA94}\mount SMS Provider 16/04/2014 15:11:19 7856 (0x1EB0)
*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3766) : Failed to insert OSD binaries into the WIM file~*~* SMS Provider 16/04/2014 15:11:36 7856 (0x1EB0)
*~*~Failed to insert OSD binaries into the WIM file ~*~* SMS Provider 16/04/2014 15:11:36 7856 (0x1EB0)
Auditing: User FAC\administrator called an audited method of an instance of class SMS_BootImagePackage. SMS Provider 16/04/2014 15:11:36 7856 (0x1EB0)
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=9281008 SMS Provider 16/04/2014 15:11:36 7856 (0x1EB0)
Jan Hoedt -
Hello All,
What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File with Windows, D:\ Data drive with BCDBoot).
MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
TechNet VHD Native Boot on Windows 8.1:
http://technet.microsoft.com/en-us/library/hh825689.aspx
http://technet.microsoft.com/en-us/library/hh825691.aspx
The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
which works for US before we upgrade to Windows 10 with utilizing MDT.
I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
I reported getting the diskpart script working first here:
https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
Here it is:
rem work around any USB disk left in or any CDROM detected by PE as drive D
select volume D
assign letter=F noerr
rem select the formatted volume and reassign it's drive letter
select volume C
assign letter=D
rem create and setup VHD file
create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
select vdisk file=D:\DEV_WIN81.VHD
attach vdisk
create partition primary
active
format FS=NTFS quick label="Developer Win81 VHD"
assign letter=C
rescan
exit
(type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
The Task Sequence looks like this:
I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
Question:
Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
get any issues.
I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
<![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
<![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
<![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
<![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
<![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
<![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
<![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
<![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
<![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
<![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
<![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
<![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
<![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
<![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
<![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
<![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
<![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
<![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
<![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
<![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
<![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
<![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
<![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
<![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
<![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
<![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
<![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
<![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
<![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
- and fail with an error if you have added a VHD Native Boot volume.
This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
fact what was the C:\ after Format HDD step is now the D:\ .
A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast. -
SCCM OSD using MDT task sequence
Hi all,
Is it right if I capture an image from a Windows 7 machine using SCCM capture media, then deploy it to an existing Windows XP(for migration) using "Create a new
Microsoft Deployment task sequence" wizard (this option appears after integrating MDT with SCCM)? I have this scenario but the targeted machine is not getting joined to domain, I suspect the issue is with sysprep as image that we get using sccm capture
media does not sysprep the reference machine.
What do you think?I checked the logs and I believe the issue is with sysprep, I found the below in the netsetup.log:
12/15/2014 20:18:54:823 NetpChangeMachineName: from 'OSD-PC' to 'OSD-PC' using 'ssc.gov.jo\majmajali' [0x1000]
12/15/2014 20:18:54:823 NetpDsGetDcName: trying to find DC in domain 'SSC', flags: 0x1010
12/15/2014 20:18:54:823 NetpDsGetDcName: found DC '\\DC5' in the specified domain
12/15/2014 20:18:54:823 NetpGetLsaPrimaryDomain: status: 0x0
12/15/2014 20:18:54:823 NetpGetDnsHostName: Read NV Domain: ssc.gov.jo
12/15/2014 20:18:54:838 NetpGetComputerObjectDn: Cracking account name SSC\OSD-PC$ on
\\DC5
12/15/2014 20:18:54:838 NetpGetComputerObjectDn: Crack results: (Account already exists) DN = CN=OSD-PC,CN=Computers,DC=ssc,DC=gov,DC=jo
12/15/2014 20:18:54:838 NetpModifyComputerObjectInDs: Initial attribute values:
12/15/2014 20:18:54:838 DnsHostName = OSD-PC.ssc.gov.jo
12/15/2014 20:18:54:838 ServicePrincipalName = HOST/OSD-PC.ssc.gov.jo RestrictedKrbHost/OSD-PC.ssc.gov.jo HOST/OSD-PC RestrictedKrbHost/OSD-PC
12/15/2014 20:18:54:838 NetpModifyComputerObjectInDs: Computer Object already exists in OU:
12/15/2014 20:18:54:838 DnsHostName = OSD-PC.ssc.gov.jo
12/15/2014 20:18:54:838 ServicePrincipalName = TERMSRV/OSD-PC.ssc.gov.jo RestrictedKrbHost/OSD-PC.ssc.gov.jo HOST/OSD-PC.ssc.gov.jo TERMSRV/OSD-PC RestrictedKrbHost/OSD-PC HOST/OSD-PC
12/15/2014 20:18:54:838 NetpModifyComputerObjectInDs: There are _NO_ modifications to do
12/15/2014 20:18:54:838 ldap_unbind status: 0x0
12/15/2014 20:18:54:838 NetpChangeMachineName: status of setting DnsHostName and SPN: 0x0
The windows XP machine name to be migrated is OSD-Test, but the task sequence is making computer name the same as the reference (OSD-PC) despite task sequence is already configured to migrate that XP machine network and windows configuration (including
hostname).
I believe you are right, I should create build and capture task sequence in MDT, and in the reference machine I run the below command to capture an image:
cscript “\\MDT server\Deploymentshar1$\scripts\litetouch.vbs. After this capture is done the machine will get into oobe (if all is ok). What do you
think? -
SCCM 2012 SP1 MDT task sequence fails on reboot does not retain ip
we are having a sccm 2012 sp1 server that used for installation of win 8.1 Enterprise , the task sequence works perfectly fine but when we run the same task on HP Elite 8300 system having Intel 82579LM Adapter from Windows XP , after the reboot the
task fails as no ip address is assigned the NIC , We did download the WInPE Adapter drivers from HP site and injecting to the x86 Boot Image (6.2.9200) however the task still fails ,
Our environment uses all static ip address , the same task as mentioned earlier has worked fine with Different brands of HP elite 8200/8100 , infact the elite 8200 also uses the same NIC card
Find below the smsts.log file
Main error in the log file is
No physical network adapters found OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
Found network adapter "Intel(R) 82579LM Gigabit Network Connection" with IP Address 169.254.181.151. TSMBootstrap 2/12/2014 1:05:41 PM 1984 (0x07C0)
Xtract from LOG
SMSTSRebootDelay=60 Reboot 2/12/2014 1:01:56 AM 3496 (0x0DA8)
SMSTSRebootMessage=A new Microsoft Windows operating system is being installed. The computer must restart to continue. Reboot 2/12/2014 1:01:56 AM 3496 (0x0DA8)
SMSTSRebootRequested=WinPE Reboot 2/12/2014 1:01:56 AM 3496 (0x0DA8)
Process completed with exit code 0 TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
!--------------------------------------------------------------------------------------------! TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
Successfully completed the action (Restart to Windows PE) with the exit win32 code 0 TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
Set authenticator in transport TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Clear local default environment TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Updated security on object E:\_SMSTaskSequence. TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Save the current environment block TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Executing command line: "bcdedit.exe" TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
CreateProcess failed. Code(0x80070002) TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Command line execution failed (80070002) TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Staging boot image UNB0003A TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
ResolveSource flags: 0x00000000 TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
SMSTSPersistContent: . The content for package UNB0003A will be persisted TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
Set authenticator in transport TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
WinHttp credentials set TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
List of files to be downloaded TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
Downloaded file from http://unb-ho-sccmdb.exch1.mas.unb.com:80/SMS_DP_SMSPKG$/UNB0003A/sccm?/WinPE.UNB0003A.wim to E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim TSManager 2/12/2014 1:02:22 AM 1876
(0x0754)
VerifyContentHash: Hash algorithm is 32780 TSManager 2/12/2014 1:02:22 AM 1876 (0x0754)
Found boot image E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim TSManager 2/12/2014 1:02:25 AM 1876 (0x0754)
Copying boot image locally... TSManager 2/12/2014 1:02:25 AM 1876 (0x0754)
Failed to find ADK installation root registry key TSManager 2/12/2014 1:02:32 AM 1876 (0x0754)
Opening image file E:\_SMSTaskSequence\WinPE\sources\boot.wim TSManager 2/12/2014 1:02:32 AM 1876 (0x0754)
Applying image 1 to volume E:\_SMSTaskSequence\WinPE TSManager 2/12/2014 1:02:32 AM 1876 (0x0754)
Closing image file E:\_SMSTaskSequence\WinPE\sources\boot.wim TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
Capturing WinPE bootstrap settings TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
==============================[ OSDNetSettings.exe ]=========================== OSDNetSettings 2/12/2014 1:02:36 AM 2064 (0x0810)
Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} OSDNetSettings 2/12/2014 1:02:36 AM 2064 (0x0810)
No adapters found with non-empty DNSDomainSuffixSearchOrder OSDNetSettings 2/12/2014 1:02:36 AM 2064 (0x0810)
Adapter "ROOT\SYMC_TEEFER2MP\0000" not found OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
No physical network adapters found OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
OSDNetSettings finished: 0x00000000 OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
Process completed with exit code 0 TSManager 2/12/2014 1:02:38 AM 1876 (0x0754)
Installing boot image to hard drive TSManager 2/12/2014 1:02:38 AM 1876 (0x0754)
Backing up existing boot system before trying to set up new boot system TSManager 2/12/2014 1:02:38 AM 1876 (0x0754)
BootLoader::backup: C:\, E:\_SMSTaskSequence\backup TSManager 2/12/2014 1:02:39 AM 1876 (0x0754)
BootLoader::restore: E:\_SMSTaskSequence\WinPE, C:\ TSManager 2/12/2014 1:02:43 AM 1876 (0x0754)
Saving bcd store to E:\_SMSTaskSequence\WinPE\boot\BCD TSManager 2/12/2014 1:02:43 AM 1876 (0x0754)
Executing command line: "E:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager 2/12/2014 1:02:45 AM 1876 (0x0754)
Process completed with exit code 0 TSManager 2/12/2014 1:02:46 AM 1876 (0x0754)
Updated security on object E:\_SMSTaskSequence. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Save the current environment block TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object E:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object E:\_SMSTaskSequence. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Save the current environment block TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
<![LOG[LOGGING: Finalize process ID set to 780]LOG]!><time="01:04:01.537+480" date="02-12-2014" component="TSBootShell" context="" type="1" thread="784" file="tslogging.cpp:1495">
1/1/1601 12:00:00 AM 1995266923 (0x76ED5B6B)
==============================[ TSBootShell.exe ]============================== TSBootShell 2/12/2014 1:04:01 AM 784 (0x0310)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' TSBootShell 2/12/2014 1:04:01 AM 784 (0x0310)
Debug shell is enabled TSBootShell 2/12/2014 1:04:01 AM 784 (0x0310)
Waiting for PNP initialization... TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(3)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
WinPE boot path: E:\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Booted from fixed disk TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Found config path E:\_SMSTaskSequence TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go. TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Restoring boot system from E:\_SMSTaskSequence\backup TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Successfully loaded the BCD boot system TSBootShell 2/12/2014 1:04:05 AM 796 (0x031C)
Successfully loaded an exported NTLDR boot system TSBootShell 2/12/2014 1:04:05 AM 796 (0x031C)
BootLoader::restore: E:\_SMSTaskSequence\backup, C:\ TSBootShell 2/12/2014 1:04:05 AM 796 (0x031C)
Successfully merged logs from cache. TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430) TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Loading bootstrap settings from E:\_SMSTaskSequence\WinPE TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Loading saved WinPE settings TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00450037004500350042004200360039002D0036003100390038002D0034003500350035002D0042003500430041002D003600430034003600410032004200350045004200370038007D00' TSBootShell
2/12/2014 1:04:06 AM 796 (0x031C)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Configuring WinPE bootstrap settings TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Creating WinPE answer file TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Setting hive location to "X:\windows\system32" TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Getting namespace "Microsoft-Windows-Setup" for architecture "x86" TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Configuring global network settings TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Join type: TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
DNS domain: exch1.mas.unb.com TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
DNS domain search order: TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
IP filter sec enabled: false TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
No adapters found in environment. Performing global configuration only. TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Writing configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Successfully saved configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Executing command line: wpeinit.exe -winpe TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
The command completed successfully. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Starting DNS client service. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Finalizing network settings TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
No adapters found in environment. Performing global finalization only. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Finalizing global network settings TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
DNS domain: exch1.mas.unb.com TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
DNS domain search order: TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
DNS for WINS enabled: false TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
LMHosts file enabled: true TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Host lookup file: TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
WINS scope ID: TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
The command completed successfully. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL' TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Adding SMS bin folder "X:\sms\bin\i386" to the system environment PATH TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Failed to open PXE registry key. Not a PXE boot. TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Resuming Task Sequence in WinPE TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00' TSMBootstrap
2/12/2014 1:05:40 AM 1984 (0x07C0)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00' TSMBootstrap
2/12/2014 1:05:40 AM 1984 (0x07C0)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Loading the Task Sequencing Environment from "E:\_SMSTaskSequence\TSEnv.dat". TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Updating the local data path in the Task Sequencing Environment. TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogMaxSize to 1000000 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogMaxHistory to 1 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogLevel to 0 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogEnabled to 1 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogDebug to 1 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Command line for extension .exe is "%1" %* TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Set command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Executing command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
==========[ TsProgressUI started in process 2004 ]========== TsProgressUI 2/12/2014 1:05:41 AM 2008 (0x07D8)
Command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:W
In dire need of help,
I have already gone through the below articles on the NET
http://social.technet.microsoft.com/Forums/systemcenter/en-US/0fe5cded-51cf-487a-97e3-837fb3426a3e/install-software-updates-in-osd-reboots-leaves-clients-in-provisioning-mode?forum=configmgrosd
http://social.technet.microsoft.com/Forums/systemcenter/en-US/c590e486-d3ca-423f-8953-e596160f3567/updates-hang-during-osd-kb2509007-not-working-for-me?forum=configmgrosd
Awating response,
Hasan RezaWell Finally I sorted my issue ,
Just want to share the solution, may be it would be helpful to some one else and save some times
The problem was that the Xp images has lot of hidden NIC installed , this would not allow the system to work with the correct NIC card and Ip address (System -> View Hidden Devices) , what I did 2 things
1) Copied the OSD Script folder from the SCCM Server to the Client pc and ran that ztigather.wsf and captured the output , it was evident that it showed capturing multiple adapters , (There are some blogs that pointed out that OSD can capture only one nic
due to the only one Adapter0 section being defined in the ZTIgather.xml file,)
2) I open the registry at the xp pc navigated to HKLM-> System ->Current Control Set-> Services-> TCPIP -> Parameters-> Interfaces ->
Expect for the NIC card that had the Ip address assigned I deleted all other nic card's guid,
As then post running deleting the old scanstate (USMTUTIL /rd c:\statestore) , reran the task and VOILA..
All worked fine , below are the two post I followed , though notvery relevant but they were helpful and help me reached the conclusion.
Thanks,
Hasan Reza.
http://systemscenter.ru/mdt2012.en/ztigatherwsf.htm
http://social.technet.microsoft.com/Forums/windowsserver/en-US/8acb7cd1-7028-4ffe-86c9-eb43041cf8b3/how-do-i-get-rid-of-second-169254xx-ipv4-address-on-windows-server-2008-sp2-x86?forum=winservergen
Maybe you are looking for
-
XML File to SAP R/3 using SAP XI
Hello Everyone, I'm hoping someone has done this scenario and can provide a step by step example for me. The scenario I have is as follows: -- An XML file is placed manually on a UNIX SAP Server -- SAP XI should, once the file is placed on the serve
-
Assigning a default value to a user property
Hi everyone, do you know how can I assign a default value to a user property? It would be great if I should be able to assign it from the administration without writing any code (like profile web services...). Thank you! Alberto Marchiaro
-
Can I Install Photshop 10 on computer with no CD Rom?
Are you able to install Photoshop 10 progarm on computer with no CD Rom?
-
i have a macbook pro running 10.6 imac running 10.6 macpro running server 10.5.8 MBP logs into iMac no problem, iMac ARD and Sharing settings are identical to server, but server will not allow login without asking permission (so i know server see's i
-
Returning Non-Numeric character
Hi All, Im using Oracle 11gR2. Following is my sample data and i want to search the string having non-numeric characters in it. with t as select '123' val from dual union select ' 123' val from dual union select '1123' val from dual union select 'A12