Upgrading SBS 2003 to Windows Server 2003 Standard/Ent.

i want to upgrade my SBS 2003 Prem. Edition to Windows Server 2003
Standard/Ent. Edition without loosing domain. I am running to Exchange server
on SBS. I have heared a SBS migration kit performing these steps easily. i
have thoroughly technet site but didnt find any SBS migration kit or SBS
migration article.

regards

Upgrade IMO is not what you are doing LOL
Yes I'm bias of SBS

If you are running out of Licenses >75
You need a Transition Pack
http://www.microsoft.com/windowsserv...ransition.mspx

You can save Domain with it.

Russ

--
Russell Grover - SBITS.Biz
Microsoft Gold Certified Partner
Microsoft Small Business Specialist
World Wide Remote SBS2003 Support - http://www.SBITS.Biz
Get Help Now! http://www.crossloop.com/SBITSdotBiz


"S H A R I Q U E" <SHARIQUE@discussions.microsoft.com> wrote in message
news:8ADD94A9-04D2-4CF6-A28E-0DBDA058FD0D@microsoft.com...
>i want to upgrade my SBS 2003 Prem. Edition to Windows Server 2003
> Standard/Ent. Edition without loosing domain. I am running to Exchange
> server
> on SBS. I have heared a SBS migration kit performing these steps easily.
> i
> have thoroughly technet site but didnt find any SBS migration kit or SBS
> migration article.
>
> regards
>

Not sure I'd call that an upgrade, but regardless - you have two choices - a
Transition Pack, which will convert the existing to Windows Server 2003
Standard Edition with no limitations plus Exchange Server 2003 Standard
Edition. Plus your Premium components are unlocked as well. You'll need the
Premium Transition Pack appropriate to your version (SP1 or R2), and the
same number of CALs you currently have.

The "migration" you're referring to is probably Swing Migration
(www.sbsmigration.com) - that's a solution, assuming you want to lose your
investment in SBS and buy full, new, copies of Windows Server and Exchange,
along with your CALs.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"S H A R I Q U E" <SHARIQUE@discussions.microsoft.com> wrote in message
news:8ADD94A9-04D2-4CF6-A28E-0DBDA058FD0D@microsoft.com...
>i want to upgrade my SBS 2003 Prem. Edition to Windows Server 2003
> Standard/Ent. Edition without loosing domain. I am running to Exchange
> server
> on SBS. I have heared a SBS migration kit performing these steps easily.
> i
> have thoroughly technet site but didnt find any SBS migration kit or SBS
> migration article.
>
> regards
>

which option is better choice..Swing migration or Transition Pack..can i save
domain using both strategies....
what is the cost associated with transition pack suppose that i have 100 CAL
requirements, that is, difference of 25 users from SBS users.
i assume that using Swing migration i dont need to pay for Transition Pack
or purchase transition pack either.
furthermore, i have yet to find any technet resource regarding migrating SBS
2003 to Windows Server 2003 Standard/Ent. Edition ....
or if you have any detailed documentation for Swing Migration or transition
pack.



"Charlie Russel - MVP" wrote:

> Not sure I'd call that an upgrade, but regardless - you have two choices - a
> Transition Pack, which will convert the existing to Windows Server 2003
> Standard Edition with no limitations plus Exchange Server 2003 Standard
> Edition. Plus your Premium components are unlocked as well. You'll need the
> Premium Transition Pack appropriate to your version (SP1 or R2), and the
> same number of CALs you currently have.
>
> The "migration" you're referring to is probably Swing Migration
> (www.sbsmigration.com) - that's a solution, assuming you want to lose your
> investment in SBS and buy full, new, copies of Windows Server and Exchange,
> along with your CALs.
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "S H A R I Q U E" <SHARIQUE@discussions.microsoft.com> wrote in message
> news:8ADD94A9-04D2-4CF6-A28E-0DBDA058FD0D@microsoft.com...
> >i want to upgrade my SBS 2003 Prem. Edition to Windows Server 2003
> > Standard/Ent. Edition without loosing domain. I am running to Exchange
> > server
> > on SBS. I have heared a SBS migration kit performing these steps easily.
> > i
> > have thoroughly technet site but didnt find any SBS migration kit or SBS
> > migration article.
> >
> > regards
> >
>
>

In article <8ADD94A9-04D2-4CF6-A28E-0DBDA058FD0D@microsoft.com>,
SHARIQUE@discussions.microsoft.com says...
> i want to upgrade my SBS 2003 Prem. Edition to Windows Server 2003
> Standard/Ent. Edition without loosing domain. I am running to Exchange server
> on SBS. I have heared a SBS migration kit performing these steps easily. i
> have thoroughly technet site but didnt find any SBS migration kit or SBS
> migration article.

