Forum Replies Created
I’ve used GP Health Reporter to have a look at several terminal servers and I found some strange results:
On more than one TS GP Health Reporter reports a GPC/GPT version mismatch for ALL GPO’s…
When looking with ADSIEdit and Explorer (gpt.ini) at the version numbers of an affected GPO they match!!
When inspecting the version numbers manually I used the same DC as reported by GP Health Reporter.
Also GPResult does not report any issues and DFSR/sysvol health is reported good by dcdiag.
Ran the GP Health Reporter as Administrator.
Any idea what can cause this?
I’ll try to describe the relevant part of the environment.
Users connect to a Citrix XenApp farm. The Citrix servers are rebooted every night which is quite common. The Citrix servers are virtualized on Hyper-V and are provisioned by Citrix Provisioning Services (CPS). It is configured in such a way that the Citrix VMs servers boot from an small ISO which causes them to contact CPS which in turn presents a VHD from which the Citrix VMs ultimately boot. This process means that changes that happen during the day, e.g. temporary files written, are discarded when the VMs reboot at night.
When a user logs on the Citrix software takes care of downloading the appdata part of the user profile to the Citrix server before the desktop is presented. On top of that some folders like desktop, documents etc. are redirected to a file server.
So maybe one could say that in a way users are always logging on to a fresh OS. But I must say I’m not certain if this is a correct assumption.
I.m.h.o this should mean that since the “always wait for network…” is a machine policy, it gets applied at VM boot.
I have confirmed that the policy is applied.
Question remains why do I see Folder Redirection warnings?
So should I care about these warnings?
Is testing folder redirection as simple as writing something to a redirected folder and monitoring the file server to see if it gets there?
First of all thank you for your time trying to help me.
Maybe I’m missing something but it is my understanding that if you have the computer setting “Always wait for the network at computer startup and logon” enabled in a GPO and one can confirm that this setting is applied with tools like gpresult, registry, etc, there is no need to logon twice because this setting is forcing foreground processing. Still we are seeing error 1274.
Am I missing something?
- Quirks in Restricted Groups Policy on AD Groups
- Understanding the Registry Policy Archive File
- Hijacking Administrative Templates
- What Does Group Policy Do When It Can’t Contact a DC?
- Sending GPOs Down the Wrong Track–Redirecting the GPT