Config_Mgr_noob

Thanks for the heads up. Was just about to upgrade when I bumped into your forum. Will wait until 1702 comes out. Thanks.

They were pretty much 1511 security updates and cumulative updates injected. The crazy part is, I injected the same updates to my Win10 image using the offline servicing. Not sure it if was during the process that it may have corrupted the In-place package? On another note, after I was able to successfully do an In-place upgrade from Windows 7 to 10, I am being prompted for the Ctrl+Alt+Del sequence to login. I looked into the computers secpol and saw that the "Interactive logon: Do not require CTRL+ALT+DEL" is set to 'Not Defined'. Shouldn't this not require a user to press Ctrl+Alt+Del to login? We are trying to aim for all in-place upgrades to not be prompted to do Ctrl+Alt+Del. Are these settings carrying over from Windows 7?

I believe my upgrade package got corrupted during update injection using offline servicing. Deleted my package and imported a more recent version of Windows 10. Hopefully this doesn't happen again when I inject updates to the new package.

I used the Offline servicing method to update the installer package.

Hello everyone, Not sure if I'm posting this on the right forum so please let me know and I'll post at Windows 10 forum. I have been testing out the new Windows 10 In-place upgrade with specified drivers within the task sequence. I have been successful at upgrading my test machines from Windows 7 to 10. Recently, I decided to inject updates to the upgrade package to be able to apply updated Windows 10 to make the process much smoother. Now, after applying the task sequence and rebooting into the Operating System, I get a black screen with the cursor. After I do a force reboot, I am prompted with a blue background and the spinning white dots. Not sure if this has to do with the updates I injected or something else? If so, is there a way to remove injected updates from the Upgrade Package? Has anyone come across this yet?

Hey anyweb, I just tried a few test and I believe I figured out what was my initial problem. I re-imaged a PC with Windows 7 and it had the old SCCM client, 5.00.8239.1000 installed. My site server is currently at 5.00.8458.1000. As soon as I upgraded the test PC to 5.00.8458.1007, the upgrade took place and the directory changed to reflect the 'c:\drivers' variable. Now I my smsts.log are showing the appropriate executing command line. Thanks again!

Ok great. Thanks, anyweb!

Hi anyweb, Perfect! I see that. But is there a way to clean up with index to not have SCCM show all the languages?

Hello everyone, I just recently started configuring my sccm for WIN 10 servicing. As I began to download updates and upgrades from Microsoft, the downloads began to pull down all languages for both the feature and Upgrade patches for Windows 10. I checked on the language configuration within the SUP and only English was ticked. I went to WSUS console and noticed that in here all languages were ticked. I made the changes to only have English ticked and resynced my Windows 10 Updates. Unfortunately, all languages are still being displayed. Is there any way I can delete/remove all non-required updates with different languages from SCCM? I have already ran the "Server Cleanup Wizard" at the WSUS console level and resynced but still no avail. Am I missing something here on how to remove unwanted updates from SCCM console? This can be inefficient when trying to create Servicing Plans to apply only particular updates i.e. Enterprise and English only updates.

I'm sending 2 smsts.log to you via message. The first log is for one laptop that was successful using the method that noahw86 provided and the second smsts.log shows a failed attempt to inject drivers that I just tried to do. Not sure why the log shows the "drivers01" for the driver location instead of the actually indicated directory within my TS. Can you see why the OSD process is not changing the directory as specified?

Hi anyweb, I know this is a few months old post but wanted to try and see if anyone here can help. I am having the exact same issue as noahw86 where the directory is not being created during the "Download Package Content" step. I specified the directory as indicated on this tutorial but the directory does not get created and the driver content looks like it gets downloaded within the default task sequence directory. So when the "Upgrading Operating System" step runs it fails since I'm indicating the variable %Drivers01%. I attached a screenshot of my smsts.log below to show you the executing step and how the variable is not being changed. Could this be a bug within 1602?

Hey anyweb, Not sure if you had the time to view my last post? I tried again filtering my updates by NAP eval but still all are showing No. Would you happen to have time to assist?

Yup, verified that all of my Software Updates are set to 'No' under NAP Evaluation.

No worries, I understand you get very busy. Thank you for your reply. Yes, I am actually available (surprisingly) right now if you are? Where should I send you the information for the log in session?

Hey anyweb, Not sure if you had the time to view my log above but I did bump into another forum who had the same issue. However, when I checked for the NAP evaluation for each of my software updates, they were already all set to 'No'. Should I place them a NAP evaluation schedule and re-run the 1606 prereq check?

Hi anyweb, Thanks for the suggestion. The Restart Computer step seemed to do the trick. The only thing I had to do is move some steps around like the MDT toolkit package after the reboot and the Format and Partition UEFI step in front of the Restart step. On a side note, I do see the background image to be oversized still but I don't mind that part. I hate to be picky but would you happen to know how I can customize the background image during PE throughout the OSD process? Or if you can refer me to any resources I can try out? Thank you again!

Hey anyweb, I was able to upgrade my site to 1602 with both hotfix (KB3155482 and KB3174008). However, when I try to upgrade to 1606, I get prereq check failed. I took a screenshot of the ConfigMgrPrereq.log below. When I go into the Site Servicing Status, it gives me the same error as before regarding the NAP for the Default Client Settings. I checked it again and it is still enabled. Any ideas to try?

Hello everyone, I have a few Lenovo laptops that seem to have the same issue when I try to image it using the UEFI bios setting instead of legacy. The display keeps coming up too large and cuts off a few sections of any UDI windows. I tried injecting the specific laptop's display drivers into the boot image but no avail. I screenshot what I am receiving plus the drivers within my boot image. Has anyone come across this and got this resolved? Not sure what else to do. Thanks in advance!

I don't see any issue popping up within the ConfigMgrPrereq.log. However, I was able to perform the initial 1602 upgrade from within the console. Not sure if I have to go in order from 1511 and onwards but I thought we could skip a few builds and go directly to the latest 1610 build? I did see some errors within the main ConfigMgrSetup.log file. Do you foresee an issue with this moving forward?

Hello, I recently upgraded my primary site to 1511. I'm trying to continue upgrade the site using the built in "Updates and Servicing" tool. After running the prereq, I keep getting a failed message below. Now I checked my Default Client Settings for the NAP and it has already been enabled. Not sure what I'm missing here but can anyone shed some light to this? I feel like it might be a simple answer that I'm overlooking here. Thank you in advance.

Scratch my last post. Got the test to run against the database. Thank you!

Hey anyweb, we've attempted to do it on our production SQL server but was unable since it is hosting live SCCM database. Unfortunately, we do not have any other SQL box that is licensed to run this. I did, however, looked into the SCCM upgrade path here and found I was missing the CU4 (1501) update. I applied it and now have the version prior to the 1511. I ran the testdbupgrade and still the same error message. Any other thoughts you might have on my issue? I can upload you the ConfigMgrSetup.log and ConfigMgrPrereq.log if that'll help out?

Ok, I'll reach out to my sysadmin to see if we can perform the test upgrade on a production SQL server; I'll let you know what the outcome is. Thanks again for all your help and knowledge! Still the best

Sorry for the late reply. Unfortunately, I do not have access to the production SQL server (and the adminsitrators are away) nor do have an available license to apply to the test SQL. Any other suggestions you might have to test out?

Yeah I just spun up a server and used the a trial version of SQL to just test the DB. But if that could be the cause then would the Express still work even if the production DB is on a full version of SQL?