|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I gather this isn't as automated as I had hoped judging from the list of
similar issues and depth/detail of the replies I've seen.
I have older hardware running SBS 2003 Std. It is running Exchange 2000,
DNS, no DHCP, 1 NIC, IIS. It is my home setup (training, lab, websites).
I have new server sitting and waiting. It has 1 NIC, but I wouldn't mind
adding 2nd NIC if recommended. Currently routers allowing all servers/WSs to
access internet.
I have not seen much on migrating from SBS 2003 to SBS 2003 R2 (mostly just
2000 and pre-2000).
I would like to transfer Exchange mailboxes and mail. logins/settings, DNS
settings, AD. Ideally, I'd like to end up with same IP on new server, but
I'm not married to the idea.
Also, I "think" I made a mistake setting up my original SBS server. My
public domain is "myDomain.com". I created my server as "local.myDomain.com"
and that seems to haunt me to this day as I run DNS tests from external sites
testing how well my site comforms to standards. I'm guessing I probably pay a
penalty if I don't keep the exact same nasme on new server?
This is just me mostly on this SBS server and WSs - but I have other member
servers, work stations, actually 3 routers (1 wires, 1 wireless, 1 wireless
dedicated to xBoxs - long story), so I'd have to tweak a limited number of
devices to change to a new internal DNS IP if I picked a new one. But I
would like to retain my mail on several mail ids (my personal, the admin).
Maybe I should not bother to try to "clone" old server to new server - just
create new SBS server and manually rebuild taking old SBS off network?
|
|
doug <dmartin[ at ]newsgroups.nospam> wrote:
[Quoted Text] > I gather this isn't as automated as I had hoped judging from the list
> of similar issues and depth/detail of the replies I've seen.
>
> I have older hardware running SBS 2003 Std. It is running Exchange
> 2000, DNS, no DHCP, 1 NIC, IIS. It is my home setup (training, lab,
> websites).
>
> I have new server sitting and waiting. It has 1 NIC, but I wouldn't
> mind adding 2nd NIC if recommended. Currently routers allowing all
> servers/WSs to access internet.
I don't like two NICs on a domain controller/DNS/WINS box - if you aren't
using ISA, don't bother.
>
> I have not seen much on migrating from SBS 2003 to SBS 2003 R2
> (mostly just 2000 and pre-2000).
>
> I would like to transfer Exchange mailboxes and mail.
> logins/settings, DNS settings, AD. Ideally, I'd like to end up with
> same IP on new server, but I'm not married to the idea.
The IP address can always be changed later ...unlike your internal DNS
domain name.
>
> Also, I "think" I made a mistake setting up my original SBS server.
> My public domain is "myDomain.com". I created my server as
> "local.myDomain.com" and that seems to haunt me to this day as I run
> DNS tests from external sites testing how well my site comforms to
> standards. I'm guessing I probably pay a penalty if I don't keep the
> exact same nasme on new server?
If you want to move your entire AD structure over, then you're stuck with
it. But I don't see why you would think local.mydomain.com would be a
problem....it shouldn't, if your DNS server is configured properly. I use
stuff like that all the time. If local.mydomain.com is not a valid *public*
subdomain then it should work fine.
>
> This is just me mostly on this SBS server and WSs - but I have other
> member servers, work stations, actually 3 routers (1 wires, 1
> wireless, 1 wireless dedicated to xBoxs - long story), so I'd have to
> tweak a limited number of devices to change to a new internal DNS IP
> if I picked a new one. But I would like to retain my mail on several
> mail ids (my personal, the admin). Maybe I should not bother to try
> to "clone" old server to new server - just create new SBS server and
> manually rebuild taking old SBS off network?
Check out www.sbsmigration.com for just the ticket.
|
|
www.sbsmigration.com - took a look previously. They seem to be a "for
profit" group. Is it worthwhile for a one time hit?
I understand there are post-build migration utilities to move settings from
old box to new. But the docs all pertain to moving from 2000 to 2003 or
pre-2000 to 2003. I'm SBS 2003 Std migrating to SBS 2003 Prem R2. The
research I did do on these tools indicated MS supported them during initial
migration that they should not be used after this. If they are tailored for
old box being SBS 2000 and not SBS 2003, do I not get to use them?
Appreciate the info regarding "local" in computer name. No it isn't public
- but DNS and Mail checks of my server keep "seeing" it and reporting it as
being non-compliant.
"Lanwench [MVP - Exchange]" wrote:
[Quoted Text] > doug <dmartin[ at ]newsgroups.nospam> wrote:
> > I gather this isn't as automated as I had hoped judging from the list
> > of similar issues and depth/detail of the replies I've seen.
> >
> > I have older hardware running SBS 2003 Std. It is running Exchange
> > 2000, DNS, no DHCP, 1 NIC, IIS. It is my home setup (training, lab,
> > websites).
> >
> > I have new server sitting and waiting. It has 1 NIC, but I wouldn't
> > mind adding 2nd NIC if recommended. Currently routers allowing all
> > servers/WSs to access internet.
>
> I don't like two NICs on a domain controller/DNS/WINS box - if you aren't
> using ISA, don't bother.
>
> >
> > I have not seen much on migrating from SBS 2003 to SBS 2003 R2
> > (mostly just 2000 and pre-2000).
> >
> > I would like to transfer Exchange mailboxes and mail.
> > logins/settings, DNS settings, AD. Ideally, I'd like to end up with
> > same IP on new server, but I'm not married to the idea.
>
> The IP address can always be changed later ...unlike your internal DNS
> domain name.
> >
> > Also, I "think" I made a mistake setting up my original SBS server.
> > My public domain is "myDomain.com". I created my server as
> > "local.myDomain.com" and that seems to haunt me to this day as I run
> > DNS tests from external sites testing how well my site comforms to
> > standards. I'm guessing I probably pay a penalty if I don't keep the
> > exact same nasme on new server?
>
> If you want to move your entire AD structure over, then you're stuck with
> it. But I don't see why you would think local.mydomain.com would be a
> problem....it shouldn't, if your DNS server is configured properly. I use
> stuff like that all the time. If local.mydomain.com is not a valid *public*
> subdomain then it should work fine.
>
> >
> > This is just me mostly on this SBS server and WSs - but I have other
> > member servers, work stations, actually 3 routers (1 wires, 1
> > wireless, 1 wireless dedicated to xBoxs - long story), so I'd have to
> > tweak a limited number of devices to change to a new internal DNS IP
> > if I picked a new one. But I would like to retain my mail on several
> > mail ids (my personal, the admin). Maybe I should not bother to try
> > to "clone" old server to new server - just create new SBS server and
> > manually rebuild taking old SBS off network?
>
>
> Check out www.sbsmigration.com for just the ticket.
>
>
>
|
|
doug <dmartin[ at ]newsgroups.nospam> wrote:
[Quoted Text] > www.sbsmigration.com - took a look previously. They seem to be a "for
> profit" group.
Meaning, it's not free? No, not free.
> Is it worthwhile for a one time hit?
I'd say so, yes. Anything else will take ages and a lot of manual labor.
>
> I understand there are post-build migration utilities to move
> settings from old box to new. But the docs all pertain to moving
> from 2000 to 2003 or pre-2000 to 2003. I'm SBS 2003 Std migrating to
> SBS 2003 Prem R2.
Not relevant.
> The research I did do on these tools indicated MS
> supported them during initial migration that they should not be used
> after this.
Which tools? The SBS migration stuff is not a boxed product - it's mainly
documentation w/some nice little utilities you can either use, or not.
> If they are tailored for old box being SBS 2000 and not
> SBS 2003, do I not get to use them?
?
>
> Appreciate the info regarding "local" in computer name. No it isn't
> public - but DNS and Mail checks of my server keep "seeing" it and
> reporting it as being non-compliant.
What DNS and mail checks? You can control how Exchange identifies itself to
other mail servers in the vsmtp properties.
>
>
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> doug <dmartin[ at ]newsgroups.nospam> wrote:
>>> I gather this isn't as automated as I had hoped judging from the
>>> list of similar issues and depth/detail of the replies I've seen.
>>>
>>> I have older hardware running SBS 2003 Std. It is running Exchange
>>> 2000, DNS, no DHCP, 1 NIC, IIS. It is my home setup (training, lab,
>>> websites).
>>>
>>> I have new server sitting and waiting. It has 1 NIC, but I wouldn't
>>> mind adding 2nd NIC if recommended. Currently routers allowing all
>>> servers/WSs to access internet.
>>
>> I don't like two NICs on a domain controller/DNS/WINS box - if you
>> aren't using ISA, don't bother.
>>
>>>
>>> I have not seen much on migrating from SBS 2003 to SBS 2003 R2
>>> (mostly just 2000 and pre-2000).
>>>
>>> I would like to transfer Exchange mailboxes and mail.
>>> logins/settings, DNS settings, AD. Ideally, I'd like to end up with
>>> same IP on new server, but I'm not married to the idea.
>>
>> The IP address can always be changed later ...unlike your internal
>> DNS domain name.
>>>
>>> Also, I "think" I made a mistake setting up my original SBS server.
>>> My public domain is "myDomain.com". I created my server as
>>> "local.myDomain.com" and that seems to haunt me to this day as I run
>>> DNS tests from external sites testing how well my site comforms to
>>> standards. I'm guessing I probably pay a penalty if I don't keep the
>>> exact same nasme on new server?
>>
>> If you want to move your entire AD structure over, then you're stuck
>> with it. But I don't see why you would think local.mydomain.com
>> would be a problem....it shouldn't, if your DNS server is configured
>> properly. I use stuff like that all the time. If local.mydomain.com
>> is not a valid *public* subdomain then it should work fine.
>>
>>>
>>> This is just me mostly on this SBS server and WSs - but I have other
>>> member servers, work stations, actually 3 routers (1 wires, 1
>>> wireless, 1 wireless dedicated to xBoxs - long story), so I'd have
>>> to tweak a limited number of devices to change to a new internal
>>> DNS IP if I picked a new one. But I would like to retain my mail
>>> on several mail ids (my personal, the admin). Maybe I should not
>>> bother to try to "clone" old server to new server - just create new
>>> SBS server and manually rebuild taking old SBS off network?
>>
>>
>> Check out www.sbsmigration.com for just the ticket.
|
|
|