Application Scheduling and Maintenance Windows

Hi There. I have a scenario that I want to get some clarification. I think I know how it will work but wonder if I'm understanding it correctly.
I have clients across a WAN that I want to deploy an application to but the bandwidth is limited and I can't put local DPs there. I want to prestage the content and then enforce its installation after the server side of the app has been upgraded
on Saturday.
The collection that the clients are a member has a maintenance window defined daily from 2am to 5am. I was going to deploy the app and make it available for tonight at 8pm thinking that the client would see the deployment and begin to download
it. The application deadline is set for 2 days from now on Saturday at 8pm. Am I correct in thinking that the client will install the application tonight at 2am during it's first available maintenance windows??
If so, my plan is to temporarily replace the daily 2am to 5am maintenance window with a maintenance window that starts at the deployment deadline on Saturday at 8pm. It seems to me that then the client would see the application, download it and wait
to install until 8pm on Saturday when it would be enforced. I also plan to hide the deployment so that it does not show up in software center.
Is my thinking correct?

If your objective is to prestage the content on the client cache, the only way I know that it works, is when the "available" schedule is reached, SCCM will evaluate the deployment and if applicable (meets requirement, detection rules, etc), it will automatically
download the content to the cache folder...
So, if you make it "available" today at 8pm and "required/deadline" for this Saturday 8pm, the clients will download the content after 8pm today (regardless of maintenance windows). The issue, as stated previously, is that if a user decides to go in the
software center app, they can manually trigger the install as soon as the deployment "available" date is reached (~today 8pm). You can configure the notifications...
The actual automatic install (triggered by the client agent software) will only happen on/after Saturday at 8pm; assuming that the maintenance window permits it. Be VERY careful with maintenance windows. If you have it set for 2am-5am daily, the deployment
will install on Sunday 2am-5am, as the window is closed on Saturday at 8pm (deadline)... Also the PC has to be powered on for the install to happen.
As with many things in SCCM, there is always other settings that can affect the result. E.g., you can set the deployment to install/reboot outside maintenance windows...
You may want to test this to confirm...

Similar Messages

Hi, I am unable to install new itunes version to windows 7 PC. It requires application support and gives windows error 2. I have tried to save on desktop and run as administrator but errors remains, what other options do I have

Hi, I am unable to install new itunes version to windows 7 PC. It requires application support and gives windows error 2. I have tried to save on desktop and run as administrator but errors remains, what other options do I have?

Hello, hanliefromzaf.
Thank you for visiting Apple Support Communities.
Here is an article that I would recommend going through when experiencing this issue.
iTunes for Windows: Unable to install or open
http://support.apple.com/kb/ts5376
Cheers,
Jason H.

Software Updates and Maintenance Windows

We are running SCCM 2012 R2 Primary Site Server.
We created the Collection for Windows Server 2012 R2 machine and Software Update group containing Software Updates for Server 2012 R2.
We set the maintenance windows on collection "11:00 AM- 2:00 PM"
We deployed the Deployment Package to collection at 11:00 AM, it downloaded the updates but didn't install any updates for 1 hour. At 2:00 PM it said that the No service window available to run updates .
Why didn't SCCM do anything for 1 hour?
Attached is the snippet from Update deployment.log
Evaluation initiated for (1) assignments.- 12:56 PM
Progress received for assignment ({D45DB820-AF28-4FAC-AAFC-7819937A412E})- 12:56 PM
Update (Site_64D995A8-C176-4B35-AFE0-724BB6793EBD/SUM_74b0949d-a84d-4599-8060-e7b982720886) added to the targeted list of deployment ({D45DB820-AF28-4FAC-AAFC-7819937A412E}) - 12:56 PM
Evaluation completed for the assignment {D45DB820-AF28-4FAC-AAFC-7819937A412E} - 12:56 PM
CUpdateAssignmentsManager received a SERVICEWINDOWEVENT END Event- 2:00 PM
No current service window available to run updates assignment with time required = 1 - 2:00 PM
Attempting to cancel any job started at non-business hours.- 2:00 PM

How to enable client randomization? Does it need to be enable for SCCM to deploy updates?
You can download the updatedeployment.log from below link
https://onedrive.live.com/redir?resid=F3743C55DC76B1EE!1099&authkey=!AL40dKaAzl-_trc&ithint=folder%2c.log

Software Updates, Tray Pop-ups and Maintenance Windows

