Nemwar7

Thanks guys, I will try some of the recommendations you have mentioned and come back with the results. It's a slow process as I normally have to wait a day before I can verify if a theory is correct or incorrect.

Forgot to mention, when the computer is in this state, I cannot ping it.

optiplex 380, 390 and 3010. We had schedules running to wake-up computers and shut them down for windows updates, but removing the schedules makes no difference.

Hi, I have an issue which is effecting multiple sites and multiple dell optiplex models. All was working well until about 4 months ago. Teachers would come into school in the morning and the green power button would be lit up, the dvd drive can be ejected, but there is no display. Pushing the power button does not bring it out of a hibernate\standby state. The only way to get the computer to boot up is to do a dirty shutdown. However there are no event logs saying that there was a dirty shutdown. I have tried: updating bios firmware updating video drivers setting shutdown/wakeup schedules. Full windows update Removed all power management settings. BIOS config has not changed. Has anyone else come across this issue or have any advise on what direction I should be heading towards. Thanks, Warren

Use Group policy preferences. Install the font on 1 pc. Find the registry entry for that font. HKLM\Software\Microsoft\WindowsNT\CurrentVersion\Fonts Create a registry item in gpp duplicating the registry key on the pc you installed the font. Deploy the font file to c:\windows\fonts\ using gpp files. This is all assuming you have a 2008 server or RSAT on a vist or 7 pc.

Weird, logons are all below 20 seconds even when I logon a whole ICT suite using Ranger. I will keep an eye on it anyway. Cheers for the feedback. Have you found an alternative way of doing this yet?

I have had no issues with it. I have done it on multiple sites and had it for over a year with no issues. Do you have evidence of it decreasing logon performance? A microsoft post?

We have had this issues as well. We resolved it by setting up a file screen for desktop.ini.