SCCM 2012 RTM to SP1 to R2 Boot Images Migration What steps to be consider

We are Migrating SCCm 2012 to SP1 then to R2…
My question would be specific to Boot images.
We are in RTM edition, we have different boot images got created by our Imaging guys, These boot Images also have network/mass storage drivers are added along with some WINPE Back Group screen wallpaper, when cross checked the boot image properties. And
finally these the Boot Images are distributed to all the required distribution points.
Help me to understand what are the action steps to be taken now? In the process of RTM to SP1 and R2
HunBoy Started learning from this page

From RTM to SP1, the upgrade process will upgrade your WinPE 3.x boot images to WinPE 4.0 (if it can). From SP1 to R2, the upgrade process will not upgrade your boot images but will instead create new ones. Only WinPE 5.0 and WinPE 3.1 boot images are supported
by R2 -- the 3.1 boot images are meant for supporting XP since WInPE 5.0 doesn't support XP (God help you if you're still on XP though).
Thus, you need to get your "imaging" guys to create new WinPE 5.0 boot images.
Jason | http://blog.configmgrftw.com

Similar Messages

SCCM 2012 RTM to SP1 Upgrade - Windows ADK 8.1

Hello,
I am after some advice. We have two physical locations containing a single SCCM 2012 primary site server in one location and distribution point server in the other location.
Both servers are also configured as DHCP Servers and DHCP scope options have been configured correctly to allow both DHCP and Windows Deployment Services to co-exist.
OSD was working fine, until I upgraded the primary site server to SCCM 2012 SP1. During the upgrade process, I installed Windows ADK 8.1 which would appear is not supported however no errors were reported during the upgrade process.
Issues I have encountered;
- I can no longer PXE boot with the following error 'PXE-E55: ProxyDHCP service did not reply to request on port 4011'
- The x:\remoteInstall\Boot\Fonts directory is empty suggesting the boots images were not finalised.
- When updating the distribution points with the boot images i get the following error via the wizard;
• The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4566;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"UKS0003B\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889
SMSPXE.log contains the following errors;
Failed to copy X:\RemoteInstall\SMSTempBootFiles\XXX00014\WINDOWS\Boot\PXE\wdsmgfw.efi to X:\RemoteInstall\SMSBoot\x86\wdsmgfw.efi
InstallBootFilesForImage failed. 0x80070002
Warning: Failed to copy the needed boot binaries from the boot image X:\RemoteInstall\SMSImages\XXX00014\WinPE.XXX00014.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)
Failed adding image X:\RemoteInstall\SMSImages\XXX00014\WinPE.XXX00014.wim. Will Retry..
The system cannot find the file specified. (Error: 80070002; Source: Windows)
Failed to read ADK installation root registry value
I am looking for some advice on the best way to rectify this issue. Options I am considering are as follows, however I am unsure of the outcome should I attempt these;
1 - Upgrade to SCCM 2012 R2 which supports ADK 8.1
2 - Uninstall Windows ADK 8.1, install 8.0
3 - Attempt to restore back to SCCM 2012 RTM using file system backups and SCCM backups.
Any help or suggestions would be much appreciated.

Thank you both for your replies and advice
The configMgr 2012 environment is primarily used for OSD, and software updates for Servers only.
I have followed Peter’ advice, and uninstalled WADK 8.1 and installed 8.0 and I am currently investigating errors within the SMSPXE.log, and I have seen other posts elsewhere within these forums
with the same issue with suggested solutions which I shall investigate.
With regards to DHCP on the ConfigMgr site servers – I could not agree with you more.
Unfortunately, my company use a third party DHCP solution which was incapable of supporting PXE-boot for OSD.
We were therefore required to have a separate Microsoft DHCP solution on the site servers to by-pass this issue.
The intention is to upgrade to Configmgr 2012 R2.
My understanding is that there is no direct upgrade process from SCCM 2012 RTM to R2, therefore I have upgraded to SP1 and would prefer all features are working correctly before progressing to R2.
Many thanks again,
Regards,
JohnRox

