webguy

Thanks. I'll test it out here shortly on a device that I have tricked into thinking it needs to be rebooted. Curious I see that for the pending reboot you returned it to Exit99 I thought you said for the task sequence to kick off after the reboot it would have to be Exit0. Either way I will test and adjust. I will suggest for sanity of the end user to do the hardware check before disk space, vpn, etc. no sense having them clean up disk space, connect power or disconnect from VPN if they are then going to be told their hardware is not compatible with the upgrade. Just a thought. /Paul

Thanks will do. I do however see an issue with the logic as it stands right now based you your response. You do the pending reboot check before you check VPN connection, disk space, battery power or hardware support. If the computer has a pending reboot you are telling the system to Exit0 and reboot which in theory should kick off the task sequence however if the system is not compatible or not enough disk space or not on AC power none of those items would be checked. Better logic would be: - Hardware Support - Power - Disk space - VPN - Pending Reboot Thoughts?

So if I am reading the above correctly after the reboot the task sequence should start automatically or will the user still have to login? Won’t the wrapper script run again?

Thanks. After comparing the updated script I have a question. For pending reboot check it appears you removed the AddRunOnce sub and changed the Exit99 to Exit0. My question is once the computer restarts how will it know to kick off the task sequence? Also won't adding Exit0 which has the entry to remove the NumberOfUpgradeDefers thus resetting the counter back to zero before the task sequence has completed.

It's been a while. All is good, just saw your fix for the reboot check, I will have to apply that to my modified script. I do have a question as it relates to using this process to upgrade to the next release of Windows 10. If a user defers the install to the last minute it registers in the registry under HKCU:\Software\windows-noob the number of deferrals left. If after upgrading to Windows 10 1703 they have 0 deferrals left when you apply this process for 1709 it will immediately launch the upgrade without any opportunity to defer. I've gone through the code a few times and have not seen anywhere that once the task sequence kicks off it clears these registry entries. Just a thought but it might be beneficial to add this functionality in, otherwise for each upgrade you will have to change the key that is written. I was going to write something but my VBScript is lousy, but I thought I would check here first to see if you had some solutions especially if you have used this method to upgrade from previous versions.

In the .HTA file I changed the following line: If DPI > 120 then DESIGN_DPI = 160 'dots per inch 'DESIGN_WIDTH = 450 'pixels 'DESIGN_HEIGHT = 365 'pixels DESIGN_WIDTH = dw 'pixels DESIGN_HEIGHT = dh 'pixels to If DPI > 120 then DESIGN_DPI = 96 'dots per inch <<--- 'DESIGN_WIDTH = 450 'pixels 'DESIGN_HEIGHT = 365 'pixels DESIGN_WIDTH = dw 'pixels DESIGN_HEIGHT = dh 'pixels This seems to have solved my scaling problems. You still need to adjust the Window size from above, reference: Call ReSizeWindow (425,335,500,535) in the code above the ReSizeWindow function. When the DPI is <120 the formula uses the design width and height 500,535 respectively. However when the DPI is >120 it will use the numbers 425,335 and then factor accordingly. To get mine to work I had to reduce those numbers somewhat but it now almost displaces the same as on a system with DPI set to 96.

Thanks, I will take a look here shortly and see. With regards to the SUM collections are they more in reference to Windows Servicing, or are you using them in relation to Windows Update deployments? One other issue I came across today in testing is with the WindowsResize for the HTA. I had to adjust the original window size to: Before Progress Bar: 425,335,500,545 After Progress Bar: 425,335,500,595 And it loads fine for anyone with a DPI setting of 96. But we came across a few systems with DPI greater than 120, this one was 144. And the box actually shrunk in size and does not show any of the buttons though they are their just not visible in the box. Any thoughts on this one?

Thanks. Much appreciated. So I'm not sure I understand the purpose of the SUM Collections? Where would they by used in terms of Windows 10? Is this more for servicing? One other item in the script I noticed, Line 277 says # add some exclude rules (exclude LTSB from all SUM collections except SUM Windows 10 LTSB), yet the code has SUM Windows 10 Other being excluded from the collections not LTSB. Not sure which is supposed to be correct. But this is probably mute anyways until I get a better understanding of what SUM is used for

