anyweb

do you have both x64 and x86 boot images on the dp and enabled for PXE ?

are you using Windows ADK 10 and MDT 2013 Update 1?

do you have any antivirus exclusions on the folders been used by dism ?

no I would upgrade it this way, run all steps on the CAS and once you've verified all is good, start on PRI1, PRI2 and so on. Do make sure to run the testdbupgrade on a COPY of the database backup. good luck and let us know how it goes for you

Already well known and respected for their simple, powerful, and reliable backup software, Altaro Software, has released the next major version of their backup application. In today’s changing IT landscape, multi-hypervisor deployments are becoming more and more common. With changing capabilities and ever different pricing structures, IT administrators are always on the lookout for technologies that provide new improved functionality and also provide cost savings measures. As a result many administrators are finding themselves in environments that contain both Hyper-V and VMware based workloads. As is the case with any production workload, the data associated with that service or business needs to be protected, and that can become difficult in multi- hypervisor deployments in the event that the current backup solution in place is targeted at one platform or the other. Historically Altaro Software’s backup application was targeted primarily at Hyper- V based workloads, but with the version 6 release of their software, support for VMware’s vSphere platform has been added as well. So, in those situations where you have a multi-hypervisor deployment, Altaro VM Backup has you protected. If you’ve used Altaro’s backup products in the past, you’ll notice that the name has changed to reflect the expanded platform support. The product is no longer known as “Altaro Hyper-V Backup”. It is now just simply, “Altaro VM Backup”. It’s not just a name change and a couple of software bits that are different though. Altaro has really pulled out all the stops when it comes to providing backup services to VMware customers. There is complete feature parity in providing backups between each platform. Regardless of target hypervisor you get all the same great benefits of Altaro VM Backup. That includes things like full VM and granular recovery. It provides full cluster support and offsite backup with WAN acceleration. Also included are some truly great advanced features such as in-application chat support and sandbox verification features to make sure those protected workloads are actually valid. Many administrators are so focused on getting successful backups of their workloads that they often forget about the other major part of a backup plan: RECOVERY! If you can’t recover from a backup, it doesn’t do much good does it? Altaro VM Backup provides a testing mechanism in which the application will actually conduct a test restore in an isolated state, verify that the workload is bootable, and then notify you if any issues are encountered. It’s this type of reliable, simplistic approach that makes Altaro VM Backup so Great. The application was designed to be simple to use, yet still powerful, reliable and feature-rich. Backups can quite literally be setup in just a couple of clicks, and the installation of the application is extremely simple as well. Additionally if you do manage to run into issues of some kind, Altaro’s world-class tech support is only a couple of clicks away. The application features in-app chat support to provide one additional avenue for getting your issues resolved in a timely manner by a support team that has made it their mission to provide the best customer service possible in the backup and recovery space. Pricing and licensing is also a large differentiator between Altaro Software and its competition. Most of Altaro’s competitors license their products based on the number of CPU sockets in the target host(s). Altaro doesn’t believe in hindering businesses for having more CPUs in their hypervisors. So, this is why Altaro VM backup is licensed per physical host that is being protected and not per socket. You don’t have to worry about the number of sockets in your host when placing an order. In addition to the paid version, a full-featured, 30-day trial is available for download here , in the event that you want to test it inside of your organization. On top of that, once the 30 day trial ends, the product is still able to protect up to two virtual machines for free on that host! This provides great value and gives you a chance to meaningfully test the product before committing to a purchase. If you’d like to learn more, be sure to check out the webpage at http://www.altaro.com and the Hyper-V Hub for great tips and howtos in the world of Microsoft virtualization. Disclaimer: The article is from a windows-noob recommends partner.

ok good point, i'll add a note about it, although i'd also say i'd recommend not separating the SQL server.

do you mean your DB is remote to the primary ?

i'd go with windows 8.1 with update which can support hyperv Gen 2 vm's, or if you are adventurous use Windows 10 which can do the same thing, also consider upgrading to 16gb of ram. cheers niall

yes, it's even mentioned in the official FAQ. Are the files on the Microsoft Evaluation Center suitable for use in production? Yes. You can transition from a product evaluation to a full version of the product by using Site Maintenance and entering your existing product key.

while it's not needed, it's always a good idea to consider it, here's my upgrade guide for your information in case you missed it. http://www.windows-noob.com/forums/index.php?/topic/12852-how-can-i-upgrade-to-system-center-2012-r2-sp1-with-mdt-2013-update-1-integrated/

choose the Package called Configuration Manager Client Package, it should have a last update date of when you upgraded to SP1.

