Windows cannot access the file gpt.ini for GPO on workstations running on a domain using sbs 2011

It's probably cause you did not complete a successful replication between the old DC and the new.

Check for the path you get in the error and see if it EXISTS.
If so:
 check authorization: should be read access for "authenticated users", that includes the computers account.

if not:
 you can choose to restart the old DC and try to resolve replication issues by using technet guides or whatever else.

OR

if you had no special GPO in place, you can choose to delete them and recereate, unless is the default domain policy, for which there's a special procedure to follow. (let me know if we're in that case).

Some other  clues and suggestions here:
http://support.microsoft.com/kb/294257/en-us

Get-GPO : The specified directory service attribute or value does not exist. (Exception from HRESULT: 0x8007200A)
At line:1 char:8
+ Get-GPO <<<<  -Id 247FB84B-891B-4B09-9616-7C069C613612
    + CategoryInfo          : NotSpecified: (:) [Get-GPO], COMException
    + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.GroupPolicy.Commands.GetGpoCommand

can u paste the full command and error ?

typical, it worked that time, I must have mistyped some thing, even thou i tried it 4 times, give me a sec to do the rest

that policy has now been removed, it was for DisplayName      : Update Services Client Computers Policy

is there any point to reproduce this for the moment ?

Yuo need to first verify does this policy quid exist in sysvol folder 247FB84B-891B-4B09-9616-7C069C613612.check this path \\mydomain.local\SysVol\mydomain.local\Policies\ in sysvol folder.In GPMC console you also need to verify what is the name of this policy.Check GPMC and check the policy name and quid if the policy is missing or not required you need to delete the same from AD database if not required.You need to open adsiedit and check the Path=CN=Policies,CN=System,DC=DomainName,DC=com.

If the old DC is not demoted check the sysvol folder of old DC it could be that policies are not replicated to new DC.In this case case you need to perfrom d4 (authorative restore of sysvol)on old DC and d2(non authorative restore of sysvol) on new DC.

The event you mentioned indicates that server is Journal wrap error state.Your first step should be finding why JRNL_WRAP_ERROR error has occurred. Normally, JRNL_WRAP_ERROR occurs due to drive/partition being corrupted, antivirus locking and corrupting the file during sysvol scan, heavy size of the files inside sysvol and netlogon shares.http://support.microsoft.com/kb/290762

You need to exclude sysvol/netlogon from antvirus scan, check the drive for corruption or bad sector and also restore a sysvol using burflag key i. perform authorative and non authorative restore of sysvol.If you have single DC then you need to perfrom D4 or multiple then D2 only.Follow same link above.