Nope I just downloaded the script you have attached to this post, unzipped it and copied the file to my lab machine. The file date on the scrip is 2017-03-22 If I make the following change then it works: - if ($CollectionName -eq $Collection_1 -or $CollectionName -eq $Collection_2 -or $CollectionName -eq $Collection_3) + if ($CollectionName -eq $Collection_1 -or $CollectionName -eq $Collection_2 -or $CollectionName -eq $Collection_3 -or $CollectionName -eq $Collection_8) The other question I have is about the collection for SUM Windows 10 Other, why there there a query of: select * from SMS_R_System where SMS_R_System.AgentName = 'Manual Machine Entry' trying to figure out its purpose as I also see that query in OSD Build and OSD Limiting. And maybe I am not understanding but what is the actual purpose of the SUM Collections?

Just a note, I was running the CreateDeviceCollectionsWindows10.ps1 script in our lab and it fails to create the OSD collections. With the exception of the OSD Servicing Required Deployment collection. Looked at the script and there are when it tries to create OSD Limiting it is using itself as the limiting collectionbut it hasn't created it yet. Then of course any collection that needs OSD Limiting as the limiting collection also fails to create. Are there supposed to be queries or collections used in the OSD collections or are they blank.

Ok I think I have everything in place now. Starting the task sequence testing. A few quick questions: One you hit upgrade now you have a 4-hour timer, is that to allow for the files to be transferred to the computer or just to give the user some indication when the update will start? While not mentioned in your notes is there any advantage to setting the deployment options under Distribution Points? For example: Download all content locally before the task sequence starts? In the wrapper.vbs you reference the VPN, if the preface behind this to ensure the content is downloaded, would item 2.1 negate the need for testing for VPN connectivity? For testing if you defer the update is there a way to force task to kick off again?

Yeah, found them but not where I was having problem, but it seems to work now. I could not make the VPN test work with Windows 10 as it was not coming back as 0.0.0.0. Ended up doing this and it seems to work. 'Check for VPN 'UpgradeLog.WriteLine TimeStamp & " " & "Checking for VPN connectivity..." Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_NetworkAdapterConfiguration") For Each objItem In colItems If(InStr(objItem.Description,"Cisco")) Then msgBox objItem.Description & " - Enabled: " & objItem.IPEnabled IsVPNConnected = objItem.IPEnabled End If Next If(IsVPNConnected) Then 'UpgradeLog.WriteLine TimeStamp & " " & "VPN found informing user..." msgBox "Cisco VPN connection detected, please do not try to run the Windows 10 upgrade on a VPN connection. Try the upgrade in the office instead." AddRunOnce() Exit99 Else msgBox "VPN not detected" 'UpgradeLog.WriteLine TimeStamp & " " & "VPN not found..." End If 'For Each objItem In colItems ' msgBox objItem.DefaultIPGateway ' strDefaultIPGateway = Join(objItem.DefaultIPGateway, ",") ' If strDefaultIPGateway = "0.0.0.0" Then ' 'UpgradeLog.WriteLine TimeStamp & " " & "VPN found informing user..." ' msgBox "Cisco VPN connection detected, please do not try to run the Windows 10 upgrade on a VPN connection. Try the upgrade in the office instead." ' AddRunOnce() ' Exit99 ' Else ' 'msgBox "VPN not detected" ' 'UpgradeLog.WriteLine TimeStamp & " " & "VPN not found..." ' End If 'Next

Thanks, I found the problem my system was running 1607 and we are applying this to 1703. Once I changed the Target Build at the top to the correct build it all worked out. Now I'm just fighting the pending reboot check and battery check as I am testing those functions out. The system does not seem to have a pending reboot and it moves on, but it says its on power when its really on battery and it keeps telling me the drive space is low when I have 100GB free. I downloaded the scripts again, both have a date of 10/10 but I am noticing some differences when I compare the two, so looking for differences now.

Hmmm, I've done that a few times but the HTA never loads, I'm assuming the powershell script that you are loading is the Start-Upgrade.ps1. I'll go back and do some more digging. Another question regarding UserIgnoringHTA, for testing purposes I lowered the threshold from 8 hrs to 5 minutes. The window moves as intended but then it closes right away, is this as intended? Would it not be better to move and then close if not touched after 5 minute.

Another question about the upgrade.hta file. Just modifying the text in the file to meet out needs. When executing the HTA file it loads and I have the option to select the checkbox and upgrade now or defer, if I click defer the registry entries are created which is good, but when I load the file again after making some additional adjustments the number of deferals is still listed as 5, it does not appear to be declining. Any thoughts on where to look or why this might be occurring. I can post the HTA file if needed.