Jump to content

Recommended Posts

Posted

So, well over a year ago I created a GPO to add a scheduled task to the ICT Suite computers to shutdown at 6pm at one of the Primaries I support. Everything was going fine, or so I thought!

 

Yesterday I was asked to just check over the PCs make sure they were working as they had some staff training that evening. Which I did and reported back to the head, she then said "they aren't going to shut down at 5pm like they usually do are they?"

 

I had a look into it and she was right! the scheduled task was running at 5pm everyday. I checked the GPO again to make sure I'd not mistakenly set it to 5, nope GPO said 6pm. I changed the setting on the GPO to 7pm and did a GPupdate on the client and it changed to 6pm! So no matter what time I set it to run on the GPO, when it gets pulled down to the client its an hour early.

 

Time is correct on both DC and client, both on the same time zone. I assume its some issue with daylight savings, but why would it do this? anyone come across it before?

 

Server is 2012r2 clients Windows 7

 

Cheers Dave

Posted
iirc scheduled tasks dont take account of bst/gmt and always run on teh one they are created so if you create a task at 4pm now it will run at 3pm(or is it 5 anyway an hour wrong) in july
Posted
iirc scheduled tasks dont take account of bst/gmt and always run on teh one they are created so if you create a task at 4pm now it will run at 3pm(or is it 5 anyway an hour wrong) in july

 

They do if you apply the hotfix :) But aye otherwise no :D

 

Steve

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...