I've created an image and resealed it manually. I've then
changed some configuration stuff. Can I issue the reseal
command again?

Is there a way to find out if reseal has already been
executed?

Thanks

Tim:

MS does not recommend resealing more than once. You can tell if you have
already done the reseal since the files get deleted after it has been run.

Search the NG archives for why MS recommends to only reseal once. I
remember that someone from MS answered this.

HTH... Doug
"Tim Houle" <(E-Mail Removed)> wrote in message
news:08c801c3bd99$6dc4b600$(E-Mail Removed)...
> I've created an image and resealed it manually. I've then
> changed some configuration stuff. Can I issue the reseal
> command again?
>
> Is there a way to find out if reseal has already been
> executed?
>
> Thanks

Keith:

I basically do the same thing ;-)

.... Doug
"Keith Rathband" <(E-Mail Removed)> wrote in message
news:br78fq$5um$1$(E-Mail Removed)...
> What i've done in the past, is setup / configured my system without it
being
> sealed - create a clone of the system as a backup (is norton ghost to do
> this).
>
> I then set then reseal the image, and clone that image to all the systems
> for deployment.
>
> If in the future if i need to change the image for some reason. I burn the
> image of the unsealed backup image onto a system. Carry out all the
changes
> that i need to do. Create a new backup of the unsealed image.
> Re-seal the image again - clone it and deploy it.
>
> This get round having to start from scratch every time you want to add
> somehing to an image that has already been sealed.
>
> Keith.
>
>
>
> "Doug Hoeffel (eMVP)" <(E-Mail Removed)> wrote in
message
> news:uAzF$(E-Mail Removed)...
> > Tim:
> >
> > MS does not recommend resealing more than once. You can tell if you
have
> > already done the reseal since the files get deleted after it has been
run.
> >
> > Search the NG archives for why MS recommends to only reseal once. I
> > remember that someone from MS answered this.
> >
> > HTH... Doug
> > "Tim Houle" <(E-Mail Removed)> wrote in message
> > news:08c801c3bd99$6dc4b600$(E-Mail Removed)...
> > > I've created an image and resealed it manually. I've then
> > > changed some configuration stuff. Can I issue the reseal
> > > command again?
> > >
> > > Is there a way to find out if reseal has already been
> > > executed?
> > >
> > > Thanks
> >
> >
>
>

What i've done in the past, is setup / configured my system without it being
sealed - create a clone of the system as a backup (is norton ghost to do
this).

I then set then reseal the image, and clone that image to all the systems
for deployment.

If in the future if i need to change the image for some reason. I burn the
image of the unsealed backup image onto a system. Carry out all the changes
that i need to do. Create a new backup of the unsealed image.
Re-seal the image again - clone it and deploy it.

This get round having to start from scratch every time you want to add
somehing to an image that has already been sealed.

Keith.



"Doug Hoeffel (eMVP)" <(E-Mail Removed)> wrote in message
news:uAzF$(E-Mail Removed)...
> Tim:
>
> MS does not recommend resealing more than once. You can tell if you have
> already done the reseal since the files get deleted after it has been run.
>
> Search the NG archives for why MS recommends to only reseal once. I
> remember that someone from MS answered this.
>
> HTH... Doug
> "Tim Houle" <(E-Mail Removed)> wrote in message
> news:08c801c3bd99$6dc4b600$(E-Mail Removed)...
> > I've created an image and resealed it manually. I've then
> > changed some configuration stuff. Can I issue the reseal
> > command again?
> >
> > Is there a way to find out if reseal has already been
> > executed?
> >
> > Thanks
>
>