RE: [mssms] Upgrading Config Mgr

[Heaton, Joseph@Wildlife]

Sorry to interrupt the hijack :P, but a quick question on my original question

Do you guys wait any real amount of time between updating the primary site, and 
the secondary sites?  Or do you update the secondaries as soon as the primary 
is complete?

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of John Marcum
Sent: Tuesday, December 19, 2017 12:23 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Echoing some of the comment below I'd like to say that the PFE may say it's a 
"best practice" but I'd challenge him to provide some official documentation 
that states that. I'd also ask for references for the PFE, I've had some bad 
experiences with Microsoft PFE's who claim to be experts in ConfigMgr, I'm not 
by any means saying there are not any good ones, but I am saying  that is the 
goods ones are booked MCS will absolutely send someone to you who is not 
actually a specialist in ConfigMgr because that guy is sitting on the bench 
costing them money.



Sensitivity: Confidential between partners
From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Tuesday, December 19, 2017 10:01 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

You really should ask again for 2nd opinion / clarification why this needs to 
be done.

If you doing months of work for something you don't need to do and I was the 
SCCM team I would be pretty unhappy.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Tuesday, December 19, 2017 10:05 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

The SCCM team worked with our TAM to get an SCCM PFE to come up with the safest 
solution for getting off of this cluster.  Trust me, I'm watching a train of 
SCCM releases roll by with numerous features I would love to take advantage of. 
 But I'm not on the SCCM architect team, so my OSD opinions and wants are 
irrelevant.  :)

Mike

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dam, Bryan
Sent: Tuesday, December 19, 2017 9:50 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Yea, we've just done that twice in the last two months to get to SQL 2016 
without any problems on the ConfigMan side of things.  I mean ... what's your 
disaster recovery plan if you can't reliably restore the database to a new 
server?
  Bryan

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: Tuesday, December 19, 2017 9:28 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

I don't your PFE and I don't know all of the details involved here, but based 
on what has been written below, no way. Also, be skeptical of anyone who simply 
says "best practice" as that typically implies they don't actually know any 
technical details and are blindly following some generic recommendation that 
doesn't take your environment, requirements, and circumstances into account.

J

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Tuesday, December 19, 2017 8:47 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Yeah, this seems weird to me.  Full disclosure I haven't done much with SQL 
clusters and SCCM so maybe there is something I'm missing.

I know if you want to use another SQL server for SCCM you can perform a site 
reset and use the option to point to a new SQL server (I've done this in the 
past no issue).

  *   
https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/

Maybe others on the email list can chime in and maybe they know if there is 
some gotcha with a SQL cluster that I'm unaware of.

Rob

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Monday, December 18, 2017 11:32 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

The Microsoft PFE for 

[mssms] RE: OT Powershell & Laps

[Jerousek, Jeff]

These questions are impossible to answer without knowing how you're assigning 
the $computer variable, but do a 
   $computer | get-member
And make sure it's the string you think it is.

Thanks,
Jeff Jerousek

-Original Message-
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Stuart Watret
Sent: Tuesday, December 19, 2017 11:53 AM
To: mssms@lists.myitforum.com
Subject: [mssms] OT Powershell & Laps

Anyone know why this happens?

Laps has some commandlets

If I try 
Get-AdmPwdPassword -Computername Sam1

its fine.

if i use a variable for the comp name like this,

Get-AdmPwdPassword -Computername $Computer

I get ‘URI formats are not supported’

The computer name has no spaces  - it’s very odd and google isn’t helping.

Ta

Stuart

RE: [mssms] Upgrading Config Mgr

[John Marcum]

Echoing some of the comment below I'd like to say that the PFE may say it's a 
"best practice" but I'd challenge him to provide some official documentation 
that states that. I'd also ask for references for the PFE, I've had some bad 
experiences with Microsoft PFE's who claim to be experts in ConfigMgr, I'm not 
by any means saying there are not any good ones, but I am saying  that is the 
goods ones are booked MCS will absolutely send someone to you who is not 
actually a specialist in ConfigMgr because that guy is sitting on the bench 
costing them money.



Sensitivity: Confidential between partners
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Robert Spinelli
Sent: Tuesday, December 19, 2017 10:01 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

You really should ask again for 2nd opinion / clarification why this needs to 
be done.

