Deployment of Slipstream Image

Hey Guys,
Trying to deploy an SOE image out that will intergrate certain ThinkVantage programs (Active Protection, Mobility Center etc)
I'm having some issues trying to rehide the Lenovo Recovery Partitions, both of them.
This SOE image will also intergrate other programs such as our Anti Virus solution, and Office 03.
I need a hand hiding the recovery partition like it should be.
A hand on that would be great
Cheers
PS.
Deployment will be taking place with Vista Business x32, on T500 MT: 8082 systems.
Message Edited by SgtDPilla on 11-02-2008 10:59 PM

Are you using Ghost or other imaging tool? Please specify.

Similar Messages

Deployed Windows 7 Image failing to start -SCCM 2012 SP1

Hello, I am deploying windows 7 image using SCCM 2012 SP1, the installation goes thru fine but when it is in the process of restart, a blue screen is displayed for a split second and then it tries to reboot again with same results. Are there any logs on
the SCCM server I can check to see where the problem may be?

This generally means inaccessible boot device. How are you partitioning the drive and applying the image?
This is one way to do it
http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part_18.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

How do you set up a deployment server to image a Macbook Air

I have 240 Macbook Airs to deploy. Having problems gettng them to netboot to the deployment server using the USB network adapter.
The server is 10.6.8. Does it need to be updated to Lion to work?

The new MacBook Airs should boot off a Snow Leopard server machine running Netboot for these machines. At least the 85+ machines I've imaged off my SL NetBoot box do, so that's not the issue. Are using Netboot or something else? What image/build of Lion is on the box that you're trying to boot these machines against? I agree with Captfred if you're trying to use some system restore image for the MacBook Airs, I wouldn't bother. I compiled a custom boot image that installs 10.7.2 already out of the box and all of the Airs fired up just fine.

Trouble booting to WDS server to deploy or capture image

Hello, we have an existing WDS server running Server 2008 R2 with SP1. I am having trouble getting a Surface Pro 3 to boot to the WDS (even after creating updated deploy and capture boot images). I can get the Surface to PXE boot, and I am
able to choose the Deploy or Capture boot image, but then I get the message that an error occurred obtaining an IP address from the DHCP server. During the PXE boot, the device does obtain an IP address in the correct range. I tried adding the
Surface ethernet adapter drivers to the boot wims but since they are not signed I get errors that they cannot be added. Any suggestions?

Added drivers to boot images using DISM with the /ForceUnsigned override.

Operating System on x64 can be deployed with boot image x86

Hi,
I want to know if there is any limitation to deploy Operating System and Wim image on x64 (64 bit) using a boot image x86 (32 bits)
Thanks

Hi,
That is what I'm trying to accomplish because during the years with SCCM 2007 we were available to deploy x64 OS
(windows 7, 8, 8.1) using x86 boot image without any problem. Since we migrated to SCCM 2012 R2 CU 2 we have experimenting different and
intermittent issues:
we are using x86 boot image to deploy x64 OS and
x64 drivers package. When the system reboot to start the setup, we get a black screen with a movable cursor (but nothing to click on!).
when I change the task sequence to use x64 boot image (note: using the same x64 OS and same drivers package) the process continue with success.
I'm searching any technical documentation from Microsoft to better understand this issue. What can be the reason why it work fine with x64 boot image and not with x86.

Taking and deploying lenovo e540 image

Hi- I am trying to make a viable image from a lenove E540 Thinkpad using zcm 11.3. When deploying an image made from the factory installation I get only the blinking cursor after rebooting the target machine. I have checked to be sure the bios is set to both uefi and mbr and other bios settings. The OS is configured for MBR not GPT. Secure Boot is disabled.
There is no problem when using an image from a thinkpad with windows 7 configured from a normal windows 7 disc.
I am assuming the problem has to do with the MBR and so am thinking I should save a backup of the MBR as described here on page 161 sec 3.11.3
https://www.novell.com/documentation...ot_imaging.pdf
Does this strategy makes sense or is there something more straightforward? I have read that lenovo uses a non-standard linux boot record and that in ghost special switches need to be used in order to preserve it correctly. Is there something similar in ZCM 11.3?
Andrew

Thank you for your advice. It was a motherboard problem, but it is changed so everything works fine now

Windows 8 deployment using Zenworks imaging services

