Jump to content




anyweb

Root Admin
  • Content count

    7,423
  • Joined

  • Last visited

  • Days Won

    271

anyweb last won the day on December 15

anyweb had the most liked content!

Community Reputation

404 Excellent

About anyweb

  • Rank
    Administrator
  • Birthday 11/24/1966

Contact Methods

  • Website URL
    http://www.niallbrady.com

Profile Information

  • Gender
    Male
  • Location
    Sweden
  • Interests
    Deploying Operating systems and more with System Center Configuration Manager

Recent Profile Visitors

4,131,083 profile views
  1. no don't go changing stuff in WSUS, it's ConfigMgr's job to do that, you can do an inplace os upgrade, it's supported, but you'll have to uninstall WSUS first
  2. this guide is for setting up a lab, and it's based on server 2016 only, I havn't tested it with Server 2012r2 so your results may vary, please use the newer version of my lab. thanks
  3. well something is wrong with your internet, possibly DNS, the 0x80072ee7 error means this The server name or address could not be resolved Source: Winhttp -----
  4. do you actually have an internet connection on that computer ? is there a proxy configured ? INFO: Downloading http://go.microsoft.com/fwlink/?LinkId=841442 as ConfigMgr.LN.Manifest.cab $$<Configuration Manager Setup><12-07-2017 14:07:47.233+00><thread=5288 (0x14A8)> INFO: checking if there's an explicit proxy server. $$<Configuration Manager Setup><12-07-2017 14:07:47.233+00><thread=5288 (0x14A8)> ERROR: WinHttpSendRequest failed 80072ee7 $$<Configuration Manager Setup><12-07-2017 14:07:59.285+00><thread=5288 (0x14A8)> ERROR: Download() failed with 0x80072EE7 $$<Configuration Manager Setup><12-07-2017 14:07:59.285+00><thread=5288 (0x14A8)> ERROR: Failed to download language pack manifest (0x80072EE7) $$<Configuration Manager Setup><12-07-2017 14:07:59.285+00><thread=5288 (0x14A8)>
  5. not sure i understand your question and by the way there's a newer version of this guide here
  6. Daniel shows you an example of how to do that here http://www.danielclasson.com/powershell-script-for-configuring-configuration-manager-2012-collection-update-settings/ cheers niall
  7. the upgrades from 1703 to 1709 for me (in testing) have gone without a hitch, however... after the upgrade is done and after one or two reboots we've witnessed a white spinning circle of dots which never completes, it just stays there, we've seen this on Surface Pro 4 and HP X360 g2 and as of yet have not identified the cause, once we figure it out i'll post an update here.
  8. hi and Welcome ! the first thing to fix is your SMS_MP_CONTROL_MANAGER, you need to find out what is wrong with the management point (MP) as that is how your clients communicate back to SCCM, so right click on the component, show messages, all, and see what it tells you, those errors need to be fixed first and then we'll move on towards the other issues, feel free to post the errors here and we'll do what we can to help cheers niall
  9. good point, I'm not authenticating against the proxy in this example (was not needed) but if you need to use the following in addition to the above reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyUser /t REG_SZ /d username reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyPass /t REG_SZ /d password
  10. can you post your entire smsts.log as an attachment so I can take a look ?
  11. Introduction Microsoft describes Windows AutoPilot as “Windows AutoPilot is a suite of capabilities designed to simplify and modernize the deployment and management of new Windows 10 PCs”. That roughly translates to a cloud based method of deploying new Windows 10 devices. To use Windows AutoPilot you'll need to fulfill some requirements namely: Devices must be registered to the organization Company branding needs to be configured Devices have to be pre-installed with Windows 10 Professional, Enterprise or Education, of version 1703 or later Devices must have access to the internet Azure AD Premium P1 or P2 Microsoft Intune or other MDM services to manage your devices Windows 7 is not going to gain access to this new technology and new devices are the target (from the OEM for example). There is a way to re-provision existing Windows 10 devices via a Windows Reset but I’ll cover that in another blog post. This post will explain how you can get around one obstacle that currently exists (29th of November 2017) with Windows AutoPilot, and that is the ability to connect to the Internet across a Proxy. Windows AutoPilot needs to be able to connect to the internet to do it's magic, and proxies can throw a spanner in that. In this post I assume you have already enrolled a Windows 10 device into Windows AutoPilot and that you plan on connecting the new Windows 10 device to the internet via a Proxy. All screenshots are from a Windows 10 version 1709 computer (Fall Creators Update). Windows AutoPilot default behavior (with direct connection to Internet) During OOBE (Out of Box Experience) on a Windows AutoPilot enrolled device, the following should be observed in the order listed below: 1. Vocal Intro from Cortana (unless it's a Hyper-v VM) 2. Let’s start with this region. Is this right? [United States] <Yes> 3. Is this the right keyboard layout? [US] <Yes> 4. Want to add a second keyboard layout? <Skip> 5. Now we can go look for updates…(takes some time to download things and do magic) 6. Welcome to [Tenant Name] <Next> Windows AutoPilot default behavior (with a proxy) When a Windows AutoPilot enrolled device is booted behind a Proxy, it goes through these steps in OOBE: 1. Vocal Intro from Cortana (unless it's a Hyper-v VM) 2. Let’s start with this region. Is this right? [United States] <Yes> 3. Is this the right keyboard layout? [US] <Yes> 4. Want to add a second keyboard layout? <Skip> 5. Let's connect you to a Network. In the above scenario, the Windows AutoPilot magic that should occur cannot take place due to a lack of direct Internet connectivity and therefore the following things will not happen: Automatically join devices to Azure Active Directory (Azure AD) Auto-enroll devices into MDM services, such as Microsoft Intune (Requires an Azure AD Premium subscription) Restrict the Administrator account creation Create and auto-assign devices to configuration groups based on a device’s profile Customize OOBE content specific to the organization In other words, Windows AutoPilot can't configure the device and you'll need to do those actions manually. Solution Before starting this step, download the following PowerShell script SetWindowsAutoPilotProxy.ps1 edit the highlighted variables below and replace them with your proxy details copy the edited script to your target Windows AutoPilot device. Next, boot the Windows 10 device that is enrolled into Windows AutoPilot, once OOBE starts it will take you to the Let's start with region question. Press Left shift and F10 keys together, a command prompt should appear. In the cmd prompt that appears type the following PowerShell then type the following Set-ExecutionPolicy UnRestricted Next, run the script by typing .\SetWindowsAutoPilotProxy.ps1 and press Enter. The script will run quickly and you'll see a reboot prompt, you can ignore it, if you look carefully you can see your proxy settings in the PowerShell output. This will gracefully reboot the computer with the Proxy settings in place and it will start the OOBE again except this time with a direct connection to the internet (via the Proxy). The OOBE experience after configuring proxy settings After the reboot you'll get prompted with the usual OOBE screens, followed by Is this the right keyboard layout ? and whether you Want to add a second keyboard layout ? and the License Agreement screen and now that the proxy settings are set, it will check directly with the Internet to verify for updates, after accepting the EULA you'll get to the Windows AutoPilot specific part of the process. You’ll know when that happens because your tenant name (and branding if configured) will appear. After entering your credentials Windows setup will configure your profile and depending on your settings, you may have to confirm Microsoft Verification for Windows Hello for Business (setup PIN) Enter and confirm your PIN after confirming the PIN you’ll see the Enrollment Status Screen (if configured in Windows Enrollment options in Intune), note that this is a Windows 10 version 1709 capability.. Once you click on Got it, Windows is ready to use and Intune policies are applied (such as Applications, start menu and more.) That’s it, job done. cheers niall
×