We moved a couple clients from SBS to Win 2003 Std R2 solutions that had
outgrown their limitations of SBS.

The SwingIT method works very well, and we didn't transition, just got a
temporary server (high-end workstation was used) and then did the Swing
offline, restored a backup off-network, got it all working, removed old
server, installed new server, 15 minutes of down-time in most cases, and
everything kept working.

What made things really easy for us was that in all cases we had the
Exchange part of SBS uninstalled and were already using a separate
Exchange server (not part of SBS) because of requirements, so it made
the Exchange migration a non-issue.

http://www.sbsmigration.com/


--
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@rrohio.com (remove 999 for proper email address)

for the sake of clarity can you go a bit deeper....as to HOWs of
sbsmigration...
i have managed to grasp following ideas from your reply.
is it possible that i install Windows Server 20003 Stndrd/Ent. on separate
machine make it ADC of SBS...then replicate AD schema and
attributes...transfer FSMO roles to new server and decommision old one.

i would appreciate your clarity in your reply.
is this what initial process ????

"Leythos" wrote:

> In article <8ADD94A9-04D2-4CF6-A28E-0DBDA058FD0D@microsoft.com>,
> SHARIQUE@discussions.microsoft.com says...
> > i want to upgrade my SBS 2003 Prem. Edition to Windows Server 2003
> > Standard/Ent. Edition without loosing domain. I am running to Exchange server
> > on SBS. I have heared a SBS migration kit performing these steps easily. i
> > have thoroughly technet site but didnt find any SBS migration kit or SBS
> > migration article.
>
> We moved a couple clients from SBS to Win 2003 Std R2 solutions that had
> outgrown their limitations of SBS.
>
> The SwingIT method works very well, and we didn't transition, just got a
> temporary server (high-end workstation was used) and then did the Swing
> offline, restored a backup off-network, got it all working, removed old
> server, installed new server, 15 minutes of down-time in most cases, and
> everything kept working.
>
> What made things really easy for us was that in all cases we had the
> Exchange part of SBS uninstalled and were already using a separate
> Exchange server (not part of SBS) because of requirements, so it made
> the Exchange migration a non-issue.
>
> http://www.sbsmigration.com/
>
>
> --
> - Igitur qui desiderat pacem, praeparet bellum.
> - Calling an illegal alien an "undocumented worker" is like calling a
> drug dealer an "unlicensed pharmacist"
> spam999free@rrohio.com (remove 999 for proper email address)
>

The Swing IT method is fundamentally based on retaining the origin server(s)
'as is' for business continuance. In a 'pure' swing the only change to the
origin AD is the addition of a DC, the 'swing server'.