Hi,
I would like to find some guidelines or best practices stuff in order to help me with the deployment of Windows 8.1
For our current method with Windows 7, we used SYSPREP with offline drivers for multiples machines in a local folder ex. C:\Drivers.
Now it seems that it won't work anymore with Windows 8, and when we ask for help in the Microsoft forums we are pushed to products like MDT,WDS and SCCM.
Does anyone here had a successful Windows 8 deployment ?
Thank you in advance for your input

Originally Posted by anto28
Yes i have
I asked this question a multiple forums but i have not received any satisfying answer yet...
Can you elaborate with the DPinst way ?
At what point do you use this command to inject drivers ? In the audit mode ?
I think DPInst require the hardware to be present in order to work, no ?
What if you want to install drivers for 7-10 different machine type in your image ?
Thank you Thomas.
Simply put, you call dpinst on first login after the image is deployed on the workstation by adding the following to sysprep unattend xml:
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>c:\drivers\dpinst.exe /path C:\drivers\pnp</CommandLine>
<Order>1</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
and dpinst xml should look something like this:
<?xml version="1.0" ?>
<dpinst>
<search>
<subDirectory>*</subDirectory>
</search>
<legacyMode/>
<quietInstall/>
<suppressWizard/>
<scanHardware/>
</dpinst>
You could add all the drivers to the base image or then use addon images for specific workstations models that places the workstation specific driver into: C:\drivers\pnp.
Thomas

SCCM 2012: PXE deploy: import boot images?

Hi,
We fully configured sccm 2012 and did osd via bootable media. Now we want to configure PXE.
We enabled it (http://prajwaldesai.com/deploying-sccm-2012-part-14-build-and-capture-windows-7-64-bit/).
My questions:
*Is that all that needs to be done?
*It seems to me we need to import boot images in WDS?
*If we do, which to import then (both x86 and x64 probably) + there is a winpe and a winpe.....wim made by sccm, which one to import then?
*on DHCP we change the boot server hostname but what about the bootfile name, what is the path of that? \boot\x64\wdsnbp.com?
Please advise.
J.
Jan Hoedt

I keep on getting TFTP open timeout
I find in smspxe.log that it reaches to the SCCM-server but then something goes wrong. Not sure what.
How can I troubleshoot find more info, please advise?
00:51:55:2A:5C:C5, 0A190A42-FFDe6-5e69-9e41-70e481B852E3: device is not in the database.   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
Getting boot action for unknown machine: item key: 2046820352   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.prod.ourcompany.be:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.prod.ourcompany.be:80 CCM_POST /ccm_system/request   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
Jan Hoedt
Note: what I also can see:
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 000.000.000.000

Deployment Failure - thick image - (5627) dism.exe (MDT 2012 Update 1)

I installed MDT 2012 Update 1 on a new server and was testing it out with our Windows 8 deployment. I captured a thick image which works fine when I boot to Win PE and apply it using dism.
I imported the image into the the deployment share (custom, no setup/sysprep) and created a Custom Task Sequence with just 3 tasks to do a custom format (command line using dism), apply the image (choose specific disk and partition), and restart the computer.
However, when I go through the task sequence, it comes up with some errors and appears that it gets sysprepped again because it prompts me to answer questions that weren't a part of my original sysprep (EULA, adding a new user, etc).
Any idea where I need to look to get this fixed? I've shared the BDD.log and LTIApply.log on my SkyDrive.
https://skydrive.live.com/?cid=0FB4C394CC7A79E1&id=FB4C394CC7A79E1%21105
Here's a snip of the results
<![CDATA[FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found
FAILURE ( 5627 ): 2: Run DISM.exe
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB; Source: Unknown)
Failed to run the action: Install Operating System. Execution has been aborted
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015FB; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]]>
Please advise.
Thanks in advance.

I installed MDT 2012 Update 1 on a new server and was testing it out with our Windows 8 deployment. I captured a thick image which works fine when I boot to Win PE and apply it using dism.
I imported the image into the the deployment share (custom, no setup/sysprep) and created a Custom Task Sequence with just 3 tasks to do a custom format (command line using dism), apply the image (choose specific disk and partition), and restart the computer.
However, when I go through the task sequence, it comes up with some errors and appears that it gets sysprepped again because it prompts me to answer questions that weren't a part of my original sysprep (EULA, adding a new user, etc).
Any idea where I need to look to get this fixed? I've shared the BDD.log and LTIApply.log on my SkyDrive.
https://skydrive.live.com/?cid=0FB4C394CC7A79E1&id=FB4C394CC7A79E1%21105
Here's a snip of the results
<![CDATA[FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found
FAILURE ( 5627 ): 2: Run DISM.exe
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB; Source: Unknown)
Failed to run the action: Install Operating System. Execution has been aborted
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015FB; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]]>
Please advise.
Thanks in advance.
Hi Mathew,
I have the similar error deploying a image (no sysprep) using the standard client task sequence. There are 2 partitions, one 500MB for boot and the other remaining partition is for OS. Do you have solutions to resolve the errors? Greatly appreciate
any advice given. Thanks.
Regards,
Eng Chai
Eng Chai

