HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- RDP - Setting initial date & time on ProLiants (pr...
ProLiant Deployment and Provisioning
1839310
Members
2749
Online
110138
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2010 02:26 AM
04-01-2010 02:26 AM
RDP - Setting initial date & time on ProLiants (probably work with others...)
Not a question, but spent loads of time figuring it out so sharing the love!
Using ALtiris RDP to provision new servers, I use logging extensively, a lot of which date/time stamps actions that are taken. It's not unusual for the date & time to be a fair way out if the boxes have been sitting in a store room for months.
A second problem (for windows at least) is if the BIOS date/time stamp is out by too much, when the server is joined to a domain or Windows Time is configured to sync with any other time source (e.g. NTP), it will fail to sync.
To get accurate time stamping in logs, and resolve the time sync issue, the very first job I now run is an RDP task that uses Altiris tokens in a WinPE boot environment to 'initialise' the date & time which works a treat. The WLogEvent lines print output to the status detail of the job so you've also got a documented result of what it's done:
**********
REM Sync initial date and time to RDP server
WLogevent -c:0 -l:1 -ss:"Date will be set to: %DATE%"
date %DATE%
WLogevent -c:0 -l:1 -ss:"Time will be set to: %TIME%"
time %TIME%
**********
Using ALtiris RDP to provision new servers, I use logging extensively, a lot of which date/time stamps actions that are taken. It's not unusual for the date & time to be a fair way out if the boxes have been sitting in a store room for months.
A second problem (for windows at least) is if the BIOS date/time stamp is out by too much, when the server is joined to a domain or Windows Time is configured to sync with any other time source (e.g. NTP), it will fail to sync.
To get accurate time stamping in logs, and resolve the time sync issue, the very first job I now run is an RDP task that uses Altiris tokens in a WinPE boot environment to 'initialise' the date & time which works a treat. The WLogEvent lines print output to the status detail of the job so you've also got a documented result of what it's done:
**********
REM Sync initial date and time to RDP server
WLogevent -c:0 -l:1 -ss:"Date will be set to: %DATE%"
date %DATE%
WLogevent -c:0 -l:1 -ss:"Time will be set to: %TIME%"
time %TIME%
**********
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP