Re: Side by Side upgrade to CM2007

I think I understand what you are doing but by creating the child site you will have the issues that I outline before with packages, reporting , collection locking, etc. None of this items are show stoppers however you need to be aware of them as they will give you headache.

As with any upgrade it is best to perform the upgrade within a lab thereby allow you to work through all the issues before you upgrade production.





"Carol Deavy" <CarolDeavy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:88E026F8-E7B9-4A48-8C78-F96663A8541C@xxxxxxxxxxxxxxxx
Thanks for your replies.

I am now really unsure if I am going about the upgrade properly?

This is what I have done (in a testing environment)
Upgraded existing Windows 2003 SMS 2003 server to CM 2007
Created new Windows 2008 server, installed another instance of SQL on new
server, now installing new Configuration Manager site to use new SQL instance

My plan is to have the new CM be a child site for the upgraded CM and once
the information has flowed down from the upgraded site to the new CM child
site, I should be able to upgrade my clients then break the relationship and
have the child site become the central site. Does this make sense? Am I on
the right track? Is there something I should be aware of that I should or
should not do?

"Garth" wrote:

I'm easily confused. :-)

Doing what you suggest will mean a few things.



· Only existing package and collection will flow downs to that site

o Source directories will not flow down, only compressed packages

o Package and collection may need to be “unlocked”

· All Reports and Queries will need to be export and imported.

· All client inventory data is lost. But that is not usually a big
deal.

· Keep in mind that all junk from above will also come down to the
new site too.



"Carol Deavy" <CarolDeavy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EA0E9B51-8980-4B24-A7BD-902346AA2B55@xxxxxxxxxxxxxxxx
> I'm confused and maybe I didn't explain things well??
>
> I have a serve which has been upgraded from SMS to CM. This server has > a
> locally install SQL for SMS/CM
>
> I now want to set up a new Windows 2008 server with CM in a new site. > I
> was
> thinking I would then allow the information to sync up with the > existing
> upgraded server before I break the relationship and be left with only > the
> new
> Windows 2008 CM server.
>
> If I install a new SQL on the new Windows 2008 CM box, how does the
> information between the existing upgraded CM sync with the new CM?
>
> Have I confused you more??
>
> "Garth" wrote:
>
>> Where is the database for the new ConfigMgr server on the old server >> or
>> locally?
>>
>> If it is on the old server, start again and install SQL locally.
>>
>>
>>
>>
>>
>>
>> "Carol Deavy" <CarolDeavy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:CF1135C1-A96D-416C-85E3-19A1B6E2A5D4@xxxxxxxxxxxxxxxx
>> > Just upgraded my SMS to CM2007 and now want to continue with the >> > steps
>> > I
>> > outlined for a side-by-side upgrade, however, I just ran into a
>> > question
>> > I'm
>> > not sure I thought about before this point. I have a new Windows >> > 2008
>> > server
>> > which I want to install CM2007, join it to the upgraded CM2007, then
>> > eventually break the relationship so that I only have the new >> > CM2007;
>> > however, what do I do with SQL? Currently the SQL database is
>> > installed
>> > on
>> > the existing upgraded CM2007 box but my plan is to decommission this
>> > box
>> > after the completed side-by-side upgrade to Configuration Manager is
>> > completed. I assume I use the existing database then install SQL on >> > my
>> > newly
>> > created CM2007 box after, but what is the migration from the >> > existing
>> > SQL
>> > database to the new SQL? I must have missed something in the >> > upgrade
>> > documentation...
>>


.

Relevant Pages

  • RE: MSDE to SQL Server
    ... I understand that you want to upgrade MSDE instances ... We can upgrade the instance SHAREPOINT to SQL and it is not recommended ... Business Server 2003 ...
    (microsoft.public.windows.server.sbs)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... After you uninstall SQL 2005, the instance which you upgraded will not go ... Uninstall and then reinstall ISA server. ... Uninstall and then reinstall the Monitoring component. ... Tools to Maintenance, change Monitoring component to Install, and then ...
    (microsoft.public.windows.server.sbs)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... What's the error message you see when installing SQL? ... the easier way is to restore the server from recent backup. ... Screen shot of the error when you install SQL 2005 Workgroup edition. ... <The server-based applications that were running fine are: McAFee EPO, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now ... A word mail merge document could access a SQL database via ... We want to install to gain an understanding. ... Once we've managed to install the SQL Server Client we can start to ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: how do I change the user install wizard to create user folder in different location?
    ... Some people read the instructions in such a way that they install both a new ... instance of sql, ... Never slight the SBS wizards. ... I reinstalled from scratch using the Dell OpenManage Server ...
    (microsoft.public.windows.server.sbs)
Loading