Oh crap you're right, lol. I totally had that backwards. SORRY! I guess I had a long day too hahaha. I'll test again. Sorry Cesar! On Mar 4, 2015 6:01 PM, "Robert Spinelli" <[email protected]> wrote:
> Maybe I'm reading this wrong, it's been a long day, but you ran it when > the machine is within a MW. Since the machine has an active open MW it > ran, which is what I would expect to happen. > > > > If you ran it when the MW wasn't active it shouldn't install the > application and then when the MW opens it should then install the missing > application. > > > > I'm going to end up opening a call with MS, as I'm seeing some weird stuff. > > > > Thanks > > > > Rob > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *ccollins9 > *Sent:* Wednesday, March 4, 2015 4:54 PM > *To:* mssms > *Subject:* Re: [mssms] Application Deployment Evaluation Cycle - Does it > honor maint windows? > > > > Actually, no, elsalvoz is incorrect. I was thinking the same as him/her, > but wasn't 100% sure, so before answering I tested it real quick. It looks > like maintenance windows are ignored when an app fails to be found during > the app deployment evaluation. > > > > As you can see in the log excerpts below, the machine is in maintenance > window and has 799 seconds left (~13 minutes) at 4:41PM > > > > Then I run the deployment eval cycle in line 2 > > > > Then it installs, discovers and completes enforcement between 4:44PM-4:45PM > > > > Surprising TBH > > > > > > 1. (ServiceWindowManager.log) ActiveServiceWindow has 799 seconds > left ServiceWindowManager 3/4/2015 4:41:41 PM 7780 > (0x1E64) > > > > 2. (AppDiscovery.log) ActionType - Install will use Content Id: Content_+ > Content Version: 1 for AppDT "Adobe Flash 16.0.0.305" AppDiscovery > 3/4/2015 4:44:49 PM 9928 (0x26C8) > > > > 3. (AppEnforce.log) Starting Install enforcement for App DT "Adobe Flash > 16.0.0.305" appEnforce 3/4/2015 4:44:50 PM 9928 (0x26C8) > > > > 4. (AppEnforce.log) Discovered application AppEnforce 3/4/2015 4:45:02 > PM 9928 (0x26C8) > > > > 5. (AppEnforce.log) App enforcement completed (11 seconds) for App DT > "Adobe Flash 16.0.0.305" AppEnforce 3/4/2015 4:45:02 PM 9928 > (0x26C8) > > > > > > > > > > > > > > > > > > > > On Wed, Mar 4, 2015 at 3:36 PM, elsalvoz <[email protected]> wrote: > > I think the same concept applies. Test it though :) > > Cesar > > On Mar 4, 2015 12:23 PM, "Robert Spinelli" <[email protected]> > wrote: > > Just to be clear, the apps was already installed let's say a week ago, > someone removes the app, and application deployment evaluation runs on its > own schedule. So if app dep eval runs outside of the maint window it will > re-install the application that was removed when the maint window become > open? > > > > I don't think I made it clear in my original email that that app was > already installed and someone removed it. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *elsalvoz > *Sent:* Wednesday, March 4, 2015 3:13 PM > *To:* [email protected] > *Subject:* Re: [mssms] Application Deployment Evaluation Cycle - Does it > honor maint windows? > > > > Yes, app can only run during MW. The logs and status messages would state > waiting for MW to run. > > Unless of course, you override the deployment to ignore WM. > > Cesar > > On Mar 4, 2015 11:56 AM, "Robert Spinelli" <[email protected]> > wrote: > > I've been trying to test this out, but can't seem to get the scenario > tested. > > > > If you have a maintenance window defined and application deployment > evaluation run does it honor the maint window? If the maint window is for > 4PM-6PM and app deploy eval kicks off at 2PM, will it try again when the > maint window opens? > > > > Thanks > > > > Rob > > > > > > > > > > > > > >