Can WE join existing SCCM 2012 RTM to new SCCM 2012R2 CAS

Hi All
Is it possible to join sccm 2012 RTM to new sccm 2012R2 CAS or we have to upgrade the RTM to R2 then we can?

No. You can only, since SP1, expand an existing primary site to a CAS during the installation of the CAS. See for more information:
http://technet.microsoft.com/en-us/library/jj591551.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

CAS and three primary hierarchy SCCM 2012 r2 can i get any runbook from microsoft for Step by step installation

Hi All
need CAS and three primary hierarchy SCCM 2012 r2 can i get any runbook from microsoft for Step by step installation
need step by step installation guide with screenshots.

There's a lots of installation guide but each guide is for a "standard" installation, your environment is unique and you should get help to be sure to implement SCCM to fulfill your needs.
Installing SCCM without any experience will be tricky and maintain it will be even harder. This is not a simple product.
http://sccmentor.wordpress.com/2014/01/08/sccm-2012-r2-step-by-step-installation-guide/
http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-step-by-step-guides/
Benoit Lecours | Blog: System Center Dudes

SCCM 2012 OSD Retain Computer Name on re-image rebuild

I am migrating our PC workstation Windows 7 build process from MDT 2010 lite touch to SCCM 2012 zero touch. Everything is working expect
one thing.
When I re image a PC, if the PC is already known to AD I want it to keep the previous machine name, so that it retains its collection memberships
for software. If I put the PC into the collection that the OSD task sequence is advertised to, the machine successfully rebuilds with the same machine name. Starting from Windows - i.e the configuration manager client.
If I initiate the rebuild via PXE boot the machine gets a new name.
I have read that if the OS is booted from PXE or boot media then the deployment type is new computer. But if the TS is advertised to an
existing client and initiated from the config manager client, the deployment type is refresh.
I'm currently using itx-solutions.nl AutoNameControl to get RIS style naming i.e. PC-123, PC-124 etc.
When I used MDT and lite touch I used MaikKoster Deployment Webservice and obtained the machine name via the GetComputerNameByNetbootGuid
service. This worked perfectly. I don't know what exactly sets this in AD, but have noticed the PC's built with SCCM have no value for NetbootGuid so this doesn't work.
How do I always get the PC to retain the same name on rebuild?

Thank you are correct - It turns out it was the AutoNameControl. It creates a new name regardless.
I set a TS variable called ExisitngClient as the first step of my TS - but put a condition on it, to check for the existence of CcmExec.exe on the client. If it exists then I set the variable to TRUE.
Then later on when the AutoNameControl runs, I put a condition of IF ExistingCient not equals TRUE.
Meaning it only runs if it didn't have Config Manager on before the format.
It seems to work.
Thanks for the help

SCCM 2012 RTM & Windows Mobile 6.5 device inventory

Hi all
I have an issue collecting the right hardware information on these devices. I have setup device enrollment which works fine but I can't get it to inventory either the IMEI of the device or phone number.
Looking at the hardware inventory classes I cant seem to find anything relating to IMEI or phone number under mobile device classes.
Am I going to have to go down the custom mof route? Searching around it seems that IMEI and number collection was in SCCM 2007 but can't find it in 2012...
Any help would be greatly appreciated.

Hi Panu
Thanks for your response, it seems that the Device ID field is blank on the harware inventories for my 6.5 devices :( So far I have tried a Psion EP10 and a HTC HD2 both with the same results.
Unfortunately Activesync is not an option due to additional licensing costs and with the number of devices being rolled out it would take us over our Exchange standard mailbox limit.
Looks like I have 2 slightly different problems then:
1) Why is the device ID not being returned?
2) Do I need to create a custom mof file to collect the phone number?

SCCM 2012 R2 Boot WIM DISM - Drivers Failing -hr:0xc0000135‏

