GPT.INI Write Lock

[jstigerwalt]

During testing, I have come across an issue with a very large domain of 60k machines, the GPT.INI file gets locked by a process not allowing the file to be written to. This doesn't allow the version number to be updated to match the attribute number updated in AD. An easy work around is to try this again in a few minutes or rename the the GPT.INI to GPT.INI.BAK and recreate it with the new version number. As a bonus I think it would be great to display in console the updated version number if manual changes are needed. I had to manually update the GPT.INI file and had to query AD to see what was the updated number was set in AD.

Application Update Ideas:

• If GPT.INI can not be written to, maybe loop for a minute and try again. If this still fails we could rename and create our own from a read copy of the original. We can also check permissions to see if we can do this. I have not looked at the code to see what is already done.
• Display the current version number in console, then display the updated version number that will be set. Instead of having to use SharpView to get this, we could just do it here.

[jsdhasfedssad]

Hi,

Is the error you get by any chance this? That would explain a lot for me.