Hello,

Please check "Details" tab for further details. Sometimes policies take a lot time to be updated due to low resources on SQL Server or on embedded database. 

You can also try to create a new group and create new policy and apply it to that group for testing it.

Regards,

Oykun

Its not because of the server delay, because on details tab policy created date and time are fine, but the time in policy serial number is wrong. Its exactly -5:30 hrs than the actual time so I guess its showing time in GMT as I am in IST which is +5.30 hrs.

The problem is, every other thing in SEP is showing time in IST only this policy serial number is in GMT, why?

Actually , now the policy time will be GMT time. Is your time zone ( GMT +5:30), then it is as per design.

if you want it to set to local timezone check this link

http://www.symantec.com/business/support/index?page=content&id=TECH165766

Hi Mahendra,

Check the Date format in  home page select the preferences link check for date format if you select DDMMYYYY change to MMDDYYYY restart the machine and refresh the home page.

I tried to change the date format but its not working, All the other logs and reports are showing time in IST, its only the time in policy serial number which is in GMT.

I think its not posible to change it as the policy serial number will not carry the time zone information with it and this will create confusion with the multi site environment. Thats why its been kept in GMT by design. Its just an assumption, It would be better if we can get a confirmation from any Symantec enployee regarding this.

Thanks

changing date format from log preference will not help.

try this link

http://www.symantec.com/business/support/index?page=content&id=TECH165766

restart SEPm service and try editing the policy