The swing server is then taken offline (after replicating the AD) while the
FSMO roles remain with the origin server(s). You then 'seize', rather than
transfer, the FSMO roles on the swing server while it is disconnected from
the origin AD. At this time the additional DC (swing server) can be removed
from the origin AD and the origin is back to a pre-swing condition. (nobody
['cept me, maybe] normally bothers to do this. The presumption is that the
origin AD is going to, eventually, be discarded. Who cares if it has an
orphan DC?)

At this time you have one DC (the swing server) containing a copy of your AD
and you clean that copy up (I would remove any additional DCs from the AD
copy but you might want to run that idea past Jeff, I don't always follow
the procedure to his letter), including any references to Exchange.

At this point you can shut down all existing DC's in the origin AD and put
the swing server online but here comes the 1st mention of SBS (you will note
that until now I have not mentioned SBS, the swing process is 'designed for'
but not 'limited to' SBS). _Normally_ you would build your SBS at this point
using Jeff's version of 'Adding SBS to an existing AD', which is only
slightly different to the MS way of doing same. Machines and Users can
hardly tell the migration has happened because of the process. Most
'swingers' do not put the swing server online, only the eventual SBS.

In an SBS to SBS swing, and assuming you are using Exchange, you have
additional tasks about copying DATA and 'forklifting' the Exchange stores.
This is _basically_ the only 'down time' for users.

in non-SBS to SBS, SBS to non-SBS, non-SBS to non-SBS, or multiple DC swings
there are other points to consider and these will likely contribute to
further down time. eg. in a multiple DC swing I would DCPromo all origin
servers that are to be retained in the swung domain out of DC roles while
connected to the origin AD and back to DC roles after the swing.

"S H A R I Q U E" <SHARIQUE@discussions.microsoft.com> wrote in message
news:C57DE0A7-22A3-49EE-B393-9D3366C3900D@microsoft.com...
> for the sake of clarity can you go a bit deeper....as to HOWs of
> sbsmigration...
> i have managed to grasp following ideas from your reply.
> is it possible that i install Windows Server 20003 Stndrd/Ent. on separate
> machine make it ADC of SBS...then replicate AD schema and
> attributes...transfer FSMO roles to new server and decommision old one.
>
> i would appreciate your clarity in your reply.
> is this what initial process ????
>
> "Leythos" wrote:
>
>> In article <8ADD94A9-04D2-4CF6-A28E-0DBDA058FD0D@microsoft.com>,
>> SHARIQUE@discussions.microsoft.com says...
>> > i want to upgrade my SBS 2003 Prem. Edition to Windows Server 2003
>> > Standard/Ent. Edition without loosing domain. I am running to Exchange
>> > server
>> > on SBS. I have heared a SBS migration kit performing these steps
>> > easily. i
>> > have thoroughly technet site but didnt find any SBS migration kit or
>> > SBS
>> > migration article.
>>
>> We moved a couple clients from SBS to Win 2003 Std R2 solutions that had
>> outgrown their limitations of SBS.
>>
>> The SwingIT method works very well, and we didn't transition, just got a
>> temporary server (high-end workstation was used) and then did the Swing
>> offline, restored a backup off-network, got it all working, removed old
>> server, installed new server, 15 minutes of down-time in most cases, and
>> everything kept working.
>>
>> What made things really easy for us was that in all cases we had the
>> Exchange part of SBS uninstalled and were already using a separate
>> Exchange server (not part of SBS) because of requirements, so it made
>> the Exchange migration a non-issue.
>>
>> http://www.sbsmigration.com/
>>
>>
>> --
>> - Igitur qui desiderat pacem, praeparet bellum.
>> - Calling an illegal alien an "undocumented worker" is like calling a
>> drug dealer an "unlicensed pharmacist"
>> spam999free@rrohio.com (remove 999 for proper email address)
>>

I don't have costs - you should do your own calculations. Both methods will
retain your domain.

The Swing Migration is quite reasonable (but includes no CAL or license
conversions), and will do what you want. You'll be on your own for CALs -
it's simply a set of tools, documentation and support for migration to/from
SBS. It won't affect your existing license - you'd need to purchase new
licenses for Server, Exchange, CALs and any others you're using. See the
sbsmigration web site for details. Even though it's primarily designed to
migrate from one version of SBS to another version of SBS, it can certainly
be used for what you want.

Transition pack will convert your existing licenses into full product
licenses, and remove the single domain/no trust limitation os SBS. You
purchase CALs to match your existing CALs, and if you need additional beyond
the current CAL level, you purchase those separately as normal product CALs.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"S H A R I Q U E" <SHARIQUE@discussions.microsoft.com> wrote in message
news:06F65534-367C-44FB-BE2E-2CE3C78ECEFF@microsoft.com...
> which option is better choice..Swing migration or Transition Pack..can i
> save
> domain using both strategies....
> what is the cost associated with transition pack suppose that i have 100
> CAL
> requirements, that is, difference of 25 users from SBS users.
> i assume that using Swing migration i dont need to pay for Transition
> Pack
> or purchase transition pack either.
> furthermore, i have yet to find any technet resource regarding migrating
> SBS
> 2003 to Windows Server 2003 Standard/Ent. Edition ....
> or if you have any detailed documentation for Swing Migration or
> transition
> pack.
>
>
>
> "Charlie Russel - MVP" wrote:
>
>> Not sure I'd call that an upgrade, but regardless - you have two
>> choices - a
>> Transition Pack, which will convert the existing to Windows Server 2003
>> Standard Edition with no limitations plus Exchange Server 2003 Standard
>> Edition. Plus your Premium components are unlocked as well. You'll need
>> the
>> Premium Transition Pack appropriate to your version (SP1 or R2), and the
>> same number of CALs you currently have.
>>
>> The "migration" you're referring to is probably Swing Migration
>> (www.sbsmigration.com) - that's a solution, assuming you want to lose
>> your
>> investment in SBS and buy full, new, copies of Windows Server and
>> Exchange,
>> along with your CALs.
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>>
>> "S H A R I Q U E" <SHARIQUE@discussions.microsoft.com> wrote in message
>> news:8ADD94A9-04D2-4CF6-A28E-0DBDA058FD0D@microsoft.com...
>> >i want to upgrade my SBS 2003 Prem. Edition to Windows Server 2003
>> > Standard/Ent. Edition without loosing domain. I am running to Exchange
>> > server
>> > on SBS. I have heared a SBS migration kit performing these steps
>> > easily.
>> > i
>> > have thoroughly technet site but didnt find any SBS migration kit or
>> > SBS
>> > migration article.
>> >
>> > regards
>> >
>>
>>