Hello OSD Experts,
I have upgraded my SCCM 2012 RTM to SP1(Not installed any Cumulative updates) then to SCCM 2012 R2 Successfully... I did not get any errors.
Before Upgrade my SCCM 2012 RTM/SP1 Images are removed from DP Targets.
Now my next high priority task is I wanted to integrate my Hardware models NIC & Mass Storage Drivers to my Boot Images, So that my OSD will work without any issues. But am getting errors, when I try
to add by DISM command to the Boot Images.
I have taken Default boot.wim file from SCCM 2012 R2 and copy pasted to my work location and ran the DISM command... however I am not successful in this for integration.
Has anyone have already have solution for this let me know.
<<<AV is in Disabled state during DISM.. Still no Luck>>>
<<<<<I tried to ran the DISM on Windows 8 & Windows 2008 R2>>>>>
Attached my DISM.Log @OneDrive... http://1drv.ms/1gdUi6w
Failed to create Dism Image Session in host. - CDISMManager::LoadImageSession(hr:0xc0000135)
DISM Manager: PID=3200 A problem ocurred loading the image session. Retrying... - CDISMManager::CreateImageSession(hr:0xc0000135)
DISM.EXE: Unable to start the servicing process for the image at 'E:\Boot_WIM\SCCMR2_WIMS\X86\Temp'. HRESULT=C0000135
<<< I have already checked this link but no luck... http://social.technet.microsoft.com/Forums/en-US/6b9facc4-9174-4ae7-a8a0-98d88d7f8a95/dism-error-0xc0000135-when-attemptign-to-add-drivers-to-mounted-2012-image?forum=mdt
>>>
Thank you In Advance,
HunBoy Started learning from this page

Hi,
You could use SCCM console to add these drivers. From the SCCM console, go to Operating Systems -> Drivers. Right click and select Import Drivers and follow the wizard. Or go to Operating Systems -> Boot Images -> Right click the boot image in question
-> select Properties. Select the Drivers tab and click on the add button on the right and then select the NIC drivers.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path

Hi everybody,
I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
<04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
<04-25-2014 02:06:47> ********************************************
<04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
minimum supported installed build version is [7804].
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Unsupported upgrade path;    Error;
Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
<04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Active Replica MP;    Passed
<04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Parent site replication status;    Passed
<04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
=====
<04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;
SQL Server sysadmin rights;    Passed
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;    SQL Server sysadmin rights
for reference site;    Passed
<04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Site server computer account administrative rights;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server security mode;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
<04-25-2014 02:07:09> INFO: Target computer is a Windows server.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Unsupported site server operating system version for Setup;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Domain membership;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Pending system restart;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server version;    Passed
<04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Edition;    Passed
<04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
Instance:.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Tcp Port;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
<04-25-2014 02:07:09> INFO: SQL Server memory is limited.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Configuration for SQL Server memory usage;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
<04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
Server to reserve a minimum of 8 gigabytes (GB) of memory.
<04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;    SQL Server process memory allocation;
Warning;    Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
http://go.microsoft.com/fwlink/p/?LinkId=233759.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Case-insensitive collation on SQL Server;    Passed
<04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFO: getaddrinfo returned success.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Validate FQDN of SQL Server Computer;    Passed
<04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
<04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Primary FQDN;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
=====
<04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
<04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Failover Cluster;    Passed
<04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Deployment Tools installed;    Passed
<04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;    Windows Preinstallation Environment
installed;    Passed
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
SMS Provider machine has same domain as site server;    Passed
<04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:10> ***************************************************
<04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
<04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
Prerequisite checking result into the registry
<04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
<04-25-2014 02:07:10> INFO: Setting registry values
If you wonder whether it might be related to this error:
-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
I've already tried the
Preinst /DELSITE XXX command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
Finally, the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
the impression that it's being cached somehow.
Any help would be highly appreciated,
Thank you.
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Hello again everybody,
I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
primary sites.
If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
DELETE
FROMServerDataWHERESiteCode='XXX'
DELETE
FROMSC_SiteDefinitionWHERESiteCode='XXX'
And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
Thank you all anyways for your answers and comments,
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Migrate from 2012 rtm to 2012 R2

