Verify that the following folder C: \ Windows \ system32 \ ServerManager \ Cache no files exist CbsUpdateInfo.bin y CbsUpdateState.bin and if we copy from another server with the same characteristics, patch level and installed roles and start the Server Manager to remove these become.

Take ownership and give the user permissions will copy the necessary files (Corrupt) in this case megacrack.es \ xavixaus.

Many of you in implementing your companies estaréis Windows Server 2008 R2, many of you You will wear Symantec Ghost to make images and many of you do not you prove to restore that image assuming that if it has always worked properly because it has to fail now ?.

Well, for those who give things for granted I show that you can never trust you anything and I urge you to reconsider as always with a good example.

In our environment as we are good professionals we must be sure that things after the time and in case of error can restore, we have backups, process of disaster recovery tested and reliable systems and reliable for our customers they are comfortable with the decision to contract-us.

The example I will show is a solution to a problem that should not have checked the 2 things or more times would not have been detected until really after the time I had realized that no clone which had made from Windows Server 2008 R2 worked. So if this is your case, comprobad-the now before things get any worse.

The error will explain how to fix it:

When restoring a clone made with Windows Server 2008 ghost R2 without having done a sysprep (not always what we do, clean registry keys, administrator password, etc ...) the following error appears to us 0xc000000e

This message was undeliverable. Please try again later or contact your network administrator. The client operation failed. Error: [0x80004005-0x0004b9-0x000501].

So begins our story today, why is this happening and how you can fix.

One of the easiest things to fix it there in case you for example a user or a low-level technician. (You know, reboot and ready). But as we are a little more veterans and we do not like the reset and ready and want to know the why of all things so that in future no longer arrive or to happen.

Well, This problem happens when a domain user changes the password to a session torn from Outlook, the password is changed in the domain with which it does in the Exchange, but the outlook has not been synchronized since they of take a little longer, there has again been validated with the new credentials. '

Solution: Only closing and opening the Windows session again the problem will be solved.