New Server -Coming from SBS2003 domain

We have purchased a new 2003 R2 Server (Hardware, OS & CALs) that is
going to replace a SBS2003 Server. The Client OSs are a mixture of
2kPro, XP SP2 & SP3.We want to keep the same Domain name when we
install the new Server.

We assume on the clients we will just have to join them to the "new"
domain, and we can either keep the same computer name or change it.

Does anyone foresee any issues with connecting these clients? For
instance what will happen to the user profiles (desktops,
Favorites,etc) when they connect to this new Server.

Or, would we be better off using a new domain name? Pros/Cons??

Thanks!

 

"PorBar" <compsosinc@gmail.com> wrote in message
news:79758e8b-ec94-4195-ace8-618f996834b7@33g2000vbe.googlegroups.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> We have purchased a new 2003 R2 Server (Hardware, OS & CALs) that is
> going to replace a SBS2003 Server. The Client OSs are a mixture of
> 2kPro, XP SP2 & SP3.We want to keep the same Domain name when we
> install the new Server.
>
> We assume on the clients we will just have to join them to the "new"
> domain, and we can either keep the same computer name or change it.
>
> Does anyone foresee any issues with connecting these clients? For
> instance what will happen to the user profiles (desktops,
> Favorites,etc) when they connect to this new Server.
>
> Or, would we be better off using a new domain name? Pros/Cons??
>
> Thanks!
><!--colorc--><!--/colorc-->


If you are keeping the same name, see if this helps.

SBS 2003 to Server 2008/Exchange 2007


Keep in mind, you shouldn't have to do anything with the client machines or
anything else, if staying in the same domain. Just keep in mind as well, the
differences and the GPOs that SBS put in place. I mean you can keep them,
but just be aware of that.

I also cross-posted this to the SBS newsgroup for more specific exposure.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
for regional support phone numbers.

 

More importantly, what is the motivation for the move away from SBS?

What is the purpose of the new server?

(doing it Ace style, which would also be the way I would)
If you add the new box as a member to the SBS AD it will be subject to SBS
policies. When you promote the new box to a DC in the SBS AD it will hold a
copy of same policies. When, and if, you subsequently remove SBS from the AD
the policies will remain in force, just under the control of the new server.

(in a throwaway AD scenario)
It doesn't matter that the new AD has the same name as the old, it will have
a new domain SID. The only real problem would be if you allowed two same
named servers on the one ethernet.

"Ace Fekay [MCT]" <aceman@mvps.RemoveThisPart.org> wrote in message
news:O18EB5yKKHA.3000@TK2MSFTNGP04.phx.gbl...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "PorBar" <compsosinc@gmail.com> wrote in message
> news:79758e8b-ec94-4195-ace8-618f996834b7@33g2000vbe.googlegroups.com...<!--coloro:green--><span style="color:green <!--/coloro-->
>> We have purchased a new 2003 R2 Server (Hardware, OS & CALs) that is
>> going to replace a SBS2003 Server. The Client OSs are a mixture of
>> 2kPro, XP SP2 & SP3.We want to keep the same Domain name when we
>> install the new Server.
>>
>> We assume on the clients we will just have to join them to the "new"
>> domain, and we can either keep the same computer name or change it.
>>
>> Does anyone foresee any issues with connecting these clients? For
>> instance what will happen to the user profiles (desktops,
>> Favorites,etc) when they connect to this new Server.
>>
>> Or, would we be better off using a new domain name? Pros/Cons??
>>
>> Thanks!
>><!--colorc--><!--/colorc-->
>
>
> If you are keeping the same name, see if this helps.
>
> SBS 2003 to Server 2008/Exchange 2007
>
>
> Keep in mind, you shouldn't have to do anything with the client machines
> or anything else, if staying in the same domain. Just keep in mind as
> well, the differences and the GPOs that SBS put in place. I mean you can
> keep them, but just be aware of that.
>
> I also cross-posted this to the SBS newsgroup for more specific exposure.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> for regional support phone numbers. <!--colorc--><!--/colorc-->

 

On 9/1/2009 11:59 AM, PorBar wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> We have purchased a new 2003 R2 Server (Hardware, OS & CALs) that is
> going to replace a SBS2003 Server. The Client OSs are a mixture of
> 2kPro, XP SP2 & SP3.We want to keep the same Domain name when we
> install the new Server.<!--colorc--><!--/colorc-->

