Jeff May-Stahl

I have found other posts with the same issue but no resolutions. It seems that the Feb and March CUs broke something, preventing upgrade to 1709. Upgrading to 1703 seems to be working. On my systems, removing the latest CU fails. I'm not sure if they are unable to be removed in general or if it is just my environment.

Interestingly, the upgrade does work when run via command line manually from the package folder that sccm downloads to the machine.

It seems to work with 10586.1358 but not the machines that are 10586.1478

Yes. They were updated earlier this month.

Windows 10 1511 Having the same issues with 1607 machines. Going to 1709 with both.

The SP4 logs are more indicative of most of our machines. The setupact log just stops after the errors as in the screen shot I posted (Windows::Compat::Appraiser::WicaDeviceInventory::GetInventory (409): Finished reading Device Inventory. 0 Devices). In both SMSTS logs it just sits at the executing command line, the device says running action:Upgrading Operating System and SCCM says in progress. And it will sit there for days until the device is restarted and the deployment is deleted. The desktop setupact log does look different but the smsts and device acted the same and it never upgraded. It worked on about 150 machines, now it doesnt work on any. I tried checking Ignore any compatability messages, tried using the dynamically update windows. No change.

This seems to be where its getting held up

Ok, Here are the logs from a SP4 and a Desktop. Thank you! 1511DesktopLogs.zip 1511SP4Logs.zip

My upgrade task sequence to go from 1511 and 1607 to 1709 was working perfectly. Now it just hangs forever (days) when it starts the upgrade the task os step. There are no errors in the SMSTS log, it just stops at the executing command line step. Setupact and Setuperr logs show some errors but I could use some help figuring out what happened to make this stop working!

I am running into this same issue while trying to upgrade 1511 to 1709 via task sequence. Worked fine on all my 1511 desktops but will not work on any of my Surface Pros or VMs. Acutally will not run on any 1607 machines either. Just hangs forever.

I have been upgrading systems from 1511 to 1709 with a task sequence and it was working fine until I got the mobile devices. This task sequence was tested to work on the Surface Pros fine. I upgraded all the desktops with no problems. But now when deployed to 64 Surface Pros only 4 were successful. The rest just got stuck "in progress" at the executing command line step "Executing command line: "C:\_SMSTaskSequence\Packages\P010001A\SETUP.EXE" /ImageIndex 3 /auto Upgrade /quiet /noreboot /postoobe "C:\WINDOWS\SMSTSPostUpgrade\SetupComplete.cmd" /postrollback "C:\WINDOWS\SMSTSPostUpgrade\SetupRollback.cmd" /DynamicUpdate Disable"

I tried reenabling GPO and pointing to this server but it still gives the Group Policy Settings overwritten by higher authority (Domain Controller) error

I am using SCCM 1710 and attempting to use servicing plans for the first time and am totally frustrated. The client never downloads the update and results in an error 0x87D00692 - Group Policy conflict. The UpdatesDeployment and WUAHandler logs show essentially the same error which I have attached a screenshot of. At first, when I saw this, it would say that WSUS was pointing to my old server which made sense. I have since disabled all group policy having to do with Windows Update as I want SCCM to control updates but I am still getting the errors showing a Group Policy conflict. rsop and GPResults both don't show anything to do with Updates. I am at a loss. Do I just re-enable the GPO and set it to point at my new server? (WUAHandler log on the server shows the same errors)

I am setting up SCCM CB for software updates and have a question. I have set up several baselines and also some ADRs. I was wondering though, after I did it, what the best practice is with Windows 10 updates. I did not include the Cumulative Updates in the baseline, assuming they'll get done through the ADRs but now I am wondering if I should. What is the rule of thumb here? Thanks!

1702 is installed on a new server, new hierarchy. What is the best practice to upgrade the clients? The new sccm is discovering everything, I created a pre-production test collection and set the client to upgrade that collection but it is not working.

Thanks for the help Niall. Was the FQDN issue causing the product id error? I was confused because the log originally said success for the FQDN. My bad on that one.

