You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A suggested update to the listed "Prerequisites" on the main page. Where "If you are using offline mode install the ADLDS role on a Windows Server edition in order to use dsamain.exe and mount the NTDS database. is listed based on my use of ADTimeline the OS version of the server being used for analysis needs to match the version of the server where the "ntds.dit" came from. If the ".dit" file(s) came from a Win2k8 server then the OS of the analysis server also needs to be Win2k8. Failure to do this will cause dsamain to be unable to mount the database. To test this I've used databases from every version of Windows Server from Windows 2000 - Windows 2022. The databases were only able to successfully mount when the OS versions matched. As a test, I took the kape collection that was provided via a SANs class and tried to run ADTimeline on the .dit file. Essentially, this is a server that I know nothing about and have NO credentials. Once I figured out what version the servers OS had been using the SOFTWARE registry hive and the "CurrentVersion" key information the DB mounted and ADTimeline worked perfectly.
It would be helpful to people who use your tool to have this little piece of info. This knowledge makes the difference between it working and not working.
The text was updated successfully, but these errors were encountered:
A suggested update to the listed "Prerequisites" on the main page. Where "If you are using offline mode install the ADLDS role on a Windows Server edition in order to use dsamain.exe and mount the NTDS database. is listed based on my use of ADTimeline the OS version of the server being used for analysis needs to match the version of the server where the "ntds.dit" came from. If the ".dit" file(s) came from a Win2k8 server then the OS of the analysis server also needs to be Win2k8. Failure to do this will cause dsamain to be unable to mount the database. To test this I've used databases from every version of Windows Server from Windows 2000 - Windows 2022. The databases were only able to successfully mount when the OS versions matched. As a test, I took the kape collection that was provided via a SANs class and tried to run ADTimeline on the .dit file. Essentially, this is a server that I know nothing about and have NO credentials. Once I figured out what version the servers OS had been using the SOFTWARE registry hive and the "CurrentVersion" key information the DB mounted and ADTimeline worked perfectly.
It would be helpful to people who use your tool to have this little piece of info. This knowledge makes the difference between it working and not working.
The text was updated successfully, but these errors were encountered: