Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 27, 2015 7:49 AM
Hello,
I'm trying to deploy a Windows 7 task sequence to a VM. After it downloads the files, it says "Windows is starting up..." and "Preparing network connections..." then hangs on a blank SCCM screen then reboots.
I have tried adding the VM Network Drivers to the boot image but no avail.
Do i need to add Storage ? Also in TS i select my OS as 2:2 .
Found below in smsts.log
X:\sms\data\Winpe does not exist
X:\smstswinpe\winpe does not exit
As
All replies (19)
Thursday, September 3, 2015 4:24 AM ✅Answered | 1 vote
Hi Jason,
I just changed NIC to E1000 and now i can deploy the image...
As
Thursday, August 27, 2015 8:02 AM
Hi,
Are other installations succefull? I would checkt the time on the system so that it is correct and the network access account and verify network connectivity.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter @ccmexec
Thursday, August 27, 2015 10:19 AM
Hi,
This is the first test. and totally new to SCCM. This VM is new and no OS installed before.
<![LOG[Loaded Windows Imaging API DLL (version '6.3.9600.17029') from location 'C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll']LOG]!><time="16:32:57.768-600" date="08-26-2015" component="SMSPXE" context="" type="1" thread="19884" file="wimfile.cpp:346">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\SGS00004\boot.SGS00004.wim]LOG]!><time="16:32:57.768-600" date="08-26-2015" component="SMSPXE" context="" type="1" thread="19884" file="wimfile.cpp:430">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\SGS00004\boot.SGS00004.wim
PackageID: SGS00004
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="16:32:57.773-600" date="08-26-2015" component="SMSPXE" context="" type="1" thread="19884" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\SGS00004\boot.SGS00004.wim]LOG]!><time="16:32:57.773-600" date="08-26-2015" component="SMSPXE" context="" type="1" thread="19884" file="wimfile.cpp:466">
<![LOG[InstallBootFilesForImage failed. 0x80004005]LOG]!><time="16:33:00.540-600" date="08-26-2015" component="SMSPXE" context="" type="3" thread="19884" file="bootimagemgr.cpp:1608">
<![LOG[Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\SGS00004\boot.SGS00004.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)]LOG]!><time="16:33:00.540-600" date="08-26-2015" component="SMSPXE" context="" type="3" thread="19884" file="bootimagemgr.cpp:1275">
<![LOG[Failed adding image E:\RemoteInstall\SMSImages\SGS00004\boot.SGS00004.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="16:33:00.540-600" date="08-26-2015" component="SMSPXE" context="" type="3" thread="19884" file="bootimagemgr.cpp:1180">
<![LOG[File E:\RemoteInstall\SMSTemp\2015.08.26.16.32.57.03.{886FB8F0-F180-4EA8-A041-A811579D4425}.boot.bcd deleted.]LOG]!><time="16:33:00.540-600" date="08-26-2015" component="SMSPXE" context="" type="1" thread="19884" file="bootimagecache.cpp:267">
<![LOG[File E:\RemoteInstall\SMSTemp\2015.08.26.16.32.57.03.{886FB8F0-F180-4EA8-A041-A811579D4425}.boot.bcd.log deleted.]LOG]!><time="16:33:00.540-600" date="08-26-2015" component="SMSPXE" context="" type="1" thread="19884" file="bootimagecache.cpp:282">
<![LOG[Found new image SGS00005]LOG]!><time="16:33:00.540-600" date="08-26-2015" component="SMSPXE" context="" type="1" thread="19884" file="bootimagemgr.cpp:1123">
AS
Thursday, August 27, 2015 10:44 AM
Hi,
Check out Nialls great guides to get started, really helpful.http://windows-noob.blogspot.se/2013/01/sccm-2012-guides.html
Have you configured a Network access account? it sounds like that could be the issue if not, https://albertneef.wordpress.com/2013/03/01/change-network-access-account-in-sccm-2012/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter @ccmexec
Thursday, August 27, 2015 4:04 PM
For OSD you need Network Drivers and HDD Controller Drivers in the Bootimage and later on a Driverpackage with Network and HDD Controller (+more) also if OS hasnt the Drivers included.
To Check LAN and HDD Access in the Bootimage:
Command Support in Bootimage --> F8 --> ipconfig --> IP?
and for Disk diskpart --> list disk
Drivers in the Bootimage must fit to the Bootimage.
e.g. Win PE 5.0 = Windows 8.1 Drivers and Windows PE 3.1 Windows 7 SP1
Regards
Thursday, August 27, 2015 6:01 PM
Most of the time when the computers reboots before selecting a TS is related to drivers. As other states, add your VM NIC drivers to the boot image and enable command prompt support in your boot image.
Press F8 and see if you have a valid IP address and try to ping your SCCM server.
Benoit Lecours | Blog: System Center Dudes
Monday, August 31, 2015 6:35 AM
Hi All,
I can Ping and list the disk? Do i have to add Network and disk drivers to both x64 and x86 boot images?
after adding update DP or anything more to do?
How do i copy the smsts.log to network?
Monday, August 31, 2015 6:54 AM
Hi,
Did you configure a Network access account?
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter @ccmexec
Monday, August 31, 2015 7:04 AM
HI Jorgen,
Under Software Distribution Component Properties -Network Access Account i just add the Domain\SCCMAdmin
But i login to this SCCM Server with MyAdmin login.
Noticed that SMSTS log got time info is different to actual time?
How do i copy this file to local pc ?
As
Monday, August 31, 2015 9:15 AM
Hi,
As I wrote before, time could be an issue as well, you need to make sure that the time is correct as well on the client you deploy.
The NEtwork access account should not be SCCM Admin, it should be a normal user account without any other permissions in SCCM.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter @ccmexec
Monday, August 31, 2015 11:58 AM
Hi,
This is New VM and no Tools installed so change the BIOS time and add new domain\SCCMInstall user to Primary server Local User group
add this user to Network Access and test the share .
do i need to update anything after this?
just test the F12 again but same blank screen
As
Monday, August 31, 2015 12:20 PM
Hi,
You can use that account, however the password is stored as a variable on the clients in clear-text during OS Deployment so it is not recommended.
If you have enabled F8 command shell for the boot images you can press F8 and verify the time as well.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter @ccmexec
Tuesday, September 1, 2015 12:36 AM
Hi
I just run the same TS on physical PC and i can go pass the Apply Operating System but this VM still the blank Screen.
BIOS Time/ Date is now correct but Date Format is : 09-01-2015
NIC and Drive Drivers are correct: Can ping and diskpart but cannot net use to map drive?
Network Access Account added. (SCCMClient Install and add to Local Policy to access this network ...
SCCM01 server firewall Diable
SMSts.log got following errors
failed to get client identity (80072ee2)
SynctimewithMP() >failed 80072ee2
Failed to get time information from MP : http//sccm01.domain.com
HRESULT =80004005
As
Tuesday, September 1, 2015 12:51 AM
"but cannot net use to map drive?"
If you can't do this, it's a good best most other network related activities won't work either.
80072ee2 = "The operation timed out"
This means *something* is preventing the communication from being complete. What that something is is unknown and cannot be determined by the client. You'll have to troubleshoot network communication between the client and MP.
Jason | http://blog.configmgrftw.com | @jasonsandys
Thursday, September 3, 2015 1:10 AM
HI Jason,
You are correct. But i cannot find what this is.
1. Ipconfig /all gives my Primary DNS /Secondary DNS and 127.0.01 ?
2. Can ping both IP and FQDN
3, Can not map to IP or FQDN ( Net use h: \Ip\share .....)
4. SCCM Server IPV4 settings correct.
SMSTS.log
CLibSMSMessageWinHttpTransport::Send: URL: SCCM.domain.com:80
Error. Received 0x80072ee7 from WinHttpSendRequest.
As
Thursday, September 3, 2015 1:46 AM
It's something either configured on the server itself (like some security software) or something in/on your network. Unfortunately, either way, it's something unique to your environment. A network trace/sniff may help you identify what's going on. Reviewing the I.IS log on the MP may also help in narrowing down the issue
Thursday, September 3, 2015 2:49 AM
HI Jason,
Thanks, I found new Vmxnet3 Driver ( release 2012 ) and add to the drivers and update the Boot image (x64)
I'm deploying windows 7 x64 .
My DHCP set 067=smsboot\x64\wdsnbp.com and 066 :Servername.domain.com
Network Access Account set to SCCMINstall and full access to the share
Do i have to add this to Manage Access Account in Boot Image?
As
Thursday, September 3, 2015 3:05 AM
First, using DHCP options is usually not the best option; iphelpers are much preferred and work much better. This is not the source of your issue though as you are well past PXE boot.
Full access to what share? Task Sequences don't connect to any shares and no you don't have to add the account to anything. Also, you're well past any use of the boot image. This has nothing to do with your issue either though.
There is "something" preventing the network communication from completing. A permissions issue would not prevent the communication.
The VMWare driver is a possibility though as the VMXNet driver is known to be quite buggy, so much so that most folks stop using that NIC type altogether -- I think it's more than just the driver that's buggy but also the implementation by VMWare. This goes for both the client *and* the server hosting the MP and DP. Switch them both to the E1000 (I think that's the other option in VMWare) or better yet, ditch VMWare and use Hyper-V :-)
Jason | http://blog.configmgrftw.com | @jasonsandys
Thursday, September 3, 2015 11:46 AM
Hello,
This happens if your boot image does not have the required NIC driver installed in boot image. Hence it reboots after preparing the network connection. So please add the driver and update the boot image to DP and check.
Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"