Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About steve11

  • Rank
  1. Thanks again Hotdog. I have updated the WUA to 7.6.7601.18937 which appear to have removed the earlier errors but I am not faced with further errors. The updatesstore.log is showing: Failed to refresh Resync state message. Error = 0x87d00310. The updatesdeployment.log is showing: InstallMandatoryUpdates failed, error 87d00708 It appears to be quicker now but basically the same result. The UpdatesStore.log is also reporting "Querying update status of 57 updates." which is exactly how many updates are available in the Deployment Package. I don't feel comfortable with starting afresh with using WSUS, but feel at this stage if I cant progress I will use offline servicing to install updates. Any thoughts on my continuing problem or this path would be great! WindowsUpdate.log UpdatesStore.log UpdatesDeployment.log WUAHandler.log smsts.log
  2. Thank you Hotdog, but still no luck here after I installed the latest WUA (7.6.7600.320) Still Timing out waiting for the updates refresh to complete and running. I have attached latest relevant logs if needs be. WindowsUpdate.log smsts.log
  3. I am trying to build and capture a Winddows 7 X64 Image using SCCM 2012 R2 (SP1). I have also installed Cumulative Updates 1 for R2 SP1 and made sure the client Patches CU1 during setup. I have been using Software Updates to clients on the Domain successfully but the OSD is failing to complete with the error "timeout period expired. Error: 800705B4" in the SMSTS.log (see attached). I have ensured the Client install includes the following (note the FQDN is different to this, trying to not publish to the world): SMSMP=server.com SMSSLP=server.com DNSSUFFIX=com I have added the hotfix KB2522623 and also included the following command prior to the updates: WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE I have made sure the client correctly connects with an IP on the active Boundary. Also I have made sure the updates are correctly Distributed to the DP. I am at a loss for what is happening here? Please see SMSTS.log, SoftwareUpdates.log, UpdatesHandler.log, UpdatesDeployment.log, UpdatesStore.log, and WUAHandler.log below for more info. Here is excerpt from SMSTS.log when it fails: executing command: C:\Windows\system32\cmd.exe /k executed command: C:\Windows\system32\cmd.exe /k FALSE, HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1273) Timedout waiting for updates refresh complete notification WaitForRefreshUpdatesComplete(spInstall), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1331) RefreshUpdates(), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,923) InstallUpdates(pInstallUpdate, tType, sJobID, sActiveRequestHandle), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\main.cpp,248) Setting TSEnv variable SMSTSInstallUpdateJobGUID= Process(pInstallUpdate, tType), HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\main.cpp,302) Process completed with exit code 2147943860 !--------------------------------------------------------------------------------------------! Failed to run the action: Install Software Updates 1st Pass. This operation returned because the timeout period expired. (Error: 800705B4; Source: Windows) MP server http://SERVER.comPorts 80,443. CRL=false. Setting authenticator Set authenticator in transport Sending StatusMessage Setting message signatures. Setting the authenticator. CLibSMSMessageWinHttpTransport::Send: URL: SERVER.com:80 CCM_POST /ccm_system/request Request was successful. Set a global environment variable _SMSTSLastActionRetCode=-2147023436 Set a global environment variable _SMSTSLastActionSucceeded=false Clear local default environment The execution engine ignored the failure of the action (Install Software Updates 1st Pass) and continues execution smsts.log UpdatesDeployment.log UpdatesHandler.log UpdatesStore.log WUAHandler.log WindowsUpdate.log
  4. We are seeing a problem where the Windows 7 SP1 OSD wrongly exits to the Ctl-Alt-Del screen: This problem is occuring with about %25 of our Newly Imaged PCs during the Software Updates step of the Task Sequence. The only consistent error in the smsts.log is as follows: Failed to set log directory. Some execution history may be lost. The system cannot find the file specified. (Error: 80070002; Source: Windows)The Updates are 2532531, 982018, 2529073, 2732487 and do not include any Service Packs - and I have tried with "Continue on error" ticked and unticked. Also after the reboot the system is definately getting a vaid IP address. See OSD Task Sequence for where the it fails/exits the OSD without completion.
  5. Thanks Peter, Thought this was the case. If I were considering to upgrade to SCCM 2012 will this allow me to deploy expired updates?
  6. I work in a SCCM 2007 environment that requires lengthy User Acceptance Testing which delays updates being deployed immediately. I am underresourced to deploy updates every month and therefore I have a lot of expired updates that need deploying in between my update cycles. If I deploy updates without testing I run the risk of stopping critical apps from working (particularly Web apps from experiance) as a result of untested patches. Is there any way to perhaps "Un-Expire updates" as I understand the only workaround seems to be to put each individual update into a software distribution package and deploy that way which is very tedious.
  7. Hi Trevor, as I said, I did try the Task Sequences but they are problematic if there are dependant programs which require reboots in between. I have found that in a TS, when a reboot occurs, the secondary program does not work as it does when in a OSD Task Sequence. Fot these I cant reset the return code to 0 (when a 3010 code is given) as vendors are enforcing a full reboot in between dependant applcations.
  8. Thanks Peter: I like the logic of a vbscript encapsulated installed but hve avoided this as for me it goes against the reason for using SCCM. Assuming that I chose this option I was thinking that we have approx a dozen applications (like Office, Adobe Reader, Flash, Primo PDF, as well as some other 3rd party Business apps) - which I was wanting to persist in the users "Run advertised programs". This would allow ad hoc reinstalls if the application needed a reinstall. This would mean that we would have 12 x 700 advertisements persistent on our network all the time. Would the servers be able to handle 8400 pending advertised programs? By the way I cant always reset the return code to 0, in particular I have a large app that is require to be reinstalled if Office is installed - the vendor have made a strict rule that the PC must be rebooted after Office is installed (which is before the app itself is installed) Thanks Lucid: This option you have given is the most appealing to me becuase it minimises the number of pending advertised programs to a minimum. The only problem here is if a user needs a reinstall of an app, once it is uninstalled you are reqiured to do the following to install it again: 1)Force Hardware inventory (wait several minutes for completion) 2)Update the appropriate collection to force qery to run, and wait until the PC appears 3)Force Machine Policy Update to download advertisement/package 4)Go into "Ran advertised programs" and run the installer ** I have tried to simplify this process using "SCCM Client Centre" or the "Right click" tools, and even tried to make a vbsript to step through this sequentially but either way its a little messy and I would like to know if anyones experiences with this style of persistent installer are good?
  9. Thanks for the Task Sequence option, however I have found TS are problematic if there are dependant programs which require reboots in between. After reboots in a TS forcing the secondary program does not work as it does when in a OSD Task Sequence. I have changed my thinking on this - if I set no mandatory assignments and allow the install to be controlled ONLY by using the "Run advertised programs" icon, this safeguards the application being reinstalled by mistake. This introduces one issue: if I make this Advertisement available to all PCs wont this A: Put a heavy load on the servers B: If the advertisement is set to download content, the local cache on all PCs will be overloaded with these "persistent" adverstisements?
  10. Ok Peter thanks for the tip - However I realise creating a second advertisement is not good and hence the reason for posting this. Asking for a "Best Practice" on this matter may be asking for too much, so instead I would like to know if I am installing applications like Office 2007, Adobe Reader, Adobe Shockwave, etc out to approx 700 desktops and I need to occasionally reinstall those applications if they are misbehaving - how do go about doing this? I do not want to user Task Sequences for this purpose as my current deployments are using simple Program Advertisements and they work great. I would like to follow a query based solution here which determines if the program has been removed and reinstalls automatically - As I stated earlier this has its own flaws:
  11. I need to reinstall successfully installed programs in SCCM 2007 R3. This may be needed anywhere from several days to several months after the program is deployed. I need this when the client has problems relating to the program and it needs to be reinstalled. My original advertisements are all set to "Rerun if failed previously". This works perfectly when the deployments do fail. I have avoided setting this to "Always rerun program" as this will keep installing the same program over the top at any subsequent Mandatory assignment - that is the last thing I want! I have tried creating a 2nd Collection and a 2nd Advertisement set to "Always rerun program", and only used this when I need to reinstall... This is a messy workaround that I want to avoid. What is my best option (best practice) here? Note: I have seen that I could create all my Advertisements = "Always rerun program" and set the Collections to populate based on a Query for whats missing in "Add/Remove programs". I am concerned with this option as the Software Invertory cannot be forced real time therefore the Advertisement will be out of sync with whats actually installed on PCs. This could have the effect of [a] Reinstalling over the top and Not reinstalling until the next Software Inventory which could take several hours. Note2: I have tried the Right Click tools but always get the following execmgr.log error: The program Office Upgrade will not run because it has been run before and it succeeded and policy indicates it should rerun only it it has previously failed. execmgr 13/07/2011 14:05:36 3092 (0x0C14)
  • Create New...