I am a bit confused, if you read the migration hierarchy scenarios (http://technet.microsoft.com/en-us/library/gg682006.aspx) you can migrate from 2007 to 2012 rtm or SP1 or R2.
you can migrate from 2012 SP1/R2 to another 2012 SP1/R2
yesterday I was investigating the possibility to migrate a pilot 2012 RTM environment to a new 2012 R2 environment we just setup. as a test I was able to migrate a driverpackage, so hey: it seems to work, but why is this scenario not covered in the
technet online doc?
so: if object migration from 2012 RTM to 2012 R2 is supported, are there limitations to that scenario?

I haven't done it either but know of several cases where this has successfully been done. However, as with any migration, there are niggling issues. Unfortunately you won't be able to get any assistance with these - as you are in an "unsupported"
scenario.
I would have preferred for this to be tested properly and deemed to be "supported".
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

MDT Boot Image Creation

I just upgraded my SCCM 2012 RTM to SP1 and then to R2
I uninstalled the WAIK and installed 8.1 ADK
MDT 2012 Update 1
Now I am trying to add new MDT Boot images and I get this error
Started processing.
Creating boot image.
Copying WIM file.
Error while importing Microsoft Deployment Toolkit Task Sequence.
System.Exception: Unhandled exception occurred:
System.IO.FileNotFoundException: Could not find file '\winpe.wim'.
File name: '\winpe.wim'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileInfo.get_Length()
at Microsoft.BDD.Core.DEInfo..ctor(FileInfo theFile)
at Microsoft.BDD.Core.DirectoryUtility.BeginCopyFile(String theSourceFile, String theDestFile)
at Microsoft.BDD.ElevatedProxy.NewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
Jacob

You need to remove the old MDT integration components and then reintegrate MDT with the new R2 installation of Configuration Manager by running the Configure ConfigMgr Integration utility from the start menu (inside the Microsoft Deployment Toolkit folder)
, if your on Server 2012 make sure you run the utility as an administrator (elevated) otherwise it will fail.
If you haven't already done so you will also need to update MDT to 2013 as 2012 Update 1 isn't supported in R2.
Its also a good idea to create new MDT Integrated Task Sequences and copy over any custom actions from your old ones to the new ones.
Cheers
Damon

Extract drivers from boot image

I have a boot image and my team members added lot of drivers on top of boot images.... Now I want to get a report to get the list of drivers that are integrated
and their source path as I must have to keep them in a separate folder so that in my up coming migration project I can use them again to integrate in new boot images when migrated from sccm 2012 RTM to SP1 and R2
Kindly through some light on this
HunBoy Started learning from this page

You should not use the drivers from your old boot images in your new boot images.
Windows PE drivers are not the same for every verison of ConfigMgr.
Win PE 5.0 = SCCM 2012 R2
Win PE 4.0 = SCCM 2012 SP1
Win PE 3.0 = SCCM 2012 RTM
And the drivers you need are:
Win PE 5.0 = Windows 8.1
Win PE 4.0 = Windows 8
Win PE 3.0 = Windows 7
Windows PE 5.0 also includes many new drivers so drivers that you needed in older versions of PE might not be required any more...
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

SCCM 2012 SP1 - Build and Capture - ReCapture impossible

Hi all
i upgrade my SCCM 2012 RTM to SCCM 2012 SP1 yesterday. Today i started a recapture of my Windows 7 and Windows 2008 R2 Base Image.
For that i have 2 VMs located in different SCCM Collections. And a Build and Capture Task Sequence is deployed to the collections.
Before SP1 the behavior was:
- Reset Required PXE Deployment in SCCM for the VMs
- Start VM
- VM boots with PXE
- VM installs and capture the Installation
And that i could do all the time so often as i want.
Now with SP1 it is the same procedure but just for one time. After one success Build and Capture Task, the vm is unable to do the task sequence again. The VM is booting into the PXE and then i can see in the smsts log:
There are no task sequences available to this computer
But there are. The Task Sequence is set to "Always rerun".
The only "fix" is to completely recreate the computer item in sccm.
What is here wrong? Is this a known bug?
best
JBAB

Hi, your problem is that when you deploy the task over the collation you only specified "media and PXE" was available to and probably the machines that you try to capture already had the sccm client. You can try to deploy the sequence task to a collation
including the the option "configuration manager, media and PXE", or you can also deploy the task sequence to de "unknown devices" collation and delete the objects of the two virtual machines in configuration manager

SCCM 2012 SP1 CU4 migrated DP shows package status "unknown"

I have a SCCM 2012 SP1 CU4 environment and have shared SCCM 2007 distribution points.
Today I migrated one of the DP's which seems to work well.
However all my packages shows now the status "unknown" for this migrated DP.
This is a problem which should be fixed in CU4 according to the CU4 description. But it is not :-(
Any idea how to solve this ? R2 install ?

Some additional information:
I noticed that the package sources are still available at the "old" ditribution point share abd not on the new sccm 2012 distribution point share. When performing actions described in step 3 below the package becomes available on the distribution point
share......then i guess i can remove the content from the "old" distribution point share ????
I noticed that when a package got the status "unknown" for de migrated DP the following action fix the problem:
--> i remove the DP from the package and immediately add it again, the package status becomes "Successful".....hummm....ok....maybe a script could be created for this
I noticed that when a package got the status "unknown" and the package is also located on the "distribution point share" then following will fix the issue:
--> edit the package and remove the migrated DP and remove the checkbox for string on the distribution point share. Then add the DP again, click Apply and then set the checkbox for storing on the distribution point share and Apply again. Then wait and package
will become available Successful and the package will become available on the distribution point share
But i have 800 packages and 50 to be migrated DP's.....this is not a solution....but what is ????
Any help, ideas, tips, hints, recommendations ?
My overal thoughts are that migrating of a SCCM 2007 DP is not really working at all !!!!!
Or does someone has other experience with e.g. R2 installed ? If so then I will upgrade first...

SCCM 2012 Console (SP1 with CU4)

I am trying to package the SCCM 2012 console (with SP1) and with and without CU4. Both packages give me the following error in the event log. 'the virtual application.....could not be started because the App-V subsystem 'Virtual FileSystem' could not
be initialized....'
I've re-sequenced the app, had another package create a different package too and both get the same error.

Hello,
See this article on howto enable more extensive debug-logs;
http://www.tmurgent.com/TMBlog/?p=1247
Nicke Källén | The Knack| Twitter:
@Znackattack

Win PE 4.0 SCCM 2012 R2

Hi
Wondering if somebody could assist - Have an environment where there is a requirement to upgrade from SCCM 2012 RTM SP1 to SCCM 2012 R2 with CU 1.
There are multiple Boot Images created already that are managing a Windows 7 deployment.
Due to the Windows 7 Deployment I am reluctant to move to WINPE 5.
Is there anyway of upgrading to SCCCM 2012 R2 without a requirment to rebuild the WIN PE Bootimages and still have customisible/managable WINPE 4.0 Boot Images through SCCM 2012 R2.
Any guidance is appreciated
RDunne76

Hi,
it is possible to deploy Windows 7 using WinPE 5.0 without issue (like Torsten mentioned before)
If you want to use WinPe 4.0 have a look at this description:
Customizing WinPE 3.1
and WinPE 4.0 boot images for use in ConfigMgr 2012 R2
Greetings
Eric
Eric Berg -- http://www.ericberg.de -- MCSE: Private Cloud MCSE: Server Infrastructure MCSE: Desktop Infrastructure

SCCM 2012 RTM to SP1 to R2 Boot Images Migration What steps to be consider

Similar Messages

Maybe you are looking for