that's an update for the client, i.e. a patch and should only be used as a patch using Installation Properties in the Setup Windows and ConfigMgr something like below two steps xcopy the patch step xcopy ".\*.*" "c:\Windows\ccmsetup\KB3074857\client\x64" /D /E /C /I /Q /H /R /Y /S setup windows and configmgr step SMSCACHESIZE=20000 CCMLOGMAXHISTORY=5 CCMLOGMAXSIZE=5000000 PATCH="C:\Windows\ccmsetup\KB3074857\client\x64\configmgr2012ac-sp2r2sp1-kb3074857-x64.msp" instead of using the update, point to your Configuration Manager Client Package, choose the one that is most recent.

which client package are you using in the setup windows and configmgr step ? it works fine for me.

as regards #1 are you pointing to the path and media as i show here as regards #2 see the errors below <![LOG[Sysprep state set to IMAGE_STATE_UNDEPLOYABLE]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="0" thread="3056" file="offlineos.cpp:386"> <![LOG[The OS has not been generalized using sysprep.exe, or sysprep did not complete.]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="1" thread="3056" file="offlineos.cpp:402"> <![LOG[bSysPreped, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,514)]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="0" thread="3056" file="prepareos.cpp:514"> <![LOG[Sysprep did not complete successfully]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="3" thread="3056" file="prepareos.cpp:514"> <![LOG[RunSysprep(sCmdLine, bActivate, m_bDebug), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,1375)]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="0" thread="3056" file="prepareos.cpp:1375"> <![LOG[Unable to sysprep the machine, hr=80004005]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="3" thread="3056" file="prepareos.cpp:1389"> <![LOG[pCmd->Sysprep(bActivate, bMsd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\main.cpp,270)]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="0" thread="3056" file="main.cpp:270"> <![LOG[Sysprep'ing the machine failed, hr=80004005]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="3" thread="3056" file="main.cpp:270"> <![LOG[De-Initialization successful]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="0" thread="3056" file="prepareos.cpp:1147"> <![LOG[Exiting with error code 16389]LOG]!><time="13:09:21.876+300" date="09-03-2015" component="PrepareOS" context="" type="1" thread="3056" file="main.cpp:293"> <![LOG[Process completed with exit code 16389]LOG]!><time="13:09:21.938+300" date="09-03-2015" component="TSManager" context="" type="1" thread="1824" file="commandline.cpp:1124"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:09:21.938+300" date="09-03-2015" component="TSManager" context="" type="1" thread="1824" file="instruction.cxx:805"> you need to examine your sysprep log files for more info as to why it failed sysprep The errors will be logged in the following folder:- C:\Windows\System32\Sysprep\Panther and the following files will point to the failure:- setupact.log setuperr.log

look through the log file and search for the word 'failed' you'll see a few issues highlighted below <![LOG[Connection to "\\gonzo\deploy$\Images\STUDENT BUILDS\Golden Image V3 (With All ICT Serif Software)" failed with credential conflict. Using existing connection.]LOG]!><time="09:09:46.108-60" date="09-01-2015" component="OSDCaptureCD" context="" type="2" thread="1712" file="tsconnection.cpp:330"> and later on <![LOG[sysprep did not complete successfully]LOG]!><time="09:18:02.430-60" date="09-01-2015" component="PrepareOS" context="" type="3" thread="1636" file="prepareos.cpp:514"> <![LOG[RunSysprep(sCmdLine, bActivate, m_bDebug), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,1375)]LOG]!><time="09:18:02.430-60" date="09-01-2015" component="PrepareOS" context="" type="0" thread="1636" file="prepareos.cpp:1375"> <![LOG[unable to sysprep the machine, hr=80004005] so... look next in C:\Windows\System32\Sysprep\Panther and the following files pointing to the failure:- setupact.log setuperr.log can you attach them ?

without logs there's nothing we can say, try looking at the smsts*.log and appenforce.log and any logs specified when installing the actual app

so did you follow brandons advice as i linked to ?

is it only in the WinPE phase (x:) that it fails with PowerShell ?

you can manually test the new windows pe images (winpe 10 or winpe 5.x) by installing the appropriate ADK on another machine and extracting the boot images from there then import them into configmgr like so http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/

what base language was windows 7 set to before language packs were installed ?

attach the smsts.log please...

to work with Windows 10 you need the Windows 10 ADK.

you neglected to post anything that resembles an error, are you getting an error when you run the script, if so, what is it ?

and what error are you getting ?

to get updated boot wims either update to ADK 8.1 and use those boot images it provides, or consider upgrading to SP2 which will include WinPE 10 which is backwards compatible with Windows 7 deployments.