[MJ]

Hello,
I had an XPe image that during a second boot of the FBA runs a script that
sets the IP address to a static one. We now have to add EWF Ram Reg to the
image. It should be noted that in the final version of this code, we will be
running a custom shell, so there will be no command shell access.

Here's a summary of the problems:
The static ip script used to run on a second first boot run.

Now with EWF Ram Reg, the IP script runs, then the system boots up, but it
seems that the script is no longer considered part of the fba.

Every time the system boots now, it runs the script - and the script doesn't
work!

I can only set the static ip now if I run the script manually after boot and
commit the ewf. Unfortunately once we have a custom shell this method will
be a problem.

Does anyone have any idea how to get the EWF Ram Reg and Static IP script to
play nice together?

Thanks!
MJ

[Slobodan Brcin \(eMVP\)]

MJ,

I have no ides of what script you are talking about, but regardles of that.

Why can't your shell launcher change IP address? Why would that be a problem?

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xehowNamingNetworkInterfacesOnRun-TimeImage.asp

Regards,
Slobodan


"MJ" <MJ@discussions.microsoft.com> wrote in message news:D1776ED4-2C98-4F6D-B866-A52F528F7A8F@microsoft.com...
> Hello,
> I had an XPe image that during a second boot of the FBA runs a script that
> sets the IP address to a static one. We now have to add EWF Ram Reg to the
> image. It should be noted that in the final version of this code, we will be
> running a custom shell, so there will be no command shell access.
>
> Here's a summary of the problems:
> The static ip script used to run on a second first boot run.
>
> Now with EWF Ram Reg, the IP script runs, then the system boots up, but it
> seems that the script is no longer considered part of the fba.
>
> Every time the system boots now, it runs the script - and the script doesn't
> work!
>
> I can only set the static ip now if I run the script manually after boot and
> commit the ewf. Unfortunately once we have a custom shell this method will
> be a problem.
>
> Does anyone have any idea how to get the EWF Ram Reg and Static IP script to
> play nice together?
>
> Thanks!
> MJ

[MJ]

Slobodan,
We have a custom script the runs as an FBA Command that uses NetSh to change
the IP during FBA. We can't do it at boot every time because we have very
strict timing requirements for boot time.

"Slobodan Brcin (eMVP)" wrote:

> MJ,
>
> I have no ides of what script you are talking about, but regardles of that.
>
> Why can't your shell launcher change IP address? Why would that be a problem?
>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xehowNamingNetworkInterfacesOnRun-TimeImage.asp
>
> Regards,
> Slobodan
>
>
> "MJ" <MJ@discussions.microsoft.com> wrote in message news:D1776ED4-2C98-4F6D-B866-A52F528F7A8F@microsoft.com...
> > Hello,
> > I had an XPe image that during a second boot of the FBA runs a script that
> > sets the IP address to a static one. We now have to add EWF Ram Reg to the
> > image. It should be noted that in the final version of this code, we will be
> > running a custom shell, so there will be no command shell access.
> >
> > Here's a summary of the problems:
> > The static ip script used to run on a second first boot run.
> >
> > Now with EWF Ram Reg, the IP script runs, then the system boots up, but it
> > seems that the script is no longer considered part of the fba.
> >
> > Every time the system boots now, it runs the script - and the script doesn't
> > work!
> >
> > I can only set the static ip now if I run the script manually after boot and
> > commit the ewf. Unfortunately once we have a custom shell this method will
> > be a problem.
> >
> > Does anyone have any idea how to get the EWF Ram Reg and Static IP script to
> > play nice together?
> >
> > Thanks!
> > MJ
>
>
>

[Slobodan Brcin \(eMVP\)]

Hi,

Your shell can determine when it is required to change IP address and do that only when needed.

