Rip and Replace

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Rip and Replace

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Rip and Replace

Page: [1]

Message

<< Older Topic Newer Topic >>

Rip and Replace - 7/31/2008 1:35:52 PM

gquitugua

Posts: 15
Score: 0
Joined: 9/27/2005
Status: offline

We are currently running SMS 2003 and are migrating to SCCM. Our entire network/SMS infrastructure has changed so I needed to rearchitect SMS but I figured since I'm implementing SCCM, I would basically decommission SMS and then stand up a new SCCM box. Does anyone see any problems with going this route? I'm not concerned about the client data in the database.

Post #: 1

RE: Rip and Replace - 7/31/2008 2:44:47 PM

dnemec

Posts: 36
Score: 0
Joined: 7/19/2001
From: Beaverton, Oregon
Status: offline

If there's no requirement to keep the historical data of SMS 2003, then, IMHO it is best to stand up SCCM separately and then migrate the clients from SMS to SCCM.

I did this when moving from SMS 2.0 to SMS 2003, and I'll be doing this again soon when we move from SMS 2003 to SCCM.

Good luck!
Dale

(in reply to gquitugua)

Post #: 2

RE: Rip and Replace - 8/7/2008 12:25:44 PM

mserafine

Posts: 1660
Score: 157
Joined: 4/7/2003
Status: offline

I second Dale's comment.

_____________________________

Mark Serafine, MCSE, MCTS | Senior Premier Field Engineer - Manageability (SMS, MOM, System Center) | Microsoft Corporation

(in reply to dnemec)

Post #: 3