Re: Memory: By Slot



Enjoy that mof edit...took me 3 months to get it right lol

"Kim Oppalfens" <Kim dot Oppalfens@google mail.com> wrote in message
news:%23eBky3H1FHA.3856@xxxxxxxxxxxxxxxxxxxxxxx
> Yups,
>
> Clients will load new file at their next computer policy download &
> evaluation cycle.
> (Actually they don't load the file, the management point translates it
> into a wmi policy for them).
> At the hardware inventory after they received the policy the inventory
> should start flowing in.
>
> --
> Kim Oppalfens
> Telindus Belgium
> MVP Windows Server System - SMS
> "Jase" <jtwolfe@xxxxxxxxxxx> wrote in message
> news:Xns96F3CD2F0E48CJTWolfelittlercom@xxxxxxxxxxxxxxxx
>> Thanks for the info. This will be my first SMS_def.MOF update, so if you
>> wouldn't mind checking my steps and making sure I didn't miss anything,
>> I'd appreciate it:
>>
>> *) Add code block to x:\SMS\inboxes\clifiles.src\hinv\sms_def.mof (I
>> added it under the '#pragma namespace ("\\\\.\\root\\cimv2\\SMS")'
>> section)
>> *) Verify the file with mofcomp -check ..\sms_def.mof
>>
>> Shortly there after the file was backed up to x:\SMS\data\hinvarchive\ as
>> sms_def.mof.bak
>>
>> I don't see any further instructions in the operations guide (chapter 2)
>> - and as I understand it, the clients will load the new file and run a
>> new hardware inventory here pretty quick.
>>
>> All this sound right? Thanks again
>>
>>
>> "Jeff Gilbert" <jeff.gilbert@xxxxxxxxxxx> wrote in
>> news:#SKcM6E1FHA.1564@xxxxxxxxxxxxxxxxxxxx:
>>
>>> Add the below to your mof, run a hardware inventory and you will pick
>>> up the physical memory installed on a system and which slot it resides
>>> in:
>>>
>>> [ SMS_Report (TRUE),SMS_Group_Name ("Physical Memory"),SMS_Class_ID
>>> ("SMSExpert|Physical_Memory|1.0") ]
>>> class Win32_PhysicalMemory : SMS_Class_Template
>>> {
>>> [SMS_Report (TRUE)] string BankLabel;
>>> [SMS_Report (TRUE), SMS_Units("Megabytes")] uint64 Capacity;
>>> [SMS_Report (TRUE)] string Caption;
>>> [SMS_Report (TRUE)] string DeviceLocator[];
>>> [SMS_Report (TRUE)] uint16 FormFactor;
>>> [SMS_Report (TRUE)] string Manufacturer;
>>> [SMS_Report (TRUE)] uint16 MemoryType;
>>> [SMS_Report (TRUE)] uint32 PositionInRow;
>>> [SMS_Report (TRUE)] uint32 Speed;
>>> [SMS_Report (TRUE),Key] string Tag;
>>> [SMS_Report (TRUE),Key] string CreationClassName;
>>> };
>>
>>
>
>


.



Relevant Pages

  • Re: Memory: By Slot
    ... Clients will load new file at their next computer policy download & ... At the hardware inventory after they received the policy the inventory ...
    (microsoft.public.sms.inventory)
  • Re: Hardware Inventory does not work with XP (NO SP2)
    ... What's your download policy set to? ... inventory resync has not kicked-in. ... cycle" on your clients through the sms control panel applet. ... BTW do you have set your Hardware inventory cycle to 7 days? ...
    (microsoft.public.sms.inventory)
  • Re: Memory: By Slot
    ... wouldn't mind checking my steps and making sure I didn't miss anything, ... - and as I understand it, the clients will load the new file and run a ... new hardware inventory here pretty quick. ...
    (microsoft.public.sms.inventory)
  • Re: LSM conversion to static interface
    ... effective only after loading policy, ... as well first load a security module without making the system insecure. ... to have multiple "root" users with unique UIDs. ... Policy is dead simple since it is based on UIDs. ...
    (Linux-Kernel)
  • Re: iptables & tcp wrappers
    ... >> I've found it quite helpful to create a shell script to load the ... > The first lineshould define the default policy, ... The reason I chose to load allow rules, ... deny all as opposed to a deny policy is as for simplicity. ...
    (Focus-Linux)