anyweb

glad to hear it, and thank you for the thanks

not yet, maybe this weekend or tonight, i'll spin up the lab again, actually i've started writing a blogpost now and hopefully it'll be finished tonight.

so you did an inplace upgrade of the operating system, did you also restart all the SMS related services after the upgrade ? including post upgrade tasks such as those mentioned here ? https://byteben.com/bb/sccm-site-server-in-place-upgrade-from-windows-server-2012-r2-to-windows-server-2019/#4

I haven't tested constrained language mode with this, but according to this blog post paragraph, you can do as follows let me know how you get on

Introduction Microsoft released TP2008 yesterday, more details here, but I was busy building my deck so I didn’t blog anything, but I did the upgrade and waited until today to see what’s new. And as usual, it’s a list of loads of new additional features. So what is new and exciting in this technical preview release of ConfigMgr? Collection query preview When editing queries for collections you can now preview the results real time. So let’s try it. I created a new collection and added a query for Windows 10 version 1903. You can now click on the green triangle to see the results of your query. and it displays like so… Cool stuff ! This means you can test your queries while creating a collection. Analyze SetupDiag errors for feature updates With the release of Windows 10, version 2004, the SetupDiag diagnostic tool is included with Windows Setup (previously you’d have to download it if you wanted to review it’s data). If there’s an issue with the upgrade, SetupDiag automatically runs to determine the cause of the failure. Configuration Manager now gathers and summarizes SetupDiag results from feature update deployments with Windows 10 servicing. To see these errors, check the Windows 10 servicing dashboard in Software Library. Mine is currently blank, I guess I need to start upgrading existing devices to 2004 and see what data it gathers. Collection evaluation view Microsoft has integrated the functionality of Collection Evaluation Viewer into the Configuration Manager console. This change provides administrators a central location to view and troubleshoot the collection evaluation process. The console now displays the following information: Historic and live information for full and incremental collection evaluations The evaluation queue status The time for collection evaluations to complete Which collections are currently being evaluated The estimated time that a collection evaluation will start and complete I’m not sure why mine has no data yet but i’ll see if I can get it to populate. Delete Aged Collected Diagnostic Files task You now have a new maintenance task available for cleaning up collected diagnostic files. Delete Aged Collected Diagnostic Files uses a default value of 14 days when looking for diagnostic files to clean up and doesn’t affect regular collected files. The new maintenance task is enabled by default. See task sequence size in the console This is interesting, and will show you the size of your task sequence. It’s a new column which is enabled by default, I’m not sure why all my task sequences are reporting 0KB but I’ve asked Microsoft PG for comment. So it turns out if you edit any task sequence (add a comment in the description or whatever) then Apply the changes then it will display the task sequence size (thanks to Adam Gross for the tip). Monitor scenario health Configuration Manager is complicated to troubleshoot. It’s especially complex to understand system latency and the backlog between components. Cloud service-attached features increase that complexity. You can now use Configuration Manager to monitor the health of end-to-end scenarios. It simulates activities to expose performance metrics and failure points. These synthetic activities are similar to methods that Microsoft uses to monitor some components in its cloud services. Use this additional data to better understand timeframes for activities. If failures occur, it can help focus your investigation. There are more features, but these were the one’s I looked at, as always Microsoft is innovating ! cheers niall

Hi @Mayur ok then you are contradicting what you said earlier, oh well, if it is indeed returning the correct ip address then that means godaddy is working, the 'request timed out' could be because of your firewall solution blocking ping or windows firewall itself, and it's not the end of the world, you now need to verify that you can browse the IIS welcome page on your url by browsing on a phone (not connected to wifi, use 3g instead..) to the http://pki.windows-noob.com obviously use your own url for this testing. if that doesn't work, then your vyos firewall is not routing port 80 correctly to the local ip address of the webserver cheers Niall.

then you may have issues with godaddy, because the ip address (in yellow) is returned from the DNS provider, if it returns no ip address then it is not resolving the url to an ip. use https://dnschecker.org/ to verify what your configured url is telling you

so are you saying the you don't see any ip address like I have higlighted in yellow below ?

you are not answering my question, if you ping your pki.yourdomain.com it should return the IP address you configured in godaddy, does it ? and does that ip address also correspond to the internet ip address which www.whatismyipaddress.com revealed on the webserver ?

after you ping the url pki.whatever.com it should list the correct INTERNET based ip address which you are sharing internet from in your pki lab, does it ?

well it could be your firewall solution that's blocking it, i don't know, I use smoothwall and it works just fine. when you ping the url, it should return the correct ip address, does it ?

I am not able to ping nor browse from mobile/laptop/desktop. what do you mean you are not able to ping ? what ip address does it resolve to ?

