NickolajA

Unless you're only playing around with a script as a detection method, go ahead. But if it's for a MSI / EXE / whatever kind of software installation, I'd attempt to create a detection method by using the built in options first. Also, if you're using the script based method, remember to use e.g. Write-Output "True" only when if the script has detected that the software installation has successfully been installed. Explained more in detail here: http://blog.kloud.com.au/2014/08/12/powershell-detection-method-for-sccm-2012-application-compliance-management/

I'd suggest just like Garth did, to remove the Software Update Point role, make sure it uninstalls correctly. Then remove the WSUS features and add them back, followed by installing the Software Update Point role again.

Great! That would have been my next suggestion to do it on the OS Image itself. I'm glad it's working for you

Thanks for letting us know how you were able to solve it!

Cool! I'm glad you were able to figure it out :-)

The fix you're referring to was the slow downloads of WIM files, during the Apply Windows Image step. It was addressed in CU1 for 2012 R2. Microsoft also released a hotfix for it (KB2910552).

Here's a great book (I haven't read it myself though): http://thedesktopteam.com/blog/raphael/configmgr-automation-from-zero-to-hero/ Also have a look at Kaida's excellent PowerShell example resources: http://cm12sdk.net/?page_id=10

Or you could manage it with Intune instead and OMA-DM, much cooler ;-)

You should definitely consider upgrading your environment to at least CU5 for 2012 R2, or why not go all the way to SP1 for 2012 R2. I remember there were some issues as well like geckostech describes, but I couldn't find any good source about it right now.

Here's a guide for how to upgrade to ConfigMgr 2012 R2 SP1: http://www.scconfigmgr.com/2015/05/18/how-to-upgrade-to-configmgr-2012-r2-sp1-in-your-hierarchy/

I'm quite sure it doesn't, but please correct me if I'm wrong. Have a look at this post for how to deploy firmware updates: http://sunbehindtheclouds.com/2015/01/21/managing-surface-pro-drivers-and-firmware-in-the-enterprise/

Issue 2: In exactly what log are you seeing that issue?

Could you try and change the deployment properties on the Task Sequence from "Access content directly from a distribution Point" to "Download content locally" and give it a go?

Exactly like Peter said, they've been manually defined by the creator. Here's an example of how it could look like: $CollectionName = "Test Collection" $DeplymentIntent = "Install" $DeploymentName = "Test Deployment" Start-CMSoftwareUpdateDeployment -CollectionName $CollectionName -DeploymentType $DeploymentIntent -DeploymentName $DeployMentName -DeploymentAvailableDay(Get-date) -DeploymentExpireTime (Get-Date) Bare in mind though, this is a really basic way of writing a PowerShell script.

Awesome, thanks for sharing your findings!

You'd have to wait for it to actually trigger an alert.

Ever since ConfigMgr 2007, there's a known issue in ConfigMgr when it comes to Software Updates installations during OSD. I'd really suggest that you start looking into creating reference images on a monthly basis and import them for testing and then use in production. Otherwise your OSD will take forever to install 140 updates for each machine, which is also a terrible waste of time to be frank. Offline Servicing will only work for Windows updates, not for e.g. Office updates.

That sounds weird, configuring the deployment start time (available time) as Jörgen says should fix this issue. Are the time zone configured properly on your Primary Site server?

I've written a guide for upgrading to ConfigMgr 2012 R2 SP1 with some known issues and general guide lines: http://www.scconfigmgr.com/2015/05/18/how-to-upgrade-to-configmgr-2012-r2-sp1-in-your-hierarchy/ From what you're saying regarding the prerequisites checker messages, you should not run into any issues. But I recommend that you fix those SQL related warnings.

From the logs you can see that your content hashes are not correct: DownloadContentAndVerifyHash() failed. 80091007. I'd suggest that you re-distribute all of your packages, and attempt to split up the Install Software steps into a single Package per step for troubleshooting purposes. There were other issues as well, like the following: Failed to run the action: KB2840642 .NET 4.5 Update. The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade. (Error: 8007066A; Source: Windows)

You should always install all prerequisites for any Site System role in ConfigMgr. If you're uncertain of the prerequisites, use my tool that I've created: https://gallery.technet.microsoft.com/ConfigMgr-2012-R2-e52919cd

You could also split out Office 2013, so that's not being installed during the same step. But as Jörgen says, you should really look into the other applications and why there's an active MSI installation going on.

Not really sure why it would do that, doesn't sound right. Could you attach the AppEnforce.log from that particular system?

I'm gonna go against everyone here and recommend a side-by-side migration. I'd assume that the old server that was not meant for production may have a few "bad" configuration choices, meaning installing everything on the C: drive etc. If you go with the restore scenario, remember to bring up a SQL Server with the same version as before. Also remember to make sure any IP Helpers or such are configured against the new server IP, unless you'd want to reuse that as well. Anyhow, it will almost take you the same time to perform a restore as it takes to side-by-side migrate the whole environment.

It's not supported to even change the name of the Primary Site server, so changing the domain name is definitely not supported. Even if you'd attempt such an operation, it will in the end break for some reason. I'd suggest that you migrate your existing environment side-by-side to a new environment that you install in the new domain.