May 11 2017 05:09 PM
May 11 2017 05:09 PM
I'm trying to setup a new SP4 with the guide here. However when it runs through the Windows installation, it fails with this at Installing Updates
Windows could not apply the unattended settings during pass [offlineServicing]
I then look at the setuperr log file and it's saying
Error [0x0606ae] IBS [SetupCl library] Required profile hive does not exist: [\??C:\WINDOWS\system32\config\systemprofile\NTUSER.DAT].
InstantiateCBSUnattendPass: dism.exe returned with failing exit code -2146498555
Callback_UnattendInitiatePass: An error occured while initiating unattend passes; hr = 0x80004005
Any ideas what is going wrong?
May 12 2017 12:44 AM
May 12 2017 12:44 AM
May 15 2017 08:57 AM - edited May 15 2017 08:59 AM
Hi Graham,
I have succefully install SRS V2 using this AutoUnattend.xml.
Obtain a copy of the 64-bit version of Windows 10 Enterprise Anniversary edition version 1607 (English language).
Using rufus tool, create an bootable USB with windows 10 iso image https://rufus.akeo.ie/
Select windows 10 iso image using disk icon, then Select FAT32 in file system and
click Start.
Navigate to the directory folder you selected as the destination folder for the SRSDeploymentKit-2.0.2.0.msi installer package.
Select all files in the directory and copy them to the root USB device: directory.
Download the latest Surface Pro 4 drivers. Be sure to get the ZIP file, not the MSI or Wintab files.
Open the driver ZIP file and copy the folder SurfacePro4_Win10_* to the directory "USB :\AutoUnattend_Files\DistShare\Out-of-Box Drivers” on the USB disk.
In the root of your USB drive, there is a file named AutoUnattend.xml : Open it with notepad++ editor. There are two commands referring to Sysprep.exe, they are next to each other in the file.
Line 232 you need to select your sysprep deployment : (Select only ONE Path section below for use.)
I have chose to create a single unit to go live (default) --> (Line 236/237)
<Path>%SystemRoot%\System32\Sysprep\Sysprep.exe /generalize /oobe /reboot /unattend:%SystemDrive%\Rigel\x64\Scripts\Provisioning\audit.xml</Path>
or copy my AutoUnattend.xml
Hope that help
Regards,
Benoit
May 15 2017 02:48 PM
Thanks Benoit
Very odd, tried your file, downloading the drivers again (and trying both versions) and still fails with the same error). Back to normal Windows install and putting the app on top. Not idea.
May 15 2017 06:38 PM
Hello Graham
We have seen many issue with 1703.
We had to back many SRS from our client from 1703 to 1607.
Can you try with Windows 1607?
May 16 2017 12:56 AM
Hi Graham,
Obtain a copy of the 64-bit version of Windows 10 Enterprise Anniversary edition version 1607...
And this process will works like a charm :)
It's a sysprep issues ...
May 16 2017 01:00 AM
May 16 2017 02:24 AM
May 16 2017 02:24 AM
So the 1607 build worked. For others struggling, I used the SurfacePro4_Win10_15063_1701801_1.zip driver pack with the 1607 build and not the SurfacePro4_Win10_1701001_0.zip.
Aug 15 2017 02:12 PM
Hi Benoit,
I'm having the same issue as Graham so I followed your procedure and used your autounattend.xml file and i get the error:
Windows cannot read the <ProductKey> setting from the unattend answer file.
My ISO is Win10_1607_English_x64
If I uncomment in the XML the product key section and remove the serial number, I get further in the installation process but then I get the same error as Graham:
windows could not apply unattend settings during pass offlineservicing
Do you have any idea what I could do wrong? Any help would be greatly appreciated.
Thank you very much!
Aug 16 2017 03:52 AM
Aug 17 2017 12:41 AM
What issues did you face with 1703 ?
I've seen an odd story where external monitors stopped working and getting the following message on the SP4 "The room display is unplugged. Plug it back in for the best experience"
Anyone seen that?
Aug 17 2017 01:14 AM
Aug 17 2017 07:12 AM
Aug 17 2017 08:49 AM
I removed the /generalize from the sysprep line but didn't help.
Looks like I don't have an Enterprise iso but I absolutely can't find it anywhere. Only thing I can find is an evaluation for build 1703... I will try that
Aug 18 2017 02:33 AM
Hello @Deleted
Did you noticed that your SRS is also switching to fan mode turbo when using Skype App ?
We don't have this behavior on all our SRS but one does it all the time when trying to udpate WU or using SFB app.
I used drivers from package SurfacePro4_Win10_1700501_0, but wonder if a newer version could fix the turbo fan issue...?
Aug 18 2017 04:41 AM
Aug 24 2017 02:12 AM - edited Aug 24 2017 02:15 AM
Hi Maxime,
You need to use this file as is AutoUnattend.xml with the technet arcticle
After, it's possible to enter your product key if you have the correct one.
Just to let you know that an SRS bundle already exist with Logitech distributor.
Example in France with Tech Data (Maverick), you can order a pre-configured version with the reference 4232858.
Under reference 4232858: Surface Pro 4 will have a pre-installed SRS software (Windows IOT Enterprise & SRS) +SmartDock
On receipt of the Skype Room System package, you must insert the SP4 on the Logitech Smartdock.
Once done just connect to the internet and enter your Skype4B ID to use it.
So we don’t need to follow the TechNet with this ref (forget DIY with obtain a copy of the 64-bit version of Windows 10 Enterprise Anniversary edition and product key) :)
Regards,
Benoit
Aug 24 2017 07:26 AM
Bonjour Benoit,
When I tried at first, I didn't have a Windows Enterprise so that might be the issue. Juste got my licenses today so I will give a try with your AutoUnattend.xml and let you know the result. But it's also good to know that Logitech can provide a SRS bundle. I will also look that way.
Merci beaucoup!
Max
Aug 28 2017 02:41 PM
Hi Guys,
It looks like my issue was the ISO. Just tried with an enterprise ISO and everything installed correctly. Thanks for the help!
Sep 12 2017 01:34 AM
I also got the error:
"Windows could not apply the unattended settings during pass [offlineServicing]"
but that was when trying to use the Win10 1703 Ent LTSB iso.
Using the normal Win10 1703 Ent iso, everything works fine.
I guess the product key in the autounattend.xml, does not work for LTSB.
I was told from Techdata that LTSB is the same thing as Win10 Ent IoT, so I figured that I should use the LTSB iso - but I figured wrong...