Archived from groups: microsoft.public.win2000.setup (More info?)
I am not sure if this works after backup-restore:
looking into Windows\repair directory. Files in that dir may contain the
install date.
--
Mike J. Deakins
"Satheesh Kiran" <anonymous@discussions.microsoft.com> wrote in message
news:695001c493f1$5fbfe730$a501280a@phx.gbl...
>
> We are having around 15 windows 2000 servers installed
> long back. Is it possible to find out when exactly, like
> which date the OS has been installed.
>
> Thanks in Advance
> Satheesh Kiran
Archived from groups: microsoft.public.win2000.setup (More info?)
"Satheesh Kiran" <anonymous@discussions.microsoft.com> wrote in message
news:695001c493f1$5fbfe730$a501280a@phx.gbl...
>
> We are having around 15 windows 2000 servers installed
> long back. Is it possible to find out when exactly, like
> which date the OS has been installed.
Try 'systeminfo' from a command prompt, or 'netsh diag show os /v', or
'srvinfo', or 'psinfo', or Aida32.
I believe they all get it from
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\InstallDate
Or look at the date stamp for %systemdrive%\ntldr (or
%systemroot%\PCHEALTH\HELPCTR\ under >NT5.0).
Archived from groups: microsoft.public.win2000.setup (More info?)
I am unable to run the below commands in windows 2000
server OS. In XP OS systeminfo is working and its showing
me the install date.
Even the registry in windows 2000 server OS doesn't
contain the install date information.
please let me know if any alternate method is available
Regards
Kiran
>-----Original Message-----
>"Satheesh Kiran" <anonymous@discussions.microsoft.com>
wrote in message
>news:695001c493f1$5fbfe730$a501280a@phx.gbl...
>>
>> We are having around 15 windows 2000 servers installed
>> long back. Is it possible to find out when exactly,
like
>> which date the OS has been installed.
>
>Try 'systeminfo' from a command prompt, or 'netsh diag
show os /v', or
>'srvinfo', or 'psinfo', or Aida32.
>
>I believe they all get it from
>HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\InstallDate
>
>Or look at the date stamp for %systemdrive%\ntldr (or
>%systemroot%\PCHEALTH\HELPCTR\ under >NT5.0).
>
>--
>Michael Bednarek http://mbednarek.com/ "POST NO
BILLS"
>.
>
>please let me know if any alternate method is available
Try the date stamp on "%systemdrive%\System Volume Information".
>>-----Original Message-----
>>"Satheesh Kiran" <anonymous@discussions.microsoft.com>
>wrote in message
>>news:695001c493f1$5fbfe730$a501280a@phx.gbl...
>>>
>>> We are having around 15 windows 2000 servers installed
>>> long back. Is it possible to find out when exactly, like
>>> which date the OS has been installed.
>>
>>Try 'systeminfo' from a command prompt, or 'netsh diag show os /v', or
>>'srvinfo', or 'psinfo', or Aida32.
>>
>>I believe they all get it from
>>HKLM\SOFTWARE\Microsoft\Windows
>NT\CurrentVersion\InstallDate
>>
>>Or look at the date stamp for %systemdrive%\ntldr (or
>>%systemroot%\PCHEALTH\HELPCTR\ under >NT5.0).
Archived from groups: microsoft.public.win2000.setup (More info?)
Look in c:\winnt for setupapi.log this is the history of your computer and
by default all OS modifications and Hardware installations are appended
here. Its a txt file that begins recording when she's born; just look at
the first recorded date in the top of the file.
Good Luck
Elijah Landreth [MSFT]
Microsoft Server Setup Team
NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of
Microsoft.
or opinions of Microsoft.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.