I had initially hoped that everything could be done without any compiled code, and with the PowerShell script published in 2013 by Ingmar Verheij, I thought I was in luck. There are DHCP APIs available to help with that, but they aren’t particularly PowerShell-friendly (or even C#-friendly). The challenge then is to get the client to use them. That’s all it takes for the value to be delivered to the client. For example, I would use value “America/Los_Angeles” for the Pacific time zone, or “America/Chicago” for the Central time zone. I prefer the TCode (option 101) values because they are more user-friendly you can find a list of those on the IANA web site. Then you can add the values to the DHCP scopes. You can add these by right-clicking on the IPv4 node in the DHCP admin tool, choosing “Set predefined options…”:Īnd fill in the needed details for both options: That’s pretty simple to do, as you just need to add the option 100 (PCode) and 101 (TCode) definitions to the DHCP server. The first challenge is adding the needed options to a Windows Server DHCP server. But that doesn’t mean it can’t be used – it just requires some extra work. As I mentioned in the preview blog, RFC 4833 describes a mechanism that delivers time zone information via DHCP, but Windows 10 doesn’t include a mechanism for automatically consuming this information.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |