Call time of all three Run types is documented and it is not very useful for
your case.
If you look at the MSDN docs, it says:
[The RunOnce key is processed by FBA after Plug and Play device enumeration,
and again after DLL registration processing. It is then processed after
logon as the Run key. Typically, this flag is used when a reboot is required
(such as a DLL or OCX registration). ]
Just for the record, I had already read the docs on the RunOnce resource and
had posted specifically because my RunOnce Request seems to be executing in
FBA (though before FBA does network setup), but didn't seem to be executing
after logon as the Run key as it says above it should. So basically even
though it fails to execute at the right time in FBA, it should run after
first logon and thus set the shares, this doesn't happen. Why?
Run might do the trick, but the cost is too great?
It's worth a shot to see if it works I guess
Use and learn to use Filter option in TD to search for components that
contain specific files.
Also you can copy manually reg.exe it has very low dependencies (almost
none).
Come on man, you think I got this far w/o knowing how to use the Filter
option? I did search through it as well as the NG here, but there only seem
to be components for REGEDIT/registry editor. That's a bit bigger than the
simple REG.EXE command which is why I asked if you knew of a component
speficically for REG.EXE. I will try adding the REG.EXE as an extra file.
BTW:
The best way is to have fast target computer for testing hardware unrelated
XPe configurations. This will allow you to build and deploy, and complete
FBA in less than 15 minutes.
So you can experiment with elementary settings and see how they behave.
It is much faster and more accurate to try it yourself, then to ask simple
questions.
I am not even using my target device yet, I'm using my development machine
and building and deploying images to an extra disk within my system and then
booting into that disk to load XPe. I wouldn't call this method fast, the
whole process of building the image, running fba and boot for the first time
is rather time consuming in general, but I don't think that there's a method
faster than this.
I really do appreciate your help Slobodan, but please don't assume that I'm
not searching the documentation and all to find answers even if seems that
way.
RussR
Slobodan Brcin said:
Come on read the manual,at least these things are documented.
Build order is irrelevant in most cases when some sort of installation or
PnP is involved that modifies registry.
Call time of all three Run types is documented and it is not very useful for
your case.
Run might do the trick, but the cost is too great?
Use and learn to use Filter option in TD to search for components that
contain specific files.
Also you can copy manually reg.exe it has very low dependencies (almost
none).
BTW:
The best way is to have fast target computer for testing hardware unrelated
XPe configurations. This will allow you to build and deploy, and complete
FBA in less than 15 minutes.
So you can experiment with elementary settings and see how they behave.
It is much faster and more accurate to try it yourself, then to ask simple
questions.
Regards,
Slobodan
opposed set.
I keys
in
calling
it
at
the
higher phase.
Thanks
Build order won't help you if something during FBA changes value
in
registry
during the some higher phase.
I don't have these registry keys in my XPe build so I can't find
component
that is overwriting your settings.
You can always call reg.exe at some higher FBA phase to change
registry
entries, not peaty but it is working.
Regards,
Slobodan
I ended up putting this registry hack in te Extra Registry
Settings
section
and I put a build order of 1001, but it didn't do that trick.
What
build
order do you think I need to get this to not get overwritten?
Thanks
RussR,
There is a policy restriction that you have to relieve in
order
for
this
to
work correctly. If you look on a XP Pro machine under
Computer
Configuration - Windows Settings - Security Settings - Local
Policies -
Security Options and look at the properties of the
policy
for
"Accounts:
Limit local account use of blank passwords to console logon
only"
that
you
can see the by default this policy is enabled.
The reg hack for this is at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
-> limitblankpassworduse="0" to disable it.
If you disable this, I'm pretty sure that you can get access
to
the
box
without going through the password ordeal.
I'm not in front of TD right now so I can't be certain where
this
is
in
the
existing components, but if you can't find it you may be able
to
hard
code
it in to Extra Registry Settings and turn up the build order
pretty
late
so
that it overwrites the default setting.
John Vorchak [eMVP]
thanks what you said to do worked as when my target device
was
finally
up
and running with XPE, I was able to see it on the network.
When
I
logged
onto the target device it self it shows that the
folders
I
set
to
share
with
my batch script, did indeed get shared.
There's just one problem though: when I go to access
my
XPE
machine
through
"My Network Places" from another machine on the
network,
it
won't
let
me
access the files and other shared stuff that resides
on
the
XPE
machine.
It
says because of a user restriction. I think this is because
there
is
only
the default Adminstrator account and no password is
set.
I
do
not
want
to
set a password as the target device is headless. Is there
any
way
to
get
past this so that my files are visible to others on the
network
w/o
entering
password and all this junk?
Thanks
message
RussR,
Probably the easiest way is to add the script in the Extra
Files
in
TD,
then
add a new RunOnce Request (under Extra Resources) pointing
to
the
script.
The command will execute twice during FBA - which
may
fail
but
should
be
able to be ignored with no problem, and then one
last
time
after
FBA
has
completed and the image is booted for the first time and
that
should
work
with no problem.
You will need the Net.exe Utility component in your build.
John Vorchak [eMVP]
I do know how to use the net share command from the
command
prompt
and
putting it into a .bat file would be trivial. However,
I
do
not
know
how
to
set this to run as a post FBA script especially ensuring
that
it
runs
after
the network and workgroup and all of that is taken care
of.
If you could enlighten me, I would appreciate it.
RussR
message
RussR,
Probably the easiest way to do it might be to
run
a
post-FBA
script
that
utilizes the net share command in a batch script.
John Vorchak [eMVP]
On my XPe image, I have installed all the components
to
enable
File
and
Printer Sharing and Client for Microsoft Networks.
However
to
share
a
folder or drive or other resources, I have to
manually
set
the
sharing
preferences for them after FBA runs and my
image
is
usable.
The problem with this is that eventually my target
device
will
be
headless
so I want to be able to pre-set what folders and
files
will
get
shared
upon
first boot thus requring no user intervention. It
would
also
be
nice
when
deploying images to pre-set the shared resources
either
in
TD
or
some
automated script during first boot.
I have searched through the newsgroups, but
have
not
found
any
help
on
this
matter. The same goes with the MSDN stuff.
Is there a way to do this?
Thanks,
RussR
