Jump to content


SteveH

Established Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SteveH

  • Rank
    Newbie
  1. I've been testing out pushing the Win 10 1607 update via a Servicing plan and discovered that the apps I remove using DISM during the initial build task sequence have come back. I'm trying to figure out the best way to re-remove the apps. It'd be great if there was a "run this package after the update is completed" option for the servicing plan, but since there isn't (that I've seen) here's what I've come up with as options: Deploy an application containing a script to remove the apps to all Windows 10 systems with a requirement of version 1607, then it would run after they meet the criteria. Drop using the Servicing Plan and use a task sequence to deploy the update, then remove the apps as a following step in the TS. Remove the applications in question offline, then push the upgrade using a task sequence. Anyone else have any better ideas? Thanks! Steve
  2. How does Config Manager update the which version of Windows is in which branch? I just updated from 1606 to 1610 and expected to see this chart updated: And When I create a new "Business Ready" Servicing Plan I only get 1511 builds listed, "Release Ready" shows only 1607 builds. Am I missing something? Thanks!
  3. We're (still) using Microsoft's DHCP services on a 2003 server. It isn't integrated to our Active Directory, its just a standalone DHCP server. I tried adding an "ipconfig /renew" between the other steps in the task sequence but it didn't help since the "Apply Operating System" step takes such a long time on these particular client systems. Thanks!
  4. I've seen other posts that hint at this issue but haven't really found a definitive solution. I installed a large batch of Windows updates to my Windows 7 OS image and found that some of my slower desktops were getting the "... has failed with the error code (0x80070002)" while either downloading the OS image WIM or immediately after applying the WIM. I used the command prompt to run a ping while the system was building and found that about 1 hour into the build I'd lose IP and the system would "pull" an autoconfiguration 169.x.x.x address. If I manually run an ipconfig /renew I'm able to pull an IP again but it looks like PE isn't renewing the lease automatically. Once the system boots to a full Windows I'm not having any DHCP renewal issues. I've been using a WinPE 5.1 boot image for several months now but only recently experienced this problem, though I'm assuming I only notice the issue now that my Win7 WIM file is large enough to take an hour. Because of the way this particular network segment is used I'd rather not extend the lease beyond an hour. Is there anything I can do to get my PE systems to renew their IP lease like they're supposed to? Any help or advice is appreciated! Thanks
×
×
  • Create New...