anyweb

here's your first problem, and it will block you from getting any of this to work... <![LOG[PowerShell is not installed]LOG]!><time="19:34:07.669-60" date="01-08-2017" component="RunPowerShellScript" context="" type="3" thread="1228" file="main.cpp:151"> <![LOG[ExecutePowerShellScript(sScriptName, sParameters, sPackageID, sExecutionPolicy, dwPSRunExitCode), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\runpsscript\main.cpp,356)]LOG]!><time="19:34:07.669-60" date="01-08-2017" component="RunPowerShellScript" context="" type="0" thread="1228" file="main.cpp:356"> <![LOG[Run powershell script failed to run, hr=0x80004005]LOG]!><time="19:34:07.669-60" date="01-08-2017" component="RunPowerShellScript" context="" type="3" thread="1228" file="main.cpp:356"> <![LOG[Process completed with exit code 2147500037]LOG]!><time="19:34:07.684-60" date="01-08-2017" component="TSManager" context="" type="1" thread="1140" file="commandline.cpp:1124"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="19:34:07.684-60" date="01-08-2017" component="TSManager" context="" type="1" thread="1140" file="instruction.cxx:805"> <![LOG[Failed to run the action: Run PowerShell Script. Unspecified error are you sure you've added PowerShell to the correct boot image and that you've distributed that boot wim to your distribution points ?

that would only create a device in azure ad, not join it to azure ad domain, currently there's no cmdlet for it but you could create a user exit script that runs sysprep /oobe and then the user would see the OOBE experience to AzureAD join the device Microsoft is aware of this and is planning the ability soon, perhaps with Windows 10 creator update

hi, in a an attempt to make it easier to find the content you need I've created some new categories and moved things around, I hope it make's things better/easier for you, any comments or thoughts about it let me know cheers niall