I have never had a need to mess with it, but it is my (mis)understanding
that there is a "Step Up" package that will re-license your SBS as
standard products (Windows / Exchange / ISA / etc.).

If you are happy with your current domain and don't want to make
invasive changes to it, I would investigate that route to allow you to
grow out of the SBS portion. When you are no longer an SBS install you
should be able to add additional servers to your domain with out a
problem. (Last I knew, an SBS product would not want to relinquish
control to a non-SBS product, even if it was newer, say 2k3 -> 2k8.)



Grant. . . .

 

On Sep 1, 9:11 pm, Grant Taylor <gtay...@riverviewtech.net> wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> On 9/1/2009 11:59 AM, PorBar wrote:
><!--coloro:green--><span style="color:green <!--/coloro-->
> > We have purchased a new 2003 R2 Server (Hardware, OS & CALs) that is
> > going to replace a SBS2003 Server. The Client OSs are a mixture of
> > 2kPro, XP SP2 & SP3.We want to keep the same Domain name when we
> > install the new Server.<!--colorc--><!--/colorc-->
>
> I have never had a need to mess with it, but it is my (mis)understanding
> that there is a "Step Up" package that will re-license your SBS as
> standard products (Windows / Exchange / ISA / etc.).
>
> If you are happy with your current domain and don't want to make
> invasive changes to it, I would investigate that route to allow you to
> grow out of the SBS portion.  When you are no longer an SBS install you
> should be able to add additional servers to your domain with out a
> problem.  (Last I knew, an SBS product would not want to relinquish
> control to a non-SBS product, even if it was newer, say 2k3 -> 2k8.)
>
> Grant. . . .<!--colorc--><!--/colorc-->

SBS was overkill for this network..they never used Exchnage in the
last 6 years, ISA as default, etc. Now we can purchase less hardware
(SBS required special partitioning, used RAID 5, etc) and keep it
"clean" with just 2003 Server. Going to SBS 2008 would require more
overhead too..more hardware. Plus the software vendor requested we not
use SBS on the new server this time.

So..my original questions....

 

"PorBar" <compsosinc@gmail.com> wrote in message
news:5e7369ba-9093-4577-9cf0-617a48ab8b05@y42g2000yqb.googlegroups.com...
On Sep 1, 9:11 pm, Grant Taylor <gtay...@riverviewtech.net> wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> On 9/1/2009 11:59 AM, PorBar wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
>><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> We have purchased a new 2003 R2 Server (Hardware, OS & CALs) that is
>>> going to replace a SBS2003 Server. The Client OSs are a mixture of
>>> 2kPro, XP SP2 & SP3.We want to keep the same Domain name when we
>>> install the new Server.<!--colorc--><!--/colorc-->
>>
>> I have never had a need to mess with it, but it is my (mis)understanding
>> that there is a "Step Up" package that will re-license your SBS as
>> standard products (Windows / Exchange / ISA / etc.).
>>
>> If you are happy with your current domain and don't want to make
>> invasive changes to it, I would investigate that route to allow you to
>> grow out of the SBS portion. When you are no longer an SBS install you
>> should be able to add additional servers to your domain with out a
>> problem. (Last I knew, an SBS product would not want to relinquish
>> control to a non-SBS product, even if it was newer, say 2k3 -> 2k8.)
>>
>> Grant. . . .<!--colorc--><!--/colorc-->
>
> SBS was overkill for this network..they never used Exchnage in the
> last 6 years, ISA as default, etc. Now we can purchase less hardware
> (SBS required special partitioning, used RAID 5, etc) and keep it
> "clean" with just 2003 Server. Going to SBS 2008 would require more
> overhead too..more hardware. Plus the software vendor requested we not
> use SBS on the new server this time.
>
> So..my original questions....<!--colorc--><!--/colorc-->



So... did you find my response and SuperGumby's response helpful??

Ace

 

