After creating SCVMM backed desktops an XML file is created in SCVMM library that is permanently locked. This stops SCVMM library refresh. The XML file contains the sysprep customisation details. When refreshing the SCVMM library the process fails with the error "Error (802) The Script file #####.xml is already in use by another script"
This error can be the result of a failed provisioning task in SCVMM. The XML file contains the sysprep settings for the VM, this file gets mounted via the floppy drive during VM creation.
The error is seen when things don’t complete properly and SCVMM thinks the job hasn’t completed. Everything in SCVMM is a PowerShell job and when a provisioning task fails or something else happens and SCVMM doesn’t get a job completion event, it thinks the file is locked… It may or may not be locked! SCVMM just thinks it is.
To correct the problem you need to see if the vm creation job is still in the jobs logs and if the job failed or completed with warnings. Either way, it needs to be cleaned up in SCVMM since our Connection Broker doesn’t have the knowledge necessary to do the clean-up. When NO provisioning is going on you should be able to clean-up/delete these orphaned files. There is an associated hardware configuration for each of these that can be deleted as well.