If you doing months of work for something you don't need to do and I was the 
SCCM team I would be pretty unhappy.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Tuesday, December 19, 2017 10:05 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

The SCCM team worked with our TAM to get an SCCM PFE to come up with the safest 
solution for getting off of this cluster.  Trust me, I'm watching a train of 
SCCM releases roll by with numerous features I would love to take advantage of. 
 But I'm not on the SCCM architect team, so my OSD opinions and wants are 
irrelevant.  :)

Mike

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dam, Bryan
Sent: Tuesday, December 19, 2017 9:50 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Yea, we've just done that twice in the last two months to get to SQL 2016 
without any problems on the ConfigMan side of things.  I mean ... what's your 
disaster recovery plan if you can't reliably restore the database to a new 
server?
  Bryan

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: Tuesday, December 19, 2017 9:28 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

I don't your PFE and I don't know all of the details involved here, but based 
on what has been written below, no way. Also, be skeptical of anyone who simply 
says "best practice" as that typically implies they don't actually know any 
technical details and are blindly following some generic recommendation that 
doesn't take your environment, requirements, and circumstances into account.

J

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Tuesday, December 19, 2017 8:47 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Yeah, this seems weird to me.  Full disclosure I haven't done much with SQL 
clusters and SCCM so maybe there is something I'm missing.

I know if you want to use another SQL server for SCCM you can perform a site 
reset and use the option to point to a new SQL server (I've done this in the 
past no issue).

  *   
https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/

Maybe others on the email list can chime in and maybe they know if there is 
some gotcha with a SQL cluster that I'm unaware of.

Rob

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Monday, December 18, 2017 11:32 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

The Microsoft PFE for SCCM said that it is Microsoft's best practice to do a 
side-by-side migration as opposed to doing something like a backup and restore 
of the SQL database to a new cluster.

Our SQL team wanted to do a simple backup and restore to the new cluster, but 
we burned some Premier hours and the PFE advised us that doing that risked 
corrupting the entire database and forcing us into a site recovery.  He said 
the only way to properly do it was the migration.  He said we could try the 
backup/restore but that the success rate for that was not good.

[mssms] OT Powershell & Laps

[Stuart Watret]

Anyone know why this happens?

Laps has some commandlets

If I try 
Get-AdmPwdPassword -Computername Sam1

its fine.

if i use a variable for the comp name like this,

Get-AdmPwdPassword -Computername $Computer

I get ‘URI formats are not supported’

The computer name has no spaces  - it’s very odd and google isn’t helping.

Ta

Stuart

RE: [mssms] Upgrading Config Mgr

[Robert Spinelli]

You really should ask again for 2nd opinion / clarification why this needs to 
be done.

If you doing months of work for something you don’t need to do and I was the 
SCCM team I would be pretty unhappy.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Marable, Mike
Sent: Tuesday, December 19, 2017 10:05 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

The SCCM team worked with our TAM to get an SCCM PFE to come up with the safest 
solution for getting off of this cluster.  Trust me, I’m watching a train of 
SCCM releases roll by with numerous features I would love to take advantage of. 
 But I’m not on the SCCM architect team, so my OSD opinions and wants are 
irrelevant.  ☺

Mike

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dam, Bryan
Sent: Tuesday, December 19, 2017 9:50 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Yea, we’ve just done that twice in the last two months to get to SQL 2016 
without any problems on the ConfigMan side of things.  I mean … what’s your 
disaster recovery plan if you can’t reliably restore the database to a new 
server?
  Bryan

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: Tuesday, December 19, 2017 9:28 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

I don’t your PFE and I don’t know all of the details involved here, but based 
on what has been written below, no way. Also, be skeptical of anyone who simply 
says “best practice” as that typically implies they don’t actually know any 
technical details and are blindly following some generic recommendation that 
doesn’t take your environment, requirements, and circumstances into account.

J

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Tuesday, December 19, 2017 8:47 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Yeah, this seems weird to me.  Full disclosure I haven’t done much with SQL 
clusters and SCCM so maybe there is something I’m missing.

I know if you want to use another SQL server for SCCM you can perform a site 
reset and use the option to point to a new SQL server (I’ve done this in the 
past no issue).

  *   
https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/

Maybe others on the email list can chime in and maybe they know if there is 
some gotcha with a SQL cluster that I’m unaware of.

Rob

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Monday, December 18, 2017 11:32 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

