Future Tech
asked on
Strange WDS Issue
WDS Version 10.0.14393.0
Deplpoyment Workbench 6.3.8443.1000
Running on Windows Server 2016
Backstory: Deploying a Generalized Sysprep'd image of Win 10 1709. Deployment process (allegedly) ok installing the OS on to the machine.
Problem #1: Once the OS is installed, the system auto-logins as the Administrator, and then just sits there. Doesnt execute any of the scripting steps it should. A reboot of the machine once again auto-logins as the Administrator. Theres a script I cant find to stop this process. Any thoughts?
Problem #2: The task sequence isnt executing after auto-loing as Administrator. I have attached what the task sequence looks like. Problems started with creating the 1709 image, and its associated Task Sequence.
I should also note that I cannot force the machine to re-image. As soon as it contacts the WDS server, it sees the running deployment and picks back up from there. I delete the job from the Monitoring window and it re-creates itself.
task-sequence.PNG
Deplpoyment Workbench 6.3.8443.1000
Running on Windows Server 2016
Backstory: Deploying a Generalized Sysprep'd image of Win 10 1709. Deployment process (allegedly) ok installing the OS on to the machine.
Problem #1: Once the OS is installed, the system auto-logins as the Administrator, and then just sits there. Doesnt execute any of the scripting steps it should. A reboot of the machine once again auto-logins as the Administrator. Theres a script I cant find to stop this process. Any thoughts?
Problem #2: The task sequence isnt executing after auto-loing as Administrator. I have attached what the task sequence looks like. Problems started with creating the 1709 image, and its associated Task Sequence.
I should also note that I cannot force the machine to re-image. As soon as it contacts the WDS server, it sees the running deployment and picks back up from there. I delete the job from the Monitoring window and it re-creates itself.
task-sequence.PNG
Last Comment
Cliff Galiher
Nothing attached.
ASKER
Sorry about that, its attached now.
Nope...
ASKER
Its there. Look at the end of the last comment. task-sequence.png
I did not embed it like i did this one.
I did not embed it like i did this one.
Is it Local administrator or domain administrator?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
@Chethan- Your solution to stop the auto-login worked! Thank you. FWIW- it was a local admin account
I ended up trying a few things to get the loop to stop, two things worked:
1. Boot to a USB with Win 10 loaded. Get to the Disk Management part, deleted all partitions then exit out of Win 10 setup. Booted to WDS, and it worked as expected.
2. Follow this guide: http://henkhoogendoorn.blogspot.com/2014/10/mdt-2013-task-sequence-has-been.html
This also clears the offending partition and allows it to boot to WDS and works as expected.
TLDR; wipe the hard drives manually that have the dirty deployments to break the loop.
Once I wiped the Hard Drives, the "dirty" deployments were cleared.
I have deleted the offending task sequence, and will rebuild the OS and task sequence from Scratch.
I ended up trying a few things to get the loop to stop, two things worked:
1. Boot to a USB with Win 10 loaded. Get to the Disk Management part, deleted all partitions then exit out of Win 10 setup. Booted to WDS, and it worked as expected.
2. Follow this guide: http://henkhoogendoorn.blogspot.com/2014/10/mdt-2013-task-sequence-has-been.html
This also clears the offending partition and allows it to boot to WDS and works as expected.
TLDR; wipe the hard drives manually that have the dirty deployments to break the loop.
Once I wiped the Hard Drives, the "dirty" deployments were cleared.
I have deleted the offending task sequence, and will rebuild the OS and task sequence from Scratch.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: Chethan (https:#a42416379)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: Chethan (https:#a42416379)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
Windows 10
Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.
20K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
