Search the Community

We are migrating to Windows 10 in the summer... I am looking to package VLC for Win10 right now. My install script works fine and SCCM will install silently. I just need an uninstall cmd line... but I cannot find the GUID. It doesn't exist in the 7/8.1 location... I searched "VLC" and "VideoLan" in the registry and cannot find out where these entries are stored for new software installs. Thanks for any help!

So here's the deal...when PXE booting a workstation it displays the MAC and the SMS BIOS GUID-- which I've used before to import a workstation, though usually we just boot workstations as Unknown and deploy an OS through the Unknown Computers collection--but when trying to image this one particular workstation, we noted that it simply kept restarting itself after running the pre-execution hook. Taking a look at the logs revealed that when it begins the identity request, that it is logging a different SMS BIOS GUID than what is displayed when we first PXE boot. This then resolves to a different NetBIOS name (even though the MAC address is logged correctly), which is how I first noticed that the SMS BIOS GUID was wrong. For example, what is seen in SMSTS.log: Preparing Client Identity Request. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) Setting transport. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) Setting SourceID = d25404f6-c37b-4ee8-91c0-c0b6aeaa4cf4. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) Setting site code = ###. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) Setting SMBIOS GUID = 4C4C4544-0000-2010-8020-80C04F202020. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) Adding MAC Address 00:19:B9:24:65:5A. TSPxe 9/10/2012 2:50:33 PM 1220 (0x04C4) So here are how the SMS BIOS GUID's are being reported for the same workstation: 4C4C4544-0000-2010-8020-80C04F202020 <-- SMSTS log file 44454C4C-0000-1020-8020-80C04F202020 <-- pxe boot initialization You can note that they are nearly identical, with the first and third sections pretty much being the reverse of each other. All of my site system and component statuses are fine...no errors there (with the exception of an AD discovery error). On top of this, we had a workstation accidentally get imaged a couple weeks ago due to a duplicate reported MAC address. Interestingly enough, if you checked the MAC address on the workstation then it would give you the correct information, but the DDR client properties in SCCM listed the incorrect MAC. I ran the duplicate MAC address report and found a couple entries listed, and just ended up deleting them at the time (figuring that they would get added back with their correct MAC's, which they have thus far). The issue in this case though is that the client wasn't reporting the correct value back to SCCM (which was obviously not duplicated based on ipconfig /all command from the "supposedly" conflicting workstations)...which is similar to what's happening here with the PXE booting and the SMS BIOS GUID. So all that being said, has anyone else run into this problem or have any ideas on a solution? Please let me know if I can provide further information! Thanks!