Hello,
I have a farm of 20 Windows Server 2008 R2 / XenApp 6.5 HFU3 servers. They are running on 8 MS Hyper-V 2012 hosts, and are streamed from two Citrix PVS 7 servers.
Starting about 3 weeks ago, some of these servers starting failing on processing group policy on startup. This is causing start up scripts on the server not to run, which is causing issues with an app on those servers.
The system log shows Evend ID 1055 each time this happens:
Log Name: System
Source: Microsoft-Windows-GroupPolicy
Date: 3/27/2014 3:46:54 AM
Event ID: 1055
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: computer.domain.com
Description:
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event ">
<System>
<Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}"
/>
<EventID>1055</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>1</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-03-27T08:46:54.394500000Z"
/>
<EventRecordID>79452</EventRecordID>
<Correlation ActivityID="{378ED4B7-81CA-4E54-AEF7-E5818682960C}"
/>
<Execution ProcessID="1264" ThreadID="1632" />
<Channel>System</Channel>
<Computer>computer.domain.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SupportInfo1">1</Data>
<Data Name="SupportInfo2">1632</Data>
<Data Name="ProcessingMode">1</Data>
<Data Name="ProcessingTimeInMilliseconds">1532</Data>
<Data Name="ErrorCode">1355</Data>
<Data Name="ErrorDescription">The
specified domain either does not exist or could not be contacted. </Data>
</EventData>
</Event>
All servers are rebooted every night, but only 3-5 of them are having this issue. It is also not the same XenApp servers every day.
Each VM has two NIC's. The VM needs to boot up via PXE on the legacy NIC. That NIC gets an IP from DHCP. Once the synthetic NIC comes online in the VM, Citrix Provisioning Tools re-IP's the legacy NIC with an APIPA address, and all PVS and network traffic uses the synthetic NIC. The synthetic NIC gets an IP from a DHCP reservation.
We saw the same issue when the XenApp 6.5 image was first deployed. The servers were trying to process group policy before the synthetic NIC came online. This was fixed by putting the Client for MS Networks back on the legacy NIC. Now it has started happening again.
Thank you for any help you can provide.
I have a farm of 20 Windows Server 2008 R2 / XenApp 6.5 HFU3 servers. They are running on 8 MS Hyper-V 2012 hosts, and are streamed from two Citrix PVS 7 servers.
Starting about 3 weeks ago, some of these servers starting failing on processing group policy on startup. This is causing start up scripts on the server not to run, which is causing issues with an app on those servers.
The system log shows Evend ID 1055 each time this happens:
Log Name: System
Source: Microsoft-Windows-GroupPol
Date: 3/27/2014 3:46:54 AM
Event ID: 1055
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: computer.domain.com
Description:
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
Event Xml:
<Event xmlns="http://schemas.micr
<System>
<Provider Name="Microsoft-Windows-Gr
<EventID>1055</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>1</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2014-03-27T08:
<EventRecordID>79452</Even
<Correlation ActivityID="{378ED4B7-81CA
<Execution ProcessID="1264" ThreadID="1632" />
<Channel>System</Channel>
<Computer>computer.domain.
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SupportInfo1">1</Dat
<Data Name="SupportInfo2">1632</
<Data Name="ProcessingMode">1</D
<Data Name="ProcessingTimeInMill
<Data Name="ErrorCode">1355</Dat
<Data Name="ErrorDescription">Th
</EventData>
</Event>
All servers are rebooted every night, but only 3-5 of them are having this issue. It is also not the same XenApp servers every day.
Each VM has two NIC's. The VM needs to boot up via PXE on the legacy NIC. That NIC gets an IP from DHCP. Once the synthetic NIC comes online in the VM, Citrix Provisioning Tools re-IP's the legacy NIC with an APIPA address, and all PVS and network traffic uses the synthetic NIC. The synthetic NIC gets an IP from a DHCP reservation.
We saw the same issue when the XenApp 6.5 image was first deployed. The servers were trying to process group policy before the synthetic NIC came online. This was fixed by putting the Client for MS Networks back on the legacy NIC. Now it has started happening again.
Thank you for any help you can provide.