tompsmith Posted January 19, 2016 Report post Posted January 19, 2016 hello, im after some assistance if possible. Im attempting to deploy a windows 10 image, i have created a reference image from within MDT then imported the WIM in SCCM 2012 r2 sp1 Cu2. I have built a new mdt task sequence within SCCM 2012 and have downloaded the windows 10 drivers for the surface pro 4. The image deploys to a virtual machine fine and joins it to the network, but im having trouble with the Surface pro. Sometimes it finishes installing drivers and then hangs on "getting ready"... other times it completes the osd but it hasn't joined the network. There is a step in the task sequence to apply the surface pro 4 drivers and it seems to run through that ok, there is also another step to automatically apply drivers which i have switched on at present... like i said the osd completes on a vm but not my surface pro 4.... cant figure out the exact step that fails the whole OSD ive attached the SMSts.log from the surface.... i can see it doesnt find all the drivers but was hoping it would be enough to enable the OSD to complete. any help would be appreciated. smsts.log Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted January 19, 2016 Report post Posted January 19, 2016 looks like it's failing after it installs the configmgr client, can you check the ccmsetup.log file and see does it give you any clues, also is there another smsts*.log file still in C:\_SMSTasksequence\logs ? Quote Share this post Link to post Share on other sites More sharing options...
tompsmith Posted January 19, 2016 Report post Posted January 19, 2016 ive attached the ccmsetup.log and anotger smsts log file... the osd literally just finished.... took a while to eventually get there... but it didn't join the domain.... I have logged in locally with the admin account and all drivers are installed? ccmsetup.log smsts-20160119-234919.log Quote Share this post Link to post Share on other sites More sharing options...
tompsmith Posted January 20, 2016 Report post Posted January 20, 2016 there are a couple of errors in ccmsetup, I have attached a log above but here are some examples: Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 19/01/2016 16:38:37 3496 (0x0DA8)Params to send '5.0.8239.1301 Deployment Error: ' ccmsetup 19/01/2016 16:38:37 3496 (0x0DA8)A Fallback Status Point has not been specified and no client was installed. Message with STATEID='100' will not be sent. ccmsetup 19/01/2016 16:38:37 3496 (0x0DA8) This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 19/01/2016 16:38:38 3496 (0x0DA8)Unexpected row count (0) retrieved from AD. ccmsetup 19/01/2016 16:38:38 3496 (0x0DA8)Failed to get site version from AD with error 0x80004005 ccmsetup 19/01/2016 16:38:38 3496 (0x0DA8)SiteCode: USS ccmsetup 19/01/2016 16:38:38 3496 (0x0DA8) Failed to send status 100. Error (87D00215) ccmsetup 19/01/2016 16:38:37 3496 (0x0DA8)Downloading file C:\_SMSTaskSequence\OSD\USS0001C\ccmsetup.exe ccmsetup 19/01/2016 16:38:38 3496 (0x0DA8) MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent. ccmsetup 19/01/2016 16:40:04 3496 (0x0DA8) MSI: Action 16:40:03: CcmRegisterComponentsInit. Generates the list of components for CcmRegisterComponets action to register. ccmsetup 19/01/2016 16:40:03 3496 (0x0DA8)MSI: Action 16:40:03: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents. ccmsetup 19/01/2016 16:40:03 3496 (0x0DA8)MSI: Action 16:40:03: CcmRegisterComponents. Registers components passed in from CcmRegisterComponentsInit ccmsetup 19/01/2016 16:40:03 3496 (0x0DA8) MSI: Action 16:40:37: SmsSetClientHotfixVersion. ccmsetup 19/01/2016 16:40:37 3496 (0x0DA8)MSI: Action 16:40:37: SmsGenerateMIFInit. ccmsetup 19/01/2016 16:40:37 3496 (0x0DA8)MSI: Action 16:40:37: SmsGenerateFailureMIF. ccmsetup 19/01/2016 16:40:37 3496 (0x0DA8)MSI: Action 16:40:37: SmsGenerateSuccessMIF. ccmsetup 19/01/2016 16:40:37 3496 (0x0DA8) Quote Share this post Link to post Share on other sites More sharing options...
tompsmith Posted January 20, 2016 Report post Posted January 20, 2016 I found this on the setupact, the weird thing is the vm joins the domain fine but the surface pro doesn't. I can't figure it out, I have a network settings task that is set to join the pc to the domain shortly after the unattendxml file attempts to in the mdt task seqeunce.... I have an "apply network settings" task after the "apply windows settings" task which specifies to join the domain I still cant figure out why it doesn't join... the vm joins fine with the same task sequence but the surface pro doesn't.... vm setupact: 2016-01-20 11:03:32, Info [DJOIN.EXE] Unattended Join: DebugJoinOnlyOnThisError = [NULL]2016-01-20 11:03:32, Info [DJOIN.EXE] Unattended Join: TimeoutPeriodInMinutes = [NULL]2016-01-20 11:03:32, Info [DJOIN.EXE] Unattended Join: Checking that auto start services have started.2016-01-20 11:03:32, Info [DJOIN.EXE] Unattended Join: Calling DsGetDcName for ussmain...2016-01-20 11:03:32, Info [DJOIN.EXE] Unattended Join: DsGetDcName returned [uSS-LIV-DC2]2016-01-20 11:03:32, Info [DJOIN.EXE] Unattended Join: Constructed domain parameter [ussmain\USS-LIV-DC2]2016-01-20 11:03:33, Info [DJOIN.EXE] Unattended Join: NetJoinDomain succeeded!2016-01-20 11:03:33, Info [DJOIN.EXE] Unattended Join: Exit, returning 0x1 surface pro setupact: 2016-01-20 11:17:08, Info [DJOIN.EXE] Unattended Join: Checking that auto start services have started.2016-01-20 11:17:08, Info [DJOIN.EXE] Unattended Join: Calling DsGetDcName for ussmain...2016-01-20 11:17:08, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 10 seconds...2016-01-20 11:17:18, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 10 seconds...2016-01-20 11:17:28, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 10 seconds... Quote Share this post Link to post Share on other sites More sharing options...
ZeZe Posted January 28, 2016 Report post Posted January 28, 2016 I'm not sure if this is the same problem I had in the past but when I was re-imaging a test machine, I notice that sometimes it failed to register the computer to the domain. The problem was that sometimes chooses different domain controllers and the computer already existed but it wasn't replicated from other DC's... does the computer exists in the AD? If so, try to removed it and make sure all DCs have the same information... Quote Share this post Link to post Share on other sites More sharing options...
renaud83 Posted February 29, 2016 Report post Posted February 29, 2016 Hi, I have the same problem with a surface pro 4. I use SCCM 1511 but i had already this problem with sccm 2012 r2. OSD fails after a long time hang with getting ready screen. Sometimes the computer is joined to the domain, sometimes i have the "lets get connected" screen. Other surface pro 4 are deployed without issues. It appears only on one of my 40 surface. Install Windows 10 with a usb sticks works well. I have tried with several release of drivers including the last one from february. Did you have a solution ? Regards Quote Share this post Link to post Share on other sites More sharing options...
Oilers93 Posted May 3, 2016 Report post Posted May 3, 2016 Hello, I'm running into the same issue except it's happening to my desktops. They hang on the "Getting Ready" screen, don't join the domain but all the drivers seem to be listed properly in Device Manager - No yellow warning symbols. Has anyone resolved this issue and if yes then what steps did you take in doing so? Thanks! Quote Share this post Link to post Share on other sites More sharing options...
keety Posted January 18, 2017 Report post Posted January 18, 2017 Hello, Right, I've had the same issue and I've managed to fix it (well pinpoint where the issue is) It's affecting my Windows 8 and Windows 10 builds. It started happening a good 5 months or so ago, but seeing as I'm the only one testing and building these machines I looked into it for a bit, got fed up and moved on (it was only Windows 8 at the time, and I build those using media as its surface pro's) Anyway, I've been through everything, was it the WIM? Was it the fact I was pumping in an xml file to customise it? Was it drivers? After going through all of that I was no closer... I'd been using a physical machine as it was sat on my desk... the other day I thought, "Right, lets do it on a virtual to 100% rule out drivers) and bingo... it worked! So it's definitely a driver issue... so then I thought, its not affecting my windows 7 devices (all 10k of them)... and it started around September time.. so what the hell did I import then? Well we had a new HP laptop (640 G2) that came with the Intel L219 Nic... So now I've got the latest version of the drivers, Imported them and BINGO! It's back working! I know this isn't quite related to your issue but thought i'd bung it up for anyone else... Quote Share this post Link to post Share on other sites More sharing options...
NullSID Posted January 23, 2017 Report post Posted January 23, 2017 I've had issues with that. Is this two different management points ? The one you tested the vm on and the other? I had this with 4 sites in China and turned out that the service account didn't "fully" replicate all the attributes so it would die at domain join. Try using a different account that had the same permissions as your existing one under site client settings. I can't remember the exact path but it's the location you put the account to install the configuration manager client. Quote Share this post Link to post Share on other sites More sharing options...
