We have upgraded a customer to Server 2012 R2. We are trying to perform a backup but every single thing we have tried has failed with the following :
Backup of volume \\?\Volume{739fbb28-4d00-11e3-80b3-806e6f6e6963}\ has failed. Incorrect function.
We are backing up the F: drive to a NAS drive attached to the network. The setup of the network is as follows: 1 Server2012R2; 4 workstations, NAS and Watchguard firewall. Any ideas would be greatly appreciated!
When running server backup on windows 2008 R2 get the following error message.
event id 5634 unable to create vss snapshot the directory is invalid
Can anyone offer a solution? Have had the kit verified and tested by Dell and trolled the forums and knowledge sites but not much luck.
Thanks
I'm getting this error when I try to check a backup stored on a NAS. When I attempt to recover from it, I pick "A backup stored on another location" then "Remote shared folder".
I put in the path: \\192.168.16.17\public\server\2014-01-24
And what I get is the above error message: "The specified path is not a remote shared folder"
The path clearly is a remote shared folder. If I paste it into explorer it opens fine, and I can copy/delete files from it. What gives?
We have Windows 2012 Server hosting 2 VMs - Domain Controller & RDS. We have been doing Windows Server Backup incremental and have an ongoing issue with scheduled backups each night. The backup shows completed with warnings and generates 2 log files.
The first log files shows:
Backup of volume \\?\Volume{5d46f853-5db2-11e2-93e7-806e6f6e6963}\ succeeded.
Backup of volume C: succeeded.
Backup of volume F: succeeded.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: ACBCD71E-A8CA-4672-B951-52C1BE8444BE
Caption : Backup Using Child Partition Snapshot\FMLRDS1
Logical Path:
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: Host Component
Caption : Host Component
Logical Path:
The 2nd log file more often than not shows:
Backup of volume E: has failed. Backup failed as shadow copy on source volume got deleted. This might caused by high write activity on the volume. Please retry the backup. If the issue persists consider increasing shadow copy storage using 'VSSADMIN Resize
ShadowStorage' command.
Error in backup of E:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: 2B4A9541-C88B-442E-9A7A-6D8A27342C11
Caption : Backup Using Child Partition Snapshot\FMLDC1
Logical Path:
Error : 8078010D
Error Message : Enumeration of the files failed.
Detailed Error : 80070003
Detailed Error Message : (null)
We had been getting a successful backup once or twice a week which showed completed (with no mentioned of warnings) but now it regularly shows completed with warnings as noted above.
We did a manual full backup of the DC to a different external drive a few days ago and that completed without warnings and the backup shows: E: Completed 63.38 Full - VSS Copy Backup Successful, 8/27/13 3:35 PM - 4:43 PM. Data Transferred 63.38
On a side note, we can view the logs in the windows/logs/windowsserverbackup directory but when we attempt to view the details of a log file through the Local Backup Console for any log which shows completed with errors, we get a "MMC has detected an error in the snapin and will unload and then it shows Object referenced not set to instance of an object." The manual backup noted above that was successful is able to be viewed through the Local Backup Console without this error.
Any idea as to why this is failing during the scheduled backups? This hosts a database that we need to have regular successful backups.
Hello,
When I try to run a system state backup with this command: wbadmin start systemstatebackup -backuptarget:<drive letter>
I get the error
"Failed to create the shared protection point on the source volumes.
ERROR - Volume Shadow Copy Service operation error (0x8004230f)
The shadow copy provider had an unexpected error while trying to process the specified operation."
I'm not sure how to fix this. I'm logged into the machine as an Administrator.
Windows Server Enterprise 2008 SP2 64-bit
Any suggestions??
Hi people!
I'm using arcserve backup 16.5 to backup my cluster 2012 (datacenter) (2 servers). Physical and virtual machines (15 vm's).
Now after a while the vss starting to show me some errors and my backup is failing on only both hyperv physical hosts on C drive.
After much investigating with the support of arcserve they say that they cant do much about this problem and the support redirected me to Microsoft. After much calling and putting me on hold and telling me that they will call me back I'm still sitting here
getting old and gray. So hope there is someone out there to help me out with this one.
The errors are only on the hyper-V hosts. The vm's and other server 2012 are backing up just fine (have not all the updates).
Here are the errors. (when clicking on some links they show me the CSV attached to my HyperV cluster and C: drive one of them)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{1693955f-32a1-4111-a860-e780d6637f1b}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000, The operation completed successfully.
], Flush[0x00000000, The operation completed successfully.
], Release[0x00000000, The operation completed successfully.
], OnRun[0x80042314, The shadow copy provider timed out while holding writes to the volume being shadow copied. This is probably due to excessive activity on the volume by an application or a system service. Try again later when activity on the volume is reduced.
].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
-------------------------------------------------------------------------------------------------------------------------------------------
Volume Shadow Copy Service error: The I/O writes cannot be flushed during the shadow copy creation period on volume \\?\Volume{cae23b9e-4d92-11e2-93e7-806e6f6e6963}\. The volume index in the shadow copy set is 2. Error details: Open[0x00000000, The operation completed successfully.
], Flush[0x80042313, The shadow copy provider timed out while flushing data to the volume being shadow copied. This is probably due to excessive activity on the volume. Try again later when the volume is not being used so heavily.
], Release[0x00000000, The operation completed successfully.
], OnRun[0x00000000, The operation completed successfully.
].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
-------------------------------------------------------------------------------------------------------------------------------------------
Volume Shadow Copy Error: VSS waited more than 40 seconds for all volumes to be flushed. This caused volume \\?\Volume{cd77626e-893f-4893-b6d3-a1cd5c1da041}\ to timeout while waiting for the release-writes phase of shadow copy creation. Trying again when disk activity is lower may solve this problem.
Operation:
Executing Asynchronous Operation
Context:
Current State: flush-and-hold writes
Volume Name: \\?\Volume{cd77626e-893f-4893-b6d3-a1cd5c1da041}\
------------------------------------------------------------------------------------------------------------------------------------------
The flush and hold writes operation on volume C: timed out while waiting for file system cleanup.
------------------------------------------------------------------------------------------------------------------------------------------
ARCSERVE ERROR: E12502 2014-02-16 13:41:19 The volume shadow service provider has reported a bad state for the operation.
-------------------------------------------------------------------------------------------------------------------------------------------
What I have done so far (without any luck):
vssadmin list writers are all stable and no errors.
vssadmin list providers are all Microsoft
Cleaned up shadow copies
Installed all updates (server 2012 and arcserve)
No antivirus installed (removed trendmicro)
Changed the setting on C: to maximum size: no limit on shadow copies
Rebooted system many times
There is enough space on the disks
Beste Regards, Stephan
We are using a simple backup script to put all of our data onto an external drive bay connected via USB 3 each night. All our script does it this:
wbadmin start backup -backupTarget:E: -include:BACKUP_FOLDERS -quiet
The problem is that the backup will either finish around 6am or not until 1pm or so. It runs a full backup as we rotate the drives out but the issue is not drive specific. Some days the backup will finish nice and early at 6am-ish. Other days it will take until about 1pm or so. It's copying the same amount of data each time. What could I look at to see what is causing the 7 hour variance in backup times?
Thanks!
VSS writers inside virtual machine 'CONTOSO' failed to perform BackupComplete to its shadow copy (VSS snapshot) set: Catastrophic failure (0x8000FFFF). (Virtual machine ID 9851BE14-F276-459D-8D60-DF73B67EB658)
What does it mean? Writers on virtual machine are OK and all backups are successfull. Every day I have one 10172 event for one backup in Hyper-V-VMMS event log.
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {17daa546-f2b5-44a8-b88f-31fae0650076}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {75f7fecf-4696-4f0e-8d09-19809d5f35da}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {204ef83b-d168-4179-a6aa-ef01e93dae7d}
State: [1] Stable
Last error: No error
Writer name: 'WIDWriter'
Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
Writer Instance Id: {b45a4a13-60a4-4f38-bdc0-c4cc748f3513}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {aca59bd3-2f19-4c76-b54a-28f2c2d95f73}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {41ef02d7-38b9-424a-b35b-a4b1cf79bd17}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {7a6ef84a-4fff-46ed-8921-da0d12fb5028}
State: [1] Stable
Last error: No error
Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {6d28a625-90a9-47a4-bf9f-fd8a6c76e770}
State: [1] Stable
Last error: No error
Writer name: 'MSMQ Writer (MSMQ)'
Writer Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
Writer Instance Id: {5bca99fe-6db6-4994-a744-e4149ba54364}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {d8249c2a-530f-48e9-92c3-179762ed0064}
State: [1] Stable
Last error: No error
Writer name: 'TermServLicensing'
Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
Writer Instance Id: {51f5c94d-514b-4ca7-b5dd-2f11047d6a54}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {ce748865-451a-4189-8276-f2cb177629da}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {207fe098-42ab-430b-9285-c0b902729ade}
State: [1] Stable
Last error: No error
hi,
I'm testing a bare metal restore of a Windows 2008 R2 domain controller using just builtin Windows Backup. The server is a VMWare virtual machine with the following configuration:
C: Os
D: NTDS
E: Logs
F: Sysvol
Once I restore the server, which goes flawless, I reboot and after startup I get a blue screen saying that the server cannot find the AD files.
Using F8, I startup in DSRM. Diskmanagement in DSRM shows me that all disks but the C: drive are offline. Once I set the disks online and reboot the DC starts up just fine. I am able to fix it but it leaves me puzzled.
I checked the disk signatures with mountvol and they are exactly the same as the original. A co-worker mentioned he saw this with other 2008+ servers too. Couldn't find anything related online ? I even made a new backup and restores it to a new VM so it can be reproduced.Anyone know why these disks are offline after a bare metal restore ?
Anyone ?
Thanx,
Thorwald
Thorwald van Elburg
This problem was first encountered on an IBM x3650 in a cluster with an IBM x3550 for failover, however this problem is reproducible on a server running HyperV not part of a cluster.
When I try to run a VM based backup from inside the VM using the server backup utility to E: drive(which is an attached vhdx file). It fails with this error
Backup failed to complete. There is not enough disk space to create the volume shadow copy on the storage location. make sure that, for all volumes to be backup up, the minimum required disk space
for shadow copy creation is available. This applies to both the backup storage destination and volumes included in the backup. Minimum requirements: For Volume less than 500 megabytes, the minimum is 50 megabytes of free space. For volumes more than 500 megabytes, the minimum is 320 megabytes of free space. Recommended: At least 1 gigabyte of free disk space for each volume if the volume size is more than 1 gigabyte.
Detailed Error: Insufficient storage available to create either the shadow copy storage file or other shadow copy data.
In the event viewer I see this error
EventID: 521 The backup operation that started at 'TIME’ has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '0x80780119'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
This problem was not happening in our test setup using Server 2012 R2 MSDN copy, before rolling out to production using ourVolume license copy of server.So as a test I installed two VMs on a Host(MSDN), one VM using our MSDN copy of server and one with our Volume license copy of server,very simple install, install Windows backup, attach VHDx file and attempt bare metal backup. The MSDN copy is able to perform the bare metal backup. TheVolume license copy fails with the above errors.
Has anyone else run into this problem? Or any ideas on where to look to see the differences between the two VMs that is stopping the backup from completing?
Hi people!
I'm using arcserve backup 16.5 to backup my cluster 2012 (datacenter) (2 servers). Physical and virtual machines (15 vm's).
Now after a while the vss starting to show me some errors and my backup is failing on only both hyperv physical hosts on C drive.
After much investigating with the support of arcserve they say that they cant do much about this problem and the support redirected me to Microsoft. After much calling and putting me on hold and telling me that they will call me back I'm still sitting here
getting old and gray. So hope there is someone out there to help me out with this one.
The errors are only on the hyper-V hosts. The vm's and other server 2012 are backing up just fine (have not all the updates).
Here are the errors. (when clicking on some links they show me the CSV attached to my HyperV cluster and C: drive one of them)
-----------------------------------------------------------------------------------------------------------------------------------
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{1693955f-32a1-4111-a860-e780d6637f1b}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000, The operation completed successfully.
], Flush[0x00000000, The operation completed successfully.
], Release[0x00000000, The operation completed successfully.
], OnRun[0x80042314, The shadow copy provider timed out while holding writes to the volume being shadow copied. This is probably due to excessive activity on the volume by an application or a system service. Try again later when activity on the volume is reduced.
].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
-------------------------------------------------------------------------------------------------------------------------------------------
Volume Shadow Copy Service error: The I/O writes cannot be flushed during the shadow copy creation period on volume \\?\Volume{cae23b9e-4d92-11e2-93e7-806e6f6e6963}\. The volume index in the shadow copy set is 2. Error details: Open[0x00000000, The operation completed successfully.
], Flush[0x80042313, The shadow copy provider timed out while flushing data to the volume being shadow copied. This is probably due to excessive activity on the volume. Try again later when the volume is not being used so heavily.
], Release[0x00000000, The operation completed successfully.
], OnRun[0x00000000, The operation completed successfully.
].
Operation:
Executing Asynchronous Operation
Context:
Current State: DoSnapshotSet
-------------------------------------------------------------------------------------------------------------------------------------------
Volume Shadow Copy Error: VSS waited more than 40 seconds for all volumes to be flushed. This caused volume \\?\Volume{cd77626e-893f-4893-b6d3-a1cd5c1da041}\ to timeout while waiting for the release-writes phase of shadow copy creation. Trying again when disk activity is lower may solve this problem.
Operation:
Executing Asynchronous Operation
Context:
Current State: flush-and-hold writes
Volume Name: \\?\Volume{cd77626e-893f-4893-b6d3-a1cd5c1da041}\
------------------------------------------------------------------------------------------------------------------------------------------
The flush and hold writes operation on volume C: timed out while waiting for file system cleanup.
------------------------------------------------------------------------------------------------------------------------------------------
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {0d3a0201-dcb2-407e-81a6-2482e7d75854}
----------------------------------------------------------------------------------------------------------------------------------
ARCSERVE ERROR: E12502 2014-02-16 13:41:19 The volume shadow service provider has reported a bad state for the operation.
--------------------------------------------------------------------------------------------------------------
What I have done so far (without any luck):
vssadmin list writers are all stable and no errors.
vssadmin list providers are all Microsoft
Cleaned up shadow copies
Installed all updates (server 2012 and arcserve)
No antivirus installed (removed trendmicro)
Changed the setting on C: to maximum size: no limit on shadow copies
Rebooted system many times
There is enough space on the disks
Beste Regards, Stephan
Hi
I have a windows server 2012.
I try to backup my server to a shared network folder. i defined a schedule for it and then it backedup but when i see the destination folder, only the last backup exist.
How to maintain previous backups in the shared folder?
thanks...
I have a Windows Server 2012 machine that keeps failing with Windows Server Backup. If I reboot the server, the backup will work fine for a day or tow, but then it will start failing again until I reboot the server again.
The error in the backup manager says "The shadow copy provider had an error."
The event log error is as follows:
Source: VSS
Event ID:12289
Volume Shadow Copy Service error: Unexpected error CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy160,0xc0000000,0x00000003,...). hr = 0x80070005,
Access is denied.
.
Operation:
Removing auto-release shadow copies
Loading provider
Context:
Volume Name:
\\?\Volume{4bb90a74-0f22-11e3-93f3-00155d59e900}\
Execution Context: System Provider
Any help would be greatly appreciated.
Thanks!
I have a server with an Asus mother board running 2008 on two SAS drives in RAID 1 via a PIKE 1068E card on the motherboard in the specific slot. The PIKE card is failing and seems to be killing any new SAS drives I have installed in the seconday slot. I am trying to instal a new PIKE 2008 card. I have backed up the entire server using the backup snap in module to an external USB hard drive. The backup drive is 500gb, and the backup image is about 326gb. The RAID image itself is 558gb. The first time I tried to restore using the MS protocol, I got the following message:
System image restore failed. The disk set as active in BIOS is too small to recover the original system disk. Replace the disk with a larger one and retry the operation (0x80042407)"
I then shrunk the C: image to 556gb, reformatted the backup drive, and backup up the new image. I am still am running into the same problem. Is there something else I have to do?
When trying to Backup (and/or Create a System image) onto my Network w/Windows 7 Professional, after entering my username and password, I get the following pop up message: "The specified network location cannot be used. Verify the path points to a correct network location and that the supplied credentials can be used for write access to the folder." Details further show " The specified service does not exist as an installed service (0x80070424)"
I have no problems dragging and dropping anything across my network or accessing any part w/Explorer. Originally I had no password set up at all, but set one up just to try and satisfy the Backup setup windows. I've also turned off all Firewall protection and Anti-virus software. Still no luck. Am on a Home network/Home group, not a Domain.
I've successfully done this in the past with no problems. I don't know what changed - obviously something did.
I've searched the web for answers, but so far have not found any - this is my first post specifically asking for help.
Is it even worth the trouble if I can create an image onto disks or an external hard drive directly connected via USB. Win7 Professional is supposed to Backup to the Network and that is what I would really like to do. Rem: PC - Personal Computer.
Any help would be appreciated - thanks in advance.
Mike M.
Hi all,
Background of problematic server - Server 2008 R2 SP1 running as a Hyper-V host. Runs 1x guest. Backing up full server using Windows backup to a 2TB SATA harddisk. Backup used to work until an ISCSI connection is disconnected in the guest. BackupWORKS if guest is turned off
Background of guest server - Server 2008 R2 SP1. DC and Exchange 2010 installed. It's backup target used to be a NAS via ISCSI. Now it is backing up to an attached VHD file
Error on host
In event viewer > Windows Log > Application :
Event 521, Backup-
The backup operation that started at '2014-02-23T10:00:15.400000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
In event viewer > Applications and Services logs > Microsoft > Windows > Hyper-V-VMMS :
Event 10112, Hyper-V-VMMS-
The number of volumes reverted does not match the number of volumes in the snapshot set for virtual machine 'GUEST-OS' (Virtual machine ID 30437CA0-AD79-4ADD-81A7-F52D3EA9C5BB).
After a failed backup, "VSSadmin list writers" shows the below:
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {7ef38770-bb0c-4ad3-8628-6e2c2a6a5873}
State: [5] Waiting for completion
Last error: Unexpected error
Have tried applying the hotFix KB975354 (http://support.microsoft.com/kb/975354/en-us) only to be told that it isn't applicable to my system.
I can also confirm that the ISCSI connection is definitely dropped in guest. Also, I've disabled the service "Microsoft ISCSI initiator Service" in guest.
Would appreciate if anyone let me know what else to be looking out for.
Cheers,
Chriso
Environment:
Windows Server 2012 R2 Essentials running in VirtualBox in a Windows 7 host. Networking is configured and works fine.
Background:
My only backup needs are to copy the contents of two folders to a NAS folder every day at 2 AM.
I configured a backup schedule in Windows Server Backup (wbadmin) to a network location which is hosted as a Samba share on a Synology NAS.
For authentication, I created a backup user which has the same username and password as a user on the Samba share, with permission to read and write the backup folder. I added this user to the Backup Operators group.
Problem:
When I try to run the Backup Once operation to test my backup, I get the following error message:
"Windows Backup cannot read the backup destination."
What I've tried:
I verified that the location is directly accessible in Windows by copying and pasting the address from the Windows Server Backup destination into explorer. Providing the backup user credentials opened the location and creating/reading files worked fine.
Adding the backup user to the Administrators group did not have an effect.
Update 2014-02-18
I checked the backup destination and was surprised to find that the scheduled backup actually completes successfully. However, Backup Once always results in the above error message.
Hello, we have recently added an oracle database to my server, my boss would prefer we keep 100% of the computers resources to the oracle database and has insisted me to build a new server and put all of my stuff on it. The problem is that I have spent hours and hours configuring that server with exchange server, VPN, file sharing services, etc., the list goes on and on. This is every Network Administrators nightmare.
Bottom line I have made a clone of the hard drive via Acronis, I thought I might get lucky and have similar hardware that the new server I built and it would boot up, I was not so lucky, as expected I got blue screened. I want this to be as simple as possible and after looking around I found there is no recovery/repair install for windows server 2008 that I could use which would just simply write over the system files and install to the new PC hardware while keeping my system settings and configuration in place.
Does anyone have some thoughts on the best way to do this? I have already done repairs to the boot sector via CMD in the recovery disk, no luck. Anyway to copy the registry over or something like that? I just want all of my system settings and configurations transferred to the new server I built.
Thanks