User Profile
Steve_DiAcetis
Joined 9 years ago
User Widgets
Recent Discussions
Re: Windows 10 Servicing for customised image
vishalkhatpe If you instruct setup to upgrade (e.g. /auto upgrade): Performs an upgrade of Windows saving apps and data. If the upgrade installation option is not available, or the user needs to resolve an app compatibility issue, Windows Setup will exit silently and log an exit code. If you hit issues that you feel are errors (e.g. apps not migrating correctly), you can drive a resolution via the App Assure program: https://www.microsoft.com/en-us/fasttrack/microsoft-365/app-assure1KViews0likes0CommentsRe: Dynamic Updates in a disconnected environment
You're welcome ct500. Regarding UUP, I'm going to leverage my colleague Dune Desormeaux response on another thread earlier today: We are hard at work on the UUP project and a central goal of the project is to ensure that language packs and Features on Demand are persisted across feature updates deployed through ConfigMgr and WSUS (servicing as you described). Unfortunately this is a large project and we don't currently currently have a timeline for release. The functionality is not going to be released as part of the 2006 release.1.3KViews1like0CommentsRe: Dynamic Updates in a disconnected environment
Hello ct500 : Until UUP integration with WSUS ships, there are some challenges. Below are some options: You can approve DU content in WSUS, for GDR (the LCU), servicing stack updates (SSU), safe OS, etc.. but we do not have FODs published. So if you go this route, with DU enabled, and fail to acquire at the MS endpoints, we’ll fallback to WSUS for a subset of the content. So FOD and language migration will not work versus if you hit the MS endpoints for this content. Right now, for 1809, there is gap with DU publish for WSUS, where GDR DU is not published. That is a known issue, will be fixed soon. For language packs and language experience FODs, you can host these internally, and point setup to acquire them during migration using the /InstallLangPack option. Since you are moving away from calling setup.exe directly, you can pass this ‘parameter’ in via setupconfig.ini If you are targeting Win10 v2004, one of the challenges with DU has been no deliver optimization support. That is now fixed, but hasn’t shipped yet; it is in the queue for servicing and should be out soon.1.4KViews2likes2CommentsRe: SetupDiag information next release of Windows 10
gwblok When setup launches setupdiag, the parameters are: /ZipLogs:False /Format:xml /Output:%windir%\logs\SetupDiag\SetupDiagResults.xml /RegPath:HKEY_LOCAL_MACHINE\SYSTEM\Setup\SetupDiag\Results These are documented at: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/deployment-troubleshooting-and-log-files We're working with Dune Desormeaux to get ConfigMgr integration, it is on their roadmap, but I'm not aware of a release date. Dune may have more. Regarding setup parameters, no new parameters, but glad to discuss more your ideas (as well as ConfigMgr plans).1.8KViews2likes2CommentsRe: Windows Servicing Model
John_Dahl how are you rolling out feature updates? If you really need to install a driver during the feature update, you can use setup's /InstallDrivers command line option. Point it to a local path or UNC, and setup will go through the folders, look for the INF, and install the driver(s). It also works with setupconfig.ini. That said, consider a general workflow to keep drivers current separate, before running setup. For the source OS, this will increase the likelihood that you don’t hit a setup block due to a driver. You can use the same workflow on the new OS, perhaps very soon after setup completes.1.2KViews1like0Comments