Re: Mapped Drives SMS_DEF.MOF Issue

Hi,
you should be able to run this VBScript using SMS package, this program
should run under user's permission in order to retrieve the connect drive
based on user logon name, and then mofcomp the sms_def.mof.

Hope this work for you.

Hoan Le


"Garth" <Spam@xxxxxxx> wrote in message
news:OB$dk5lOHHA.3944@xxxxxxxxxxxxxxxxxxxxxxx
It depends on how the WS is locked down. I have seen cases where the users
can create mif files either as they have no access to anything under
%windir% directory, so in each case it mean testing things out.

"Bruno" <Bruno@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:56F63B89-F668-4C57-B019-B31A7D876E65@xxxxxxxxxxxxxxxx
You are right, but i am not sure that a standard user without local admin
rights can write to wmi. Let me know if i am wrong as I am not sure.

"Garth" wrote:

Once the data is within WMI there is no need to use a NOIDMif, plus MIFs
take a lot longer to process vs using WMI.

"Bruno" <Bruno@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:51F87C60-9DEB-4AEA-B7E3-4487C7F69511@xxxxxxxxxxxxxxxx
Hi
I think that the problem is that drives (like printers) are mounted by
the
user, so the local system account with which the inventory process
runs
has
no access to those. You should try to run the script as user, creating
a
NOIDMif file that will be taken into account by the next inventory
(check
that you upload noidmifs),
Brgds
bruno

"BDA" wrote:

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
    ... I'm thinking the issue is that the hardware inventory is running under ... system account then you will not get any map network drives. ... string DeviceID; ...
    (microsoft.public.sms.inventory)
Loading