i see you wanted to have client time as default...opps From: [email protected] To: [email protected] Subject: RE: [mssms] RE: Client time vs UTC Date: Sat, 7 Jun 2014 14:50:23 +0000
I've heard and seen this UTC vs. Client Local time hit ConfigMgr folks a few times... I know for sure, when you deploy an application, one of the radio buttons when selected, will allow you pick from UTC and Client local time. I think its on the scheduling tab. Mike D- From: [email protected] To: [email protected] Subject: [mssms] RE: Client time vs UTC Date: Fri, 6 Jun 2014 16:41:59 +0000 Done. Thanks! https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/890281/feature-request-make-client-local-time-the-default-for-deployments From: [email protected] [mailto:[email protected]] On Behalf Of Nash Pherson Sent: Friday, June 06, 2014 12:14 PM To: [email protected] Subject: [mssms] RE: Client time vs UTC If memory serves, some of the wizards that have Client / UTC time options will remember the last picked, but not most of them. If you were to write up a bug/feature request for this on Microsoft Connect, I’d definitely vote for it: http://myitforum.com/myitforumwp/2013/12/02/giving-feedback-on-microsoft-connect-for-configmgr-2012-help-yourself-help-the-community/ Nash From: [email protected] [mailto:[email protected]] On Behalf Of Beardsley, James Sent: Friday, June 6, 2014 10:42 AM To: [email protected] Subject: [mssms] Client time vs UTC Just had my first SCCM 2012 “Oh F” moment. The deployment time was set to 3:00 UTC instead local client time. Question… is there a way to set local client time as the default for all future deployments? I don’t know why UTC is the default… Thanks, James IRS Compliance: Any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties imposed under the Internal Revenue Code or applicable state or local tax law or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation. IRS Compliance: Any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties imposed under the Internal Revenue Code or applicable state or local tax law or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation.
