cldpeak
Posts: 270
Score: 6 Joined: 7/11/2002 Status: offline
|
I have a software update package that deploys .NET 2.0 & .NET 3.0 Our org resists enforced reboots - so I have a past, non-recuring maintenance window on the collection and suppress reboots enabled in the package. When the user received notification that a Software Update was available, the "Schedule Installation" button to allow the user to "Install required updates on a shedule" did not work until I added a deadline to the package far into the future. This seemed to work as the .NET 2.0 Update launched and installed at the user defined schedule. However, in the same packate .NET 3.0 won't install. I've gone through a couple of user schedules and at the user defined time, Updates does launch but here is what I see in UpdatesDeployment.log: - Message received: '<?xml version='1.0' ?><SoftwareUpdatesMessage MessageType='EnforceMandatoryUpdates'/>' - No current service window available to run updates assignment with time required = 1800 - No current or future service window available to run updates assignment with time required = 1800 - No service window defined to accommodate at least one update in the assignment - No service window available on user defined schedule. Installation will be retried on next schedule. Anybody run into this? Thanks! Ray
|