Re: Mapped Drives SMS_DEF.MOF Issue

Garth:

I've been watching those logs. Nothing in dataldr.log, there are some
errors related to another set of Inventory I'm grabbing using the
sms_def.mof file, but no errors on any later sections including the
mapped drives.

I'm thinking the issue is that the hardware inventory is running under
the system account and therefore doesn't see the same data in WMI that
I see when I run under my account.

I'm continuing to test...


Garth wrote:
Force an inventory cycle to occur on the WS and look at the log files.
Check the InventoryAgent.log on the client to see if there are any errors?
Are there any errors within the Dataldr.log?



"BDA" <ba@xxxxxxxxxxxx> wrote in message
news:1168982319.754492.139120@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Yes Garth it did return ALL of my drives.
Thanks for your help...


Garth wrote:
Have you use Wbemtest to check the results on the local PC?

To do so.

Start| Run | Wbemtest

click Connect
Change to root\cimv2 click connect.

select "enum classes" then "recursive" then ok.

Find SMX_Drives and double click it.

click Instances

Do you see all you mapped drivers?



"BDA" <ba@xxxxxxxxxxxx> wrote in message
news:1168976211.124181.176770@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Actually, it was run under my admin user account on the test machine in
question. i.e., it was run manually and not from an SMS package.



Garth wrote:
Which account is executing the datashift-drives.vbs? If it is the
local
system account then you will not get any map network drives.




"BDA" <ba@xxxxxxxxxxxx> wrote in message
news:1168971601.565794.48030@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I'm attempting to collect the mapped network drives of my SMS
Advanced
Clients in our SMS 2003 environment.

I'm working with the Datashift-Drives.vbs. I've added the following
to
my SMS_DEF.MOF file to collect this information from the test
client:

*************


//----------------------
// Mapped Drive Inventory
//----------------------

#pragma namespace("\\\\.\\root\\cimv2\\SMS")
[SMS_Report(TRUE),
SMS_Group_Name("SMX Drives"),
SMS_Class_ID("MICROSOFT|SMXDrives|1.0")]

class SMX_Drives : SMS_Class_Template
{
[SMS_Report(TRUE)]
Boolean Compressed;

[SMS_Report(TRUE)]
string Description;

[SMS_Report(TRUE)]
string DeviceID;

[SMS_Report(TRUE)]
Uint32 DriveType;

[SMS_Report(TRUE)]
string FileSystem;

[SMS_Report(TRUE)]
Uint64 FreeSpace;

[SMS_Report(TRUE)]
Uint32 MediaType;

[SMS_Report(TRUE), Key]
string Name;

[SMS_Report(TRUE)]
string ProviderName;

[SMS_Report(TRUE)]
Uint64 Size;

[SMS_Report(TRUE)]
string VolumeName;

[SMS_Report(TRUE)]
string VolumeSerialNumber;
};

This all appears to work in the Hardware Inventory process when I
force
a Hardware Inventory at the client level, however the only drive
displayed is my CD-ROM. Is this the intended behavior of the script
or
is it to also to list out my mapped network drives (e.g. my Y: & Z
drives are mapped). I was also concerned about the hardware
inventory
being executed via the system account vs. the logged on account.
Any
help you could give me would be appreciated.




.

Relevant Pages

  • Re: Mapped Drives SMS_DEF.MOF Issue
    ... I think that the problem is that drives are mounted by ... NOIDMif file that will be taken into account by the next inventory ... system account then you will not get any map network drives. ... string DeviceID; ...
    (microsoft.public.sms.inventory)
  • Re: Mapped Drives SMS_DEF.MOF Issue
    ... I think that the problem is that drives are mounted by the ... NOIDMif file that will be taken into account by the next inventory (check ... system account then you will not get any map network drives. ... string DeviceID; ...
    (microsoft.public.sms.inventory)
  • Re: Mapped Drives SMS_DEF.MOF Issue
    ... I think that the problem is that drives are mounted by the ... NOIDMif file that will be taken into account by the next inventory (check ... system account then you will not get any map network drives. ... string DeviceID; ...
    (microsoft.public.sms.inventory)
  • Re: Mapped Drives SMS_DEF.MOF Issue
    ... I think that the problem is that drives are mounted by the ... NOIDMif file that will be taken into account by the next inventory (check ... system account then you will not get any map network drives. ... string DeviceID; ...
    (microsoft.public.sms.inventory)
  • Re: Mapped Drives SMS_DEF.MOF Issue
    ... system account then you will not get any map network drives. ... string DeviceID; ... This all appears to work in the Hardware Inventory process when I ...
    (microsoft.public.sms.inventory)
Loading