Jaekt

I had the same problem once. What I did to solve it was: Remove the tick for command prompt, update bootimage, retick the command support, update bootimage.

Just thought I'd share some info I discovered. Recently found a bug in MDT version 8443 (can also be in earlier versions for all I know), integrated with SCCM. Noticed that the variable SMSDP would not set. The variable value of SMSDP turned blank after replacing older scriptfiles with the newest. To fix this you'll need to: 1. Edit the ZTIGather.wsf file with notepad or whatever 2. CTRL + F / search for SMSDP 3. This should bring you to line 1096 where you'll see: arrSMSDP = Split(oEnvironment.Item("_SMSTS" & oEnvironment.Item("_SMSTSBootImageID")),",") The line is supposed to be: arrSMSDP = Split(oEnvironment.Item("_SMSTSHTTP" & oEnvironment.Item("_SMSTSBootImageID")),",") 4. Update your MDT Script package Setting the correct variable to "_SMSTSHTTP" SMSDP was once again populated correctly. Hope this will be helpful.

Hi, Great guide as always, anyweb, however I have a couple of questions: 1. Can the normal "Add driver package" sequence be used in coordination with a WMI query, or do you have to use the "Download Package Content" for every driver model you want to support? 2. Does this support all Language packs installed, main or not? As I recall there was a bug in vNext (SCCM as a Service beta) it could only upgrade Win 10 en-US. I remeber I had to uninstall any language packs, upgrade, then reinstall a language pack, for it to work.. 3. After an upgrade, do all the default apps get reinstalled to default? F.ex. I do not want the app CandyCrush to be default for my Enterprise customers... does this get reinstalled after an upgrade?

Hello. Had some issues importing the MOF-file, saying "MOF file you tried to import could not be compiled... " with "SMS_Class_Template" was not found. After changing a few names, editing a bit in the MOF, it eventually compiled. Not sure what exactly caused it, but it worked in the end. I added this to configuration.mof: #pragma namespace ("\\\\.\\root\\cimv2") #pragma deleteclass("OSD", NOFAIL) [DYNPROPS] Class OSD { [key] string KeyName; String InstalledOn; String OSDBitLockerCreateRecoveryPassword; String OSDBitLockerMode; String OSDBitlockerStatus; String OSDComputerName; String OSDDomainName; String OSDDomainOUName; String OSDStateComplete; }; [DYNPROPS] Instance of OSD { KeyName="RegKeyToMOF_32"; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MPSD\\OSD|InstalledOn"),Dynamic,Provider("RegPropProv")] InstalledOn; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MPSD\\OSD|OSDBitLockerCreateRecoveryPassword"),Dynamic,Provider("RegPropProv")] OSDBitLockerCreateRecoveryPassword; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MPSD\\OSD|OSDBitLockerMode"),Dynamic,Provider("RegPropProv")] OSDBitLockerMode; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MPSD\\OSD|OSDBitlockerStatus"),Dynamic,Provider("RegPropProv")] OSDBitlockerStatus; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MPSD\\OSD|OSDComputerName"),Dynamic,Provider("RegPropProv")] OSDComputerName; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MPSD\\OSD|OSDDomainName"),Dynamic,Provider("RegPropProv")] OSDDomainName; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MPSD\\OSD|OSDDomainOUName"),Dynamic,Provider("RegPropProv")] OSDDomainOUName; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MPSD\\OSD|OSDStateComplete"),Dynamic,Provider("RegPropProv")] OSDStateComplete; }; The Report query: Select SYS.Netbios_Name0, OSD.InstalledOn0, OSD.OSDBitLockerStatus0, CS.UserName0, CS.Domain0 FROM v_R_System SYS right join v_GS_OSD OSD on SYS.ResourceID = OSD.ResourceID right join v_GS_COMPUTER_SYSTEM CS on SYS.ResourceID = CS.ResourceID where CS.domain0 LIKE @domain and CONVERT(datetime, OSD.InstalledOn0, 104) BETWEEN (GETDATE()-90) and GETDATE() order by CONVERT(datetime, OSD.InstalledOn0, 104) DESC Had to convert date since it was in a text-format.

Thanks again. Going to test your method, will report back with my results

Check the log %windir%\ccmsetup\logs\ccmsetup.log after a new installation. If the exit code (last line in the log) does not equal 0, client does not install properly.

Great article, thank you very much, Peter, and grats on the MVP well deserved I think then that relying on CMUUID/SMSUUID Change date is too unreliable then. Maybe the right solution to what I'm after is to use custom AD attributes, and pull reports from that. Guess I have to test some more.

Hi, I'm wondering what exactly the data Configuration Manager UUID Change Date means / how it updates. I was hoping I could use this data as when a client last was successfully installed a Operating System, with a Task Sequence. According to the technet-article below, answered by Quan xu and Jason Sandys, it does update whenever a computer is installed, but also when machine hardware is changed. https://social.technet.microsoft.com/Forums/systemcenter/en-US/706a2a4c-e4e9-4a0a-8c5f-787867540a09/report-or-a-query-to-show-new-computer-in-sccm I tested this on a Virtual Machine, but after changing both RAM and CPU cores, then running a Hardware Inventory, the UUID remains the same. Are there any other AD/SCCM attributes I can use for this purpose (with a date)?

Hi, Does anyone know where to pull info like an error from Windows Update? I want to make a SCCM-collection based on computers that get a specific error in Windows Update. Appreciate the help guys

Thanks for the reply, Eswar, unfortunately I do not know enough about WQL, SQL or Report Builder to go forth with the changes needed.

Hi, I'm looking to create a Report in SCCM 2012 R2. Trying to find a way to display all successfully installed computers for a specific domain, at a set date (ex. 01.01 to 30.03). It needs to exclude all failed task sequences and only show a MAC-address once (preferrably the active one). Also if possible, it would be great to show detail like: Computername, Domainname, MAC-address, Last logged on user, last logon date, Installdate / createdate Conclusion: the idea is to create a PDF of quarterly OS deployed computers. Anyone who could help me out here? Really appreciate the help

0x87D00324 = not detected after installation. The error isnt always right. Question: Did you select the deployment type as Script installer or msi? As far as i know, for detection method to function properly the requirement is to select "script installer" for .exe-files

What did you set as computername? Also is the prodct key correct?

Hi Jörgen, thanks for the reply. The SCCM 2012 Boundary Groups are not configured for Automatic Site Assignment. I did however find the reason. There was a migration configured earlier, where it was set to share DPs from old SCCM. By going to Administration -> Migration -> Source Hierarchy -> Rightclick old site (sccm 07 site) -> Configure -> Deselect "Enable distribution-point sharing for this source site". Dunno why it was set to share DPs, but its fixed now Thanks again!

Hi, I have 1 site thats running SCCM 2007 with IP ranged boundaries and a site with SCCM 2012 running on same IP ranged boundaries. The problem is that the SCCM 2012 site automatically creates boundary groups and boundaries of the old SCCM, pointing the clients to the wrong distribution points. Is there any fix for this, to avoid clients being pointed to the wrong DPs. I have tried setting deny read in AD, on the System Management container, for both SCCM server objects, but they are still created.