[bookie32]

Hi guys!
I have had a dualboot scenario a while now with Windos Server 2008r2 and Ubuntu, but today I received the folloing code 0xc0000034 and I have tried running a repair cd to see if that will fix it....nada.
Can't even get into safety mode.....
I know there is a fix for this problem, but how can I install it when the computer wont boot? Check here
How can I fix this without a reinstall......


bookie32

This post has been edited by bookie32: 17 May 2012 - 11:32 PM

[Tripredacus]

That's nice to have a fix but not tell anyone how to install it. It does say that it can't be used offline, so that's definately a problem.

[allen2]

Indeed, pretty stupid from MS not offering a proper way (the only way seems to restore) but perhaps the usual tools procmon, regshot or installrite can help you to find (monitoring the patch installation on another windows 2008 install) how to apply the fix offline and repair your install.

[bookie32]

Hi guys!

allen2
Would you lie to give a little more info....
My biggest problem is I haven't backed up MDT 2010 and all the settings
I can go in and backup files with Linux, but I laid down so much work and to have to reinstall is not nice....
If I have understood things right - then windows server haven't a usual way of turning back the clock because of problems?!
All I have is the wim file I created when everything was installed and that I can reinstate....is there a better way so I can avoid heart attacks....

bookie32

[allen2]

Here is what i'll try:
1) install another windows 2008 R2 somewhere else (a VM would be my first choice) and disable UAC (as it might block installrite)
2) install installrite (as it should be the easiest way) and start it to take the "picture" before applying the MS Patch.
3) install the patch following installrite directions.
4) after installation (and perhaps reboot if needed), installrite will compare what was modified and will tell you which files/reg entries were modified.
5) filter the registry entries and system files found.
6) copy the files and create the reg entries you decided after filtering.
7) boot with a winpe or a windows 2008R2 install CD (then select repair to get the command prompt).
8) copy the files and import reg entries (remember to load the offline hives) from step 6.
9) reboot and see if it's fixed.
10) use another tool to replace installrite if installrite failed to get the files/reg entries added/modified/removed.

Perhaps, if i find enough time, i'll try playing with this but i don't know if it will be soon.

[bookie32]

Hi allen2!
No probs...grateful for the help!

bookie32

[allen2]

It looks like that either Microsoft updated the article or i didn't read it properly the first time but Ms is providing a workaround to repair the install.
Anyway i'll try tracing the changes made by the update.

[allen2]

OK here is what the update is doing (it doesn't ask for a reboot):
- added registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version]
"6.1.7601.17592"=hex(2):25,53,79,73,74,65,6d,52,6f,6f,74,25,5c,77,69,6e,73,78,73,5c,78,38,36,5f,6d,69,63,72,6f,73,6f,66,74,2d,77,69,6e,64,6f,77,73,2d,73,65,72,76,69,63,69,6e,67,73,74,61,63,6b,5f,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,5f,36,2e,31,2e,37,36,30,31,2e,31,37,35,39,32,5f,6e,6f,6e,65,5f,30,62,30,65,34,62,34,30,32,35,63,66,34,30,34,39,00,

- deleted registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version]
"6.1.7600.16385"=hex(2):25,53,79,73,74,65,6d,52,6f,6f,74,25,5c,77,69,6e,73,78,73,5c,78,38,36,5f,6d,69,63,72,6f,73,6f,66,74,2d,77,69,6e,64,6f,77,73,2d,73,65,72,76,69,63,69,6e,67,73,74,61,63,6b,5f,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,5f,36,2e,31,2e,37,36,30,30,2e,31,36,33,38,35,5f,6e,6f,6e,65,5f,30,39,33,35,62,37,36,63,32,38,39,65,30,66,64,35,00,

- modified registry:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CMF\SqmData]
"CMFStopTime"=hex(B):40,9d,a0,c3,45,31,cd,01,

-added files:

C:\Windows\servicing\Packages\Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB2533552_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB2533552_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Sessions\30224771_2298723297.back.xml
C:\Windows\servicing\Sessions\30224771_2298723297.xml
C:\Windows\servicing\Version\6.1.7601.17592
C:\Windows\servicing\Version\6.1.7601.17592\amd64_installed
C:\Windows\servicing\Version\6.1.7601.17592\x86_installed
C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_for_KB2533552_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\amd64_installed
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\apds.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\apircl.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\apss.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\CbsCore.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\CbsMsg.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cmiadapter.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cmitrust.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cmiv2.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\CntrtextInstaller.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\dpx.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\DrUpdate.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\drvstore.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\esscli.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\fastprox.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\GlobalInstallOrder.xml
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\helpcins.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\locdrv.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\mofd.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\mofinstall.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\msdelta.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\mspatcha.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\OEMHelpIns.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\PkgMgr.exe
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\poqexec.exe
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\repdrvfs.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\smiengine.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\smipi.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\SvcIni.exe
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wbemcomn.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wbemcore.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wbemprox.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\WcmTypes.xsd
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wcp.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wdscore.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wmicmiplugin.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wmiutils.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wrpint.dll
C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\xmllite.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\apds.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\apircl.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\apss.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\CbsCore.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\CbsMsg.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cmiadapter.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cmitrust.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cmiv2.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\CntrtextInstaller.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\dpx.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\DrUpdate.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\drvstore.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\esscli.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\fastprox.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\GlobalInstallOrder.xml
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\helpcins.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\locdrv.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\mofd.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\mofinstall.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\msdelta.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\mspatcha.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\OEMHelpIns.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\PkgMgr.exe
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\poqexec.exe
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\repdrvfs.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\smiengine.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\smipi.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\SvcIni.exe
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wbemcomn.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wbemcore.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wbemprox.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\WcmTypes.xsd
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wcp.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wdscore.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wmicmiplugin.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wmiutils.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wrpint.dll
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\x86_installed
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\xmllite.dll
C:\Windows\winsxs\Catalogs\ba47519f54b38889385eefca5ab020c0ac61c1b841622d3de94b2a3a43bcb250.cat
C:\Windows\winsxs\FileMaps\$$_servicing_version_6.1.7601.17592_a11607b30a47f76f.cdf-ms
C:\Windows\winsxs\Manifests\amd64_41132c9135820a69ab9fcde658ad1324_31bf3856ad364e35_6.1.7601.17592_none_66b394c89e0fceda.manifest
C:\Windows\winsxs\Manifests\amd64_fc1bde87f5bc34c852e947acaa841765_31bf3856ad364e35_6.1.7601.17592_none_4d581c651c62820b.manifest
C:\Windows\winsxs\Manifests\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f.manifest
C:\Windows\winsxs\Manifests\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049.manifest

- modified files

C:\Windows\servicing\Sessions\Sessions.back.xml
C:\Windows\servicing\Sessions\Sessions.xml
C:\Windows\System32\poqexec.exe
C:\Windows\System32\catroot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb
C:\Windows\SysWOW64\poqexec.exe
C:\Windows\winsxs\FileMaps\$$.cdf-ms
C:\Windows\winsxs\FileMaps\$$_servicing_fc2045b9046cc796.cdf-ms
C:\Windows\winsxs\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms
C:\Windows\winsxs\FileMaps\$$_syswow64_21ffbdd2a2dd92e0.cdf-ms
C:\Windows\winsxs\FileMaps\_0000000000000000.cdf-ms
C:\Windows\winsxs\ManifestCache\e4e8be02b8fae2a7_blobs.bin

- deleted files

C:\Windows\servicing\Version\6.1.7600.16385
C:\Windows\servicing\Version\6.1.7600.16385\amd64_installed
C:\Windows\servicing\Version\6.1.7600.16385\x86_installed
C:\Windows\winsxs\FileMaps\$$_servicing_version_6.1.7600.16385_9f2f8c770d21b01b.cdf-ms

[bookie32]

Hi Mate!

Thanks a lot for your time and effort....I will get to that as soon as I have a mo and report back here when I have sorted it or need more help....


Thanks again!

bookie32

[bookie32]

Hi again!
Been a bit busy...but I have looked at the workaround, but that doesn't work because there is no pending.xml file to load. I have checked in linux and sure enough it isn't there.
I tried this from a windows server Enterprise r2 cd and pointed to the usb with the script.vbs on it , but like I said there is no "pending.xml" to be found.
I haven't had time to do a VMware install to test your theory, but will get onto that.

