anyweb

that sounds very likely, so it's working fine now apart from the unexplained past failures ?

hi, no you only attached a screenshot of the error, i need the entire smsts.log file

First of all: Great post! is so helpfull! thanks ! It's working like a charm but i have some issue when checks for pending reboot, can you expand on this, do you mean that it is not detecting pending reboots for you or ?

did you see this bit ? Specifies the local administrator password. This value is ignored if the Randomly generate the local administrator password and disable the account on all supported platforms option is enabled.

hard to tell without reading the entire log to see the failure properly can you attach it ?

is the ps1 script actually available in the package mentioned ?

ok i've modified the msi again please re-download it and let me know

i'll look into it...

ok here's the USER version of the msi with my 3 edited scripts added, i've not tested it, that's up to you so go ahead and test it and if I need to fix something let me know, Download the User version of the MSI here: TriggerBitlockerUser.msi cheers niall

hi Bob, I based my version of the script on the end user being a local admin, if you need the non-admin version I can supply that also

hi if you do teamviewer I can take a look,

Microsoft have released the latest Technical Preview release of System Center Configuration Manager namely System Center Configuration Manager Technical Preview 1712. There are two main versions (of Configuration Manager) available: System Center Configuration Manager (Current Branch) System Center Configuration Manager (Technical Preview) System Center Configuration Manager (Current Branch) is designed for use in production, for managing anything from small to very large Enterprises whereas System Center Configuration Manager (Technical Preview) is for lab environments only and is limited to 10 clients. The Technical Preview releases are released monthly, and contain the latest and greatest features being trialed in the product, and usually these new features are the result of feedback from uservoice. Current Branch releases on the other hand are released only a few times per year and contain stable, tested features that are mature enough to release into production environments. System Center Configuration Manager Technical Preview 1712 is now available. This release offers the following new features: Surface Device dashboard improvements – The Surface dashboard now displays firmware version for Surface devices rather than operating system version. Improvements to Office 365 client management dashboard – The Office 365 client management dashboard now displays a list of relevant devices when graph sections are selected. Install multiple applications in Software Center – Click the multi-select icon on the Applications tab in Software Center. In this mode, select multiple applications and then install all together using the Install Selected button. Client-based PXE – Configure clients to respond to PXE requests without adding the distribution point role. This release also includes the following improvements based on your feedback from UserVoice: Renamed collections display in existing collection membership rules – When a collection is a member of another collection and it is renamed, the new name is updated under membership rules. Allow user interaction when installing applications as system – Now users can interact with an application installation user interface in system context even during a task sequence. Do not automatically upgrade superseded applications – In this release you have the option to configure an application deployment to not automatically upgrade any superseded version. Device list displays primary user – Device lists under Assets and Compliance, Devices, now display the primary user by default. The last logged on user can also be added as an optional column. Upgrading to Technical Preview 1712 Normally I’d guide you through the upgrade process using screenshots and text, but for this release I recorded a video of the entire upgrade process from start to finish and it’s available for you to watch on youtube.com here. Recommended reading Capabilities in Technical Preview 1712 for System Center Configuration Manager – https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1712 Update 1712 for Configuration Manager Technical Preview Branch – Available Now! – https://cloudblogs.microsoft.com/enterprisemobility/2017/12/16/update-1712-for-configuration-manager-technical-preview-branch-available-now/ What’s new in Configuration Manager 1712 Technical preview AKA “MVP Edition” – http://ccmexec.com/2017/12/whats-new-in-configuration-manager-1712-technical-preview-aka-mvp-edition/ Upgrade to System Center Configuration Manager – https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/upgrade-to-configuration-manager

thanks ! I appreciate the feedback and would be interested in seeing what you do with it :-)

here it is

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

so you updated to 1710 and rebooted and still see this ?

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

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 -----

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)>

not sure i understand your question and by the way there's a newer version of this guide here

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

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.

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

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

can you post your entire smsts.log as an attachment so I can take a look ?