System state backup in windows 2000


















The best programming languages to learn in Check for Log4j vulnerabilities with this simple-to-use script. TasksBoard is the kanban interface for Google Tasks you've been waiting for. Paging Zefram Cochrane: Humans have figured out how to make a warp bubble. Show Comments. Hide Comments. My Profile Log out. Join Discussion. Add your Comment. At first glance, the Backup tab looks like every other backup program in the world, but things aren't what they seem.

But lacking a system state the new drive which I can select as the boot unit on the controller will, of course, never boot. To avoid altering that installation in ANY way is the main reason for having the replacement drive to use in place of it. The only solution that comes to mind is to do an entirely new install of W2K NOT as a Domain Controller with Active Directory on yet another drive off the RAID controllers and boot with that and have access to the external backup containing the system state as well as the replacement drive I am preparing.

Then Backup should not balk at restoring the System State to the new location. Should that not work? Or is there an easier way to get the original system state restored onto the replacement drive? Prep your domain and forest using adprep32 adn promote the new box to become a DC. The old system is still there if something went wrong with the R2 box. You really can't dual boot two DCs on the same box Have they been running with only one DC?

Highly recommend at least two DCs in any enviornment. I much appreciate your reply which basically says that I'm probably on the wrong track. But you should also know how I got here and then consider again if what I intend to do is doable. Yes, I would have preferred that the client go for yet another server but he only got this fairly expensive one about three years ago and the old W2K OS was gotten there through hard drive cloning from his previous server which also proved to be a great challenge due to the great discrepancy between the old and new server hardware.

I was very close to despair before I got that working. In addition, less than a year ago he got a less expensive second server with W2K8 R2 dedicated, as a separate server with access to financial info on the W2K server, to running his general website and also a second website providing his staff and clients info on client accounts which also required running SQL Server there.

Highly recommend at least two DCs in any enviornment. I much appreciate your reply which basically says that I'm probably on the wrong track. But you should also know how I got here and then consider again if what I intend to do is doable.

Yes, I would have preferred that the client go for yet another server but he only got this fairly expensive one about three years ago and the old W2K OS was gotten there through hard drive cloning from his previous server which also proved to be a great challenge due to the great discrepancy between the old and new server hardware.

I was very close to despair before I got that working. In addition, less than a year ago he got a less expensive second server with W2K8 R2 dedicated, as a separate server with access to financial info on the W2K server, to running his general website and also a second website providing his staff and clients info on client accounts which also required running SQL Server there. There is no further intent to use this second server for any other purposes.

Now, after having asurred the client since late last year that his expensive server was more than adequate even for future plans to install Exchange except his W2K would need to be replaced soon but before the Exchange preferrably with W2K8 R2, I would have to go back and say I can't install the W2K8 R2, now critical with the loss of all Microsoft support for W2K, unless he purchase yet another server.

I would look like an utter incompetent and even risk losing him, my best client by far. My understanding is that W2K3 would need to be used as an intermediary. So I figured I would lend the client or charge him a nominal rental for providing a temporary server with W2K3 to accomplish this migration and then take it back afterwards. That being the case why is the dual boot idea unfeasible?

The hardware is pretty up-to-date Intel only replaced the processor and motherboard late last year with improved product and supports both W2K Advanced Server and W2K8 R2.

Why can this not be done? I notice you made no comment about my System State restore problem probably because if I had another server for W2K8 R2 and could keep the W2K server on the network as well, this System restore problem would no longer exist. What you advise sounds like it has promise. If I am to take a server to my client temporarily, it makes more sense to me that it have Windows Server R2 rather than Windows Server , but did I not read, even in this forum, that direct migration of Windows Server Active Directory is not possible to Windows Server R2 but that the migration must be to Windows Server first?

Perhaps I misunderstood. But I think many others are confused about this. Hi mwacsny,. Please have a look at the two articles I listed earlier. Then you will have a good understanding about the process. Hope this helps. Office Office Exchange Server. Not an IT pro?



0コメント

  • 1000 / 1000