M
M
Hello group,
I thought I was having issues with my domain controller restore procedure
for non-authoritative restores when after restoring all drives and system
state the group policies gave the following error.
gpotool: e ERROR: Err: CreateTime different between Adm
As I have 164 policies(at the time of writing and still growing!) this was
repeated for all but two which had a different file/folder to complain
about.
gpotool: e ERROR: Err: CreateTime different between ACCESS10.ADM
After contacting Mircrosoft they said that there is an issue with the
restore procedure where the the milliseconds portion of time is not
restored with the file. This is for the ntcreate filetime property. This was
not a concern as the policies were all OK and only gpotool complained. The
only way to fix this is to demote and promote again! More burflags d2
restores wouldn't fix the issue. Maybe the 2003 version of gpotool doesn't
compare the millisecond portion of the timestamp. I haven't checked.
I still haven't found out why this error is not presented for all files and
folders. I would have thought for all policies every single file and folder
would have this issue. But it's only happening for one file or folder per
policy. Weird. If I find out why I'll post here.
This post is done for archival purposes just in case someone else is combing
google for answers
Short answer is your policies are OK
Regards
M@
I thought I was having issues with my domain controller restore procedure
for non-authoritative restores when after restoring all drives and system
state the group policies gave the following error.
gpotool: e ERROR: Err: CreateTime different between Adm
As I have 164 policies(at the time of writing and still growing!) this was
repeated for all but two which had a different file/folder to complain
about.
gpotool: e ERROR: Err: CreateTime different between ACCESS10.ADM
After contacting Mircrosoft they said that there is an issue with the
restore procedure where the the milliseconds portion of time is not
restored with the file. This is for the ntcreate filetime property. This was
not a concern as the policies were all OK and only gpotool complained. The
only way to fix this is to demote and promote again! More burflags d2
restores wouldn't fix the issue. Maybe the 2003 version of gpotool doesn't
compare the millisecond portion of the timestamp. I haven't checked.
I still haven't found out why this error is not presented for all files and
folders. I would have thought for all policies every single file and folder
would have this issue. But it's only happening for one file or folder per
policy. Weird. If I find out why I'll post here.
This post is done for archival purposes just in case someone else is combing
google for answers
Short answer is your policies are OKRegards
M@