Windows updates are not typically affected by DDP | E outside of Windows Feature updates (upgrading to Windows 10 from Windows 8.1, or the "feature" builds of Windows 10 [i.e "Creators" update or "Anniversary" Update]).
Do you have more information on the issue you're encountering? Which specific updates are you attempting to install? What version of DDP | E are you currently running within your environment?
dell-dale p
2 Intern
•
156 Posts
0
July 24th, 2017 07:00
Hi RyanIG,
Windows updates are not typically affected by DDP | E outside of Windows Feature updates (upgrading to Windows 10 from Windows 8.1, or the "feature" builds of Windows 10 [i.e "Creators" update or "Anniversary" Update]).
Do you have more information on the issue you're encountering? Which specific updates are you attempting to install? What version of DDP | E are you currently running within your environment?
RyanIG
4 Posts
0
July 27th, 2017 07:00
Hey Dale,
It's actually a Feature update we are seeing this issue with(1703) below is a screenshot of what we are seeing,
http://imgur.com/a/3LwET
Is there anyway to install these updates while still apart of the domain ?
We're running version - 8.12.0.26 of DDPE | E
dell-dale p
2 Intern
•
156 Posts
1
August 2nd, 2017 14:00
hi RyanIG!
the error you are seeing is specifically due to not having ran WSProbe -z before attempting to run the update. could we run through this process:
- Close the Update window
- open an administrative command prompt
- run the command "Wsprobe -z" (no quotes)
- attempt to re-run the Windows Feature Update
if you reboot before the update kicks off, you will have to re-run the WSProbe -z command from an administrative command prompt.