hi i've removed you login details you should ever post anything like that publicly, anyhow i'm online now (I'm in Europe, Sweden) so GMT+1, send me a mail when you are online and i'll try and connect, i'll pm you my address

thanks for buying my book, i really appreciate it ! the first error is in line 33, this line new-item -path "DS001:\Media" -enable "True" -Name "MEDIA001" -Comments "" -Root "C:\HydrationNoob\ISO" -SelectionProfile "Everything" -SupportX86 "False" -SupportX64 "True" -GenerateISO "True" -ISOName "HydrationNoob.iso" -Verbose so did you install MDT 2013 as per the previous step ? if you cannot solve it i'm happy to do a teamviewer session with you and help you fix it cheers niall

hi can you attach your smsts.log so we can see the steps and failure

Introduction Brad Anderson (corporate vice president for Enterprise Mobility at Microsoft) wrote a blog post today about “What ConfigMgr Customers were Doing During the 2016 Holiday Break” and it revealed how the answer to a question posed by their own staff internally, was answered, here is that question. How many upgrades will there be during the last two weeks of the year? Online Telemetry offered the answer The answer, it turns out, came quickly via telemetry as customers upgraded over the Christmas period even though this was traditionally a ‘no go area’ in terms of change management (as many people would be on vacation and therefore unable to help if something goes wrong). What is this telemetry thing though ? it’s actually something built into the Configuration Manager Current Branch product which gives Microsoft feedback about the how the product is installed, when it was installed, and so on. This data is used to make the product better by gathering meaningful data. This telemetry has it’s own description and it is “Diagnostics and usage data for System Center Configuration Manager” and there is a FAQ here. By default, this telemetry is enabled (Online, persistent connection). You can of course change that setting but you really should stick to the default as anything else will make future upgrades as painful and slow as the ‘old way of doing things’. To decide what type of telemetry to use for your organization by selecting whether the Service Connection Point (a Configuration Manager role) is: Online (recommended) Offline This is the heart of where telemetry comes from in ConfigMgr, and performs many functions such as allowing ConfigMgr to notify you when new updates are available (like 1610 or 1702 when it becomes available) or providing feedback to Microsoft about when and how you upgrade. This data, helps to make the product work better, and allows fixes to problems to get installed or made available quicker than ever before. This same telemetry showed Microsoft that when SCCM 1610 Current Branch was made generally available (December 8th, 2016) that the uptake for this latest update was “both consistent and fast.” This is understandable as ever since Microsoft released the ‘cloud friendly’ System Center Configuration Manager (Current Branch) version of ConfigMgr, customers have been upgrading faster and more often than ever before, regardless of the size of their infrastructure. Why are customers upgrading ? In the past, customers continued using the same old client management software for years (like SMS 2003 or SCCM 2007) and waited until it was no longer supported before jumping somewhat begrudgingly to the next release. Today, that has back-flipped, now more customers are upgrading before product support ends because they want to avail of the new features and security updates that the latest release of ConfigMgr provides, such as supporting Windows 10 version 1607, and they can see what these updates are and they see them as soon as they are available (in the ConfigMgr console) much like a Windows user would see a Windows update being made available. Brads post explains how customers are much more confident about their upgrades and the key takeaways are that System Center Configuration Manager upgrades are: Easier Safer Simple Reliable Low risk These key takeaways are why ConfigMgr admins are happy to upgrade even in a season where upgrades were once a ‘no go area’, and the telemetry is there to prove it. Two years ago, if you tried convincing your change management board about the values of upgrading your ConfigMgr infrastructure during the Christmas period, people would have laughed at you, today upgrading is the norm. Read more > https://blogs.technet.microsoft.com/enterprisemobility/2017/01/06/check-out-what-configmgr-customers-were-doing-during-the-2016-holiday-break/ cheers niall

can you explain this part of your original post "I have multiple language packs installed in my reference image"

looks ok to me, but are all computers using the same timezone ? have you tried condensing it (and speeding up testing) into a test run in a lab, by changing the 'weeks' into 'hours' for example...

well I think it's broken, I've submitted a bug on Connect, please vote it up or comment on it too if you want, Microsoft will fix this https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/3118154/mvp-bug-get-cmalert-is-not-working-as-designed cheers niall

I get weird results too both with SCCM 1606CB and SCCM 1610CB, i'm checking with Microsoft PG and will come back to you

have you tried grabbing the unattend.xml after it's modified after the apply operating system step and before the restart computer step ?

the file in the associated application/package you are deploying most likely....

this is how my SCCM 1610 CB vm looks like now....

i've just turned on that lab again (SQL 2016/Server 2016/SCCM 1610CB) and will let it 'catch up' with itself for a bit and then check the cpu usage, right now it's high but that's expected when resuming a vm from a saved state..... i'm using hyperv are you too ?

the error translates to Failed to verify the executable file is valid or to construct the associated command line. Source: System Center Configuration Manager ----- you can use Cmtrace to convert these errors into meaningful text

does it fail consistently or randomly ? what version of MDT is it occurring with ?

i'd suggest you open a ticket with Microsoft CSS, did you have any replication issues prior to the upgrade ?

thanks for clarifying that, I never got around to it due to time constraints and went the eval route for my blog post, along with a follow up here > How can I change System Center Configuration Manager from an Eval edition to a Licensed edition ? I've also added this point to the guide, thanks again !

yes but you might want to upgrade it at some point Windows Server 2008 R2 with SP1 (x64) - Standard, Enterprise, DatacenterWindows Server 2008 R2 is now in extended support and no longer in mainstream support, as detailed by the Microsoft Support Lifecycle. For more information regarding future support for these operating systems as site system servers with Configuration Manager, see Removed and deprecated features for System Center Configuration Manager. Site servers: Central administration site Primary site Secondary site Site system servers: Application Catalog web service point Application Catalog website point Asset Intelligence synchronization point Certificate registration point Distribution point Distribution points support several different configurations that each have different requirements and in some cases support installation not only on servers, but on client operating systems. For more information about the options available for distribution points, see Manage content and content infrastructure for System Center Configuration Manager. Endpoint Protection point Enrollment point Enrollment proxy point Fallback status point Management point Reporting services point Service connection point Site database server Site database servers are not supported on a read-only domain controller (RODC). For more information, see You may encounter problems when installing SQL Server on a domain controller in the Microsoft Knowledge Base. Additionally, secondary site servers are not supported on any domain controller. SMS_Provider Software Update point State migration point Windows Server 2008 with SP2 (x86, x64) - Standard, Enterprise, DatacenterWindows Server 2008 is now in extended support and no longer in mainstream support, as detailed by the Microsoft Support Lifecycle. For more information regarding future support for these operating systems as site system servers with Configuration Manager, see Removed and deprecated features for System Center Configuration Manager. Site servers: Central administration site Primary site Secondary site Site system servers: Application Catalog web service point Application Catalog website point Asset Intelligence synchronization point Certificate registration point Distribution point Distribution points on this operating system do not support Multicast. Distribution points on this operating system are supported for PXE, but do not support network booting of client computers in EFI mode. Client computers with BIOS or with EFI booting in legacy mode are supported. Distribution points support several different configurations that each have different requirements and in some cases support installation not only on servers, but on client operating systems. For more information about the options available for distribution points, see Manage content and content infrastructure for System Center Configuration Manager. Endpoint Protection point Enrollment point Enrollment proxy point Fallback status point Management point Reporting services point Service connection point Site database server Site database servers are not supported on a read-only domain controller (RODC). For more information, see You may encounter problems when installing SQL Server on a domain controller in the Microsoft Knowledge Base. Additionally, secondary site servers are not supported on any domain controller. SMS_Provider Software Update point State migration point https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-operating-systems-for-site-system-servers

here's the process https://www.windows-noob.com/forums/index.php?/topic/4683-using-sccm-2012-rc-in-a-lab-part-12-updating-an-operating-system-image-using-offline-servicing/ however it does not apply to office updates

I like offline servicing myself, what OS are you interested in patching ?

to support Windows 10 servicing, your software update point (SUP) needs to be running WSUS 4.0 or later, and that means Windows Server 2012 or later, with SCCM CB 1610 you can do an in place upgrade of the operating system from Server 2008 to Server 2012R2 see > https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1602#site-infrastructure also take note of the Warning... WarningBefore you upgrade to Windows Server 2012 R2, you must uninstall WSUS 3.2 from the server. For information about this critical step, see the New and changed functionality section in Windows Server Update Services Overview in the Windows Server documentation.

it doesn't work that way, you can only upgrade to a newer version of Windows 10 using the upgrade task sequence, or using a frontend HTA to 'refresh' while in WinPE, but that would mean having to define your own USMT ruleset, i'd suggest if you want to upgrade, then do it in Windows or instead of applying the 1511 wim why not simply apply the 1607 wim ?

are you referring to updating the WIM files using offline servicing ? that process is covered in step 4 in the first guide linked below: How can I use the Upgrade Task Sequence in System Center Configuration Manager (Current Branch) ? A deeper look at the Upgrade task sequence in System Center Configuration Manager (Current Branch) if you have any issues let me know