hi Muray, this does not look like my setup, but then again DNS providers have different views of the same thing, obviously you need to use your own domain name (eg: pki.mydomain.com) and your own internet ip address once you've made the change in your DNS provider, you can test if it works by pinging the url and see what ip address it returns, or try and browse the url from your phone (external network) for example you can ping or browse http://pki.windows-noob.com it should respond as the lab is online now.

hi Muyar, the 192.168.x.x address at godaddy will never work, as that's a local lab ip range, it must instead point to the actual internet ip address you have in your lab (use www.whatismyipaddress.com to find out)

ok, if you really want to use the capture method (and i recommend against it), then you can capture the wim of the OS partition only, and deploy that in your deploy operating system task sequence https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/capture-and-apply-windows-system-and-recovery-partitions but really, don't do that, instead, use default Operating System wim files from microsoft (they are updated monthly now), and add the customizations in your task sequence instead.

Hi Muyar, thanks, so you configured the DNS cname in your DNS provider but it's not redirecting to your webserver, is that correct ? did you also configure smoothwall ?

Introduction I received a brand new HP Laptop (HP EliteBook 830 G6) to verify our current Autopilot setup, and I went through OOBE. All seemed well and I was curious about the version of Windows shipped so I ran WinVer. The following screen appeared. Notice how the registered owner and registered organization fields are automatically populated with HP's default settings, this was a Windows Autopilot enrolled HP delivered with HP's business clean image (no bloatware). The following registry key reveals where those values are set. HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion if the following REG_SZ keys are missing: RegisteredOrganization RegisteredOwner You'd see the following instead. So now that I knew why I was seeing those values I decided to fix it. Step 1 - Add a PowerShell script to Endpoint Manager In Microsoft Endpoint Manager select Devices and then select Scripts as shown here (alternatively, choose Devices, Windows, PowerShell Scripts...) Click on Add and select Windows 10 as the operating system. Fill in the Name of the script and a description, note that the Name does not have to match the actual name of the script. Note: you must be a logged in member of windows-noob.com to download this script. Next, point it to the PowerShell script which you can download here and select to Run this script using the logged on credentials. Next select the Groups you want to assign it to, I selected my Windows 10 Autopilot DEVICES group Step 2. Test an Autopilot device Start OOBE (out of box experience) on an Autopilot enrolled device. move through the screens and you'll have to enter your credentials at the welcome to your Tenant name screen after signing in successfully the Enrollment Status Page will appear (if configured to do so) Step 3. Verify changes If everything went according to plan, after a while Windows Autopilot will be completed and you'll be logged on to the desktop, you can now verify the changes by typing WinVer. Troubleshooting If things didn't go as planned take a look at the IntuneManagementExtension.log with CMTrace. It's found in the C:\ProgramData\Microsoft\IntuneManagementExtention\Logs folder and confirm that the script ran successfully and that it ran in User context (user was a local admin in this case). If you need to run it as SYSTEM then change the variable for RegisteredOwner in the script to something else. job done ! Downloads Here's the PowerShell script used above ConfigureRegistered_User_Org.ps1

hi, which Powershell script are you using exactly ? and have you verified that the computer is in a collection with the policy targeted to it during OSD ?

Why oh why do this, please explain ? most people nowadays deploy a clean WIM and add apps/settings during the task sequence or use Windows Autopilot

SysAdmin Day has arrived, and with it, gratitude for all the unsung heroes that 2020 has needed. Your hard work has made it possible for all of us to keep going, despite all challenges thrown our way. Now it is Altaro’s turn to thank YOU. If you are an Office 365, Hyper-V or VMware user, celebrate with Altaro. Just sign up for a 30-day free trial of either Altaro VM Backup or Altaro Office 365 Backup – it's your choice! What can you win? Receive a €/£/$20 Amazon voucher when you use your trial of Altaro Office 365 Backup or AltaroVM Backup Get the chance to also win one of their Grand Prizes by sharing your greatest 2020 victory with Altaro in an up to 60-seconds video. What are you waiting for? Sign up now!

welcome to the forums Sunny

hi Mniceguy81, i'm fine, working in my back garden keeping myself busy before my vacation ends and back to work... for your questions. 1. as long as the account is a local administrator of the computer that is fine, doesn't need to be the built in local admin account 2. it's up to you, to keep it simple create a new lab, and later add pki to it, that's the way i do it, in other words, i create a SCCM lab first (http) then go through the PKI labs (8 parts) then convert sccm to https (2 parts), you'll find it all here > good luck !

what have you tried exactly ? and what didn't work ?

Why are you using SCCM 2012 R2 it's been replaced by the much more feature rich Microsoft Endpoint Manager 2002, as regards capturing domain joined computers, not a good idea as there will be things left behind from the act of being domain joined on that machine, however, if you are determined to do this (and I wouldn't) then take a look at this blog post.

i presume the collection is setup using a query, can you share the query so we can see what you are looking for... also, have you checked that the computer is actually present in that specific OU prior to ending up in the collection ?