I will try to keep it to the point.
End Users in Europe power down their machines every night. Patch Tuesday rolls around, we set the deadline to patch for one week
later (the following Tuesday) @ 10pm.
So they come in that following Wednesday morning, power on their system and bam, software updates are installed and reboots are forced right
there in their earlier AM which is upsetting them.
Our settings? Deployment is required, detail level is “only success and error messages”, “Display in Software Center and show all notifications”, and when the installation
deadline is reached allow the following activities to be performed outside the maintenance window: “Software Update Installation” and “System Restart”.
So before I get a whole bunch of, “disable reboots” or “notify your users” or “use WOL”. I want to discuss this on another angle.
We are getting reports that users are not seeing the notifications. As you can see it is set to all notifications. Likely they are happening and they are not seeing
them.
Main Question: Is there a way via a registry tweak or client setting that will do one of the following:
Make the tray popups more frequent
Make the tray popups last longer
Bring the main “hey things to patch screen” come up without clicking the tray popup
Anything we can do to make the notification BEFORE the deadline more in their faces would be ideal. Anyone?

This happened because patch updates reached deadline and installed forcefully and restart the machines. from
the software center and system tray. Just configure that in the deployment
Unless the site wide hide deployments option is selected,
you will get icons in the system tray. When that is selected, you do NOT get icons at all. If this is enabled, but you suppress the deployment itself, then you get the icons but not balloons.
Sharad Singh | My blogs: SharadTech | Twitter:
@SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

RE: OS Deployments and Maintenance Windows

Hi
I have an MDT task sequence that I am using from within SCCM 2012 R2. Its deployed to a collection for which I have specified a maintenance window. However, when I boot this test OSD client with the media I am still able to deploy the image even outside
the maintenance window.
Where can I start looking to sort this out?
Karl

If you don't want the deployment to be applicable to the device at all, then yes you have to make sure that the device is not targeted by the deployment. That can be by deleting the deployment, or by making sure the device is not member of the collection
anymore.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Deadline, Business Hours vs. Maintenance Windows

I read the blog about Business Hours vs. Maintenance Windows, but I still have two questions
http://blogs.technet.com/b/server-cloud/archive/2012/03/28/business-hours-vs-maintenance-windows-with-system-center-2012-configuration-manager.aspx
Event 1: Application A
No Maintenance Windows & No Wake on LAN;
Business hours is 5am to 10pm;
User start laptop at 8AM and close at 5PM every day;
Deadline is 11PM, Thursday;
Available is 9Am, Monday, User clicks "Install Later".
So when A will be installed?
Event 2: Application B
Maintenance Windows is 1AM to 4AM , NO Wake on LAN, B has not been configured that install when out of Maintenance Windows;
Business hours is 5am to 10pm;
User start laptop at 8AM and close at 5PM every day;
Deadline is 11PM, Thursday;
Available is 9Am, Monday, User clicks "Install Later".
User never start laptop in Maintenance Windows time, so if it mean that B will never be installed?

To add a couple of clarifying points to the article linked:
- Business hours are meaningless after a deployment's deadline and are only used before the deadline.
- Business hours are only relevant if a user has explicitly stated for a deployment to be enforced outside of their business hours.
- The intent of business hours is to allow users to schedule enforcement of a required deployment before a deadline but outside of their work hours so it never interrupts them.
The article does say all of this, just not as directly.
For Event 2 (application b), this is why using maintenance windows usually doesn't work well for workstations. Why would the business hours be set for 5AM to 10PM though? That really makes no sense based on my third point above. Of course in this case, if
the system is totally off, it doesn't really matter anyway.
Jason | http://blog.configmgrftw.com | @jasonsandys

Maintenance Window not honoured?

Hi Folks,
The more I read through these forums on how the Maintenance Window works the more I feel my deployment was set-up correctly. However, I had a number of workstations unexpectedly install Win7 SP1 and restart during business hours (which are defined as
06:00 to 23:00 with a Configuration Baseline).
My SP1 deployment is set-up as follows:
Set as Install, Required, pre-deploy software to user's primary device (checked),
Advertised at 08:30 with a deadline of 23:30 the same day (last Friday)
User Experience is 'Show All Notifications', and has 'Software Installation' and 'System Restart (if required to complete the installation)' unchecked.
No restart flags specified on SP1 command line, just using /quiet and /nodialog
Should Config Manager enforce specific behaviour regardless of the applications intended behaviour set to 'No specific action'
However, a small number of users turned their workstations off when leaving last Friday. When they came in today (Monday morning) the installation was triggered straightway.
Checking the logs at one of those affected I can see that the Maintenance Window is detected but for some reason is not honoured. I can't see any mention of the user triggering the restart either.
Am I missing something?
Thanks,
Mic

