FBA Command

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to run an VBS Script using the FBA command - i tried the exampe in Sean Limings book - that works - but that uses a Minlogon and a Task Manager shell. When I try to do the same thing with Windows logon and the Explorer shell - the script does not execute. My question - does the FBA command work if you use Winlogon and the Explorer shell? If yes, then can somebody guide me to some resource to get it to work
KS
 
KS,

Yes, FBA commands certainly work on Winlogon based images.
I don't know what exactly command you are trying but be aware about the bug with WSH engine on XPe. Use Hotfix Q824704.

http://groups.google.com/groups?hl=...=1&[email protected]

--
Regards,
KM, BSquare Corp.

I am trying to run an VBS Script using the FBA command - i tried the exampe in Sean Limings book - that works - but that uses a
Click to expand...
Minlogon and a Task Manager shell. When I try to do the same thing with Windows logon and the Explorer shell - the script does not
execute. My question - does the FBA command work if you use Winlogon and the Explorer shell? If yes, then can somebody guide me to
some resource to get it to work
 
This is what I am doing: Two things:

1 I have a VB Script which reads System Name from the BIOS using the WMI object W32_ComputerSystem. I am trying to run this using the FBA Command. It did not work

2 I tried using my EXE program which basically reads the Type 0 data from BIOS and displays - I was trying to execute this EXE using FBA command and that too did not work
Basically I have a DMI.EXE file - which i put in root and created a FBA command to execute this exe.

KS
 
KS,

What System Name from the BIOS you meant?

To know where XP keeps the machine name, read this thread:
http://groups.google.com/groups?hl=...=1&selm=#[email protected]

--
Regards,
KM, BSquare Corp.

This is what I am doing: Two things:

1 I have a VB Script which reads System Name from the BIOS using the WMI object W32_ComputerSystem. I am trying to run this
Click to expand...
using the FBA Command. It did not work
2 I tried using my EXE program which basically reads the Type 0 data from BIOS and displays - I was trying to execute this EXE
Click to expand...
using FBA command and that too did not work
 
KS,

This is not BIOS computer name but just OS machine name (the same as I mentioned earlier).

QFE: http://www.microsoft.com/downloads/...e7-a2d9-4e75-b6ba-9570653f0891&displaylang=en

I don't know about your script but first try to change the computer name in the registry (the values I mentioned in the previous
post to this thread). If it works for you but the script doesn't, you may switch to a simpler script that basically just updates the
registry values and reboot.
 
Yes I understand -- I am just trying to run this script to prove the FBA Command execution - which I have not been successful - as yet. I have created a component just like the Message1 component in Sean Limings book - and have created a configuration using the Winlogon Sample Macro and add this component. The script does not execute in second boot - that is what i want to do first. Then I have a code that reads Type 1 information - I want to use that to continue install only if i read a certain string in the SMBIOS.

Can you lead me to some resource that will give me some direction on doing this?
Thanks for all the information you provided I am now going to try with the QFE for Wscript.exe
 
KS,

I am sorry. I have not read the Sean's book (which is very good as I heard) so I can not understand "the Message1 component" and
"Type 1 information" terms.
If you want, you can describe what you did to create the command (or port the SLD file here).

I am not sure how you set up the script launch command but I hope it is implemented through a FBA Generic Command.
XPe docs are what I'd suggest you to look at:
http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconFBAGenericCommand.asp

Use reg.exe or regedit.exe to change the registry values.

--
Regards,
KM, BSquare Corp.

Yes I understand -- I am just trying to run this script to prove the FBA Command execution - which I have not been successful - as
Click to expand...
yet. I have created a component just like the Message1 component in Sean Limings book - and have created a configuration using the
Winlogon Sample Macro and add this component. The script does not execute in second boot - that is what i want to do first. Then I
have a code that reads Type 1 information - I want to use that to continue install only if i read a certain string in the SMBIOS.
Can you lead me to some resource that will give me some direction on doing this?
Thanks for all the information you provided I am now going to try with the QFE for Wscript.exe
Click to expand...
Minlogon and a Task Manager shell. When I try to do the same thing with Windows logon and the Explorer shell - the script does not
execute. My question - does the FBA command work if you use Winlogon and the Explorer shell? If yes, then can somebody guide me to
some resource to get it to work
 
Firstly, Thank you for your patience.

This is the sld file

<?xml version="1.0" encoding="UTF-16"?>
<!DOCTYPE DCARRIER SYSTEM "Mantis.DTD">

<DCARRIER
CarrierRevision="1"
DTDRevision="16"
<TASKS
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PLATFORMS
Context="1"

<REPOSITORIES
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"
<REPOSITORY
RepositoryVSGUID="{91FEFFAE-A147-407C-8706-EEAF05787DA8}"
Revision="4"
BuildType="16"
Context="1"
PlatformGUID="{B784E719-C196-4DDB-B358-D9254426C38D}"
<SRCPATH>.\WMIVBSFile</SRCPATH>

<PROPERTIES
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"
</PROPERTIES>
Click to expand...

<DISPLAYNAME>WMIRepository</DISPLAYNAME>

<VERSION>1.0</VERSION>

<DATECREATED>8/4/2004 9:22:21 PM</DATECREATED>

