Client In Multiple Collections - Some have no maintenance windows

If a client is in several collections and a few have maintenance windows is it correct that any deployments targeted to a collection the client is a member of will only run within the earliest maintenance window available regardless of deadline?
So even if it is also in a collection with no MW the deployment to that collection won't run until the MW starts even if it is after the deadline?

Maintenance Windows are not relative to deployments in way and the collection a deployment is applicable to is irrelevant.
MWs they are applied to the clients within that collection. The client then uses all MWs applied to it to restrict the execution of all/any deployments assigned to it (although there are multiple MW types for the different deployment types so that
is of course considered). The collection that the MW or deployment was targeted at is not considered (and in fact not known to client at all).
Also, no MW equates to a 24x7x365 MW.
Jason | http://blog.configmgrftw.com

Similar Messages

  • Client consuming multiple webservices that have shared classes

    My Java client application is accessing two webservices (ServiceA and ServiceB). Both of these webservices us a shared class (CoolRect). I use wscompile to generate stub files for these webservices. When I try to use CoolRect, it gives an "ambiguous" error. Basically I must declare my CoolRect like:
    ServiceA.CoolRect rectA;
    ServiceB.CoolRect rectB;
    The problem is that I cannot assign one to the other:
    rectA = serviceA.getCoolRect();
    rectB = rectA;
    This generates an "incompatible types" error. These are identical classes from common source base used by the webservices. Is there some way to get wscompile to generate stubs so this isn't a problem? All solutions appreciated. Thanks

    Hi Javier...
    Thanks for helping out, though I didn't see any change after applying the configs you suggested.
    The changed config contains the following:
    access-list local_redistribute_out standard permit 172.31.255.0 255.255.255.0
    route-map local_redistribute_out permit 10
    match ip address local_redistribute_out
    router ospf 1000
    router-id 192.168.210.1
    network 10.21.0.0 255.255.0.0 area 1
    network 192.168.210.0 255.255.255.252 area 0
    area 1
    log-adj-changes
    redistribute static subnets route-map local_redistribute_out
    crypto dynamic-map VPN_SOFTWARE_CLIENT 10 set transform-set ESP-AES-256-SHA
    crypto dynamic-map VPN_SOFTWARE_CLIENT 10 set security-association lifetime seconds 288000
    crypto dynamic-map VPN_SOFTWARE_CLIENT 10 set reverse-route
    crypto map EXTERNAL_MAP 1 ipsec-isakmp dynamic VPN_SOFTWARE_CLIENT
    I can confirm the following:
    ASA# ping 10.21.9.42
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 10.21.9.42, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
    After doing the capture, the show capture capin indicated 0 packets captured, 0 packets shown.
    My pertinent local routing table entries contain:
    $ netstat -rn |grep utun0
    default            utun0              UCSI            2        0   utun0
    10.21/16           172.31.255.7       UGSc            0       13   utun0
    172.31.255.7       172.31.255.7       UH              3        0   utun0
    172.31.255.255     utun0              UHW3Ii          0       56   utun0     12
    192.168.210        172.31.255.7       UGSc            1       11   utun0
    216.185.64.6       utun0              UHW3Ii          0      586   utun0    140
    I hope you see something in here that can help.
    Thanks.
    Ken.

  • Maintenance Windows - When a client belongs to more than one collection

    Hi,
    I am a little confused with maintenance windows as I have never had to use them before. I have client that belongs to Collection A with no maintenance window, and Collection B with a maintenance window.   I typically push out apps during
    the day (after they have been tested) so I never use maintenance windows.  I am deploying an application to Collection A (no MW), but it shows in the status that it is waiting for a maintenance window. I assumes it's in this state due to me creating Collection
    B with a maintenance window because I need to push something out this weekend and can only perform this from 10pm to 2am.  If you are deploying an app to a collection, shouldn't look at the maintenance window for THAT collection, instead of
    looking at all the NW for collections a client is added to?  Is there anyway around this?
    Thanks!

    Maintenance Windows are applied to and enforced by the client agent itself. The client enforces the MWs on any and all activity it performs regardless of collection targeting. In fact, clients don't know anything about collections at all. 
    Jason | http://blog.configmgrftw.com

  • How stop the automatic statistics collection job after the maintenance wind

    Hi,
    we are for a solution to stop the automatic statistics collection job after the maintenance window finished.
    we disable all jobs except the automatic statistics collection, because this is the only one we want to run. Then we define specific values for the interval and duration parameters of the maintenance window to customize this task.
    But for their systems it is very important that this job/task will immediately stop when the window is closed!!!
    So, how could we ensure this behavior.
    For Oracle 10g it is easy because the statistic job always exists and it is possible to set its duration and create an addtional event based job which kills all jobs that are running over duration.
    In Oracle 11g the statistic job is created by the system during the maintenance window is open.
    We are not able to modify parameters of this system job. After the maintenance window closed the job is already running - only with another resource priority - but it is running.
    Please help me in this scenario
    Thanks&Regards
    Prem

    ?So basically you are saying is if none of the tables are changed then GATHER_STATS_JOB will not run, but i see tables are updated still the job is not running. I did >query dba_scheduler_jobs and the state of the job is true and scheduled. Please see my previous post on the output
    Am i missing anything here, do i look for some parameters settings
    So basically you are saying is if none of the tables are changed then GATHER_STATS_JOB will not run,GATHER_STATS_JOB will run and if there are any table in which there's a 10 percent change in data, it will gather statistics on that table. If no table data have changes less than 10 percent, it will not gather statistics.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/stats.htm#i41282
    Hope this helps.
    -Anantha

  • SCCM 2012: Child collections with Maintenance Windows

    Hello
    after searching and reading many posts about maintenance window, I've realised, I have to ask my own question:
    Assume a parent software update collection and an ADR, deployed on it. Every one of the child collections (included by Membership rule: include collections) has an own Maintenance Window.
    Question: what exactly happens on the Dead Line, configured in ADR?
    I suppose, the selected updates will be deployed to the child collections, but download, installation and reboot will occure only during the configured Maintenance Window on the child collection. The software updates will be listed in Software Center of
    the server, which is member of this collection, the status will be "past due - will be installed" or somethig of this kind, the download status will be shown as 0%.
    Am I right?
    Questions Background: we have a large infrastructure with more than 1500 servers, devided in 11 pools (software update collections) with 11 different maintenance windows. So, I will create only one ADR, which will be deployed to the parent software
    update collection, or "wrapper collection". I hpe, the configured maintenace windows of the child collections will remain active.
    Thanks for your feedback.
    Kind regards: P. trifonov

    Yes you are right. the SU will get installed at the next available MW, no matter which collection that MW belongs too.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Multiple Deployments During Single Maintenance Window

    I have a maintenance window that runs from 10PM to 4AM daily. I have three deployments with deadlines during that time. I'm also using the default restart times of 90 minutes and then 15. One of them runs at 11PM, the next at 1AM, and the last at 3AM. Two
    are software updates. 
    So if the first runs at 11PM and the updates install (they had already downloaded prior to the deadline) successfully. They each have a max runtime of 5 minutes. Now a user is still logged in from earlier that day. The 90 minute restart countdown starts.
    Will the second deployment still run at 1AM if the first one hasn't completed its restart yet?

    I'm not 100% sure, but I think it will need the restart first.

  • Commit changes at deadline or during a maintenance window (requires restarts)?

    What happens in an application deployment if I uncheck "Commit changes at deadline or during a maintenance window (requires restarts)"?  If I have an application deployed to a collection with a maintenance window with a scheduled to be available
    now with an installation deadline of one week, what would happed?  What about if the application was deployed to a collection that did not have a maintenance window and there were no maintenance windows defined in any other collection the member clients
    were in?

    This is for Embdedded devices, like ThinClients.
    That means write filter commits either at deadline or during a maintenance window.
    Your application still installs as you schedule it, available now and install week from now. If you have maintenance window and selected to not install or reboot outside of maintenance window, then everything happens within maintenance window. If you don't
    check that box for write filter, then your app or setting you have just pushed does not get saved when device is rebooted.
    Same scenario with no maintenance windows. If you don't have maintenance window then your app downloads and installs as you schedule the dates. Write filter would not commit these changes and everything would go away after reboot.

  • Maintenance Windows are not being honored - SCCM 2012 R2

    I have a TS that runs a command to reboot our systems, and this TS is deployed to a test device collection with the following settings:
    - Deployment settings: Install and required
    - Deployment schedule: every 1 hour
    - Rerun behavior: Always rerun program
    The test device collection has the following maintenance windows set:
    - Recurrence: Weekly
    - Recur every: Saturday
    - Start time: 2am
    - End time: 3am
    - Apply this schedule to: Task sequences
    Despite the maintenance window, my test machine is getting rebooted every hour. Am I missing anything here?
    Thanks.

    I did but there's not much there as to why the MW is being ignored
    Mandatory execution requested for program * and advertisement PS120015 execmgr 3/7/2014 12:00:00 PM 2648 (0x0A58)
    Creating mandatory request for advert PS120015, program *, package PS10006A execmgr 3/7/2014 12:00:00 PM 2648 (0x0A58)
    The created request is a Task Sequence request execmgr 3/7/2014 12:00:00 PM 2648 (0x0A58)
    Execution Request for advert PS120015 package PS10006A program * state change from NotExist to WaitingDependency execmgr 3/7/2014 12:00:00 PM 2648 (0x0A58)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PS10006A",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 3/7/2014 12:00:00 PM 2648 (0x0A58)
    An existing MTC token was not supplied, using ExecutionRequest's Id as MTC token and this execution request is the owner of resultant MTC task. execmgr 3/7/2014 12:00:00 PM 2648 (0x0A58)
    Request a MTC task for execution request of package PS10006A, program * with request id: {C67D2DA3-4BE8-49A9-9989-F4CC8D5BBED3} execmgr 3/7/2014 12:00:00 PM 2648 (0x0A58)
    Execution Request for advert PS120015 package PS10006A program * state change from WaitingDependency to Ready execmgr 3/7/2014 12:00:00 PM 2648 (0x0A58)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PS10006A",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 3/7/2014 12:00:00 PM 2648 (0x0A58)
    MTC task with id {C67D2DA3-4BE8-49A9-9989-F4CC8D5BBED3}, changed state from 0 to 4 execmgr 3/7/2014 12:00:00 PM 2556 (0x09FC)
    MTC signaled SWD execution request with program id: *, package id: PS10006A for execution. execmgr 3/7/2014 12:00:00 PM 2556 (0x09FC)
    Sending ack to MTC for task with id: {C67D2DA3-4BE8-49A9-9989-F4CC8D5BBED3} execmgr 3/7/2014 12:00:00 PM 2556 (0x09FC)
    Executing program  in Admin context execmgr 3/7/2014 12:00:00 PM 2556 (0x09FC)
    Execution Request for advert PS120015 package PS10006A program * state change from Ready to NotifyExecution execmgr 3/7/2014 12:00:00 PM 2556 (0x09FC)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PS10006A",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 3/7/2014 12:00:00 PM 2556 (0x09FC)
    Executing program as a task sequence. execmgr 3/7/2014 12:00:00 PM 2556 (0x09FC)
    Executing TS Program execmgr 3/7/2014 12:00:00 PM 2556 (0x09FC)
    Task Sequence started execmgr 3/7/2014 12:00:00 PM 2556 (0x09FC)

  • Application (WMF 3.0) won't install during maintenance window, but will install when there is no maintenance window

    Hi All,
    I'm just getting into the Application model in SCCM 2012 R2 and I like what I see so far, but i'm running into an issue.  When i set up an Application for WMF 3.0 with a prerequisite of .Net 4.0 and deploy it to a set of test systems that do not have
    any maintenance windows applied to it, it works great.  If it doesn't have .Net 4.0 it installs both that and WMF 3.0 and reboots.  If it already has .Net 4.0, it will skip that and just install WMF 3.0 and reboot. 
    However, if i deploy it to systems that have a maintenance window applied, the application recognizes that it needs .Net and WMF 3.0 or just WMF 3.0, but it never actually runs. 
    Here is the applicable entry from the appintenteval.log, and i've bolded the line where it shows that WMF 3.0 is not installed
    ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66/12 :- Title = WMF 3.0, Direct seleted dependencies = ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558/7 title=.Net
    4.0,     AppIntentEval    4/24/2014 8:20:19 AM    1768 (0x06E8)
    ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66/12 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Installed, ConfigureState = NotNeeded, Title = WMF 3.0    AppIntentEval  
     4/24/2014 8:20:19 AM    1768 (0x06E8)
    ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558/7 :- Current State = Installed, Applicability = Applicable, ResolvedState = Available, ConfigureState = NotNeeded, Title = .Net 4.0    AppIntentEval  
     4/24/2014 8:20:19 AM    1768 (0x06E8)
    ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/Application_de66c10e-111e-4d68-95a8-5cee3f144081/13 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Installed, ConfigureState = NotNeeded, Title = WMF 3.0    AppIntentEval  
     4/24/2014 8:20:19 AM    1768 (0x06E8)
    ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/RequiredApplication_de66c10e-111e-4d68-95a8-5cee3f144081/13 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, ConfigureState = NotNeeded, Title = ApplicationIntentPolicy  
     AppIntentEval    4/24/2014 8:20:19 AM    1768 (0x06E8)
    and here are the entries from the AppDiscovery.log that are relevant:
    Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558" AND Revision = 7)"    AppDiscovery  
     4/24/2014 8:20:19 AM    2776 (0x0AD8)
        Performing detection of app deployment type .Net 4.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, revision 7) for system.    AppDiscovery    4/24/2014 8:20:19
    AM    2776 (0x0AD8)
    +++ Discovered application [AppDT Id: ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, Revision: 7]    AppDiscovery    4/24/2014 8:20:19 AM    2776 (0x0AD8)
    +++ Detected app deployment type .Net 4.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_4e541fdb-f444-4c5f-91f9-82c358325558, revision 7) for system.    AppDiscovery    4/24/2014 8:20:19 AM  
     2776 (0x0AD8)
    Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66" AND Revision = 12)"    AppDiscovery  
     4/24/2014 8:20:19 AM    2508 (0x09CC)
        Performing detection of app deployment type WMF 3.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, revision 12) for system.    AppDiscovery    4/24/2014 8:20:19
    AM    2508 (0x09CC)
    +++ Application not discovered. [AppDT Id: ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, Revision: 12]    AppDiscovery    4/24/2014 8:20:19 AM    2508
    (0x09CC)
    +++ Did not detect app deployment type WMF 3.0(ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66, revision 12) for system.    AppDiscovery    4/24/2014 8:20:19 AM  
     2508 (0x09CC)
       ActionType - Install will use Content Id: Content_c6b448d0-7b59-4796-bb29-3f7fbfa6e70d + Content Version: 1 for AppDT "WMF 3.0" [ScopeId_DDF2880D-575F-42D9-A30B-E026F0EFDA4F/DeploymentType_0418fd00-0911-41d8-97f5-d7f04f58bd66],
    Revision - 12    AppDiscovery    4/24/2014 8:20:20 AM    2508 (0x09CC)
    I have a 2 hour maintenance window applied to this system.  From the serviceWindowManager.log:
    OnIsServiceWindowAvailable called with: Runtime:7200, Type:2    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window...    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
            Biggest Active Service Window has ID = {02B82DF5-3360-4BCC-8154-9258F0B856C3} having Starttime=04/24/14
    08:20:00    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
                Duration is 0 days, 02 hours, 00 mins, 00 secs    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
    FindBiggestMergedTimeWindow called with TimeStart=04/24/14 08:20:21 and TimeEnd=04/24/14 10:20:00    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
            Biggest Chainable Service Window for Type=1 not found    ServiceWindowManager    4/24/2014 8:20:21 AM    1768 (0x06E8)
    I'm not sure what else to try next and appreciate any help anyone can offer.

    Thanks.  I checked that setting and i have it set to false, so i don't think that's it. 
    I've done a little more experimenting.  I've changed my maintenance window back to 30 minutes.  Prior to the MW opening, i'll run an application evaluation deployment cycle on the system.  It will show the system as required WMF 3.0 but since
    the MW isn't open, it won't install at the time. 
    When the MW opens, i'll watch the ServiceWindowManager.log and it sees that it's a 30 minute MW and that the run time is 15 minutes but it still says the program can't run:
    ActiveServiceWindow has 1800 seconds left    ServiceWindowManager    4/24/2014 2:20:00 PM    2032 (0x07F0)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    4/24/2014 2:20:00 PM    2032 (0x07F0)
    OnIsServiceWindowAvailable called with: Runtime:900, Type:6  
     ServiceWindowManager    4/24/2014 2:20:00 PM    2032 (0x07F0)
            Biggest Active Service Window for Type=6 not found    ServiceWindowManager    4/24/2014 2:20:00 PM    2032 (0x07F0)
    Program cannot Run! Setting *canProgramRun to FALSE    ServiceWindowManager    4/24/2014 2:20:00 PM    2032 (0x07F0)
    OnIsServiceWindowAvailable called with: Runtime:900, Type:2    ServiceWindowManager    4/24/2014 2:22:32 PM    816 (0x0330)
    If however, i kick off another application evaluation deployment cycle on the system during the open MW, the deployment kicks off right away and finishes. 
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    4/24/2014 2:22:32 PM    2940 (0x0B7C)
    OnIsServiceWindowAvailable called with: Runtime:900, Type:3    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window...    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
            Biggest Active Service Window has ID = {02B82DF5-3360-4BCC-8154-9258F0B856C3} having Starttime=04/24/14 14:20:00    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
                Duration is 0 days, 00 hours, 30 mins, 00 secs    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
    ActiveServiceWindow has 1571 seconds left    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    4/24/2014 2:23:49 PM    816 (0x0330)
    This is not the behavior i would expect.  I would think that if the client knows it has a pending application deployment that is required, when the MW opened up, it would start the install immediately or close to the beginning of the MW.  It shouldn't
    need to have an application evaluation deployment cycle kicked off during the MW. 

  • Maintenance Windows and Installation Deadline

    I know this has been discussed many times in the past, but I wanted to clarify in my mind what I think happens.
     I have a maintenance window on a collection that is daily between 3:30am and 5:30am.  I create a deployment for software updates with an available time at 2:00am.  I specify the installation deadline in the deployment for 3:00am.
    In the Deadline behavior (user experience) I do not have either option checked (Software updates installation and System restart). So, my MW will not be ignored.
    With these settings, the needed updates will be downloaded, but not installed until the start of the maintenance window at 3:30am. (in essence, the deadline should be "before" the MW if I want them to install at the next MW).
    Thanks!

    I did:
    <![LOG[New Service Window Policy notification received.]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager" context="" type="1" thread="996" file="servicewindowmanager.cpp:217">
    <![LOG[CCM::ServiceWindowManager::CServiceWindowHandler::OnPolicyCreated - A policy change has occurred. New policy has been created.]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager"
    context="" type="1" thread="996" file="servicewindowhandler.cpp:2044">
    <![LOG[    Populating instance of ServiceWindow with ID={3DE9CD79-CC8A-4CDD-AD75-74191AB07BFA}, ScheduleString=786F1B4010100008, Type=4]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager"
    context="" type="1" thread="996" file="servicewindowhandler.cpp:104">
    <![LOG[        StartTime is 1/16/2015 3:30:00 AM]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager" context="" type="1"
    thread="996" file="servicewindowhandler.cpp:176">
    <![LOG[        Duration for the Service Window is Total days: 0, hours: 02, mins: 00, secs: 00]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager"
    context="" type="1" thread="996" file="servicewindowhandler.cpp:106">
    <![LOG[    The Service Window={3DE9CD79-CC8A-4CDD-AD75-74191AB07BFA} has started at 1/16/2015 3:30:00 AM]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager"
    context="" type="1" thread="5032" file="servicewindowhandler.cpp:1200">
    <![LOG[OnIsServiceWindowAvailable called with: Runtime:1, Type:4]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420"
    file="servicewindowhandler.cpp:2258">
    <![LOG[        Biggest Active Service Window has ID = {3DE9CD79-CC8A-4CDD-AD75-74191AB07BFA} having Starttime=1/16/2015 3:30:00 AM]LOG]!><time="03:30:00.071+300" date="01-16-2015"
    component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1336">
    <![LOG[           
    Duration is 0 days, 02 hours, 00 mins, 00 secs]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1337">
    <![LOG[ActiveServiceWindow has 7200 seconds left]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1248">
    <![LOG[Program can run! Setting *canProgramRun to TRUE]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1249">
    <![LOG[OnIsServiceWindowAvailable called with: Runtime:900, Type:2]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="4760"
    file="servicewindowhandler.cpp:2258">
    <![LOG[No Restricting Service Windows exist. It can therefore run...]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="4760"
    file="servicewindowhandler.cpp:1510">

  • Maintenance Window Question

    Hello Experts,
    i'm sorry if its been already answered, I have a question on MW.
    CollectionA---> has a MW set between 6PM - 6AM ( Monday - Sunday) ( which is set to ->This Schedule Applies to all deployments)
    CollectionA---> has another MW 8PM-10PM ( Sat-Sunday) ( which is set to ->This schedule applies to Software deployments)
    Since there is an overlap, what would happen when Software updates are pushed, Will it run on Sat or sun at 8PM or at 6PM.
    Thank you.

    Hi,
    It depends on the Deadline you set for the updates to install, as you have a maintenance windows that allows all deployments each night, software updates will run then. If you schedule them to start at saturday morning it will start at 6 PM SAT as that
    maintenance windows has the eraliest start time and apply to all deployments.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Impdp and scheduler maintenance window

    Environment: Oracle 11.1.0.7.0 running on HP-UX B.11.31 U ia64.
    I was performing import using impdp. Before starting the import, I manaully disabled the maintenance window.
    But once, import over, when I try to enable the maintenance window, when I checked, it got already enabled.
    On investigating found that the timing of enable match with the import finish time.
    Before performing the import using impdp, I have disabled maintenance window using;
    DBMS_SCHEDULER.DISABLE(name=> mwindow,force=>TRUE);
    After Import, when i checked the maintenance window using;
    SELECT
    w.window_name,
    w.repeat_interval,
    w.duration,
    w.enabled
    FROM dba_scheduler_windows w
    the value as ENABLED = TRUE.
    On querying the select * from DBA_SCHEDULER_WINDOW_LOG, the timing of LOG_DATE matches with the import impdp finish time. However on the column ADDITIONAL_INFO
    has value of REASON="manually enabled"

    Are you doing a system import here ?
    If you are doing a system import then properties of the maintenance window will also be imported and that may include enabling the window.
    Since a system export exports system-level properties as well, you might need to disable the maintenance window before doing your system export.
    Hope this helps,
    Ravi.

  • I have multiple devices that have my iCloud E-mail, I want to disable the E-Mail on some of the devices but keep it on others, I do not have physical access to the ones I want to disable but I do have access to the devices I want to keep receiving mc

    I have multiple devices that have my iCloud E-mail, I want to disable the E-Mail on some of the devices but keep it on others, I do not have physical access to the ones I want to disable but I do have access to the devices I want to keep receiving mail, can I do this with a simple password reset or will that still leave all devices enabled?

    The simple way would be to uncheck 'Mail' in System Preferences (or Settings)>iCloud, but as you would need access to the devices in question to do that you will have to change your password, at http://appleid.apple.com. You will then need to sign out and back on all the devices you want to be able to receive mail, and it's important that you follow this procedure and note the warning:
    Firstly, if you have 'Find My iPhone/iPad/iMac' enabled on any of your devices, turn it off.
    Go to http://appleid.apple.com and click 'Manage your Apple ID'. Sign in with the current ID.
    Where it says 'Password & Security' and gives your current ID email address, click 'edit'.
    Enter your new password and click 'Save changes'.
    Now you will need to go to each of your devices and sign out in System Preferences (or Settings)>iCloud - 'Sign out' on a Mac, 'Delete this account' on an iOS device (this will not delete the account from the server).
    Then sign back in with your new ID. Your iCloud data will disappear from your devices when you sign out, but reappear when you sign back in.
    I re-iterate: before you start, turn off 'Find My Mac' (or whatever) or you will need the services of Support.
    The devices on which you have not changed the password will throw up continual error messages as they attempt to contact iCloud and fail.

  • Need some help archiving and photos that are in multiple collections.

    After creating a new catalog for photos from a collection, I'd want to remove the photos from Lightroom and keep on disk.  In the collection, there are some photos that are in multiple other collections and I'd want to keep those images in their other collections and so not removed them from Lightroom.
    Need some advice on how to easily identlfy those images that are in other collections and thus might not want to remove those images from Lightroom.

    Well, Bob, that works, but agreeing with Geoff, I don't think this is the best solution to the problem; in fact I don't even think this is a good solution to this problem.
    If there isn't a lot of space left, and the user wants to do something about the photos in those collections, then the photos should be moved (in Lightroom, or via this process: http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm) to a different drive. This generates more free space on the SSD drive. The photos remain in the Lightroom catalog, and they remain in the multiple collections that they are in now.
    MrhoniKeith -- your photos probably should not go on the SSD in the first place. Photos ought to be stored on a normal hard drive, not an SSD. You can move them to a regular hard drive en masse, freeing up plenty of space on the SSD via this method: http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm. This is the BEST solution to your problem -- keep everything in a single catalog, with photos on a normal hard disk. The idea of having multiple catalogs to help free up space on one drive works opposite to the best practices of using Lightroom, in which most people recommend using a single catalog for all of your photos, except in special cases where the photo's contents are completely non-overlapping, for example Personal and Business catalogs.
    Removing photos from some collections but not others will NOT free up space. That's not how Lightroom works. Lightroom has not made multiple copies of your photos for each collection. Deleting photos from collections will NOT free up space.

  • SCCM 2012 R2: easy way to disable/enable MULTIPLE maintenance windows at once?

    I have been racking my brain on this one for a while.
    Scenario: you have an ADR set up that is deploying updates once a month. You have multiple collections set up that each have their own special maintenance window (example: 1st weekend - sat - 8-9pm)
    Then, one week you are asked to not deploy updates for the upcoming weekend. Well, the ADR already ran and the machines for "1st weekend" are just waiting for the maintenance window to open. Now, at this point you can obviously go into EACH collection
    associated with "1st weekend" and disable the maintenance window. But if you are asked to do this often and/or you have multiple collections with maintenance windows this could be a hassle.
    Is there a way to easily enable and disable multiple maintenance windows at a time?
    GUI: I have not found a way to select multiple collections and disable all MWs
    PowerShell-module: set-CMMaintenanceWindow doesn't appear to have ability to modify "IsEnabled" property of MWs
    PowerShell-WMI: Can't find in WMI where to modify "Isenabled" Property
    Please see my other thread
    regarding PowerShell
    What other creative options are there? Disable a service via PowerShell on members of "1st Weekend" collections? Which service? Should I be looking in SQL? Where? Other options in GUI?
    I may end up getting stuck doing this manually but I want to make sure I am not overlooking something first... it's such a simple task - just seems like there should be an easy way to accomplish this.
    (And please, for the sake of my question, lets not get into the semantics of whether or not the ADR technically DEPLOYS the updates or not.)

    I didn't even think about that.... so having one MW that is disabled or having no MW at all would allow the client to install at will? I guess I was thinking that if it had a MW but it was disabled it just wouldn't update.
    The MWs on the collections are all different.
    Perhaps I need to re-assess my approach...
    The original plan was to have one ADR (patch tuesday) update 1 SUG (which is deployed to all machines) each month. Machines would then install based off MWs.
    Now I'm thinking it might be best to have 2 ADRS:
    ADR1- updates existing SUG which is already deployed to Dev/Test machines.
    ADR2- creates new SUG - which I then manually deploy to Prod collections. 
    This would automate the deployment to Non-Prod machines but it would give me the power to withhold updates to Prod machines for the month if needed.

Maybe you are looking for