I find these records in the eventiewer on a windows 7 machine... we moved from FRS to DFRS and I wonder how ti investigate if this is related..

Retrying to retrieve account information.

Making system call to get account information.

The system call to get account information completed.

The call failed after 0 milliseconds.

Error: Retrieved account information. Error code 0x54B.

Error: Failed to register for connectivity notification. Error code 0x6BA.

Computer boot policy processing failed for EU\W031-8509$ in 1 seconds.

DCDIAG report no errors except for the error caused by not running the RODCPREP which we don't use.

• Moved by Brent HuModerator Monday, July 26, 2010 2:45 AM (From:Group Policy)
• Moved by Magon Liu Monday, July 26, 2010 2:57 AM (From:Windows 7 Miscellaneous)

I found that  0x6BA means that the RPC server is unavailable... so it means the network is not yet working properly and therefore it cannot reach the DC... how can I make the system wait longer for the network to be available... I know we already have a group policy configured with waiting for the network...

"Always wait for the network at computer startup and logon" is enabled...

Now I see that his is a Windows 7 issue look at this post

http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/289bb187-43ac-422c-9e91-925b3a4eddb7

I found another post that describes similar problems...

http://social.technet.microsoft.com/Forums/en-US/itprovistanetworking/thread/f3beb19c-b83d-422e-ba53-12eb4df81179

Windows 7 reports this in log also.

Group Policy dependency (Network Location Awareness) did not start. As a result, network related features of Group Policy such as bandwidth estimation and response to network changes will not work.

Group policy waited for 952 milliseconds for the network subsystem at computer boot.

Hi,

is this error only on that single machine? If yes, check that the machine it properly joined to the domain. The error in your first post it not FRS related. In this step the computer checks AD to get information about himself. Please first check if the compuer is correctly joined to the domain.

hope that helps,

Gunter

The machines are properly working on the domain... after Windows 7 is installed I can gpupdate /force and then see GP processing being sucessfull.. so only during login not using wireless but using GB LAN so it is not the network... I ran a debugger on a totally clean windows 7 machine from the SDK and found nothing other than system services being started during boot process.. it is no driver issue...

I guess Windows 7 just needs more time to wait for the network subsystem to be started.. can we manipulate that somehow?

Hello La1976,

Error 0x54B means ERROR_NO_SUCH_DOMAIN. According to the description, this issue only happens when a user logs on to the computer. This kind of issues usually occur because of Gigabit NIC. Please refer to the following KB.

326152 Can not connect to domain controller and can not apply Group Policy with Gigabit Ethernet devices
http://support.microsoft.com/default.aspx?scid=kb;EN-US;326152

980873  A computer cannot identify the network when the computer is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2, and is a member of a child domain
http://support.microsoft.com/default.aspx?scid=kb;EN-US;980873

Bre

Hello Brent,

Thanks for your help however the first link does not work...

Second link does not apply to Windows 7 machines...

The machine is member of a child domain but the intranetforests key gets populated...

Is there a way to make Windows 7 wait longer for the network to start?

Hello La1976,

>Is there a way to make Windows 7 wait longer for the network to start?
You may enable the "Always wait for the network at computer startup and logon" setting under Computer Configuration\Policies\Administrative Templates\System\Logon

So that we can help you resolve the issue, please try the following methods:

1.       Disabling Media Sensing for TCP/IP in Windows
How to disable Media Sense in Windows 7
http://social.answers.microsoft.com/Forums/en-US/w7desktop/thread/18277955-3f2c-4328-bd87-d3567579b645

2.       To update latest drivers for the Gigabit NIC.

3.       To enable PORTFAST on the Cisco switch.

 

Brent Hu,

I have installed the latest network driver... group policy settings, portfast enabled and disabled media sensing... no succes..

it is waiting 952 mili seconds for the network subsystem and that is not enough..

User policies are processed system policies not.

 

 

Hello La1976,

Does this issue exist for all Windows 7 clients or just some of them?

Brent Hu,

This happens on all Windows 7 machines..

When I configure the GPO setting Startup policy processing wait time to 5 seconds I have solved the issue.

Setting Path:
Computer Configuration/Administrative Templates/System/Group Policy

 

 

• Marked as answer by LA1976 Monday, August 02, 2010 8:07 AM

Hello La1976,

I'm glad to know you have resolved the issue. Thank you for your sharing.

Brent Hu,

HI, 

  I got the same issues and GPO is Applied but not processed. Look like Script cannot find.

 So got followings events in start up

20/03/2015 1:51:54 PM-  A previous instance of the Group Policy Client Service has been detected. Parameter: 627c4d4d-04fd-4ae3-9697-9c7daa5037c6

Group Policy dependency (Network Location Awareness) did not start. As a result, network related features of Group Policy such as bandwidth estimation and response to network changes will not work.

Group policy waited for 47 milliseconds for the network subsystem at computer boot.


Starting computer boot policy processing for BPO\AUD04809F8$. 
Activity id: {2ea676b9-7231-4443-a166-340d1217fecb}

Making system call to get account information. 

The system call to get account information completed. 

The call failed after 297 milliseconds.

Making system call to get account information. 

The system call to get account information completed. 

The call failed after 0 milliseconds.

Error: Retrieved account information. Error code 0x54B.

Computer boot policy processing failed for BPO\AUD04809F8$ in 1 seconds.

Making LDAP calls to connect and bind to Active Directory. 
DC03.bpo.com

Domain Controller details: 
Domain Controller Name : \\DC03.bpo.com
Domain Controller IP Address : \\10.110.187.3

20/03/2015 1:53:00 PM-  Group Policy successfully discovered the Domain Controller in 531 milliseconds.

20/03/2015 1:53:00 PM -The system calls to access specified file completed. 
\\bpo.com\SysVol\sercobpo.com.au\Policies\{2A56F8BE-F773-4EE6-8CB2-507BA1B8575C}\gpt.ini
The call completed in 32 milliseconds.

I have tried 60 Sec but nothing works.

This is my GPO Computer Policy

Computer Configuration (Enabled)


Policies


Windows Settings


Scripts


Startup


For this GPO, Script order: Windows PowerShell scripts will run first



Name

Parameters

CIC3UNinstallV4Install.ps1  
delete.bat  


Administrative Templates


Policy definitions (ADMX files) retrieved from the central store.

System




Policy

Setting

Comment

Verbose vs normal status messages Enabled  

System/Group Policy




Policy

Setting

Comment

Registry policy processing Enabled  

Do not apply during periodic background processing Enabled 
Process even if the Group Policy objects have not changed Enabled 
 

Policy

Setting

Comment

Scripts policy processing Enabled  

Allow processing across a slow network connection Enabled 
Do not apply during periodic background processing Enabled 
Process even if the Group Policy objects have not changed Enabled 
 

Policy

Setting

Comment

Startup policy processing wait time Enabled  

Amount of time to wait (in seconds): 60 
 

System/Logon




Policy

Setting

Comment

Always wait for the network at computer startup and logon Enabled  

System/Scripts




Policy

Setting

Comment

Run startup scripts asynchronously Disabled  
Run startup scripts visible Enabled  

Windows Components/Windows PowerShell




Policy

Setting

Comment

Turn on Script Execution Enabled  

Execution Policy Allow local scripts and remote signed scripts