From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Lai, Jerry
Sent: Thursday, December 17, 2009 11:37 PM
To: 'mssms@lists.myitforum.com'
Subject: RE: [mssms] Upgrade to SCCM

oops, bit of a cut-n-paste error:

1        Build a fresh SCCM Site Server ("New SCCM")
2        Detach SMS Secondary Sites from SMS Primary Site
3        Reinstall & configure Secondary Sites and attach to "New SCCM" Site
4        Attach SMS Primary as child to "New SCCM" Site
5        Reassign all computers from SMS Primary Site to "New SCCM" Site
6        In Place upgrade SMS Primary Site to SCCM Sp2 ("Upgraded SCCM")
7        Attach "Upgraded SCCM" Site as a Parent site of "New SCCM" server
8        Allow objects to replicate from "Upgraded SCCM" to child "New SCCM" Site
9        Migrate custom reports/queries (Export/Import)
10       Distribute packages to all Secondary SCCM sites
11       Decommission "Upgraded SCCM" Site Freehills Freehills

 

From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Lai, Jerry
Sent: Friday, 18 December 2009 3:22 PM
To: 'mssms@lists.myitforum.com'
Subject: RE: [mssms] Upgrade to SCCM

 

Back on topic…

We are planning on doing a quasi In-place & side-by-side upgrade. Our current SMS 2003 site only consists of 1 x Primary site server with 5x Secondary site servers attached (managing about 3000 clients including OS Deployments).

This is on overview of our plan of attack:

1        Build a fresh SCCM Site Server ("New SCCM")
2        Detach SMS Secondary Sites from SMS Primary Site
3        Reinstall & configure Secondary Sites and attach to "New SCCM" Site
4        Attach SMS Primary as child to "New SCCM" Site
5        Reassign all computers from SMS Primary Site to "New SCCM" Site
6        In Place upgrade SMS Primary Site to SCCM Sp2 ("Upgraded SCCM")
7        Attach "Upgraded SCCM" Site as a Parent site of "New SCCM" server
8        Allow objects to replicate from "Upgraded SCCM" to child "New SCCM" Site
9        Migrate custom reports/queries (Export/Import)
10       Distribute packages to all Secondary SCCM sites
11       Decommission "Upgraded SCCM" Site Freehills Freehills

Estimated server downtime (if all goes well) is one weekend.  We will be running through this process in the Virtual lab several times before we do it live.

Jerry Lai
Test & Integration Analyst
Freehills

T +61 3 9288 1780
M +61 419 898 461
F +61 3 9288 1567
www.freehills.com
Please consider the environment before printing this email

From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Michael mott
Sent: Friday, 18 December 2009 8:15 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrade to SCCM

 

Heh, just noticed the email addy

 

Mike Mott

734-6154151

UMHS MCIT Ent Device Engr Mgmt.



>>> On 12/17/2009 at  2:39 PM, in message <468346750_168023473@PE3-4-myitforum.orcsweb.com>, "Eric Morrison" <eric@kauhana.com> wrote:

Wow, is your desktop gold plated?

 

From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of John
Sent: Thursday, December 17, 2009 1:34 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] Upgrade to SCCM

 

I disagree, the only way I would not do an in place upgrade is if I needed to also replace my hardware. I upgraded SMS 2003 to SCCM where I used to work and it was a piece of cake.

BTW... we had 3000 machines there and the hardware for my central site server was $25,000. I don't know what kind of server you can get for $6000.00, my desktop cost double that.

 

 


From: "Miller, Todd" <todd-miller@uiowa.edu>
Sent: Thursday, December 17, 2009 12:26 PM
To: mssms@lists.myITforum.com
Subject: RE: [spam?####] [mssms] Upgrade to SCCM

My opinion is that there are way too many new features in SCCM that need to be freshly configured including patching and OS deployment that in place upgrade is not viable.

 

What is your risk tolerance?  What would happen to your organization if key features of SMS or even the whole thing were not available for 2-4 weeks?  Would people go crazy or would you have some time to get everything working again?  I think it is a very real possibility that it could take significant time to get patching and OS Deployment working again when doing an in place upgrade from SMS to SCCM.  If people lost the ability to remote control systems for 2 or 3 days or deploy new systems for a couple weeks, would you get roasted on a fire? 

 

You should be able to buy a new server capable of running SCCM on a site your size for around $6000 - $9000.  For my organization, this expense of new hardware was worth the reduced risk.  Plus, my older SMS hardware was due for replacement in a year.

 

I am running on SMS 2003 right now, and it is the same server I had upgraded from SMS 2.0 in 2005.  I have made lots of misguided configuration decisions that in hindsight that I would not make today.  I am seeing SCCM 2007 as a way to start fresh, taking everything I've learned about SMS and client management in general over the last 10 years and build the new site with that in mind.  .  Doing it this way, we lose historical data, but that information is secondary to having the operational data and systems available with as small a blip as possible.  I plan on taking 4-6 months to get 2007 configured the way I want and then on some day in the Spring after testing and testing and testing, I am going to move all the clients over the course of a day or two.  That's my current plan anyway.

 

 


From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Mike Meyers
Sent: Thursday, December 17, 2009 11:21
To: mssms@lists.myITforum.com
Subject: [spam?####] [mssms] Upgrade to SCCM

 

Finally they are letting us upgrade to SCCM. Anyone have a Pros and Cons to whether a side by side is better or worse than in place. We have a single site, do desktop deployment, and have hundreds of objects to move. We are currently SMS2003 SP1. 3000 Clients

Mike Meyers
IT Administrator
( 800-852-7600 x4639 * mikeme@vsp.com
( Mobile 916-384-7037 FAX: 916-463-9027
VSP, 3333 Quality Drive, Rancho Cordova, CA 95670
What's the #1 health-related work complaint? Find out at SeeMuchMore.com

MailGate.vsp.com made the following annotations
---------------------------------------------------------------------
NOTICE: This message is intended only for the individual to whom it is addressed and may contain information that is confidential or privileged. If you are not the intended recipient, or the employee or person responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution, copying or use is strictly prohibited. If you have received this communication in error, please notify the sender and destroy or delete this communication immediately. ---------------------------------------------------------------------


==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/


==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/

**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues


==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/


Freehills' offices will be closed over the holiday period from Friday 25 December 2009, and will re-open on Monday 4 January 2010.


FREEHILLS
This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. Freehills is not responsible for any changes made to a document other than those made by Freehills or for the effect of the changes on the document's meaning. Freehills accepts no liability for any damage caused by this email or its attachments due to viruses interference interception corruption or unauthorised access.



==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/


Freehills' offices will be closed over the holiday period from Friday 25 December 2009, and will re-open on Monday 4 January 2010.


FREEHILLS
This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. Freehills is not responsible for any changes made to a document other than those made by Freehills or for the effect of the changes on the document's meaning. Freehills accepts no liability for any damage caused by this email or its attachments due to viruses interference interception corruption or unauthorised access.



==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/

Published with BlogMailr



Trackbacks

No Trackbacks

Comments

No Comments