![]() ![]() ![]() ( ( 50 ) NOT NULL, ( 50 ) NOT NULL )Īnd using the data from (Windows 10 release information), I added the data thusly: ![]() It’s not readily available in SCCM, so I created a table in a secondary database:ĬREATE TABLE. This wasn’t satisfactory, and they were actually looking for the complete version/build, like shown in the ver command: I added it to the report and sent the link to the requestor: Easy enough, I could use the Version0 column in v_gs_operating_system. I was asked to add the build version to my simplified deployment report. ![]() THE FOLLWING IS OLD INFORMATION, NO LONGER RELEVANT. Inner join CM_10BuildVersion v on s.Build01 like '%' + v.OSBuild Then I just query the version with the following: select distinct v.Version + ' - ' + s.BuildExt VersionBuild from v_R_System s The only thing now I have is a OSBuild Version table to match the five digit build to the four digit version: Please see ĮDIT – The KB match to find the full build is no longer necessary, since the BuildExt field is in v_r_system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |