RE: SCCM - Boot Task Sequence Wizard from Hard Disk
- From: VladZ <vladz@xxxxxxxxxxxxx>
- Date: Mon, 15 Jun 2009 06:01:01 -0700
Hi Eric.
Thank you very much for responding to my question.
That is pretty much it. I think you understood the issue well, but just for
completeness, I’ll try to summarize again:
All I would like to do is to copy the content of boot media (CD/USB) to a
partition on the local hard disk and then boot from that HDD partition
exactly the same as it would from the removable media. Basically, it should
then set up the RAMDrive, boot PEfrom it and then we can use Task Sequences
to image the hard drive/ set up the OS as I would if I have booted from the
removable media. This is a bit like sending a standard image to the OEM so
that the TS wizard is started when the machine is shipped and powered up @
our site. It would then chose appropriate TS based on the collection we put
it into and install the OS and appropriate applications.
The problem I am encountering is that although it boots into Windows PE from
the hard disk just fine, the TS wizard fails immediately, not being able to
find the configuration / environment. (the log files content:
==============================[ TSBootShell.exe
]==============================
Succeeded loading resource DLL 'X:\sms\bin\i386\00000409\TSRES.DLL'
Debug shell is enabled TSBootShell
Waiting for PNP initialization...
Booted from fixed disk
!sVolumeID.empty(), HRESULT=80004005
(e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,472)
!sTSMDataPath.empty(), HRESULT=80070002
(e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,1393)
TS::Utility::GetTSMDataPath(rsPath), HRESULT=80070002
(e:\nts_sms_fre\sms\client\tasksequence\bootshell\configpath.cpp,231)
Failed to find the current TS configuration path
ConfigPath::FindConfigPath(sConfigPath), HRESULT=80070002
(e:\nts_sms_fre\sms\client\tasksequence\bootshell\bootshell.cpp,550)
Failed to find the configuration path.
The system cannot find the file specified. (Error: 80070002; Source: Windows)
Execution failed with error 80070002.
Finalizing logging from process 844
Finalizing logs to root of first available drive
LOGGING: Setting log directory to "C:\SMSTSLog".
-----------------------------------------------------------------------------------------------------------------------------------
When I am booting from either a CD or a USB drive with exactly the same
files/WinPE image, it works fine, boots, and then accepts and completes the
assigned TS. We also have another (non-SCCM) Win7 install method that works
just fine using boot PE from HDD / then install from WIM.
I have also tried doing some tweaking to the WinPE Wim, to include the
\SMS\Data folder to make it work like a PXE boot (as described @
http://kongkuba1.spaces.live.com/blog/cns!EEFF1607E296E5AB!311.entry?wa=wsignin1.0&sa=277353668), but that made no difference.
It is a client issue, it is failing before it ever gets to talk to the SCCM
server, but here is the info you requested:
At the moment I have a test environment (we are still and SMS2003 shop).
(And, yes, I know this is not the recommended setup but it all works fine
apart from this client issue) :
1) Windows 2008 Enterprise server (x64) (running on Hyper-V)
o Single server doing all SCCM site systems, IIS and SQL DB
2) I have just installed the SCCM SP2 Beta (to enable Win7 testing)
3) Server memory - 4GB
4) Test machines /PCs deployed to - Dell Optiplex GX620 (also tried on an
Optiplex 755, a laptop (latitude D630) and an HP desktop (don’t have the
model handy)
5) RAM in PCs 512, 1024 & 2048.
I have installed WAIK 1.1 and my PE images report version 6.1.7100.0 (I
think that is SP2 Beta version that handles Win7) I have also tried with
WinPE 6.0.6001.18000 previously – the same results
Only other option out of this for us (that I can think of) would be to
“disassemble” the OSD process, create an OS image to deploy to the hard disk
and then (somehow) start an appropriate TS to configure and install
applications. (This seems more difficult to me, but If you can think of how
we’d do this, I’d love to hear about that too :)
Sorry, massive post... :)
Any help greatly appreciated.
Vlad.
"v-ezhang@online" <v-ezhang@online>, "mic" wrote:
Hi Vlad,
Thank you for your post.
My name is Eric Zhang, and it is my pleasure to work with you on this
issue!
Please allow me to confirm that my understandings are correct. As I
understand it, the issue is:
You want to boot into the Task Sequence wizard from the local HDD, but
failed.
If I have misunderstood your concerns please feel free to let me know.
First of all, can you please supply me with the following information So I
can set up the lab environment to reproduce your issue:
1. Version of Windows Server 2003 (Enterprise, Standard, etc).
2. Service Pack level that SCCM 2007 is installed on?
3. Amount of memory in server,PC model that you are deploying to?
4. Amount of RAM in PC?
One other note that SCCM 2007 RTM used the WAIK 1.0 and WinPE 2.0 while
SCCM 2007 SP1 uses WAIK 1.1 and WinPE 2.1. If you did not update your
custome images to use the newer WinPE 2.1, you may run into problems.
So if you used a custom WinPE images. When building your custom WinPE
images, please make sure when building those images that you have done so
using the newer WinPE 2.1 in the WAIK 1.1.
SCCM 2007 SP1 will not auto update custom WinPE Boot Images and will only
update the Boot Images that are installed by default with the product. If
any modifications are done to the original default Boot Images, I cannot
guarantee that they also will be auto updated by SCCM.
.
- References:
- SCCM - Boot Task Sequence Wizard from Hard Disk
- From: VladZ
- SCCM - Boot Task Sequence Wizard from Hard Disk
- Prev by Date: SCCM - Boot Task Sequence Wizard from Hard Disk
- Next by Date: SMS2003 - SQL sys.sp_OACreate procedure error on SMS_INVENTORY_DATA_LOADER
- Previous by thread: SCCM - Boot Task Sequence Wizard from Hard Disk
- Next by thread: RE: SCCM - Boot Task Sequence Wizard from Hard Disk
- Index(es):
Relevant Pages
|