<DATEREVISED>8/4/2004 9:30:07 PM</DATEREVISED>
</REPOSITORY>
</REPOSITORIES>

<GROUPS
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"
</GROUPS>
<COMPONENTS
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"
<COMPONENT
ComponentVSGUID="{C9FFEA83-8990-49C0-83D6-7BA3A9971EDC}"
ComponentVIGUID="{8DC401E8-CB3B-4888-A95D-B1B64075B677}"
Revision="14"
RepositoryVSGUID="{91FEFFAE-A147-407C-8706-EEAF05787DA8}"
Visibility="1000"
MultiInstance="False"
Released="True"
Editable="False"
HTMLFinal="False"
IsMacro="False"
Opaque="False"
Context="1"
PlatformGUID="{B784E719-C196-4DDB-B358-D9254426C38D}"
<PROPERTIES
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<RESOURCES
Context="1"
PlatformGUID="{B784E719-C196-4DDB-B358-D9254426C38D}"
<RESOURCE
Name="File(819):"%11%","wmivbs.vbs""
ResTypeVSGUID="{E66B49F6-4A35-4246-87E8-5C1A468315B5}"
BuildTypeMask="819"
BuildOrder="1000"
Localize="False"
Disabled="False"
Context="1"
PlatformGUID="{B784E719-C196-4DDB-B358-D9254426C38D}"
<PROPERTIES
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"
<PROPERTY
Name="ComponentVSGUID"
Format="GUID"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="DstName"
Format="String"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="DstPath"
Format="String"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="NoExpand"
Format="Boolean"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="Overwrite"
Format="Boolean"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="SrcFileCRC"
Format="Integer"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="SrcFileSize"
Format="Integer"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="SrcName"
Format="String"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="SrcPath"
Format="String"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"
</PROPERTIES>

<DISPLAYNAME>wmivbs.vbs</DISPLAYNAME>

<DESCRIPTION></DESCRIPTION>
</RESOURCE>

<RESOURCE
Name="FBGenCmd(819):"d:\windows\system32\wscript.exe","d:\windows\system32\wmivbs.vbs""
ResTypeVSGUID="{FB2B6E76-FCD6-4D60-85D5-83C17D853AE3}"
BuildTypeMask="819"
BuildOrder="1000"
Localize="False"
Disabled="False"
Context="1"
PlatformGUID="{B784E719-C196-4DDB-B358-D9254426C38D}"
<PROPERTIES
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"
<PROPERTY
Name="Arguments"
Format="String"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="ComponentVSGUID"
Format="GUID"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="ErrorControl"
Format="Integer"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="FilePath"
Format="String"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="Flags"
Format="Integer"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="Phase"
Format="Integer"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="Reboot"
Format="Boolean"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="Start"
Format="Integer"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="Timeout"
Format="Integer"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"

<PROPERTY
Name="Type"
Format="Integer"
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"
1</PROPERTY>
Click to expand...
</PROPERTIES>

<DISPLAYNAME>FBA Generic Command</DISPLAYNAME>

<DESCRIPTION></DESCRIPTION>
</RESOURCE>
</RESOURCES>

<GROUPMEMBERS
<GROUPMEMBER
GroupVSGUID="{B906A849-E301-4A85-8AAB-E7BD131B322E}"
</GROUPMEMBERS>

<DEPENDENCIES
Context="1"
PlatformGUID="{B784E719-C196-4DDB-B358-D9254426C38D}"
<DEPENDENCY
Class="Include"
Type="All"
DependOnGUID="{629F38BE-328D-4915-BAAF-4F6DA282D5A2}"
MinRevision="0"
Disabled="False"
Context="1"
PlatformGUID="{B784E719-C196-4DDB-B358-D9254426C38D}"
<PROPERTIES
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"
</PROPERTIES>
Click to expand...

<DISPLAYNAME>Run WMI Script depends on Windows Script Engines - Hotfix Q318089</DISPLAYNAME>

<DESCRIPTION></DESCRIPTION>
</DEPENDENCY>
</DEPENDENCIES>

<DISPLAYNAME>Run WMI Script - KS</DISPLAYNAME>

<VERSION>1.0</VERSION>

<OWNERS>Kalyani Sundaresan</OWNERS>

<AUTHORS>Kalyani Sundaresan</AUTHORS>

<DATECREATED>8/4/2004 9:02:52 PM</DATECREATED>

<DATEREVISED>8/4/2004 11:31:55 PM</DATEREVISED>
</COMPONENT>
</COMPONENTS>

<RESTYPES
Context="1"
PlatformGUID="{00000000-0000-0000-0000-000000000000}"
</RESTYPES>
Click to expand...
</DCARRIER>

I am booting from a partition in the development system

KM
 
KS,

Can you *attach* the SLD here? (although, don't know if it is possible with the "MS CDO for W2K" based client you use).
I mean as a file attachment.
 
how can i attach the file - i can send an email to you if you would not mind giving your email id
 
KS,

You can send it to me directly. Use email address konstmor@_no_spam_hotmail.com (remove _no_spam_ part).

--
Regards,
KM, BSquare Corp.

PS. I am using Outlook Express and I am happy to use any possible feature in it including the file attachments through a newsreader.
You may want to move to OE too. It is perfect for the newsgroup conversations.
 
Back
Top