This is what I have (with the correct product key): I also just noticed the configmgrsetup.log shows <07-24-2017 12:30:49> Failed to create process of SetupWpf.exe. return value 1 1/1/1601 12:00:00 AM 286688080 (0x11168350)

I am running into a problem when I am installing SCCM from the script. It is telling me the product code is incorrect 7/24/2017 12:30:49 PM: ConfigMgrSetupWizard Verbose: 1 : Received error [The product key is not correct. You must enter the entire 25 digit product key.] from native code. I know I can install it without the script as it takes the license key just fine manually but I would like to see what I am doing wrong with the script.

Does anyone know why having the On Screen Keyboard enabled crashes some programs? We have an in house software database program that crashes as well as Worldox document management program. Both work fine when the OSK is disabled but crash when it is enabled. It is a mild inconvenience as not that many people use the OSK but, especially some SP4 users are upset.

Ok. I was planning on taking my time doing it side-by-side so that's good news. I was worried about having them both in AD. When it came to go live did you just deploy the client from the new 1607?

We currently have a functional SCCM environment in our organization. We have a primary site server running Server '08, SCCM 2012. It is functional but messy. I am wanting to install SCCM CB on a new Server 2016 from scratch and take down the old. I have installed a lab environment successfully. My concern lies in installing a new environment when an old one already exists. How will it impact me and what steps do I need to watch out for when installing the new environment when there is already an instance of SCCM on our domain. How does it impact AD? What about the existing clients? Is there anything that I am not aware of that I should be concerned with in this endeavor?

I just installed it so that you'd be able to. I would appreciate that.

Yes it is. I am on the server if that makes a difference (the hklm\software\ms\sms\setup path only exists on the server)

I am having trouble with the script to create the device collections and I'm not sure why... Would you mind taking a look... I'm sure it's just a Monday oversight on my part. Import-Module : Cannot bind argument to parameter 'Name' because it is null. At F:\Sources\windows-noob Required Windows 10 Upgrade\CreateWindows10DeviceCollections.ps1:184 char:14 + Import-Module <<<< $console + CategoryInfo : InvalidData: (:) [Import-Module], ParameterBindingValidationException + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.ImportModuleCommand Get-PSDrive : Cannot find a provider with the name 'CMSite'. At F:\Sources\windows-noob Required Windows 10 Upgrade\CreateWindows10DeviceCollections.ps1:185 char:22 + $SiteCode=Get-PSDrive <<<< -PSProvider CMSite + CategoryInfo : ObjectNotFound: (System.String[]:String[]) [Get-PSDrive], ProviderNotFoundException + FullyQualifiedErrorId : GetLocationNoMatchingDrive,Microsoft.PowerShell.Commands.GetPSDriveCommand Connecting to Set-Location : The given path's format is not supported. At F:\Sources\windows-noob Required Windows 10 Upgrade\CreateWindows10DeviceCollections.ps1:188 char:3 + cd <<<< "$($SiteCode):" + CategoryInfo : InvalidOperation: (C:\Windows\system32\::String) [Set-Location], NotSupportedException + FullyQualifiedErrorId : ItemExistsNotSupportedError,Microsoft.PowerShell.Commands.SetLocationCommand Set-Location : Cannot find path 'C:\Windows\system32\:' because it does not exist. At F:\Sources\windows-noob Required Windows 10 Upgrade\CreateWindows10DeviceCollections.ps1:188 char:3 + cd <<<< "$($SiteCode):" + CategoryInfo : ObjectNotFound: (C:\Windows\system32\::String) [Set-Location], ItemNotFoundException + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetLocationCommand

Hi Niall, I have a quick question. We have been using SCCM 2012 for years. I did not set it up originally and am not happy with some of the decisions that were made so I am "upgrading" to 1702, Server 16, SQL 16 but am setting it up from scratch rather than doing a true upgrade. My question would be do I still need to do the Active Directory steps or is that already done from 2012? I guess what I am really asking is, is there anything I should watch out for when spinning up a new server with new a sccm installation and using it in an environment that already had 2012 running?