Business hours and maintenance windows are two different things. Business hours will not prevent the installation from happening when the deadline is reached. For a very good read about this see:
http://blogs.technet.com/b/server-cloud/archive/2012/03/28/business-hours-vs-maintenance-windows-with-system-center-2012-configuration-manager.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

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.

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 - Scheduled Reboot Sleep/Hibernate

Given an appropriately scheduled maintenance window and a properly configured set of client settings (computer restart), what is the expected behavior for a client computer that enters standby/hibernate during the countdown and doesn't resume until after
it has ended?
I have been running a few tests in my environment and I'm finding that clients resuming from standby/hibernate are being forced to reboot immediately. Sometimes before I am able to hit ctrl+alt+delete and login.
Is this expected?

Is this expected?
I think this is expected. More details from Rebootcoordinator.log would be helpful.
Anoop C Nair -
@anoopmannur :: MY Site:
www.AnoopCNair.com ::
FaceBook:
ConfigMgr(SCCM) Page ::
Linkedin:
Linkedin<

About maintenance windows and client restart settings

Scenario:
I have an application which is configured so that ConfigMgr Client will force a restart after the installation. This application is going to be deployed to a collection of computers which are also members of another collection that has maintenance window
of 3 hours configured. The default client settings for all the computers have been configured so that users are notified about possible restart for 1440 minutes (24h).
When the deployment is made:
If there are logged on users (on the desktop or locked screen), will the software just install in the 3 hour maintenance window and notify the user about the reboot for 24h after the installation?
If there are not logged on users will it install and reboot the computer?
How this kind of thing should be configured so that the computers will reboot in the maintenance window if they automatically do not with these settings (if or if not there are logged on users on the computers) ?

So I tested this:
User logged on during the MW -> Software installation starts at the maintenance window but asks for the reboot from the user so no go here
User not logged on during the MW -> Software installs and reboots straight away
Solution I'm thinking:
Client Settings Collection that includes all the Maintenance Window Collections and I shall deploy different Client settings (where the reboot time is less than the actual MW) to that collection. This could be also handled with "Install only when user is
not logged on" for the application's deployment type but then again I don't think you can do that kind of setting for software updates or do you?

Scheduled system maintenance on AU and EU data centers - March 8th 2015

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our AU and EU data centers. To minimize the customer impact, the upgrade is scheduled at the most convenient hours for the regions and will take up to 6 hours to complete. During the maintenance procedure, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available for sites on all data centers (including US). Additionally, during the 6 hours maintenance procedure, all sites on the AU and EU data centers will experience 2 sessions of 1 minute downtime. Except for the 2 scheduled downtime sessions, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, March 8th, 6:00 AM UTC (check data center times)
Duration: We are targeting a 6 hours maintenance window
Customer impact:
Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin sections will not be available through the entire maintenance window on all data centers
All websites and services on AU and EU data centers will experience 2 sessions of 1 minute downtime sometimes within the maintenance window
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

Congrats to Noah and Mr. X!
System Center Technical Guru - March 2015
Noah Stahl
Make System Center Orchestrator Text Faster than a Teenager using PowerShell
and Twilio
Ed Price: "Wow, I love the breakdown of sections. As Alan wrote in the comments, "Wow! Great article!""
Mr X
How to educate your users to regularly reboot their Windows computers
Ed Price: "I love the table and use of code snippets and images! Great article!"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Scheduler and windows update unavailable / unresponsive,

Issue:
Windows Update & Task Scheduler stop working, RDP then fails and a day later the system eventually becomes completely unresponsive and require a reboots to resolve, servers are needing to be rebooted every week on average.
Environment:
Server 2012: all receive same windows updates and have the same running services and applications installed,
all mirror images of DB01
DB01*Displaying Symptoms mentioned below
DB02*fine
DB03*fine
Non Microsoft Services running:
EMC Backup Agent
AVG Antivirus
Enterprise Recon Node - Ground labs
GFI LanGuard 11
BMC Server Automation Agent
WMware Tools Service
Link to Warnings Link to Errors
Symptoms:
Windows Update is not working
(stuck in stopping state, accessing via control panel is unresponsive)
Task Scheduler not working
it shows a stop sign / busy sign (Service is running, cannot see or create scheduled tasks)
RDP eventually stops working.
Above 3 services are started by the same instance (PID) of svchost.exe , killing the svchost.exe instance that started scheduler and windows update services also kills RDP and is not a solution.
Event Logs:
Warnings - https://drive.google.com/file/d/0B4FtPRuE-MzqdFExQi1EdFpQdEk/edit?usp=sharing
Errors - https://drive.google.com/file/d/0B4FtPRuE-MzqMGZzckRwMnFNWGc/edit?usp=sharing

