Problems dual-booting Windows Server 2003

I have Windows Server 2003 on one hard drive, plus a clone of the drive on a 2nd identical drive. (It runs a 3rd party app that has problems, so when it goes down again we can boot off the 2nd drive. There is no data to worry about, just the configuration which is cloned.) It's on a Windows Small Business Server 2008 domain.

Here is my boot.ini on the 1st drive:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /fastdetect /NoExecute=OptOut
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Boot to Backup" /fastdetect /NoExecute=OptOut

1st time I tested this, I chose "Boot to Backup" at the OS choices, got to "Applying computer seetings", then got a box with this in the title bar: "lsass.exe-System Error", and this in the body: "Object name already exists." I hit OK, and a few seconds later it just went black and rebooted. (Never got to the login.) When it rebooted, I chose the initial "Windows Server 2003, Standard" OS option, it booted and logged in fine.

Later, I boot to the 2nd disk again to write down the error and stuff for this post. Same lsass error came up, but when I hit OK it continued to the login. I logged in (admin account), got to desktop with this error: "Generic Host Process for Win32 Services encountered a problem and needed to close", and Send/Don't Send error report. I hit Don't Send on 2 or 3 instances of this error it seemed. I believe it was at this point that I got a message saying Windows installed new hardware and needed to restart.

I restarted , didn't get the lsass error, logged in, and only got 1 Generic Host Process error.

I figure this is about the computer name being the same on both instances of Server03, but SBS (the domain controller) is seeing them diferently. But I need the name  to stay the same for the client requests to get to it regardless of which way we boot. How can I fix that, or is that even the problem? Also, what do I need in the boot.ini on the 2nd drive? Many thanks for reading my long question!
downtown2010Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

B HCommented:
you dont need anything in the boot.ini on the 2nd drive, if your bios says to boot the primary drive.

you can't have 2 machines with the same name, both registered in the same active directory (your sbs server).  there are computer accounts that map to SIDs (randomly generated numbers).  two computers with the same name will have different sid's.

also, what the primary hard drive knows about your active directory, the 2nd hard drive wont know, and your sbs server won't know whats going on with the two either and probably end up locking them both out of the domain.

you would be far better off fixing the software that requires this kind of dual booting... so you can eliminate the need to do this.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
downtown2010Author Commented:
Guess I already knew the answer. Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.