I don't understand why you wouldn't use the Microsoft Swing method, my 
abbreviated Swing method, or SBS MVP Jeff Middleton's Swing method. Jeff's kit 
is only USD $200, and it'll cost more time than that just to fix all the 
desktop profiles.

A very worthwhile investment.

[Note: my method is just a slight modification of the Microsoft method - and I 
don't sell anything. I've just got a couple of blog posts on what I do. See 
here: 
<http://theessentialexchange.com/blogs/michael/archive/2009/01/12/sbs-2003-hardware-upgrade.aspx>
 ]


From: Matt Plahtinsky [mailto:[email protected]] 
Sent: Wednesday, January 27, 2010 10:59 AM
To: NT System Admin Issues
Subject: Re: Downsizing to SBS. Same domain name?

No reason other than the client is requesting.  I have in the past always 
changed the internal domain name.  Looks like I should keep doing that.

Thanks

Matt
On Wed, Jan 27, 2010 at 1:15 AM, Brian Desmond <[email protected]> wrote:
If you have WINS you're going to need to pick one domain or the other to 
register in WINS while they're both still up at the same time.
Is there any particular reason the new domain needs the same name as the legacy 
domain? I'd avoid it just to avoid the potential trouble. 
Thanks,
Brian Desmond
[email protected]
c - 312.731.3132
 
From: Matt Plahtinsky [mailto:[email protected]] 
Sent: Friday, January 22, 2010 3:27 PM
To: NT System Admin Issues
Subject: Downsizing to SBS. Same domain name?
I have a client that is going to be moving from a 2003 domain with VERY old 
hardware to Small Business Server 2008 new hardware.
Here is my question.  Can you think of any problems if we keep the same 
internal domain name?  If I disconnect the pc's from the old domain ABC.LOCAL 
and connect them to the new SBS domain ABC.LOCAL could that cause any problems? 
 In the past I have always changed the internal domain/DNS names when doing 
migrations like this.  The client would like to keep the same name so that's 
why I'm asking.
With out knowing the repercussions I would think that it 
could potentially cause a ton of issues. 
Thanks
Matt

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to