As you can probably remember I have installed windows server enterprise r2 on the 120GB drive, but also have Ubuntu LTS (long term support) on the rest of the drive and it is the grub2 I am using to bring up my start menu and then choose Windows Server from the start menu.
What worries me is even when I choose Windows Server from the menu and then F8 it still throws up the error, so I can't even get to repair that way and hence the reason for running it from repair cd.

Can one reinstall Windows Server with original settings intact?

bookie32

PS Just noticed that sp1 has been installed for a while. I checked one of my wim files that I created after installing everything and that already has the sp1, so I don't unstand the error code?! Even the repair cd finds the installation but can't tell me how big it is?

This post has been edited by bookie32: 16 May 2012 - 05:47 AM

[Tripredacus]

Well there is a program on the Server 2008 R2 CD called Startrep.exe (in Sources) you can try, but you'll probably have to re-do your grub since it might not let you boot into Ubuntu afterwards. Here is some info on that program.

http://support.micro....com/kb/2261423

[bookie32]

Hi again!
Little update here...
I was starting to tear out more of the little hair that I have left when I thought in for a penny in for a pound.
I backed up the BCD and then rebuilt it and then when running repair I could see the installation.
I cd to the recovery directory on the dvd and then ran StartRep.exe. Well, it didn't rung long and said nothing to fix so I restarted but had the same error....?!!

Since fixing the BCD i hadn't updated my grub2 and so it was still giving me the same above error... I ran the repair cd again this time using bootrec to fix mbr and boot and low and behold on boot there was my server install again. chkdsk ran on all my disks and then started the server as usual.

I don’t like the bootloader for Windows, so I updated my grub and now I am getting my usual boot menu from Linux and Windows seems OK….
Right just been looking through my settings and it says Windows Server Backup isn't installed but can be.....must have had my eyes closed to have missed this one....

What is the difference between the Windows Server Backup function and a .wim file?

Might have asked this before..... my basic Windows Server installation is on the 120 ssd drive with Ubuntu and I have moved the page file to another drive and my user account and programs reside on another drive.

Question:
If I create a .wim file of the C:drive now and then will that .wim file if reinstated know that my programs and user account are on another drive?
Or does the Windows Server Backup work in some other mysterious way which is better....?

bookie32

BTW I also checked the update record and the so called helpful update KB2533552 was installed ages ago, so I am stumped as to why I had the error code?

This post has been edited by bookie32: 16 May 2012 - 09:43 AM

[bookie32]

Hi Tripredacus!
Sorry missed this post....
Thanks for the info...

Tripredacus, on 16 May 2012 - 08:32 AM, said:

Well there is a program on the Server 2008 R2 CD called Startrep.exe (in Sources) you can try, but you'll probably have to re-do your grub since it might not let you boot into Ubuntu afterwards. Here is some info on that program.

http://support.micro....com/kb/2261423

booke32

[Tripredacus]

StartRep runs very fast even if it does have something to fix.

Sorry I don't know about your backup question. Its still an area I'm lacking in experience.

[bookie32]

Hi Tripredacus
No problems...Yes , at this stage I ran several commands and maybe it was the StartRep.exe that did the work....

I didn't know about that before and it is a useful tool.

I have been reading up on the "Windows Server Backup" function and will probably give it a try as another safety net. It would be nice to be certain that reinstating from a back up would save the links between my 120ssd drive and the program files and user accounts on another.

At the moment I have the follwing setup:

120GBssd
Windows (installation) 60GB and Ubuntu 10.04lts on the other 60GB
1TB WD Black 64mb cache
Linux Swap and Home
1TB WD Black 64mb cache
This is an extended drive divided up into Program Me (user) and Vmware
2TB WD Green 64mb cache
This is a extra space for all my files from linux
2TB WD Green 64mb cache
This has most customer files MDT
Doing a back up of that lot is not really an option at the moment, but I try to keep an eye on things. Eventually I will add a virtual server to back up everything.

bookie32

[allen2]

Windows server backup does its backup to vhd file and should also take things like the mbr and not only the files like the wim do. Both backups will keep the link to your other drive/application but if you want to restore from bare metal windows server backup is better as it "should" restore also the mbr and the partition table....

[bookie32]

Hi allen2!
God you are too quick for me.....lol

Thanks for that..I will leave the new thread open to see what transpires....now there is a word for the day...

Going to read now...

Thanks again!

bookie32