Also, don't seize the roles, transfer them. On Wed, Jan 18, 2012 at 11:41 AM, Steve Kradel <[email protected]> wrote:
> Aye, "two is one, and one is none," as they say. Figure out the cost of a > full day or more of downtime--say, at a certain busy time of year for an > accounting firm--while someone tries to find backups, or realizes that the > hardware is cooked and they can't restore the backups onto the new machine > with a different hardware config... > > Add two, low-horsepower machines and make both of them DCs. Rebuild the > server with 8GB to run non-DC things (applications, file server, Exchange, > whatever). Or you could install HyperV / ESXi / Xen and have about four > virtual hosts... > > --Steve > > > On Wed, Jan 18, 2012 at 6:40 AM, Andrew S. Baker <[email protected]>wrote: > >> In that case, ADD a new DC. >> >> Having a single DC is a liability even in the smallest environment. >> >> * * >> >> *ASB* *http://XeeMe.com/AndrewBaker* *Harnessing the Advantages of >> Technology for the SMB market… >> >> * >> >> >> >> On Tue, Jan 17, 2012 at 6:32 PM, Jimmy Tran <[email protected]> wrote: >> >>> Nothing in particular. It’s a small accounting firm that runs lots of >>> tax software over the network. I just noticed there was 8GB installed but >>> only 4GB is used due to the OS limitation. I figure we minus well upgrade >>> to a 64 bit.**** >>> >>> ** ** >>> >>> *From:* Andrew S. Baker [mailto:[email protected]] >>> *Sent:* Tuesday, January 17, 2012 3:20 PM >>> >>> *To:* NT System Admin Issues >>> *Subject:* Re: ideas for migrating from 32-bit to 64-bit Server 2008**** >>> >>> ** ** >>> >>> What David said:**** >>> >>> ** ** >>> >>> -- Add a new server to the domain temporarily**** >>> >>> -- Promote to DC and take all the roles**** >>> >>> -- Move the Data somewhere temporarily (or, at the very least, ensure >>> that it is backed up)**** >>> >>> -- Rebuild the new server as a DC x64**** >>> >>> -- Join it to the existing domain and take back all of the roles**** >>> >>> -- Put the data back on the machine**** >>> >>> ** ** >>> >>> Off you go.**** >>> >>> ** ** >>> >>> What is the app or functionality that requires the 8GB RAM, btw? The >>> answer might change the approach.**** >>> >>> ** ** >>> >>> ** ** >>> >>> ** ** >>> >>> *ASB***** >>> >>> *http://XeeMe.com/AndrewBaker***** >>> >>> *Harnessing the Advantages of Technology for the SMB market…***** >>> >>> >>> >>> **** >>> >>> On Tue, Jan 17, 2012 at 5:44 PM, Jimmy Tran <[email protected]> wrote:* >>> *** >>> >>> Hi All,**** >>> >>> **** >>> >>> I have a client who currently has a Windows Server 2008 32-bit machine. >>> They need to upgrade to 64 bit so they can make use of the 8GB of ram they >>> have installed. The server is a DC and file server only. I’m thinking >>> I’ll have to recreate a whole new domain since I only have one server to >>> work with and cannot directly upgrade to 64 bit. Do you guys have any >>> suggestions on how I can do this? **** >>> >>> >>> Thanks,**** >>> >>> >>> Jimmy**** >>> >>> ** ** >>> >>> >>> ~ 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 [email protected] > 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 [email protected] with the body: unsubscribe ntsysadmin
