+1 It was the best $200 I spent during our migration from physical to virtual. I had an issue and it was a relatively common issue with the steps for resolving it clearly detailed. I couldn't tell you what the issue was, as I did this several years ago.
On Tue, Nov 6, 2012 at 4:43 PM, John Cook <john.c...@pfsf.org> wrote: > Should you decide to do the swing migration pony up for the SBS migration > package. If it's something you don't do often (or will ever again) it's > worth the knowledge and support. > > John W. Cook > Network Operations Manager > Partnership For Strong Families > 5950 NW 1st Place > Gainesville, Fl 32607 > Office (352) 244-1610 > Cell (352) 215-6944 > MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4 > > -----Original Message----- > From: James R. Costa, MCP [mailto:james.co...@gmail.com] > Sent: Tuesday, November 06, 2012 4:20 PM > To: NT System Admin Issues > Subject: RE: Strange SBS2011 migration path, looking for some input > > A mess, indeed. Thanks for your input Art. I must have been thinking of > SBS2011 Standard when I wrote about not using newer Exchange... was kinda > braindead yesterday. > > You would think Essentials was installed to replace a DC... but it was > just added to the mess. While it's a great idea to virtualize those old > servers, it's pretty pointless in this case. They shouldn't be there in > the first place. There were a total of 6 DCs in the 8 servers for about 23 > users, Exchange installed on 3 boxes, only really running on the one VM > though. Basically anything they are doing can be combined on one server. > Their whole system is pretty backwards right now. > > I'm thinking SBS 2011 Standard with appropriate user CALs is still the > right choice for them. The box it would be installed on is a Dell > Poweredge R710, 2x 6-core Xeon w/ HT, 32GB RAM, 6x 2TB/7.2k in RAID5. SO > it definitely has the horsepower and capacity they need. All of the other > servers are running Win2K/Win2K3 on effectively junk hardware... OLD Compaq > ML530 Pentium III Xeon (160lbs.), Pentium Dual-Core whitebox, etc. > > There is one older-gen Intel whitebox server that could be used for a > swing migration. Although I'm still up in the air about which path to > take. I could do a swing to that other box, although I have never done one > before, and at the same time, I'm inclined to start fresh and visit every > workstation to disjoin/rejoin to make sure everything is configured > properly. I will check on the public folders. Exporting their mail to PST > will be interesting too, as some of the users have mailboxes that are > 20-25GB in size. Would you foresee any issues in exporting mailboxes of > that size? > > Thanks again for your input!! > > James > > >>> > What a mess. > > SBS 2011 Essentials will not support Exchange. That's why he has it > installed on another box. It looks like Essentials was installed to replace > an old DC and try to update the network. But that's in the past now. > > I would plan to install a new version of SBS 2011 Premium based on the > number of servers. You get the rights for 2 physical boxes (and SQL) and > can virtualize some of the other servers on the second box. > > What are the specs for the latest box you plan on installing SBS 2011 > Standard on? > What are the other 7 servers doing and can they be combined and > virtualized? > You will need SBS 2011 Standard and the appropriate number of CALs. None > of the CALs they have now are valid for SBS 2011. > > David is right in that you can do a "swing migration". You will need > another server for this. Will one of the others work temporarily? > > Is the rest of the network, AD, users, etc. OK or do they look iffy also? > If so I would be inclined to start from scratch and build it so you know > exactly what you have. I know it's a pain but you could export the PST > files. That should cover most of their Exchange data. Unless they are using > Public Folders. > > If the client is growing, this might be a good time to start over with a > good base and review existing policies and build it to match the client's > needs and expectations. > > Art > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ < > http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin > > ________________________________ > > CONFIDENTIALITY STATEMENT: The information transmitted, or contained or > attached to or with this Notice is intended only for the person or entity > to which it is addressed and may contain Protected Health Information > (PHI), confidential and/or privileged material. Any review, transmission, > dissemination, or other use of, and taking any action in reliance upon this > information by persons or entities other than the intended recipient > without the express written consent of the sender are prohibited. This > information may be protected by the Health Insurance Portability and > Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. > Improper or unauthorized use or disclosure of this information could result > in civil and/or criminal penalties. > Consider the environment. Please don't print this e-mail unless you really > need to. > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