Hi Fraser,
Thank you for your update and patience.
After going through the logs you provided, please check my findings below.
===============================================
Log Name:      Microsoft-Windows-DeviceSetupManager/Admin
Source:        Microsoft-Windows-DeviceSetupManager
Date:          9/3/2014 6:55:47 AM
Event ID:      201
Level:         Warning
User:          SYSTEM
Description:
A connection to the Windows Metadata and Internet Services (WMIS) could not be established.
Log Name:      Microsoft-Windows-DeviceSetupManager/Admin
Source:        Microsoft-Windows-DeviceSetupManager
Date:          8/31/2014 11:37:33 PM
Event ID:      200
Level:         Warning
User:          SYSTEM
Description:
A connection to the Windows Update service could not be established.
Log Name:      Microsoft-Windows-DeviceSetupManager/Admin
Source:        Microsoft-Windows-DeviceSetupManager
Date:          15/08/2013 1:51:01 p.m.
Event ID:      202
Level:         Warning
User:          SYSTEM
Description:
The Network List Manager reports no connectivity to the internet.
Log Name:      System
Source:        DistributedCOM
Date:          9/3/2014 3:10:41 AM
Event ID:      10029
Level:         Error
User:          SYSTEM
Description:
The activation of the CLSID {E60687F7-01A1-40AA-86AC-DB1CBF673334} timed out waiting for the service wuauserv to stop.
Log Name:      Microsoft-Windows-DeviceSetupManager/Admin
Source:        DeviceSetupManager
Date:          9/1/2014 7:26:06 AM
Event ID:      121
Level:         Error
User:          SYSTEM
Description:
Driver install failed, result=0x80072EE2 for devnode 'TERMINPUT_BUS\UMB\2&2C22BCC9&0&SESSION1MOUSE0'
===========
As per my research, those events which related to Device Setup Manager generated because Device Setup Manager just goes out and pings windows update
every night to see if any devices that are installed and set up to use Windows Update to update the corresponding drivers.
Currently, I suggest we make sure the drivers on your server are all up to date via Device Manager. Meanwhile, please try setting up the Windows Update settings from
installing update automatically to manually installing updates. Then restart the server to monitor the issue.
After all the above, if the issue persists, could you please help collect the following information?
=====================================
1. Run the following command and upload the system information.
msinfo32 /nfo      C:\SYSSUM.NFO /categories +systemsummary
2. Does the issue still occur in Clean Boot mode?
If you have any questions or additional information, feel free to let me know.
Thanks for your time.
Best regards,
Sophia Sun
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

"Waiting for maintenance window" for pre-approved application installed from software catalog

My understanding is that if a user installs an application from the software catalog that does not require admin approval, it should install right away. A user selected an application yesterday which had a prerequisite that needed to be installed (.NET),
it was installed but the published application never was; it's stuck in the "Waiting for maintenance window" category. I manually reboot the PC a few times thinking that would help, but no go. The deployment's checkboxes for "Software install"
and "System Restart" are grayed out so I can't check them, though it's my understanding they don't apply anyway in this situation.
Anyone have any ideas? Also just for my own knowledge, what would cause the Software Install and System Restart checkboxes to be grayed out so they can't be checked?
-Keith
-Keith Elkin

Available deployments are not affected by maintenance windows or business hours. Examine AppEnforce.log and maintenancecoordinator.log. The Monitoring node might also be useful.
Torsten Meringer | http://www.mssccmfaq.de

HT4796 When I run migration assistant on my PC, I get a message saying windows mail is running and won't let me proceed. Windows Mail is not running. I checked Task Manager's applications, services and processes and found no references to Window's Mail.

Got a new iMac 27" for Christmas (well a little after) and tried using Migration Assistant to transfer some files. I can't get past a window on the PC that pops up indicating Quit Other Programs Before you can transfer your information, the following programs must be shutdown: Windows Mail Close these programs and run Migration Assistant again. If these programs do not appear to be running, restart your computer and try again.
I've rebooted. I've searched Task Manager - Applications, Processes and Services and there are no references to WMail. I don't or haven't knowingly used Windows Mail and Outlook isn't even installed on my PC. Does anybody know how to get around this without using external drives, USB flashdrives, etc.

Lots of fun.... The superdrive in my Macbook seems to have gone off kilter since my install. Now the CD-R won't work regardless of which operating system I use. Normal CD's and DVD's are fine, but any CD-R is taken as a blank disk.
Using an external CD drive solved this problem.

Application Scheduling and Maintenance Windows

Similar Messages

Maybe you are looking for