> > > >Jared, do you know what process is loaded into memory when NAL
distribution is in progress?

> > > They are not MSI installs. One is pure NAL distrinution and another is
> > > patch deployment - it can be anything.
> > >
> > > Windows does not stop one application from rebooting, especially when

the
> > > reboot is forced.
> > >
> > > So how to solve this issue?
> > > What process is loaded into memory when NAL distribution is in progeress?
> > >


> > I would imagine it depends on the process, if both are MSI installs,

> then
> > one will have to wait.
> >
> > As far as a reboot, doesn't windows wait until a install process is done
> > before a reboot happens?
> >
> > I have never really thought about this, but haven't seen problems

> either. :)
> >
> > --
> > Jared
> > Novell Support Forums SysOp
> > Systems Analyst at Data Technique, INC.
> > Posting with XanaNews 1.17.5.8
> >
> > Check out Novell WIKI
> > http://wiki.novell.com/index.php/IManager

>



> What mechanism exist to prevent conflicting distribution processies?
> What happends when NAL is in a middle of distribution and PatchLink is
> appliing a patch and both requiere a reboot?