I use Altiris Deployment server to deploy images. I was forced inot using
Sysprep by XP SP2. After syspreping and pulling the image I can check the
boot.ini file and it is correct, but after deploying the image it runs
through the mini-setup and cannot find the Windows forlder onthe last reboot.
When I looked at the Boot.ini file it is missing part or all of the text. I
have overcome this wiht server deployed images by copying the Boot.ini file
in as part of the final configuration, but when pulling the image I have to
boot to another OS (WinPE) and copy a new Boot.ini in. Has anyone else had
this problem? Does anyone have any idea where I might be making a mistake?
--
Robert

Drop Altiris man...

Go with the free BDD solution from Microsoft.

JP


"ROlmstead" <rolmstead@KILLSPAM.leon.k12.fl.us> wrote in message
news:F35C8F92-A444-49EF-879A-E801EA168CA6@microsoft.com...
>I use Altiris Deployment server to deploy images. I was forced inot using
> Sysprep by XP SP2. After syspreping and pulling the image I can check the
> boot.ini file and it is correct, but after deploying the image it runs
> through the mini-setup and cannot find the Windows forlder onthe last
> reboot.
> When I looked at the Boot.ini file it is missing part or all of the text.
> I
> have overcome this wiht server deployed images by copying the Boot.ini
> file
> in as part of the final configuration, but when pulling the image I have
> to
> boot to another OS (WinPE) and copy a new Boot.ini in. Has anyone else had
> this problem? Does anyone have any idea where I might be making a mistake?
> --
> Robert

XP and mini-setup do not touch BOOT.INI; only the System control panel,
recovery console, WINNT.EXE, and WINNT32 make changes.

So, if the file is being modified during the deployment process, it is
likely being corrupted by some other process or script being executed during
the process. You may want to check with Altiris to see if they have any
reports of similar problems, as I've never seen any issues like that with
any deployment tools.

-Michael Niehaus
Systems Design Engineer
mniehaus@microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.

"ROlmstead" <rolmstead@KILLSPAM.leon.k12.fl.us> wrote in message
news:F35C8F92-A444-49EF-879A-E801EA168CA6@microsoft.com...
>I use Altiris Deployment server to deploy images. I was forced inot using
> Sysprep by XP SP2. After syspreping and pulling the image I can check the
> boot.ini file and it is correct, but after deploying the image it runs
> through the mini-setup and cannot find the Windows forlder onthe last
> reboot.
> When I looked at the Boot.ini file it is missing part or all of the text.
> I
> have overcome this wiht server deployed images by copying the Boot.ini
> file
> in as part of the final configuration, but when pulling the image I have
> to
> boot to another OS (WinPE) and copy a new Boot.ini in. Has anyone else had
> this problem? Does anyone have any idea where I might be making a mistake?
> --
> Robert

Thank you for your response. I will continue to investigate. Altiris is
clueless and directed me here. Evidently, I am the only person having this
issue. Must be somthing I ate.
--
Robert


"Michael Niehaus [MS]" wrote:

> XP and mini-setup do not touch BOOT.INI; only the System control panel,
> recovery console, WINNT.EXE, and WINNT32 make changes.
>
> So, if the file is being modified during the deployment process, it is
> likely being corrupted by some other process or script being executed during
> the process. You may want to check with Altiris to see if they have any
> reports of similar problems, as I've never seen any issues like that with
> any deployment tools.
>
> -Michael Niehaus
> Systems Design Engineer
> mniehaus@microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "ROlmstead" <rolmstead@KILLSPAM.leon.k12.fl.us> wrote in message
> news:F35C8F92-A444-49EF-879A-E801EA168CA6@microsoft.com...
> >I use Altiris Deployment server to deploy images. I was forced inot using
> > Sysprep by XP SP2. After syspreping and pulling the image I can check the
> > boot.ini file and it is correct, but after deploying the image it runs
> > through the mini-setup and cannot find the Windows forlder onthe last
> > reboot.
> > When I looked at the Boot.ini file it is missing part or all of the text.
> > I
> > have overcome this wiht server deployed images by copying the Boot.ini
> > file
> > in as part of the final configuration, but when pulling the image I have
> > to
> > boot to another OS (WinPE) and copy a new Boot.ini in. Has anyone else had
> > this problem? Does anyone have any idea where I might be making a mistake?
> > --
> > Robert
>
>
>