Deploying reader via Imaging

Hi, My company is currently seeking FAST accreditation, and I have been told that we cannot install Adobe reader on our base line PCs to create images for desktop deployment. I have gone through the Reader License and cannot see anything specific, although there are indications at 2.1 that one copy of the software cannot be shared, does this mean that one downloaded installer cannot be used in an image and deployed to all new desktop PC's and I will have to install reader manually every PC in the company??

>does this mean that one downloaded installer cannot be used in an image and deployed to all new desktop PC's and I will have to install reader manually every PC in the company??
No, it doesn't mean that. But you do have to follow the guidelines for Reader distribution http://www.adobe.com/products/acrobat/distribute.html

Windows Deployment Services - Capturing Image

To Microsoft Technet,
I am currently a student and I have setup a fully functioning Windows Server. This Windows Server has AD, DHCP, WDS and MDT installed on to it. This server was setup so that we can re-deploy Windows to any of our computer labs and it will just be a fresh
install. My problem is that the students also need to upload (capture) an image of the OS to the server every now and then as part of the coursework. When uploading an image they are presented with this option:
Obviously when you click connect it asks for a username and password so that it can write to the folder. The students are not allowed to know the username and password because if they do then they break the server. They do this because they log on and mess
around with it. I am currently asking if there is a solution so they can connect to the server and it will automatically log them on as the admin.
These are solutions however I feel they would be inappropiate:
- Give them a username that has read / write access but block the logon.
- Allow "Everyone" to read / write thus no logon screen.
However I feel that both are a security risk as students can just join the folder from the network and delete other students work.
Instead I would like the windows server to automatically allow the connection by implementing the logon details. Is there a possible way to do this?
Thanks,
Thomas.
The image is off the internet (I did not make it).

Hi thomasjcf21,
Another possible is you can create shared folders for each student and give each student account full control permission, after they finish the OOBE they can upload their
image to WDS server.
The related third party article:
Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part I
http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-using-windows-deployment-services-wds-step-by-step-part-i/
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to deploy my gif images

Hi All,
I have an application, which has an images in gif format. This gif images I use in the code for to different tree nodes. I declared in a constant the image path eg. "src/TreeModelIcons/" (The src folder where my source is located, I use Eclipse.)
How can I deploy my app, for use the deployed app correctly the images? Where I want to declare the images? In a JNLP resorce section I want to define them? In a jar file contain the TreeModelIcons folder with all image. What is a correct way? What can I do for my app use the images correctly? (If I run localy my app works perfectly.)
Thank you

We put our image files in the jar to preserve the directory structure... Works fine for us. Don't know if this is the "correct" way to do it, but...

Deploying a Captured Image

I would like to broadcast a image to all machines on the network even those with SCCM clients. I have some machines that are on the domain that need to be imaged from time to time and I also have some new machines that need to be imaged. I
also need to prompt the user that starts the image process to enter the computers name. I know the computer name can be prompted by using the unknown group and prompting for the OSD but how would I do this for a machine name that is already listed
in SCCM? Would the machine fall under the unknown category once the image process starts?

Here's couple of ways to do it:
http://www.windows-noob.com/forums/index.php?/topic/5542-how-can-i-easily-prompt-for-a-computer-name-in-configuration-manager-2012/
http://t3chn1ck.wordpress.com/2009/04/24/script-to-prompt-for-system-name-in-sccm-osd/

Deploying Icons and Images Used by Forms6i

I'm looking for a solution that uses jar files for Icons; which will be easy for deployment
http://docs.oracle.com/cd/B14099_19/web.1012/b14032/configure009.htm I'm looking for the same for forms6i

Hi,
>
I'm looking for a solution that uses jar files for Icons; which will be easy for deployment
http://docs.oracle.com/cd/B14099_19/web.1012/b14032/configure009.htm I'm looking for the same for forms6i
>
jar implies java.
Forms 6i implies NO java.
Cheers,

SCCM's OSD (not MDT): Task sequence can be tweaked into imaging Windows+VHD Native Boot, but can it go all the way and deploy?

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.

Deployment of Slipstream Image

Similar Messages

Maybe you are looking for