p.MsoNormal, li.MsoNormal, div.MsoNormal {margin-top:0in;margin-right:0in;margin-bottom:10.0pt;margin-left:0in;line-height:115%;font-size:11.0pt;font-family:'Calibri','sans-serif';} .MsoChpDefault {;} .MsoPapDefault {margin-bottom:10.0pt;line-height:115%;} @page Section1 {size:8.5in 11.0in;margin:1.0in 1.0in 1.0in 1.0in;} div.Section1 {page:Section1;} Does anyone know of a way to simulate futuristic times in AD? We have a Stratum NTP Server that our DC's point to, however we want to be able to set a few of our clients to future time periods, such as 2020. Is there a way to assign the clients to a separate OU that point to a DC with that year? Will it still sync with the other DC's with the correct time? Thanks in advance....

This is not an Exchange question but, simply stop windows time service on some of your clients and then set the clock to 2020 manually. By doing this you will break Kerberos since it is dependent on accurate clocks between client and server.

I quess that's where the concern comes in. We want the clients (windows and linux) to still be members of the domain and allow user access, however we need to simulate a future time period. Because it might be several hundred clients, I don't want to manually set each one.

Hi, I agree with Lasse. If you set one DC as NTP Server and change the time to certain future time, then NTP client will synch time with NTP server. However, NTP server will be stand-alone, it cannot replicate information with other DCs, etc. So I recommend you to set up another environment with NTP server and clients. If you need further help, then please use newsgroup for AD. Discussions in Active Directory http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=4107775&SiteID=17 Hope it helps. Xiu

Time Machineis software to assist with this http://www.solution-soft.com/timemachine.shtml Otherwise a seperate envorinment is needed. For example seperate AD and Exchange Server.