The Microsoft PFE for SCCM said that it is Microsoft’s best practice to do a 
side-by-side migration as opposed to doing something like a backup and restore 
of the SQL database to a new cluster.

Our SQL team wanted to do a simple backup and restore to the new cluster, but 
we burned some Premier hours and the PFE advised us that doing that risked 
corrupting the entire database and forcing us into a site recovery.  He said 
the only way to properly do it was the migration.  He said we could try the 
backup/restore but that the success rate for that was not good.

So we’re spending months doing a side-by-side migration.

Mike



From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Monday, December 18, 2017 2:11 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

You must have something else going on with your site.  It doesn’t make sense 
you would need to do site by site over just moving to new SQL cluster.  If your 
saying you’re doing it up to clean old crap that’s different.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, December 15, 2017 7:12 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Same here.  We would never be able 

RE: [mssms] Upgrading Config Mgr

[Marable, Mike]

The SCCM team worked with our TAM to get an SCCM PFE to come up with the safest 
solution for getting off of this cluster.  Trust me, I’m watching a train of 
SCCM releases roll by with numerous features I would love to take advantage of. 
 But I’m not on the SCCM architect team, so my OSD opinions and wants are 
irrelevant.  ☺

Mike

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Dam, Bryan
Sent: Tuesday, December 19, 2017 9:50 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Yea, we’ve just done that twice in the last two months to get to SQL 2016 
without any problems on the ConfigMan side of things.  I mean … what’s your 
disaster recovery plan if you can’t reliably restore the database to a new 
server?
  Bryan

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: Tuesday, December 19, 2017 9:28 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

I don’t your PFE and I don’t know all of the details involved here, but based 
on what has been written below, no way. Also, be skeptical of anyone who simply 
says “best practice” as that typically implies they don’t actually know any 
technical details and are blindly following some generic recommendation that 
doesn’t take your environment, requirements, and circumstances into account.

J

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Tuesday, December 19, 2017 8:47 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Yeah, this seems weird to me.  Full disclosure I haven’t done much with SQL 
clusters and SCCM so maybe there is something I’m missing.

I know if you want to use another SQL server for SCCM you can perform a site 
reset and use the option to point to a new SQL server (I’ve done this in the 
past no issue).

  *   
https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/

Maybe others on the email list can chime in and maybe they know if there is 
some gotcha with a SQL cluster that I’m unaware of.

Rob

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Monday, December 18, 2017 11:32 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

The Microsoft PFE for SCCM said that it is Microsoft’s best practice to do a 
side-by-side migration as opposed to doing something like a backup and restore 
of the SQL database to a new cluster.

Our SQL team wanted to do a simple backup and restore to the new cluster, but 
we burned some Premier hours and the PFE advised us that doing that risked 
corrupting the entire database and forcing us into a site recovery.  He said 
the only way to properly do it was the migration.  He said we could try the 
backup/restore but that the success rate for that was not good.

So we’re spending months doing a side-by-side migration.

Mike



From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Monday, December 18, 2017 2:11 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

You must have something else going on with your site.  It doesn’t make sense 
you would need to do site by site over just moving to new SQL cluster.  If your 
saying you’re doing it up to clean old crap that’s different.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, December 15, 2017 7:12 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Same here.  We would never be able to just click “go” without a vetted plan in 
place and change management involved.  With 35K clients we are by no means a 
large organization, but if something were to go sideways in the upgrade and we 
skipped the planning and control, there wouldn’t be enough time to update 
resumes once they came for us.

On top of that there are other factors to figure in before you click “go”.  For 
example, in our case we are going to have to do a side-by-side site migration 
because our SQL cluster is 

RE: [mssms] Upgrading Config Mgr

[Dam, Bryan]

Yea, we’ve just done that twice in the last two months to get to SQL 2016 
without any problems on the ConfigMan side of things.  I mean … what’s your 
disaster recovery plan if you can’t reliably restore the database to a new 
server?
  Bryan

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Jason Sandys
Sent: Tuesday, December 19, 2017 9:28 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

I don’t your PFE and I don’t know all of the details involved here, but based 
on what has been written below, no way. Also, be skeptical of anyone who simply 
says “best practice” as that typically implies they don’t actually know any 
technical details and are blindly following some generic recommendation that 
doesn’t take your environment, requirements, and circumstances into account.

J

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Tuesday, December 19, 2017 8:47 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Yeah, this seems weird to me.  Full disclosure I haven’t done much with SQL 
clusters and SCCM so maybe there is something I’m missing.

I know if you want to use another SQL server for SCCM you can perform a site 
reset and use the option to point to a new SQL server (I’ve done this in the 
past no issue).

  *   
https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/

Maybe others on the email list can chime in and maybe they know if there is 
some gotcha with a SQL cluster that I’m unaware of.

Rob

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Monday, December 18, 2017 11:32 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

The Microsoft PFE for SCCM said that it is Microsoft’s best practice to do a 
side-by-side migration as opposed to doing something like a backup and restore 
of the SQL database to a new cluster.

Our SQL team wanted to do a simple backup and restore to the new cluster, but 
we burned some Premier hours and the PFE advised us that doing that risked 
corrupting the entire database and forcing us into a site recovery.  He said 
the only way to properly do it was the migration.  He said we could try the 
backup/restore but that the success rate for that was not good.

So we’re spending months doing a side-by-side migration.

Mike



From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Monday, December 18, 2017 2:11 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

You must have something else going on with your site.  It doesn’t make sense 
you would need to do site by site over just moving to new SQL cluster.  If your 
saying you’re doing it up to clean old crap that’s different.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, December 15, 2017 7:12 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Same here.  We would never be able to just click “go” without a vetted plan in 
place and change management involved.  With 35K clients we are by no means a 
large organization, but if something were to go sideways in the upgrade and we 
skipped the planning and control, there wouldn’t be enough time to update 
resumes once they came for us.

On top of that there are other factors to figure in before you click “go”.  For 
example, in our case we are going to have to do a side-by-side site migration 
because our SQL cluster is no longer supported (hardware is out of warranty).  
Best practices from the Microsoft PFE was to do a site migration as opposed to 
attempting to just moving the database to a new cluster.  So we’re going to 
spend a great deal of time migrating content, collections, sequences, etc. to 
the new site servers, test and validate it all, then start migrating clients.

Then we can click “go” and upgrade the new site to 18xx.

Mike

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Mawdsley R.
Sent: Friday, December 15, 2017 3:55 AM
To: 

RE: [mssms] Upgrading Config Mgr

[Jason Sandys]

I don’t your PFE and I don’t know all of the details involved here, but based 
on what has been written below, no way. Also, be skeptical of anyone who simply 
says “best practice” as that typically implies they don’t actually know any 
technical details and are blindly following some generic recommendation that 
doesn’t take your environment, requirements, and circumstances into account.

J

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Robert Spinelli
Sent: Tuesday, December 19, 2017 8:47 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Yeah, this seems weird to me.  Full disclosure I haven’t done much with SQL 
clusters and SCCM so maybe there is something I’m missing.

I know if you want to use another SQL server for SCCM you can perform a site 
reset and use the option to point to a new SQL server (I’ve done this in the 
past no issue).

  *   
https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/

Maybe others on the email list can chime in and maybe they know if there is 
some gotcha with a SQL cluster that I’m unaware of.

Rob

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Monday, December 18, 2017 11:32 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

The Microsoft PFE for SCCM said that it is Microsoft’s best practice to do a 
side-by-side migration as opposed to doing something like a backup and restore 
of the SQL database to a new cluster.

Our SQL team wanted to do a simple backup and restore to the new cluster, but 
we burned some Premier hours and the PFE advised us that doing that risked 
corrupting the entire database and forcing us into a site recovery.  He said 
the only way to properly do it was the migration.  He said we could try the 
backup/restore but that the success rate for that was not good.

So we’re spending months doing a side-by-side migration.

Mike



From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Monday, December 18, 2017 2:11 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

You must have something else going on with your site.  It doesn’t make sense 
you would need to do site by site over just moving to new SQL cluster.  If your 
saying you’re doing it up to clean old crap that’s different.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, December 15, 2017 7:12 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Same here.  We would never be able to just click “go” without a vetted plan in 
place and change management involved.  With 35K clients we are by no means a 
large organization, but if something were to go sideways in the upgrade and we 
skipped the planning and control, there wouldn’t be enough time to update 
resumes once they came for us.

On top of that there are other factors to figure in before you click “go”.  For 
example, in our case we are going to have to do a side-by-side site migration 
because our SQL cluster is no longer supported (hardware is out of warranty).  
Best practices from the Microsoft PFE was to do a site migration as opposed to 
attempting to just moving the database to a new cluster.  So we’re going to 
spend a great deal of time migrating content, collections, sequences, etc. to 
the new site servers, test and validate it all, then start migrating clients.

Then we can click “go” and upgrade the new site to 18xx.

Mike

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Mawdsley R.
Sent: Friday, December 15, 2017 3:55 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

It’s the same here.. and, I’d hope everywhere have some form of change control. 
 Although it obviously depends on how big the shop is.

I think everyone who has been through a failed upgrade at some point in time, 
is always slightly more weary of the potential for downtime.

Personally, I’ll upgrade my Dev environment a week or so after its out in Fast 
Ring.. then Prod a few weeks after its general release.  But I’ll submit a 
change, and communicate its upcoming upgrade to all relevant teams long before 
and in the build up to it being done.

Rich Mawdsley

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Heaton, Joseph@Wildlife
Sent: 14 December 2017 16:35
To: 

RE: [mssms] Upgrading Config Mgr

[Robert Spinelli]

Yeah, this seems weird to me.  Full disclosure I haven’t done much with SQL 
clusters and SCCM so maybe there is something I’m missing.

I know if you want to use another SQL server for SCCM you can perform a site 
reset and use the option to point to a new SQL server (I’ve done this in the 
past no issue).

· 
https://blogs.technet.microsoft.com/configurationmgr/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server/

Maybe others on the email list can chime in and maybe they know if there is 
some gotcha with a SQL cluster that I’m unaware of.

Rob

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Marable, Mike
Sent: Monday, December 18, 2017 11:32 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

The Microsoft PFE for SCCM said that it is Microsoft’s best practice to do a 
side-by-side migration as opposed to doing something like a backup and restore 
of the SQL database to a new cluster.

Our SQL team wanted to do a simple backup and restore to the new cluster, but 
we burned some Premier hours and the PFE advised us that doing that risked 
corrupting the entire database and forcing us into a site recovery.  He said 
the only way to properly do it was the migration.  He said we could try the 
backup/restore but that the success rate for that was not good.

So we’re spending months doing a side-by-side migration.

Mike



From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Robert Spinelli
Sent: Monday, December 18, 2017 2:11 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

You must have something else going on with your site.  It doesn’t make sense 
you would need to do site by site over just moving to new SQL cluster.  If your 
saying you’re doing it up to clean old crap that’s different.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, December 15, 2017 7:12 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

Same here.  We would never be able to just click “go” without a vetted plan in 
place and change management involved.  With 35K clients we are by no means a 
large organization, but if something were to go sideways in the upgrade and we 
skipped the planning and control, there wouldn’t be enough time to update 
resumes once they came for us.

On top of that there are other factors to figure in before you click “go”.  For 
example, in our case we are going to have to do a side-by-side site migration 
because our SQL cluster is no longer supported (hardware is out of warranty).  
Best practices from the Microsoft PFE was to do a site migration as opposed to 
attempting to just moving the database to a new cluster.  So we’re going to 
spend a great deal of time migrating content, collections, sequences, etc. to 
the new site servers, test and validate it all, then start migrating clients.

Then we can click “go” and upgrade the new site to 18xx.

Mike

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Mawdsley R.
Sent: Friday, December 15, 2017 3:55 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

It’s the same here.. and, I’d hope everywhere have some form of change control. 
 Although it obviously depends on how big the shop is.

I think everyone who has been through a failed upgrade at some point in time, 
is always slightly more weary of the potential for downtime.

Personally, I’ll upgrade my Dev environment a week or so after its out in Fast 
Ring.. then Prod a few weeks after its general release.  But I’ll submit a 
change, and communicate its upcoming upgrade to all relevant teams long before 
and in the build up to it being done.

Rich Mawdsley

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Heaton, Joseph@Wildlife
Sent: 14 December 2017 16:35
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrading Config Mgr

My organization requires a more formal plan for any updates.  And it goes 
through a weekly approval board, so I still have to line everything up nicely.  
I got the go-ahead to upgrade ADK today, but the server updates haven’t gone to 
the approval board yet.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret
Sent: Wednesday, December 13, 2017 12:19 PM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] Upgrading Config Mgr

You must be using lots of new features if you need a plan :) :)
Run the pre-requ