>>> If I do a "Put" to a WMI value that is tied to a registry value, does that Put command write the value to the registry?
It depends on the WMI provider implementation. It's quite possible for a WMI provider to do this, but it must explicitly support it. Cheers, Trevor Sullivan Microsoft PowerShell MVP <http://mms.mnscug.org/> From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Monday, August 4, 2014 9:55 AM To: [email protected] Subject: RE: [MDT-OSD] What writes to Deployment 4 registy? Mofcomp can write data to the registry? I thought Mofcomp can only copy data from the registry ---> WMI not the other way around. If I do a "Put" to a WMI value that is tied to a registry value, does that Put command write the value to the registry? From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Keith Garner (Hotmail) Sent: Friday, August 01, 2014 7:47 PM To: [email protected] <mailto:[email protected]> Subject: RE: [MDT-OSD] What writes to Deployment 4 registy? It's being written by the ZTITatoo.wsf file, through the ZTITatoo.mof file. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Friday, August 1, 2014 3:15 PM To: [email protected] <mailto:[email protected]> Subject: RE: [MDT-OSD] What writes to Deployment 4 registy? At the end of a deployment, my key has these values - so obviously something is populating them beyond what is evident in MDT scripts. I tried looking for the "Deployment 4" string in all the scripts too and came up empty - apart what you've shown below. Something is writing those values though. Maybe SCCM itself writes these values and not an MDT process? From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Keith Garner (Hotmail) Sent: Friday, August 01, 2014 4:52 PM To: [email protected] <mailto:[email protected]> Subject: RE: [MDT-OSD] What writes to Deployment 4 registy? Yup, looks like MDT 2012+ uses that location for some registry entries and the ZTITatoo.mof C:\DeploymentShare\Scripts>findstr /i /m /s /c:"Deployment 4" * WelcomeWiz_Initialize.vbs ZTITatoo.mof ZTIUtility.vbs C:\DeploymentShare\Scripts>findstr /i /s /c:"Deployment 4" *.vbs WelcomeWiz_Initialize.vbs: sPercent = oShell.RegRead("HKLM\Software\Microsoft\Deployment 4\ProgressPercent") WelcomeWiz_Initialize.vbs: sMessage = oShell.RegRead("HKLM\Software\Microsoft\Deployment 4\ProgressText") ZTIUtility.vbs: oShell.RegWrite "HKLM\Software\Microsoft\Deployment 4\ProgressPercent", iPercent, "REG_DWORD" ZTIUtility.vbs: oShell.RegWrite "HKLM\Software\Microsoft\Deployment 4\ProgressText", sMsg, "REG_SZ" From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Friday, August 1, 2014 2:36 PM To: [email protected] <mailto:[email protected]> Subject: [MDT-OSD] What writes to Deployment 4 registy? Does anyone know what MDT script writes to HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Deployment 4 ? This used to be done by ZTITatoo.wsf, but I don't it does that anymore. ZTITatoo.mof still appears to pull its data from there when it is compiled, and the data is still being written by some process. The reason I am asking is that I want to add a few extra values to the "Microsoft BDD Info" WMI class and I was previously doing that with a modified ZTITatoo.mof + adding a few regwrite calls to ZTITatoo.wsf. Now, there are no regwrite calls in ztiTatoo.wsf. I could write a new script to write the data into HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Deployment 4, but it has got me curious now to know where/what is writing the values to that reg key in MDT2013. Mystery. _____ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. _____ _____ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. _____ _____ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. _____
