While sitting at a customer and configuring Cluster Aware Update for a Scale out Fileserver, I ran in my most beloved known issue with CAU.
Everytime I use a prestaged computer object for cluster aware update cluster resource, I get following error messages:
In the first place I thought the delegation ins right but I configured it a short while before and when I let the cluster the CAU Object by its self, everthing is fine.
So it couldn’t be that. So I checked Technet and found the issue on the known issue pages, together with a workaround
Source: http://social.technet.microsoft.com/wiki/contents/articles/13590.known-issues-windows-server-2012-failover-clustering.aspx & https://social.technet.microsoft.com/forums/windowsserver/en-US/acd3522e-7f76-4f53-8746-0676db6b2c38/clusteraware-updating-dns-configuration
Resolution: The easiest way I tried is to reset the DNS record for the cluster object. You can do that by using the powershell command
Get-ClusterResource ‘<your CAU prestaged object’ | Update-ClusterNetworkNameResource
Let the Cluster place the CAU object automaticly and than rename it, while using
Rename-ADObject -Identity “CN=<CAU Object Name>,CN=Computers,DC=Contoso,DC=com” –NewName “<your new Object Name>”