Vacationing in Casablanca...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a problem with a hand full of my Win XP Pro boxes that i hope someone
can help with. we have about ten boxes using in and on about half of them the
time zone seems to be stuck in Casablanca. by stuck i mean that i change it
back to pacific but it only stays for a few days and in some cases only a few
hours.

i have run all available updates to all the software on the PCs effect but i
think it must be a issue with windows because their is no consistency between
the effected boxes. they have different hardware, there is no piece of
software less Win XP that on all the vacationing boxes and they are not all
on the same network...

any help would be appreciated.
 
I have a problem with a hand full of my Win XP Pro boxes that i hope someone
can help with. we have about ten boxes using in and on about half of them the
time zone seems to be stuck in Casablanca.


"And no matter what the progress
Or what may yet be proved
The simple facts of life are such
They cannot be removed."

by stuck i mean that i change it
back to pacific but it only stays for a few days and in some cases only a few
hours.

i have run all available updates to all the software on the PCs effect but i
think it must be a issue with windows because their is no consistency between
the effected boxes. they have different hardware, there is no piece of
software less Win XP that on all the vacationing boxes and they are not all
on the same network...

any help would be appreciated.


"You must remember this
A kiss is just a kiss, a sigh is just a sigh.
The fundamental things apply
As time goes by."

Sorry, I wish I could be helpful, but I can't. But I couldn't resist
the quotation.
 
Show them 'Homie can play dat'. Set a Policy with GPEdit.msc that fixes the
time zone (in a startup script)
-pacificZone.vbs--
strComputer = "."
'Change value to reflect desired GMT offset in minutes.
intGMTOffset = -480
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colCompSys = objWMIService.ExecQuery _
("Select * from Win32_ComputerSystem")
For Each objCompSys in colCompSys
objCompSys.CurrentTimeZone = intGMTOffset
objCompSys.Put_
Next
--end file--
 
each copy of windows
has 2 free technical
support tickets for help
from a certified microsoft
technician.

obviously you only
need one ticket to ascertain
a fix for all the windows you
have with the same issue.

go to microsoft.com and
look up support to begin the
process to submit the problem.

give us a ring when
you get to timbuktu...
--

db ·´¯`·.¸. said:
<)))º>·´¯`·.¸. , . .·´¯`·.. ><)))º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><)))º>


..
 
1: i don't need poetry.

2: i would much rather have a solution then a work around. as to prevent
this in other PCs and to keep it from causing more problems later.

3: remember i am already in Timbuktu... i have Microsoft software on my PCs.
 
also i don't think the problem is always present at startup. on some PCs the
switch only takes a few hours to happen with no restart in between on other
times it is several days before it happens again.
 
Better called a 'countermeasure' than a workaround. Some active agent is
changing the Zone, and it isn't anything in the Windows operating system.
Consider a log of the event viewer.
 
Ken

It's autumn not spring!

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
True Ken but your in the northern hemisphere. and probably a Humphrey
Bogart fan.

--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Back
Top