Regarding your script.
If you want it to change IP address then you can execute net programs at phase 8500, 8501.
Make sure that you execute "rundll32 netshell.dll HrRenameConnection " at phase 8500
and at 8501 something like "netsh interface ip set address "Local Area Connection" static 192.168.1.10 255.255.255.0 192.168.1.1 1"

Regards,
Slobodan


"MJ" <MJ@discussions.microsoft.com> wrote in message news:A5EC525E-7163-4260-AF12-3ECEF4653B85@microsoft.com...
> Slobodan,
> We have a custom script the runs as an FBA Command that uses NetSh to change
> the IP during FBA. We can't do it at boot every time because we have very
> strict timing requirements for boot time.
>
> "Slobodan Brcin (eMVP)" wrote:
>
> > MJ,
> >
> > I have no ides of what script you are talking about, but regardles of that.
> >
> > Why can't your shell launcher change IP address? Why would that be a problem?
> >
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xehowNamingNetworkInterfacesOnRun-TimeImage.asp
> >
> > Regards,
> > Slobodan
> >
> >
> > "MJ" <MJ@discussions.microsoft.com> wrote in message news:D1776ED4-2C98-4F6D-B866-A52F528F7A8F@microsoft.com...
> > > Hello,
> > > I had an XPe image that during a second boot of the FBA runs a script that
> > > sets the IP address to a static one. We now have to add EWF Ram Reg to the
> > > image. It should be noted that in the final version of this code, we will be
> > > running a custom shell, so there will be no command shell access.
> > >
> > > Here's a summary of the problems:
> > > The static ip script used to run on a second first boot run.
> > >
> > > Now with EWF Ram Reg, the IP script runs, then the system boots up, but it
> > > seems that the script is no longer considered part of the fba.
> > >
> > > Every time the system boots now, it runs the script - and the script doesn't
> > > work!
> > >
> > > I can only set the static ip now if I run the script manually after boot and
> > > commit the ewf. Unfortunately once we have a custom shell this method will
> > > be a problem.
> > >
> > > Does anyone have any idea how to get the EWF Ram Reg and Static IP script to
> > > play nice together?
> > >
> > > Thanks!
> > > MJ
> >
> >
> >

[MJ]

What phase does EWF Ram Reg setup run?

"Slobodan Brcin (eMVP)" wrote:

> Hi,
>
> Your shell can determine when it is required to change IP address and do that only when needed.
>
> Regarding your script.
> If you want it to change IP address then you can execute net programs at phase 8500, 8501.
> Make sure that you execute "rundll32 netshell.dll HrRenameConnection " at phase 8500
> and at 8501 something like "netsh interface ip set address "Local Area Connection" static 192.168.1.10 255.255.255.0 192.168.1.1 1"
>
> Regards,
> Slobodan
>
>
> "MJ" <MJ@discussions.microsoft.com> wrote in message news:A5EC525E-7163-4260-AF12-3ECEF4653B85@microsoft.com...
> > Slobodan,
> > We have a custom script the runs as an FBA Command that uses NetSh to change
> > the IP during FBA. We can't do it at boot every time because we have very
> > strict timing requirements for boot time.
> >
> > "Slobodan Brcin (eMVP)" wrote:
> >
> > > MJ,
> > >
> > > I have no ides of what script you are talking about, but regardles of that.
> > >
> > > Why can't your shell launcher change IP address? Why would that be a problem?
> > >
> > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xehowNamingNetworkInterfacesOnRun-TimeImage.asp
> > >
> > > Regards,
> > > Slobodan
> > >
> > >
> > > "MJ" <MJ@discussions.microsoft.com> wrote in message news:D1776ED4-2C98-4F6D-B866-A52F528F7A8F@microsoft.com...
> > > > Hello,
> > > > I had an XPe image that during a second boot of the FBA runs a script that
> > > > sets the IP address to a static one. We now have to add EWF Ram Reg to the
> > > > image. It should be noted that in the final version of this code, we will be
> > > > running a custom shell, so there will be no command shell access.
> > > >
> > > > Here's a summary of the problems:
> > > > The static ip script used to run on a second first boot run.
> > > >
> > > > Now with EWF Ram Reg, the IP script runs, then the system boots up, but it
> > > > seems that the script is no longer considered part of the fba.
> > > >
> > > > Every time the system boots now, it runs the script - and the script doesn't
> > > > work!
> > > >
> > > > I can only set the static ip now if I run the script manually after boot and
> > > > commit the ewf. Unfortunately once we have a custom shell this method will
> > > > be a problem.
> > > >
> > > > Does anyone have any idea how to get the EWF Ram Reg and Static IP script to
> > > > play nice together?
> > > >
> > > > Thanks!
> > > > MJ
> > >
> > >
> > >
>
>
>

[MJ]

Slobodan,
I changed my script phase to run at 8501. Here is the sequence of events:

1. FBA runs and reboots
2. Right away on the "Installing Components..." windows comes up and my
script runs
3. Windows boots

The EWF Ram Reg is configured correctly as well as my static ip. However,
the next time I power up, the first thing I see is #2:

"Installing Components..." and then my script runs
3. Windows boots.

It's as if the very tail of FBA has been saved as part of my EWF boot. How
can I get EWF to take a snapshot at the very very end of the entire FBA,
rather than right before my script runs?


"Slobodan Brcin (eMVP)" wrote:

> Hi,
>
> Your shell can determine when it is required to change IP address and do that only when needed.
>
> Regarding your script.
> If you want it to change IP address then you can execute net programs at phase 8500, 8501.
> Make sure that you execute "rundll32 netshell.dll HrRenameConnection " at phase 8500
> and at 8501 something like "netsh interface ip set address "Local Area Connection" static 192.168.1.10 255.255.255.0 192.168.1.1 1"
>
> Regards,
> Slobodan
>
>
> "MJ" <MJ@discussions.microsoft.com> wrote in message news:A5EC525E-7163-4260-AF12-3ECEF4653B85@microsoft.com...
> > Slobodan,
> > We have a custom script the runs as an FBA Command that uses NetSh to change
> > the IP during FBA. We can't do it at boot every time because we have very
> > strict timing requirements for boot time.
> >
> > "Slobodan Brcin (eMVP)" wrote:
> >
> > > MJ,
> > >
> > > I have no ides of what script you are talking about, but regardles of that.
> > >
> > > Why can't your shell launcher change IP address? Why would that be a problem?
> > >
> > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xehowNamingNetworkInterfacesOnRun-TimeImage.asp
> > >
> > > Regards,
> > > Slobodan
> > >
> > >
> > > "MJ" <MJ@discussions.microsoft.com> wrote in message news:D1776ED4-2C98-4F6D-B866-A52F528F7A8F@microsoft.com...
> > > > Hello,
> > > > I had an XPe image that during a second boot of the FBA runs a script that
> > > > sets the IP address to a static one. We now have to add EWF Ram Reg to the
> > > > image. It should be noted that in the final version of this code, we will be
> > > > running a custom shell, so there will be no command shell access.
> > > >
> > > > Here's a summary of the problems:
> > > > The static ip script used to run on a second first boot run.
> > > >
> > > > Now with EWF Ram Reg, the IP script runs, then the system boots up, but it
> > > > seems that the script is no longer considered part of the fba.
> > > >
> > > > Every time the system boots now, it runs the script - and the script doesn't
> > > > work!
> > > >
> > > > I can only set the static ip now if I run the script manually after boot and
> > > > commit the ewf. Unfortunately once we have a custom shell this method will
> > > > be a problem.
> > > >
> > > > Does anyone have any idea how to get the EWF Ram Reg and Static IP script to
> > > > play nice together?
> > > >
> > > > Thanks!
> > > > MJ
> > >
> > >
> > >
>
>
>

[Slobodan Brcin \(eMVP\)]

MJ,

If you are using my Reg RAM EWF component or if you are following MS guidelines then technicaly there is no EWF setup.
Fact is that EWF driver is installed even during the first FBA boot, but unfortunately due to XP design upper class filter driver is
unable to hook to non existing volumes.
So during the first boot at some point PnP will kick in and he will install volumes recognized on your present disks. On next reboot
these EWF will be atached to all these volumes and depending on EWF configuration in registry it will start to protect certain
volumes as told by you.

Now since your IP assignement is working you have two choices:
1. To make EWF disabled by default and then to enable it at phase 8502 and then reboot
2. To place prior two steps that you have tried to 8498 and 8499 phases instead of 8500, 8501. This way you will use the feature in
which EWF is nonworking and you will use common reboot at 8500.

Regards,
Slobodan




"MJ" <MJ@discussions.microsoft.com> wrote in message news:CC5684EE-4F35-4D51-8734-A74557A7A7CC@microsoft.com...
> What phase does EWF Ram Reg setup run?
>
> "Slobodan Brcin (eMVP)" wrote:
>
> > Hi,
> >
> > Your shell can determine when it is required to change IP address and do that only when needed.
> >
> > Regarding your script.
> > If you want it to change IP address then you can execute net programs at phase 8500, 8501.
> > Make sure that you execute "rundll32 netshell.dll HrRenameConnection " at phase 8500
> > and at 8501 something like "netsh interface ip set address "Local Area Connection" static 192.168.1.10 255.255.255.0 192.168.1.1
1"
> >
> > Regards,
> > Slobodan
> >
> >
> > "MJ" <MJ@discussions.microsoft.com> wrote in message news:A5EC525E-7163-4260-AF12-3ECEF4653B85@microsoft.com...
> > > Slobodan,
> > > We have a custom script the runs as an FBA Command that uses NetSh to change
> > > the IP during FBA. We can't do it at boot every time because we have very
> > > strict timing requirements for boot time.
> > >
> > > "Slobodan Brcin (eMVP)" wrote:
> > >
> > > > MJ,
> > > >
> > > > I have no ides of what script you are talking about, but regardles of that.
> > > >
> > > > Why can't your shell launcher change IP address? Why would that be a problem?
> > > >
> > > >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xehowNamingNetworkInterfacesOnRun-TimeImage.asp
> > > >
> > > > Regards,
> > > > Slobodan
> > > >
> > > >
> > > > "MJ" <MJ@discussions.microsoft.com> wrote in message news:D1776ED4-2C98-4F6D-B866-A52F528F7A8F@microsoft.com...
> > > > > Hello,
> > > > > I had an XPe image that during a second boot of the FBA runs a script that
> > > > > sets the IP address to a static one. We now have to add EWF Ram Reg to the
> > > > > image. It should be noted that in the final version of this code, we will be
> > > > > running a custom shell, so there will be no command shell access.
> > > > >
> > > > > Here's a summary of the problems:
> > > > > The static ip script used to run on a second first boot run.
> > > > >
> > > > > Now with EWF Ram Reg, the IP script runs, then the system boots up, but it
> > > > > seems that the script is no longer considered part of the fba.
> > > > >
> > > > > Every time the system boots now, it runs the script - and the script doesn't
> > > > > work!
> > > > >
> > > > > I can only set the static ip now if I run the script manually after boot and
> > > > > commit the ewf. Unfortunately once we have a custom shell this method will
> > > > > be a problem.
> > > > >
> > > > > Does anyone have any idea how to get the EWF Ram Reg and Static IP script to
> > > > > play nice together?
> > > > >
> > > > > Thanks!
> > > > > MJ
> > > >
> > > >
> > > >
> >
> >
> >

[MJ]

Slobodan,
That did the trick! I changed the phase to 8499, and now everything works
exactly as I'd like to.

I don't know what any of us would do without help from this awesome newsgroup.

Thanks!
MJ

"Slobodan Brcin (eMVP)" wrote:

> MJ,
>
> If you are using my Reg RAM EWF component or if you are following MS guidelines then technicaly there is no EWF setup.
> Fact is that EWF driver is installed even during the first FBA boot, but unfortunately due to XP design upper class filter driver is
> unable to hook to non existing volumes.
> So during the first boot at some point PnP will kick in and he will install volumes recognized on your present disks. On next reboot
> these EWF will be atached to all these volumes and depending on EWF configuration in registry it will start to protect certain
> volumes as told by you.
>
> Now since your IP assignement is working you have two choices:
> 1. To make EWF disabled by default and then to enable it at phase 8502 and then reboot
> 2. To place prior two steps that you have tried to 8498 and 8499 phases instead of 8500, 8501. This way you will use the feature in
> which EWF is nonworking and you will use common reboot at 8500.
>
> Regards,
> Slobodan
>
>
>
>
> "MJ" <MJ@discussions.microsoft.com> wrote in message news:CC5684EE-4F35-4D51-8734-A74557A7A7CC@microsoft.com...
> > What phase does EWF Ram Reg setup run?
> >
> > "Slobodan Brcin (eMVP)" wrote:
> >
> > > Hi,
> > >
> > > Your shell can determine when it is required to change IP address and do that only when needed.
> > >
> > > Regarding your script.
> > > If you want it to change IP address then you can execute net programs at phase 8500, 8501.
> > > Make sure that you execute "rundll32 netshell.dll HrRenameConnection " at phase 8500
> > > and at 8501 something like "netsh interface ip set address "Local Area Connection" static 192.168.1.10 255.255.255.0 192.168.1.1
> 1"
> > >
> > > Regards,
> > > Slobodan
> > >
> > >
> > > "MJ" <MJ@discussions.microsoft.com> wrote in message news:A5EC525E-7163-4260-AF12-3ECEF4653B85@microsoft.com...
> > > > Slobodan,
> > > > We have a custom script the runs as an FBA Command that uses NetSh to change
> > > > the IP during FBA. We can't do it at boot every time because we have very
> > > > strict timing requirements for boot time.
> > > >
> > > > "Slobodan Brcin (eMVP)" wrote:
> > > >
> > > > > MJ,
> > > > >
> > > > > I have no ides of what script you are talking about, but regardles of that.
> > > > >
> > > > > Why can't your shell launcher change IP address? Why would that be a problem?
> > > > >
> > > > >
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xehowNamingNetworkInterfacesOnRun-TimeImage.asp
> > > > >
> > > > > Regards,
> > > > > Slobodan
> > > > >
> > > > >
> > > > > "MJ" <MJ@discussions.microsoft.com> wrote in message news:D1776ED4-2C98-4F6D-B866-A52F528F7A8F@microsoft.com...
> > > > > > Hello,
> > > > > > I had an XPe image that during a second boot of the FBA runs a script that
> > > > > > sets the IP address to a static one. We now have to add EWF Ram Reg to the
> > > > > > image. It should be noted that in the final version of this code, we will be
> > > > > > running a custom shell, so there will be no command shell access.
> > > > > >
> > > > > > Here's a summary of the problems:
> > > > > > The static ip script used to run on a second first boot run.
> > > > > >
> > > > > > Now with EWF Ram Reg, the IP script runs, then the system boots up, but it
> > > > > > seems that the script is no longer considered part of the fba.
> > > > > >
> > > > > > Every time the system boots now, it runs the script - and the script doesn't
> > > > > > work!
> > > > > >
> > > > > > I can only set the static ip now if I run the script manually after boot and
> > > > > > commit the ewf. Unfortunately once we have a custom shell this method will
> > > > > > be a problem.
> > > > > >
> > > > > > Does anyone have any idea how to get the EWF Ram Reg and Static IP script to
> > > > > > play nice together?
> > > > > >
> > > > > > Thanks!
> > > > > > MJ
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>