Thanks Mohamed.

That is exactly what I need.

Nick Gailfus
Computer Technician
p. 602.953.2933  f. 602.953.0831
[email protected]| www.leonagroup.com


*Donate at*: https://www.no-shave.org/member/nickgailfus

On Tue, Dec 1, 2015 at 10:49 AM, Hatem Mohamed <[email protected]>
wrote:

> I recently came across this table of supported versions. It lists the
> supported versions on both the source and destination hierarchy side. Hope
> this helps.
>
>
> https://technet.microsoft.com/en-us/library/gg712313.aspx#BKMK_SupportedMigrationVersions
>
>
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Daniel Ratliff
> *Sent:* Tuesday, December 1, 2015 11:43 AM
> *To:* [email protected]
> *Subject:* RE: [mssms] SCCM 2012 to 2012 Migration
>
>
>
> No personal experience to confirm, but I don’t believe version matters. If
> you can migrate from 2007 to 2012, I doubt it wouldn’t work from 2012 SP1
> to 2012 R2 SP1.
>
>
>
> *Daniel Ratliff*
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Gailfus, Nick
> *Sent:* Tuesday, December 01, 2015 11:12 AM
> *To:* [email protected]
> *Subject:* [mssms] SCCM 2012 to 2012 Migration
>
>
>
> We are planning a migration between stand alone SCCM 2012 SP1 primary
> sites.  Microsoft documentation seems vague on the notion but does state
> that migration is supported between 2012 instances of the same version.
> Does this mean if we want our new hierarchy to be the latest (2012 R2 SP1)
> we would have to either upgrade the source primary sites or build the
> destination with the same version as the source and upgrade after
> completing the migration?  Thoughts?
>
> Nick Gailfus
> Computer Technician
> p. 602.953.2933  f. 602.953.0831
> [email protected]| www.leonagroup.com
>
>
>
>
> The information transmitted is intended only for the person or entity to
> which it is addressed
> and may contain CONFIDENTIAL material. If you receive this
> material/information in error,
> please contact the sender and delete or destroy the material/information.
>
>
>
>



Reply via email to