INTRODUCTION ------------ The newsgroups misc.business.marketing.moderated, misc.business.moderated, misc.business.consulting, and misc.entrepreneurs.moderated are moderated discussion groups. This periodic post summarizes the current posting policies all posters are expected to follow for these four newsgroups. Please read this policy document before posting. James Hill, Scott Jensen, Jim
I'd *still* go with sbsmigration.com. After all, right now you are considering a migration method that has no support as well (if yo are writing here, I assume you aren't planning on paying to call Microsoft priority support...) In my experience, the documentation has been quite clear and no support is necessary. It is more of safety net. And you don't have the risk of screwing something
Hi, The best thing to do, if downtime is acceptable, is do a dissimilar hardware restore. eg over a weekend. Run a FULL backup of Server A , Install Disc 1 of SBS on server B patch windows to same level, Restore FULL backup on server B with Overwriting turned on. This is the quickest way if you can do it with downtime, and it works really well. Also if it does go wrong, No damage
INTRODUCTION ------------ The newsgroups misc.business.marketing.moderated, misc.business.moderated, misc.business.consulting, and misc.entrepreneurs.moderated are moderated discussion groups. This periodic post summarizes the current posting policies all posters are expected to follow for these four newsgroups. Please read this policy document before posting. James Hill, Scott Jensen, Jim
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fermi Scientific Linux. What is it? ,----[ Quote ] | So the geegazoids at Fermi Lab and other places apparently got together to | generate a version of Linux that is as close to Red Hat as you can get and | still be Open Source legal. It is Red Hat. Yet it is not. `---- http://scienceblogs.com/gregladen/2008/07/fermi_scientific_linux_what_is
