| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 964.1 | Do a logged inventory | SUBSYS::CARLETON | A paradigm shift without a clutch | Wed Mar 19 1997 13:58 | 17 |
|
There is a way to run the PC inventory so that it puts out more
diagnostic information as it inventories the system.
This is from memory, so I could be off on the details.
On the PC, open a DOS box and type:
S:\> SET SMSLS=1
S:\> RUNSMS.BAT
Where S: is the drive letter you have mapped to the SMS_SHR share
on your SMS server.
This should produce a line of output for each inventory section as
it is processed. You will then be able to see what inventory section
is causing the error.
|
| 964.2 | thank you | LEMAN::FOUCHAULT | Vous ici ! Quelle bonne surprise... | Thu Mar 20 1997 04:20 | 3 |
| thanks for your quick answer.
Remi
|
| 964.3 | another way | TPLAB::SMEKENS | Piet Smekens @BRO, 856-7964, SI-C Brussels | Thu Mar 20 1997 04:30 | 17 |
| There is another way of doing it too:
Again on the PC client, open a DOS-window and make a connection
to your SMS server:
net use X: \\yourSMSserver\SMS_SHR
x:
Cd X86.BIN
InvDos.Exe /F /V > C:\InvDos.Log
The INVDOS.EXE with /F for force inventory and /V for verbose, combined
with the "> C:\InvDos.Log" will place the output of the INVDOS.EXE program
in the INVDOS.LOG file, on the C:\ drive of you PC client.
Hope this helps too.
-Piet.
|
| 964.4 | I have the solution ! thanks | LEMAN::FOUCHAULT | Vous ici ! Quelle bonne surprise... | Mon Mar 24 1997 00:59 | 8 |
| Thank's for this answer.
In fact, after a try with the solution in .1, I tried invdos and found that
two file in \\mySMSserver\sms_shr was BAD.
So, thank you for your HELP :-)
R�mi
|