Re: Looking for SBS migration tool
From: Kevin Weilbacher [SBS-MVP] (kweilbacMVP_at_gte.net)
Date: 11/02/04
- Next message: Marina Roos [SBS-MVP]: "Re: SBS 2003 Standard to Premium"
- Previous message: Marina Roos [SBS-MVP]: "Re: Looking for SBS migration tool"
- In reply to: MikeR: "Re: Looking for SBS migration tool"
- Next in thread: Bishop: "Re: Looking for SBS migration tool"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 2 Nov 2004 06:11:04 -0500
Mike,
If it doesn't come right awaw, don't worry -- Jeff is getting pulled down
under (literally) for 30 days to Australia for an MS sponsored speaking
tour. I would guess that getting ready for this trip has impacted the timing
of the roll out of his Swing Migration. But it is coming!
-- Kevin Weilbacher [SBS-MVP] "The days pass by so quickly now, the nights are seldom long" "MikeR" <research@rollesolutions.com> wrote in message news:eW0DPeIwEHA.3896@tk2msftngp13.phx.gbl... > Anybody have the document that Jeff created? I can't seem to get anywhere > on the site listed and registration apparently doesn't mean a whole lot??? > I haven't received a confirmation or anything and I just re-registered > just in case. > > > "SuperGumby [SBS MVP]" <not@your.nellie> wrote in message > news:%23RZKjUFwEHA.3896@TK2MSFTNGP09.phx.gbl... >>I recently did a test move from a white box to a Dell, similar differences >> >> this is what I did >> >> OK, so I moved an SBS2003 install from a white box server to a Dell 2400 >> we >> had lying around the office. (anyone want a reasonable TS?) >> >> The white box is our 'testbox', a PIII 677 which I have to check tomorrow >> the motherboard model. It's actually a dual mobo and used to have a >> couple >> of 1G CPU's in it, but times changed. It's our old SBS2K. Among other >> things >> we have a SBS2003 install on her. We change OS's by choosing which drive >> to >> boot off via the BIOS. SBS is on the SCSI, W2Kp is on the IDE. I have >> loaded >> a few OS's into VPC under W2Kp. >> >> The 2400 has a pair of PIII 733's. >> >> Different NIC's. 2 * Intel pro's vs 1 8255x and 1 HP NetServer >> >> Different drive subsystems, the white box has a 7889 adaptec, the 2400 is >> a >> PERC2 as well as having Adaptec 78xx series options. >> >> I was disappointed when Jan pointed out that every box I had available >> basically had a 'serverworks' chipset. I really wanted to do this on >> boxes >> as disparate as possible. >> >> I used an Adaptec 1200a PCI RAID card to move things, hadn't previously >> tested it in either box, wanted to live dangerously. >> >> SO, >> >> I threw the Adaptec card into the white box and started her up. Windows >> 2k3 >> loaded the HighPoint 370 driver exactly as expected. Shut her down and >> connect a spare 80G IDE we had in the cupboard, restart, and the boring >> stuff continues, the drive was available to W2k3. The drive had a >> previous >> install of windows on it so I formatted it. (I may have avoided the >> problem >> later mentioned if I'd just deleted the damned partition) >> >> So now I have an SBS which also recognises the 1200a drives. Shut her >> down >> and boot of the GHOST floppy. >> >> I'm not yet sure whether the problem was due to resizing the partition >> during the ghost or due to the order drives are detected by this system >> but >> I disconnected the SCSI and... You see, this is where things get a little >> interesting. She BSOD'd on restart. >> >> When running SBS on the white box it boots (when told to in BIOS) from >> the >> SCSI. However, as is normal IME, the IDE drive appears in Disk Management >> as >> Drive0. The SCSI device is 'C:'. If we choose to boot from the IDE drive >> it >> still appears first in DM but is now 'C:', the SCSI being D the CD E and >> the >> 2nd partition on the IDE being F. >> >> The Adaptec card appears as a SCSI device. >> >> I couldn't get the cow to boot for love of money, then I had an idea. >> >> I reconnected the SCSI drive and booted off it. Went into Disk Manager >> and >> assigned the IDE partitions to drive letters W and X. Deleted the >> partition >> on the 1200a HDD and reghosted her. Disconnected the SCSI and rebooted >> normally. I now had a bootable SBS on a drive connected to the 1200a. >> >> SO, it's time to throw the 1200a card into the target system. >> >> It had been suggested to me that the Dell may not allow the 1200a to be >> used >> as boot device. That was proven wrong in short order. I didn't bother >> testing I just disconnected every other bootable device except CD and >> floppy. >> >> She booted. (into DSRM of course) >> >> This was the, to me, most surprising bit of all. >> >> On the first reboot she suggested a single CPU and detected a few >> devices, >> installed them automagically, no CD required. >> >> Something I learned when moving '98 installs was that when Windows >> suggests >> 'I wanna restart' it's not always a good idea to do so, so when it had >> installed a few devices, not installed others because the drivers weren't >> available, and suggested 'I wanna restart' I said 'stuff you, get on with >> the job'. More devices were installed and when it eventually settled down >> and was settled for twenty minutes or so I restarted. I left her for >> 20min >> because when I've done similar things before it has _sometimes_ taken a >> while for changes to be recognised. I reckon I could have rebooted her >> immediately, into DSRM, but have no proof. >> >> Upon restart the system suggested an MPC HAL was loaded and running 2 >> CPU's, >> still no CD anywhere near her, matter of fact no CD was ever asked for. >> And >> we're back in DSRM again. >> >> And restart, and DSRM, and nothing additional detected, there's this >> thing >> called 'Base System something' in the device manager with a red cross >> against it but everything else is OK. LET'S GO FOR BROKE AND RESTART HER >> NORMALLY. >> >> Ran the 'change server IP' wiz. >> >> Ran the 'Connect to the Internet' wiz. >> >> Restarted. All OK. >> >> I know I can ghost the IDE to a RAID array on the PERC2, I don't need to >> test this but it's the only step not tested. >> >> >> >> -- >> >> Mick Malloy >> >> http://www.micropol.com.au >> >> >> "Bishop" <kenw@dcnconsulting.com> wrote in message >> news:#Q7PpAEwEHA.1148@TK2MSFTNGP12.phx.gbl... >>> Yes that phrase would be more approprate. Everything is different in >>> the >>> new system. I'm not sure what the old hardware is, probably white box. >> New >>> hardware is HP server. Thus there will be different Nic's, SCSI Card >>> and >>> array. >>> >>> I though there were non-microsoft tools for this process but I'm not >> finding >>> any. >>> >>> >>> "SuperGumby [SBS MVP]" <not@your.nellie> wrote in message >>> news:u2J$JgxvEHA.1300@TK2MSFTNGP14.phx.gbl... >>> > a swing migration is a valid method however I think this could easily >>> > be >>> > rephrased as: >>> > 'How do I move my existing installation to new hardware?' >>> > >>> > a description of the current hardware, be as specific as you can, and >>> > similarly for the new hardware would be of great assistance. >>> > >>> > "Javier Gomez [SBS MVP]" <javier_gomez@REMOVE.THIS.engineer.com> wrote >> in >>> > message news:OZ0sqeevEHA.2540@TK2MSFTNGP09.phx.gbl... >>> > > May I also suggest you take a look at the Swing Migration technique >>> > > developed by Jeff Middleton (a fellow SBS MVP): >>> > > http://www.sbsmigration.com (send him an email or fill out the form >>> > > provided on that site). >>> > > >>> > > This could potentially save you hours of hard work, etc and in my >>> opinion >>> > > the migration procedure is very well documented + gives you many >>> > > tools/scripts to acomplish everything faster and with minimal >> downtime. >>> > > Another important factor is that it works in a much broader set of >>> > > migration scenarios. >>> > > >>> > > If you have a specific question about this or some other method... >>> > > let >>> us >>> > > know and I'm sure we can help you. >>> > > >>> > > Cheers, >>> > > >>> > > -- >>> > > Javier [SBS MVP] >>> > > www.msmvps.com/javier >>> > > << SBS ROCKS!!! >> >>> > > >>> > > "Frank McCallister SBS MVP" <anonymous> wrote in message >>> > > news:%23aLB4NevEHA.1400@TK2MSFTNGP11.phx.gbl... >>> > >> Hi Bishop >>> > >> >>> > >> Check the M&M site >> http://www.smallbizserver.net/Default.aspx?tabid=99 >>> > >> >>> > >> -- >>> > >> Frank McCallister SBS MVP >>> > >> COMPUMAC >>> > >> "Bishop" <kenw@dcnconsulting.com> wrote in message >>> > >> news:uZwLIudvEHA.1520@TK2MSFTNGP11.phx.gbl... >>> > >>> Just migrating to different hardware, not OS but sounds like a >>> valiable >>> > >>> read. >>> > >>> thanks >>> > >>> >>> > >>> "wilengle@sbcglobal.net" <no-spamwilengle@sbcglobal.net> wrote in >>> > >>> message >>> > >>> news:eZDM9CdvEHA.4072@TK2MSFTNGP15.phx.gbl... >>> > >>>> Here is a common tool >>> > >>>> >>> > >>>> >>> > >>> >>> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=fa187d1e-8218-4501-9729-222bd8ebb64c&DisplayLang=en >>> > >>>> >>> > >>>> SBS Down and dirty... it Rocks! >>> > >>>> >>> > >>>> >>> > >>>> Wil Engle >>> > >>>> Whitebox Solutions >>> > >>>> remove the spam >>> > >>>> "Bishop" <kenw@dcnconsulting.com> wrote in message >>> > >>>> news:uZIpGIcvEHA.2316@TK2MSFTNGP15.phx.gbl... >>> > >>>> > We have a Windows 2000 SBS server utilizing Active Directory, >> File, >>> > >>> Print, >>> > >>>> > ISA, Exchange, Policies, and Profiles. The server is on old, >> slow >>> > >>>> > hardware >>> > >>>> > and is ready for an upgrade to new faster hardware. Looking >>> > >>>> > for >>> > >>>> > recomendations on either tools or processes that can assist on >>> making >>> > >>> the >>> > >>>> > migration smooth. >>> > >>>> > >>> > >>>> > >>> > >>>> >>> > >>>> >>> > >>> >>> > >>> >>> > >> >>> > >> >>> > > >>> > > >>> > >>> > >>> >>> >> >> > >
- Next message: Marina Roos [SBS-MVP]: "Re: SBS 2003 Standard to Premium"
- Previous message: Marina Roos [SBS-MVP]: "Re: Looking for SBS migration tool"
- In reply to: MikeR: "Re: Looking for SBS migration tool"
- Next in thread: Bishop: "Re: Looking for SBS migration tool"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