On Sep 2, 8:43 am, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "PorBar" <compsos...@gmail.com> wrote in message
>
> news:5e7369ba-9093-4577-9cf0-617a48ab8b05@y42g2000yqb.googlegroups.com...
> On Sep 1, 9:11 pm, Grant Taylor <gtay...@riverviewtech.net> wrote:
>
>
>
>
><!--coloro:green--><span style="color:green <!--/coloro-->
> > On 9/1/2009 11:59 AM, PorBar wrote:<!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >>> We have purchased a new 2003 R2 Server (Hardware, OS & CALs) that is
> >>> going to replace a SBS2003 Server. The Client OSs are a mixture of
> >>> 2kPro, XP SP2 & SP3.We want to keep the same Domain name when we
> >>> install the new Server.<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >> I have never had a need to mess with it, but it is my (mis)understanding
> >> that there is a "Step Up" package that will re-license your SBS as
> >> standard products (Windows / Exchange / ISA / etc.).<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >> If you are happy with your current domain and don't want to make
> >> invasive changes to it, I would investigate that route to allow you to
> >> grow out of the SBS portion.  When you are no longer an SBS install you
> >> should be able to add additional servers to your domain with out a
> >> problem.  (Last I knew, an SBS product would not want to relinquish
> >> control to a non-SBS product, even if it was newer, say 2k3 -> 2k8.)<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >> Grant. . . .<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro-->
> > SBS was overkill for this network..they never used Exchnage in the
> > last 6 years, ISA as default, etc. Now we can purchase less hardware
> > (SBS required special partitioning, used RAID 5, etc) and keep it
> > "clean" with just 2003 Server. Going to SBS 2008 would require more
> > overhead too..more hardware. Plus the software vendor requested we not
> > use SBS on the new server this time.<!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro-->
> > So..my original questions....<!--colorc--><!--/colorc-->
>
> So... did you find my response and SuperGumby's response helpful??
>
> Ace- Hide quoted text -
>
> - Show quoted text -<!--colorc--><!--/colorc-->

YEs, thank you guys!

 

"PorBar" <compsosinc@gmail.com> wrote in message
news:afcde5e7-5e1c-4539-9a0c-173f2e63edb9@j4g2000yqa.googlegroups.com...
On Sep 2, 8:43 am, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "PorBar" <compsos...@gmail.com> wrote in message
>
> news:5e7369ba-9093-4577-9cf0-617a48ab8b05@y42g2000yqb.googlegroups.com...
> On Sep 1, 9:11 pm, Grant Taylor <gtay...@riverviewtech.net> wrote:
>
>
>
>
><!--coloro:green--><span style="color:green <!--/coloro-->
> > On 9/1/2009 11:59 AM, PorBar wrote:<!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >>> We have purchased a new 2003 R2 Server (Hardware, OS & CALs) that is
> >>> going to replace a SBS2003 Server. The Client OSs are a mixture of
> >>> 2kPro, XP SP2 & SP3.We want to keep the same Domain name when we
> >>> install the new Server.<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >> I have never had a need to mess with it, but it is my
> >> (mis)understanding
> >> that there is a "Step Up" package that will re-license your SBS as
> >> standard products (Windows / Exchange / ISA / etc.).<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >> If you are happy with your current domain and don't want to make
> >> invasive changes to it, I would investigate that route to allow you to
> >> grow out of the SBS portion. When you are no longer an SBS install you
> >> should be able to add additional servers to your domain with out a
> >> problem. (Last I knew, an SBS product would not want to relinquish
> >> control to a non-SBS product, even if it was newer, say 2k3 -> 2k8.)<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >> Grant. . . .<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro-->
> > SBS was overkill for this network..they never used Exchnage in the
> > last 6 years, ISA as default, etc. Now we can purchase less hardware
> > (SBS required special partitioning, used RAID 5, etc) and keep it
> > "clean" with just 2003 Server. Going to SBS 2008 would require more
> > overhead too..more hardware. Plus the software vendor requested we not
> > use SBS on the new server this time.<!--colorc--><!--/colorc-->
><!--coloro:green--><span style="color:green <!--/coloro-->
> > So..my original questions....<!--colorc--><!--/colorc-->
>
> So... did you find my response and SuperGumby's response helpful??
>
> Ace- Hide quoted text -
>
> - Show quoted text -<!--colorc--><!--/colorc-->

YEs, thank you guys!


You are welcome!

Ace