Re: SBS 2003 swing migration?
http://www.sbsmigration.com/pages/96/ This looks pretty good, and I've been thinking pretty hard about doing this here at the firm. For $200 and reduced (almost no) downtime the price can't really be beat. I haven't pulled the trigger yet, because I have to get approval for every purchase not in my budget this year, and I don't have time to do it between now and next April 15th to do anything. -Jonathan On Thu, Aug 21, 2008 at 9:24 AM, Andy Shook [EMAIL PROTECTED] wrote: List, Got a client wanting me to redo his SBS environment on new hardware, in other words start from scratch on a fresh box in order to clean up from the crap-o work his former IT shop did. I can build from scratch, migrate data and join the PCs to the new domain but is there a better way? TIA, Shook ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: SBS 2003 swing migration?
http://theessentialexchange.com/blogs/michael/archive/2008/05/18/sbs-2003-ha rdware-migration-upgrade.aspx Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com From: Jonathan Link [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:33 AM To: NT System Admin Issues Subject: Re: SBS 2003 swing migration? http://www.sbsmigration.com/pages/96/ This looks pretty good, and I've been thinking pretty hard about doing this here at the firm. For $200 and reduced (almost no) downtime the price can't really be beat. I haven't pulled the trigger yet, because I have to get approval for every purchase not in my budget this year, and I don't have time to do it between now and next April 15th to do anything. -Jonathan On Thu, Aug 21, 2008 at 9:24 AM, Andy Shook [EMAIL PROTECTED] wrote: List, Got a client wanting me to redo his SBS environment on new hardware, in other words start from scratch on a fresh box in order to clean up from the crap-o work his former IT shop did. I can build from scratch, migrate data and join the PCs to the new domain but is there a better way? TIA, Shook ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: SBS 2003 swing migration?
I posted this in another place: http://theessentialexchange.com/blogs/michael/archive/2008/05/18/sbs-2003-ha rdware-migration-upgrade.aspx However, since you are now at Peak10, and you don't clarify whether you are talking about an on the side client or a Peak10 client - I just want to ensure that you are aware that if a SBS server detects another SBS server on the same network - it'll shut down. In a service provider environment, you need to ensure that each SBS server is on its own subnet (at least - its own VLAN would be better). Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:24 AM To: NT System Admin Issues Subject: SBS 2003 swing migration? List, Got a client wanting me to redo his SBS environment on new hardware, in other words start from scratch on a fresh box in order to clean up from the crap-o work his former IT shop did. I can build from scratch, migrate data and join the PCs to the new domain but is there a better way? TIA, Shook ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: SBS 2003 swing migration?
Thanks MBS, this is an on the side client Shook From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:52 AM To: NT System Admin Issues Subject: RE: SBS 2003 swing migration? I posted this in another place: http://theessentialexchange.com/blogs/michael/archive/2008/05/18/sbs-2003-hardware-migration-upgrade.aspx However, since you are now at Peak10, and you don't clarify whether you are talking about an on the side client or a Peak10 client - I just want to ensure that you are aware that if a SBS server detects another SBS server on the same network - it'll shut down. In a service provider environment, you need to ensure that each SBS server is on its own subnet (at least - its own VLAN would be better). Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:24 AM To: NT System Admin Issues Subject: SBS 2003 swing migration? List, Got a client wanting me to redo his SBS environment on new hardware, in other words start from scratch on a fresh box in order to clean up from the crap-o work his former IT shop did. I can build from scratch, migrate data and join the PCs to the new domain but is there a better way? TIA, Shook ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: SBS 2003 swing migration?
Did you ever do the 2nd article you mentioned about shutting down the old SBS box? Webster Original Message Subject: RE: SBS 2003 swing migration?To: "NT System Admin Issues" ntsysadmin@lyris.sunbelt-software.com http://theessentialexchange.com/blogs/michael/archive/2008/05/18/sbs-2003-hardware-migration-upgrade.aspx Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com
RE: SBS 2003 swing migration?
Pay the 200 bucks and use the SBS migration kit...painless. No downtime. Works as advertised. http://www.sbsmigration.com S From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 10:56 AM To: NT System Admin Issues Subject: RE: SBS 2003 swing migration? Thanks MBS, this is an on the side client Shook From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:52 AM To: NT System Admin Issues Subject: RE: SBS 2003 swing migration? I posted this in another place: http://theessentialexchange.com/blogs/michael/archive/2008/05/18/sbs-2003-hardware-migration-upgrade.aspx However, since you are now at Peak10, and you don't clarify whether you are talking about an on the side client or a Peak10 client - I just want to ensure that you are aware that if a SBS server detects another SBS server on the same network - it'll shut down. In a service provider environment, you need to ensure that each SBS server is on its own subnet (at least - its own VLAN would be better). Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:24 AM To: NT System Admin Issues Subject: SBS 2003 swing migration? List, Got a client wanting me to redo his SBS environment on new hardware, in other words start from scratch on a fresh box in order to clean up from the crap-o work his former IT shop did. I can build from scratch, migrate data and join the PCs to the new domain but is there a better way? TIA, Shook ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: SBS 2003 swing migration?
Andy, If you still have my phone number call me if you want to discuss. SBS is my area o' expertise really. Jeff Middleton's Swing Migration is the bees knees as long as your Active Directory is solid. If it's the AD you're wishing to fix, I suggest something a little more drastic. From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 6:56 AM To: NT System Admin Issues Subject: RE: SBS 2003 swing migration? Thanks MBS, this is an on the side client Shook From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:52 AM To: NT System Admin Issues Subject: RE: SBS 2003 swing migration? I posted this in another place: http://theessentialexchange.com/blogs/michael/archive/2008/05/18/sbs-2003-ha rdware-migration-upgrade.aspx However, since you are now at Peak10, and you don't clarify whether you are talking about an on the side client or a Peak10 client - I just want to ensure that you are aware that if a SBS server detects another SBS server on the same network - it'll shut down. In a service provider environment, you need to ensure that each SBS server is on its own subnet (at least - its own VLAN would be better). Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:24 AM To: NT System Admin Issues Subject: SBS 2003 swing migration? List, Got a client wanting me to redo his SBS environment on new hardware, in other words start from scratch on a fresh box in order to clean up from the crap-o work his former IT shop did. I can build from scratch, migrate data and join the PCs to the new domain but is there a better way? TIA, Shook ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
RE: SBS 2003 swing migration?
The most typical Crap-O job is when SBS is used and no one works within the wizards so everything is all over. Usually just moving the computers and user accts around in the OU's and making sure the proper GP's are in place is good. Hopefully they didn't do everything in the default GP's. If you can fix the AD with a few hours work it really worth it rather than a fresh build. That is a huge amount of work. I will be happy to help with the process we use to move to new servers with SBS, but the cats meow is sbsmigration.com If they have really hosed the GP's or you have a bad AD then exmerge the Exchange folders, export the public to pst's, copy the user and company data. If they use Sharepoint Services heavily that could be fun to move. Not an expert there. Before moving anything, I usually disjoin the computers from the domain (Making sure I have good local admin acct, favorites, desktops, etc) Then I move the data to the new server usually via USB, while that data is moving I rejoin using the SBS Wizard to the new server. Takes a bit of timing usually over a weekend to keep downtime to a minimum and then plan a day or two of fixup and cleanup items. Looking forward to the SBSmigration kit for 2008. We have about a 30 clients all with 3 to 5 year old servers needing a technology refresh running 2003 SBS. Good luck. Glad to help out with any questions as well. From: Jim Majorowicz [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:05 PM To: NT System Admin Issues Subject: RE: SBS 2003 swing migration? Andy, If you still have my phone number call me if you want to discuss. SBS is my area o' expertise really. Jeff Middleton's Swing Migration is the bees knees as long as your Active Directory is solid. If it's the AD you're wishing to fix, I suggest something a little more drastic. From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 6:56 AM To: NT System Admin Issues Subject: RE: SBS 2003 swing migration? Thanks MBS, this is an on the side client Shook From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:52 AM To: NT System Admin Issues Subject: RE: SBS 2003 swing migration? I posted this in another place: http://theessentialexchange.com/blogs/michael/archive/2008/05/18/sbs-200 3-hardware-migration-upgrade.aspx However, since you are now at Peak10, and you don't clarify whether you are talking about an on the side client or a Peak10 client - I just want to ensure that you are aware that if a SBS server detects another SBS server on the same network - it'll shut down. In a service provider environment, you need to ensure that each SBS server is on its own subnet (at least - its own VLAN would be better). Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:24 AM To: NT System Admin Issues Subject: SBS 2003 swing migration? List, Got a client wanting me to redo his SBS environment on new hardware, in other words start from scratch on a fresh box in order to clean up from the crap-o work his former IT shop did. I can build from scratch, migrate data and join the PCs to the new domain but is there a better way? TIA, Shook ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
