Ivan, Wally Mead is doing a webinar on understanding RBA Sept 9th. I think it is free:
https://attendee.gotowebinar.com/register/7243753388218510081 I agree with April, RBA can probably do what you want. Wally is the most knowledgeable person on ConfigMgr, so you really should sign up for that webinar. On Wed, Sep 3, 2014 at 3:21 PM, April Cook <[email protected]> wrote: > Isn't this why RBA in ConfigMgr was introduced? > > > On Wed, Sep 3, 2014 at 12:39 PM, Lindenfeld, Ivan <[email protected] > > wrote: > >> I was crossing over into hourly rates for Jason so I think I’ll stop. >> I can’t afford him. >> >> >> >> Ivan >> >> >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Michael Mott >> *Sent:* Wednesday, September 03, 2014 12:22 PM >> *To:* [email protected] >> *Subject:* RE: [mssms] MOF import fails >> >> >> >> Grabbing some popcorn now >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Lindenfeld, Ivan >> *Sent:* Wednesday, September 03, 2014 12:17 PM >> *To:* [email protected] >> *Subject:* RE: [mssms] MOF import fails >> >> >> >> My primary goal (among many) is to prevent the existing site from >> installing clients on the new Primary and vice versa. We have a big >> problem preventing our site from assimilating clients in the same domain >> that are not managed by us. >> >> >> >> If administration has to happen on the CAS and not on the Primary then I >> have to do very specific things with role based admin at the CAS. >> >> >> >> One note: Since this new to us group of computers will live in the same >> domain and forest as our current primary I thought that two separate >> Primaries with no CAS COULD NOT work. What would the System Management >> container look like? >> >> >> >> I have a lot of thinking and learning to do, admittedly. >> >> >> >> Ivan >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Jason Sandys >> *Sent:* Wednesday, September 03, 2014 11:55 AM >> *To:* [email protected] >> *Subject:* RE: [mssms] MOF import fails >> >> >> >> Primaries don't provide any separation though in >> administration/management or even data since everything flows up to the CAS. >> >> >> >> J >> ------------------------------ >> >> *From:* [email protected] <[email protected]> >> on behalf of Lindenfeld, Ivan <[email protected]> >> *Sent:* Wednesday, September 3, 2014 10:36 AM >> *To:* [email protected] >> *Subject:* RE: [mssms] MOF import fails >> >> >> >> I was actually baiting you, Jason. J >> >> >> >> New Primary on different continent than the existing one. Different team >> managing that Primary and separation required for compliance reasons. The >> computers there will reside in the same domain as the computers in my >> existing, mature primary so to achieve the separation I want a separate >> primary. >> >> >> >> I know I haven’t satisfied all parameters for this implementation but so >> far this is it and it sets up a model for future integrations (M&A). >> >> >> >> Ivan >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Jason Sandys >> *Sent:* Wednesday, September 03, 2014 11:14 AM >> *To:* Sherry Kissinger; [email protected] >> *Subject:* RE: [mssms] MOF import fails >> >> >> >> OK, so most people know my disdain of CASes -- not so much that they >> don't work, but like so many things, folks simple don't know when they >> should and shouldn't be used. So I have to ask, why are you "planning" a >> CAS? >> >> >> >> J >> ------------------------------ >> >> *From:* [email protected] <[email protected]> >> on behalf of Lindenfeld, Ivan <[email protected]> >> *Sent:* Wednesday, September 3, 2014 9:43 AM >> *To:* Sherry Kissinger; [email protected] >> *Subject:* RE: [mssms] MOF import fails >> >> >> >> The thing is, I am doing it at the Primary. We have no CAS. We’re >> planning one, but have done nothing but talk. ;) >> >> >> >> Not at a console away from the Primary, but AT THE PRIMARY. >> >> >> >> Aha, I am not doing it at the default client settings, I am doing it at >> the custom client settings for our workstations. You probably just nailed >> my mistake. >> >> >> >> …verified. >> >> >> >> Thank you Sherry. >> >> >> >> Ivan >> >> >> >> >> >> *From:* Sherry Kissinger [mailto:[email protected] >> <[email protected]>] >> *Sent:* Tuesday, September 02, 2014 9:57 PM >> *To:* [email protected]; Lindenfeld, Ivan >> *Subject:* Re: [mssms] MOF import fails >> >> >> >> You are doing that import by... >> 1. You are at the cas, not a primary (if you have a cas) >> 2. You are importing by going to default client settings, properties.... >> Not trying to import into a custom client setting? >> >> I ask because in 1 of your pictures selections of what to import is >> greyed out... And that usually means your console isn't at the cas >> >> On September 2, 2014 3:51:55 PM CDT, "Lindenfeld, Ivan" < >> [email protected]> wrote: >> >> Hi folks. I throw myself humbly at your feets. I am trying to grab some >> registry data, the ZTITatoo from the MDT deployments. >> >> >> >> The error from the HINV import in the console client settings is “The >> following classes for which you are trying to import settings do not >> exist. Import the required class definitions and then try to import the >> settings again.” Screenshot attached as well. >> >> >> >> I also attached my RegKey2mof screenshot. >> >> >> >> I am using REgkey2MOF 3.1 with SCCM 2012 SP1. I generate the data in >> Regkey2MOF and copy the left tab to the Configuration.mof in the area >> between the >> >> //======================== >> >> // Added extensions start >> >> //======================== >> >> And >> >> //======================== >> >> // Added extensions end >> >> //======================== >> >> >> >> I see the dataldr.log recognize that the configuration.mof has changed >> and it recompiles it successfully. But it says >> ...no inventory schema changes found. SMS_INVENTORY_DATA_LOADER >> 9/2/2014 3:01:19 PM 1072 (0x0430) >> >> Four times and then processes MIFs. >> >> >> >> >> >> Here is the configuration.mof extension, the mof for import into the >> client settings is below that. >> >> >> >> // RegKeyToMOF by Mark Cochrane (thanks to Skissinger, Steverac, Jonas >> Hettich & Kent Agerlund) >> >> // this section tells the inventory agent what to collect >> >> // 9/2/2014 3:27:12 PM >> >> >> >> #pragma namespace ("\\\\.\\root\\cimv2") >> >> #pragma deleteclass("MDTTattooFNF", NOFAIL) >> >> [DYNPROPS] >> >> Class MDTTattooFNF >> >> { >> >> [key] string KeyName; >> >> String FNFDeploymentMethod; >> >> String FNFImageType; >> >> String FNFImageVersion; >> >> String CaptureMethod; >> >> String CaptureTaskSequenceID; >> >> String CaptureTaskSequenceName; >> >> String CaptureTaskSequenceVersion; >> >> String CaptureTimestamp; >> >> String CaptureToolkitVersion; >> >> Uint32 ProgressPercent; >> >> String ProgressText; >> >> }; >> >> >> >> [DYNPROPS] >> >> Instance of MDTTattooFNF >> >> { >> >> KeyName="RegKeyToMOF_32"; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|FNF Deployment Method"),Dynamic,Provider("RegPropProv")] >> FNFDeploymentMethod; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|FNF Image Type"),Dynamic,Provider("RegPropProv")] FNFImageType; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|FNF Image Version"),Dynamic,Provider("RegPropProv")] FNFImageVersion; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Method"),Dynamic,Provider("RegPropProv")] CaptureMethod; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Task Sequence ID"),Dynamic,Provider("RegPropProv")] >> CaptureTaskSequenceID; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Task Sequence Name"),Dynamic,Provider("RegPropProv")] >> CaptureTaskSequenceName; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Task Sequence Version"),Dynamic,Provider("RegPropProv")] >> CaptureTaskSequenceVersion; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Timestamp"),Dynamic,Provider("RegPropProv")] CaptureTimestamp; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Toolkit Version"),Dynamic,Provider("RegPropProv")] >> CaptureToolkitVersion; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|ProgressPercent"),Dynamic,Provider("RegPropProv")] ProgressPercent; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|ProgressText"),Dynamic,Provider("RegPropProv")] ProgressText; >> >> }; >> >> >> >> #pragma namespace ("\\\\.\\root\\cimv2") >> >> #pragma deleteclass("MDTTattooFNF_64", NOFAIL) >> >> [DYNPROPS] >> >> Class MDTTattooFNF_64 >> >> { >> >> [key] string KeyName; >> >> String FNFDeploymentMethod; >> >> String FNFImageType; >> >> String FNFImageVersion; >> >> String CaptureMethod; >> >> String CaptureTaskSequenceID; >> >> String CaptureTaskSequenceName; >> >> String CaptureTaskSequenceVersion; >> >> String CaptureTimestamp; >> >> String CaptureToolkitVersion; >> >> Uint32 ProgressPercent; >> >> String ProgressText; >> >> }; >> >> >> >> [DYNPROPS] >> >> Instance of MDTTattooFNF_64 >> >> { >> >> KeyName="RegKeyToMOF_64"; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|FNF Deployment Method"),Dynamic,Provider("RegPropProv")] >> FNFDeploymentMethod; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|FNF Image Type"),Dynamic,Provider("RegPropProv")] FNFImageType; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|FNF Image Version"),Dynamic,Provider("RegPropProv")] FNFImageVersion; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Method"),Dynamic,Provider("RegPropProv")] CaptureMethod; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Task Sequence ID"),Dynamic,Provider("RegPropProv")] >> CaptureTaskSequenceID; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Task Sequence Name"),Dynamic,Provider("RegPropProv")] >> CaptureTaskSequenceName; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Task Sequence Version"),Dynamic,Provider("RegPropProv")] >> CaptureTaskSequenceVersion; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Timestamp"),Dynamic,Provider("RegPropProv")] CaptureTimestamp; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|Capture Toolkit Version"),Dynamic,Provider("RegPropProv")] >> CaptureToolkitVersion; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|ProgressPercent"),Dynamic,Provider("RegPropProv")] ProgressPercent; >> >> [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Deployment >> 4|ProgressText"),Dynamic,Provider("RegPropProv")] ProgressText; >> >> }; >> >> >> >> ________________BREAK________________NEWFILE_______ >> >> >> >> // RegKeyToMOF by Mark Cochrane (thanks to Skissinger, Steverac, Jonas >> Hettich & Kent Agerlund) >> >> // this section tells the inventory agent what to report to the server >> >> // 9/2/2014 3:12:13 PM >> >> #pragma autorecover >> >> #pragma namespace ("\\\\.\\root\\cimv2\\SMS") >> >> #pragma deleteclass("MDTTattooFNF", NOFAIL) >> >> >> [SMS_Report(TRUE),SMS_Group_Name("MDTTattooFNF"),SMS_Class_ID("MDTTattooFNF"), >> >> SMS_Context_1("__ProviderArchitecture=32|uint32"), >> >> SMS_Context_2("__RequiredArchitecture=true|boolean")] >> >> Class MDTTattooFNF: SMS_Class_Template >> >> { >> >> [SMS_Report(TRUE),key] string KeyName; >> >> [SMS_Report(TRUE)] String FNFDeploymentMethod; >> >> [SMS_Report(TRUE)] String FNFImageType; >> >> [SMS_Report(TRUE)] String FNFImageVersion; >> >> [SMS_Report(TRUE)] String CaptureMethod; >> >> [SMS_Report(TRUE)] String CaptureTaskSequenceID; >> >> [SMS_Report(TRUE)] String CaptureTaskSequenceName; >> >> [SMS_Report(TRUE)] String CaptureTaskSequenceVersion; >> >> [SMS_Report(TRUE)] String CaptureTimestamp; >> >> [SMS_Report(TRUE)] String CaptureToolkitVersion; >> >> [SMS_Report(TRUE)] Uint32 ProgressPercent; >> >> [SMS_Report(TRUE)] String ProgressText; >> >> }; >> >> >> >> #pragma namespace ("\\\\.\\root\\cimv2\\SMS") >> >> #pragma deleteclass("MDTTattooFNF_64", NOFAIL) >> >> >> [SMS_Report(TRUE),SMS_Group_Name("MDTTattooFNF64"),SMS_Class_ID("MDTTattooFNF64"), >> >> SMS_Context_1("__ProviderArchitecture=64|uint32"), >> >> SMS_Context_2("__RequiredArchitecture=true|boolean")] >> >> Class MDTTattooFNF_64 : SMS_Class_Template >> >> { >> >> [SMS_Report(TRUE),key] string KeyName; >> >> [SMS_Report(TRUE)] String FNFDeploymentMethod; >> >> [SMS_Report(TRUE)] String FNFImageType; >> >> [SMS_Report(TRUE)] String FNFImageVersion; >> >> [SMS_Report(TRUE)] String CaptureMethod; >> >> [SMS_Report(TRUE)] String CaptureTaskSequenceID; >> >> [SMS_Report(TRUE)] String CaptureTaskSequenceName; >> >> [SMS_Report(TRUE)] String CaptureTaskSequenceVersion; >> >> [SMS_Report(TRUE)] String CaptureTimestamp; >> >> [SMS_Report(TRUE)] String CaptureToolkitVersion; >> >> [SMS_Report(TRUE)] Uint32 ProgressPercent; >> >> [SMS_Report(TRUE)] String ProgressText; >> >> }; >> >> >> >> >> >> >> >> I know this post is a mess, thanks for taking the time. >> >> >> >> Best, >> >> >> >> Ivan Lindenfeld >> >> Manager, Enterprise Deployment/SCCM >> >> Fidelity National Financial | Jacksonville, Florida >> >> [email protected] | 904 854 8178 >> >> >> >> >> ------------------------------ >> >> NOTICE: The information contained in this message is proprietary and/or >> confidential and may be privileged. If you are not the intended recipient >> of this communication, you are hereby notified to: (i) delete the message >> and all copies; (ii) do not disclose, distribute or use the message in any >> manner; and (iii) notify the sender immediately. >> >> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------ >> >> >> >> Legal Notice: This email is intended only for the person(s) to whom it is >> addressed. If you are not an intended recipient and have received this >> message in error, please notify the sender immediately by replying to this >> email or calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This >> email and any attachments may be privileged and/or confidential. The >> unauthorized use, disclosure, copying or printing of any information it >> contains is strictly prohibited. The opinions expressed in this email are >> those of the author and do not necessarily represent the views of 1E Ltd. >> Nothing in this email will operate to bind 1E to any order or other >> contract. >> >> >> >> > >
