Scripting

Functionality-wise, I can't tell why the file might be being ignored: I'm remote at the moment and have no means to test.

(sorry this is my first script and if I didn't do it correctly, please feel free to comment).  My comment would, as ever, be that, in common with many beginners, you have ZERO error-trapping. In any programming, you shoudl always, ALWAYS assume that nothing will work.

For example, every time you create an object - no matter if it's the most basic/common object (e.g. FileSystemObject) - your code should check that the object was, in fact, created. If the code creates a file (e.g. a log file), did the file get written? You get the idea...

Also, when using an object a lot, try and get into the habit of specifying it once to save the engine having to go back and refer to its pointer each time by using the 'With...End With' construct. So, instead ofmifFile.Writeline ("START COMPONENT")
mifFile.Writeline ("NAME = ""WORKSTATION""")
mifFile.Writeline (" START GROUP")
'// and so on and so on and so on...you have:With mifFile
.Writeline ("START COMPONENT")
.Writeline ("NAME = ""WORKSTATION""")
.Writeline (" START GROUP")
End With

Next, use time-savers. NotLogToFile " ---------------------------------------------------------------- " but LogToFile String(33, "-")


Lastly, remember (what purports to be) garbage collection:Set miffile = Nothing and similar for all objects your script creates.

Have you set up the status mif as the target in the Package itself yet? I also assume you've checked for the mif and verified that it's populated and formatted properly. I haven't used SCCM extensively (still stuck with SMS 2003) but that's the very first thing that has to be done to get Mif's to report correctly.

ORIGINAL: Jsaylor

Have you set up the status mif as the target in the Package itself yet? I also assume you've checked for the mif and verified that it's populated and formatted properly. I haven't used SCCM extensively (still stuck with SMS 2003) but that's the very first thing that has to be done to get Mif's to report correctly.


Yes I have. I have setup the package to use the mif file for reporting. The mif file was created and populated correctly and I've checked the format which was created by SMS Installer and they are the same. Problem is that when I used SMS Installer to run the program and report the status with Mif and Package is setup to use mif reporting, it worked fine. Therefore, I am suspecting the script ran but the SCCM is picking up the status of the execution but not the mif reporting.

Hey Thanks VBScab. Your comments are noted.

I can tell you exactly why it doesn't work: http://www.mombu.com/microsoft/sms-admin/t-create-custom-mif-using-vbscript-429194.html

The problem was that my MIF contained blank
fields.

Example: VALUE = ""

Apparently this is a no-no but not documented ANYWHERE. Under normal
circumstances you would not have this problem as MIF generators (such
as the ISMIFCOM.dll included with the SMS 2003 SDK) replace blank
values that are passed with something like ""x\*\*\*x\*\*\*\*\*\*".
Given that I am trying to create my MIF using the OpenTextFile
function in VBSCript I was missing that one bit of information.


Hope this helps!

hey, packagedude. Thanks for the advice.

I replace the blanks with the follwing..
.Writeline (" START ATTRIBUTE")
.Writeline (" NAME = ""Locale""")
.Writeline (" ID = 4")
.Writeline (" ACCESS = READ-ONLY")
.Writeline (" STORAGE = SPECIFIC")
.Writeline (" TYPE = STRING(16)")
.Writeline (" VALUE = ""NIL""")

I am still getting the same result.

Looking at the execmgr.log
It shows:

Raised Program Started Event for Ad:C0120BA6, Package:C0100360, Program: runmiftest
Program exit code 0
Looking for MIF file to get program status
Script for Package:C0100360, Program: runmiftest succeeded with exit code 0

If it works, it will say something time Mif File Found or something like that if I recall.


The mif was created on c:\temp\miftest.mif
and I've configure the package to look for the miftest.mif

Same results.

ahcash,

Did you ever figure this out? I am running into the same situation where the package status mif is not being reported in SCCM. (The exact same program in SMS 2003 works fine...the mif status is sent back and I see this in the report.)

However, the package does not work in SCCM. The program runs fine..but the mif status is never reported. The MIF file is left in the C:\windows\temp directory.

This is working fine for me in SCCM. I have made a little bit changes in the script. Functionality wise, only change is that MIF file will be created in Windows directory.

SCCM is not picking the MIF file from Temp directory while it is picking the same from Windows directory.Don't know the reson behind this. Anyway this script serve my purpose.

Please see the below link for more details.

http://equebalahmad.blogspot.com/2010/11/sccm-deployment-generating-mif-file_28.html


Thanks

Hello

Can somone give me script to create the package and installation program name in SCCM 2007.Thanks in advance..!!

HI All,
I m new to SCCM, In my case i ve other issue, few clients are not generating MIF file, if i copy them manually it gets deleted.
Scenario Overview

Advertisement pushes definitation update package for MSFCS. with two scripts , one delpoys latest definiation, other updates the registry and MIF value.

Client server communication works fine, i ve tried reinstalling SCCM client, no luck .please help me to get this resolve as it is affecting my compliance report.