heyjim Posted January 30, 2014 Share Posted January 30, 2014 Hi all,I have a problem with WDS on Server 2012 where it doesn't seem to see the XML file when deploying an image.A bit of background:Windows 7 x64 with my applications installedCapture the image with WDS with a x64 boot.wimCreated an answer file with Windows System Image Manager just for the PE section (not bothered about Windows setup at the moment)Added the XML to the server properties in WDS under x64All I want the XML to do is set the language, create the partitions as I've selected, told it where the image.wim and added the credentials.But whenever I PXE boot into WDS, it brings up the menus as if it's ignoring the XML.Does anyone have any ideas?Thanks!WDSClientUnattend.xml Link to comment Share on other sites More sharing options...
Tripredacus Posted January 30, 2014 Share Posted January 30, 2014 When you get to the first page, open a CMD and then notepad and look at the wpeinit log file that is on the ramdrive. It will show whether or not it picked up the answer file. Link to comment Share on other sites More sharing options...
heyjim Posted January 30, 2014 Author Share Posted January 30, 2014 When you get to the first page, open a CMD and then notepad and look at the wpeinit log file that is on the ramdrive. It will show whether or not it picked up the answer file.Thanks - Do you know what directory that log file is in? Link to comment Share on other sites More sharing options...
Tripredacus Posted January 31, 2014 Share Posted January 31, 2014 X:\windows\system32\wpeinit.log Link to comment Share on other sites More sharing options...
heyjim Posted February 3, 2014 Author Share Posted February 3, 2014 (edited) X:\windows\system32\wpeinit.logThere doesn't seem to be a wpeinit.log, only a wpeinit.exe - any ideas? Edited February 3, 2014 by heyjim Link to comment Share on other sites More sharing options...
Tripredacus Posted February 3, 2014 Share Posted February 3, 2014 Use notepad to search for any log files created at the time of boot. It may also use setupact.log instead. Link to comment Share on other sites More sharing options...
heyjim Posted February 5, 2014 Author Share Posted February 5, 2014 I ended up (by accident) rebooting the WDS server and it started working for some reason Thanks for your help anyway! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now