provisioning/reprovisioning security database error

Hello Joel,

You say this affects provisioning and reprovisioning, so I wonder if this may be related to the template you are using. Have you created any new VM's from this template that do not see this error?

Have you seen this Microsoft article aimed at troubleshooting the same error you have shown above, this may help http://technet.microsoft.com/en-us/library/ee849847(WS.10).aspx

If this does not help can you let me know your sysprep settings and also if you have tried an alternative template.

Kind Regards

David

Hi David,

Thanks for the TechNet article - I read through it but didn't see anything that made me say 'a-ha!" This happens randomly during both provisioning and reprovisioning but more often on a reprovision. I've tried several templates and the behavior is the same.

EDIT: I should state that we usually delete the desktops prior to using the 'reprovision computers' task - what I'm not sure about is if the accounts get deleted from Active Directory as well?

I had thought that it might be an issue with the account we used in the sysprep process, to create the desktops, not having rights to reset the computer object, so the reprovisioned desktop can be joined/rejoined to the domain. I'm not even sure that is what's going on behind the scenes but on a reprovision, the computer object still exists, right?

Thanks for the help!

I've reviewed my sysprep settings - tried to reproduce them here........hope these help:

sysprep type=win7

import=none

operating system=vista/win7, 32 bit

registration=yes

time zone=utc-5:00 EST

product key=static

execution mode=greyed out

admin passwd=greyed out

domain=ourdomainname - also contains an AD account that can add computers to domain

ad path=OU=Workstations,OU=ourlocation,OU=location,DC=ourdomain,DC=int

local account=we specified a local account be created

firewall=all disabled

regional settings=US....Englishx3

run once=none

id string=vWorkspace Sysprep

Message was edited by: joel kilthau

Hello Joel,

You have said you usually delete the desktops prior to reprovisioning them, may I ask you to describe the steps taken in this process?

Where do you delete the desktop, in the vWorkspace Console of on VMware?

It is not required to delete the VM before reprovisioning, have you reprovisioned any VM's without first deleting them, if so do you still see the error?

Also, in your sysprep file the domain section should always be in the FQDN format, e.g. vworkspace.co.uk and the AD account should be in the format vworkspace\Administrator

Regards

David

David - they successfully complete the sysprep process and are able to join the domain.

I did not try to login locally but will do that today and I will also reprovision @ 5 VMs without deleting them first.

EDIT: I can logon locally.........

Message was edited by: joel kilthau

Thanks David - here's what we usually do......

- In the vWorkspace Management Console/Locations/Desktops/computergroup - on the Computers tab, right-click on the computers and select Delete

- We have reprovisioned without deleting the computers; we still see the random "The security database on the server....."

- We are using the FQDN format in the sysprep configuration......

Really appreciate the help!

Hello Joel,

Can you tell me if the VM's successfully complete the sysprep process when you see this error or do they fail to domain join?

If you were to create, or reprovision, 5 VM's and then see the error would this usually effect them all or only some?

Are you able to login locally and view the Windows event log, does this show any further information about why this error occurred?

David