Turns out all I had done wrong was forced my full inventory before the clients had picked up the new mof.
If anyone is interested in doing what I did.... Simply remove the bdd hardware inventory class, wait until the view and table are gone from SQL. Take the sample mof file that's posted many places online<http://www.chrisnackers.com/2009/12/04/microsoft-deployment-toolkit-tattoo-information/> and change string DeploymentTimeStamp to datetime DeploymentTimeStamp then reimport this mof as a hardware inventory class. Wait long enough for the clients to have picked up the new mof then Force a full hardware inventory and the data will now be in datetime format in your database. ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Monday, February 15, 2016 10:31 AM To: [email protected] Subject: [MDT-OSD] Tattoo Question In all the mof edits people use to collect the MDT tattoo they define the deployment time as a string value which means it ends up as an nvarchar in the database. Reporting on this would be much easier if it were datetime in the database. When I look at the deploymenttime in WMI on a client PC it is a datetime value. I tried changing the mof from string to datetime but now all of the deploymenttime values in the database are NULL. Any idea how to make this work so that the string value in the database doesn't have to be converted to datetime? [SMS_Report (TRUE) ] string DeploymentTimeStamp; [SMS_Report (TRUE) ] datetime DeploymentTimeStamp; ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
