firstcom

Hi Garth! For #1, how do you force WUA to perform a full scan? For #2, can you clarify?

Hello! We have more than 500 desktops currently in our enterprise. Of those, about 3% are being reported as out-of-compliance when they're not. The compliance report, for example, will list patches that are already installed (I've even tried to download them directly from MS again and it states they're installed) or that simply do not apply - for example, .NET 3.5 patches are being marked as required when we're on 4.x with no 3.5 .NETs installed anywhere on the system. The PCs in question have been marked as out of compliance for a couple weeks now, so it's getting annoying. Has anyone run into this before, and know how to get everything synced? Thank you!

Are you looking to build a PC completely offline? If so, you may be looking for the offline media option rather than the bootable media option.

FYI, we just rebuilt the 2nd DP from scratch. After it was complete, the sender.log file shows that packages were sent to the DP, but all 132 packages still show as "in progress" Has anyone seen this before?

When you set up an automatic deployment rule, there is an option that says "automatically enable deployment" Likewise, when you create a software update group, you can set up a deployment. I've set up ADRs for each OS with the appropriate patches that I wish to deploy. I've also set up Software Update Groups for each OS with the same name. Do you need to set up a deployment for the Software Update Groups? What I don't get is that in the ADR, you don't specify a software update group. You simply choose to add an existing software update group or to create a new software update group, but don't specify which one. I've chosen to add to an existing software update group. What's the conjunction between the two and what do you need to deploy to get this to work? When I check "enable the deployment after this rule is run" but DON'T deploy any software update groups, I don't see anything deployed at all. Can someone provide a brief tutorial on this? Thank you!

Anyone have any ideas? :-)

The distmgr.log says: Failed to get valid sitetype for this site $$<SMS_DISTRIBUTION_MANAGER><10-01-2014 13:36:39.392+300><thread=1936 (0x790)> Repeatedly.

New finding: Under Site Hierarchy, we're getting errors stating, "This component failed to retrieve the list of SMS sites from the site database. Possible cause: SQL Server problem"

This DP was created on 8/13. There are SOME packages that have been distributed successfully, but not all of them. This shows that the connection works. On 8/17 we re-configured the DP. There's a line that states that IIS was successfully configured. Some content was distributed but then it stopped taking content again.

The DP is running Windows Server 2012. Everything is up-to-date. The recent status for the DP is a mixture of "Waiting for content" and "Content is being redistributed to the distribution point" The oldest line is "Successfully completed the installation or upgrade of the distribution point on computer" There's nothing but green status marks and green up arrows indicating it's wanting/waiting to transfer content.

All of the packages and applications just say "In Progress" under Content Status. Distribution Manager instructed Scheduler and Sender to send package XXXXXX to child site "XXX"

There is no progress. There's tons of packages and applications of all sizes.

It's been trying for days/weeks. We even re-configured the DP from scratch. As far as I know we have no firewall rules in place that would prevent the connection.

Yes, I can see the files and the admin$ folder. The distribution point status just says "In Progress" There are no alerts. For distmgr.log, which primary site are you referring to? We have a "Central" site and then two primary sites that are also DPs.

We are setting up a second DP in our environment. Files are syncing fine. Resources also seem to be syncing fine. However, when we try to deploy from the second DP, it says packages aren't on it. When you sign into ConfigMgr, it agrees. A majority of the content for that DP states, "Waiting for content" under content status, and "Distribution Manager instructed Scheduler to send package XXXXX to child site XX. When you view the content list for the DP, it's also short. Re-distributing doesn't help. Any ideas on why our content isn't fully syncing?

I am trying to determine if there is a way to get alerted if a user installs a new piece of software on their PC. Does anyone know of a way to get this done? Thank you!

Tried doing a temp file cleanup. Also used CCleaner. Didn't help. :/

C:\ProgramData\Microsoft Help\ doesn't exist. FYI, this is Win7 32bit.

Any other ideas? Has anyone seen or experienced this issue before?

I've tried removing the viewers and then reinstalling and that did not help. Office 2010 was never installed on these PCs, but I've tried the FixIt already and they haven't helped either.

I've been dealing with a pretty frustrating experience installing Microsoft Office 2013 on a few PCs in our enterprise. We have Microsoft viewers installed on these PCs by default and haven't had any issues with installing Microsoft Office over it whatsoever, so I don't believe that's the issue. The "Bootstrapper Setup" keeps crashing when attempting to install it. I discovered that Office creates a log in the %temp% directory. The contents of the log are pasted below. I've Googled every error message, searched extensively, and found a few articles relating to it, but none provide a solution to this issue that I'm experiencing. As troubleshooting steps, I've tried to install a different/new copy of Microsoft Office 2013 in case there were corrupt files. Didn't help. I also tried removing all instances of the Microsoft Viewers and that didn't help. I've tried running it as a domain admin and local admin - neither helps. If anyone can advise on how to resolve this issue or offer some educated troubleshooting ideas, it would be greatly appreciated. 2014/09/05 11:22:22:746::[5564] PERF: TickCount=54866706 Name=OBootStrapper::Run Description=Begin function 2014/09/05 11:22:22:746::[5564] Operating System version: 6.1.7601 Service Pack 1. Platform ID: 2 2014/09/05 11:22:22:746::[5564] Running 32-bit setup on a 32-bit operating system. 2014/09/05 11:22:22:746::[5564] Command line: "C:\Microsoft_Office_Standard_2013\setup.exe" 2014/09/05 11:22:22:746::[5564] No command line arguments given 2014/09/05 11:22:22:762::[5564] Verify file signature in "C:\Microsoft_Office_Standard_2013\setup.exe" 2014/09/05 11:22:22:809::[5564] C:\Microsoft_Office_Standard_2013\setup.exe is trusted. 2014/09/05 11:22:22:809::[5564] Verify file signature in "C:\Microsoft_Office_Standard_2013\standard.ww\OSETUP.DLL" 2014/09/05 11:22:22:840::[5564] C:\Microsoft_Office_Standard_2013\standard.ww\OSETUP.DLL is trusted. 2014/09/05 11:22:22:840::[5564] Using setup controller dll at [C:\Microsoft_Office_Standard_2013\standard.ww\OSETUP.DLL]. 2014/09/05 11:22:22:840::[5564] PERF: TickCount=54866799 Name=OBootStrapper::Run Description=Calling RunSetup 2014/09/05 11:22:22:840::[5564] PERF: TickCount=54866799 Name=RunSetup Description=Begin function 2014/09/05 11:22:22:840::[5564] WER element [P2] is set to value [OSETUP.DLL] 2014/09/05 11:22:22:840::[5564] WER element [P3] is set to value [15.0.4569.1503] 2014/09/05 11:22:22:840::[5564] Catalyst execution began: 09/05/2014 11:22:22. 2014/09/05 11:22:22:856::[5564] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [installExecutionMode] 2014/09/05 11:22:22:856::[5564] Searching for updated versions of resource files under the 'updates' folder [C:\Microsoft_Office_Standard_2013\updates]. 2014/09/05 11:22:22:856::[5564] Found [0] resource files under the update folder. 2014/09/05 11:22:22:856::[5564] Searching for default versions of resource files under the folder [C:\Microsoft_Office_Standard_2013]. 2014/09/05 11:22:22:856::[5564] Found [1] resource files under the default folder. 2014/09/05 11:22:22:856::[5564] Running in [installExecutionMode]. Run from TEMP folder at [C:\Users\wrplume\AppData\Local\Temp\Setup00001ff4]. 2014/09/05 11:22:22:871::[5564] Loaded resource file [C:\Users\wrplume\AppData\Local\Temp\Setup00001ff4\OSETUPUI.DLL] (CultureTag=en-US). 2014/09/05 11:22:22:871::[5564] WER element [suppressModal] is set to value [false] 2014/09/05 11:22:22:871::[5564] WER element [P1] is set to value [15.0.4454.1000] 2014/09/05 11:22:22:871::[5564] Loaded Dll : C:\Microsoft_Office_Standard_2013\standard.ww\OSETUP.DLL. 2014/09/05 11:22:22:871::[5564] Catalyst version is : 15.0.4569.1503 2014/09/05 11:22:22:871::[5564] JobExecutionMode is InstallExecutionMode. 2014/09/05 11:22:23:012::[5564] Check if Office is supported on Windows 6.1.7601 2014/09/05 11:22:23:043::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:043::[5904] LIS: finished parsing LIS package "{90150000-0016-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:043::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:043::[5904] LIS: finished parsing LIS package "{90150000-00BA-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:043::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:043::[5904] LIS: finished parsing LIS package "{90150000-0115-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:043::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:043::[5904] LIS: finished parsing LIS package "{90150000-0116-0409-1000-0000000FF1CE}" 2014/09/05 11:22:23:043::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:043::[5904] LIS: finished parsing LIS package "{90150000-00A1-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:058::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:058::[5904] LIS: finished parsing LIS package "{90150000-00E1-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:058::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:058::[5904] LIS: finished parsing LIS package "{90150000-00E2-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:058::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:058::[5904] LIS: finished parsing LIS package "{90150000-001A-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:058::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:058::[5904] LIS: finished parsing LIS package "{90150000-0018-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:058::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:058::[5904] LIS: finished parsing LIS package "{90150000-002C-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:058::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:058::[5904] LIS: finished parsing LIS package "{90150000-0019-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:074::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:074::[5904] LIS: finished parsing LIS package "{90150000-0012-0000-0000-0000000FF1CE}" 2014/09/05 11:22:23:074::[5904] LIS: start parsing setup xml 2014/09/05 11:22:23:074::[5904] LIS: finished parsing LIS package "{90150000-001B-0409-0000-0000000FF1CE}" 2014/09/05 11:22:23:074::[5904] Product: STANDARD 2014/09/05 11:22:23:074::[5904] AddOnGroup Culture: en-us 2014/09/05 11:22:23:074::[5904] AddOnId: WORD.EN-US 2014/09/05 11:22:23:074::[5904] AddOnId: PUBLISHER.EN-US 2014/09/05 11:22:23:074::[5904] AddOnId: OFFICE.EN-US 2014/09/05 11:22:23:074::[5904] AddOnId: OUTLOOK.EN-US 2014/09/05 11:22:23:074::[5904] AddOnId: PROOFING.EN-US 2014/09/05 11:22:23:074::[5904] AddOnId: OSM.EN-US 2014/09/05 11:22:23:074::[5904] AddOnId: OSMUX.EN-US 2014/09/05 11:22:23:074::[5904] AddOnId: GROOVE.EN-US 2014/09/05 11:22:23:074::[5904] AddOnId: ONENOTE.EN-US 2014/09/05 11:22:23:074::[5904] AddOnId: EXCEL.EN-US 2014/09/05 11:22:23:074::[5904] AddOnId: POWERPOINT.EN-US 2014/09/05 11:22:24:041::[5564] No upgradable applications found 2014/09/05 11:22:24:041::[5564] Parsing config.xml at: C:\Microsoft_Office_Standard_2013\standard.ww\config.xml 2014/09/05 11:22:24:041::[5564] Preferred product specified in config.xml to be: STANDARD 2014/09/05 11:22:24:041::[5564] Product Deployment Mode: PerMachineManaged 2014/09/05 11:22:24:041::[5564] Target Deployment Account Security Identifier: S-1-5-18 2014/09/05 11:22:24:041::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\office.en-us\OfficeMUI.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\office.en-us\OfficeMUISet.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\powerpoint.en-us\PowerPointMUI.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\excel.en-us\ExcelMUI.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\onenote.en-us\OneNoteMUI.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\groove.en-us\GrooveMUI.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\osmux.en-us\OSMUXMUI.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\osm.en-us\OSMMUI.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\proofing.en-us\Proof.es\Proof.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\proofing.en-us\Proof.fr\Proof.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\proofing.en-us\Proof.en\Proof.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\proofing.en-us\Proofing.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\outlook.en-us\OutlookMUI.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\publisher.en-us\PublisherMUI.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\word.en-us\WordMUI.xml 2014/09/05 11:22:24:057::[5564] Loading package metadata: C:\Microsoft_Office_Standard_2013\standard.ww\StandardWW.xml 2014/09/05 11:22:24:057::[5564] Searching for patches for the current chained install in: C:\Microsoft_Office_Standard_2013\updates 2014/09/05 11:22:24:057::[5564] Applicable patch: C:\Microsoft_Office_Standard_2013\updates\FCCU_BackOffice.MSP 2014/09/05 11:22:24:088::[5564] Display level basic specified in config.xml. 2014/09/05 11:22:24:119::[5564] OS check result: 0x00001150 2014/09/05 11:22:24:182::[5564] Reading value of unintialized setting! 2014/09/05 11:22:24:228::[5564] BRANDING: Parsing Branding Data... 2014/09/05 11:22:24:244::[5564] BRANDING: Parsing Branding Data... 2014/09/05 11:22:28:908::[1884] Kicking off chained install... 2014/09/05 11:22:28:908::[1884] PERF: TickCount=54872868 Name=Job::DoCacheWork Description=Begin function 2014/09/05 11:22:31:030::[1884] OSE is detected as a registered service. Service binary is reported at location: C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE 2014/09/05 11:22:31:030::[1884] OSE service binary is detected at location: C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE 2014/09/05 11:22:31:030::[1884] OSE is avaliable at C:\Program Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE 2014/09/05 11:22:31:030::[1884] This OSE has version: 11.0.5525.0000. Skip using this version of OSE because its version is too low. 2014/09/05 11:22:31:030::[1884] Running Source Engine process detected 2014/09/05 11:22:31:030::[1884] Running version: 11.0.5525.0000 2014/09/05 11:22:31:030::[1884] Error checking already running ose version. Error code 0x00000000 2014/09/05 11:22:31:030::[1884] Stopping running the problematic Source Engine process 2014/09/05 11:22:31:030::[1884] Error attaching to OSE, error 0x00000000 2014/09/05 11:23:46:565::[1884] Cannot start standalone OSE. from C:\Microsoft_Office_Standard_2013\standard.ww\ose.exe. Error code: 0x80070102 2014/09/05 11:23:46:565::[1884] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError. 2014/09/05 11:23:46:565::[1884] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError. 2014/09/05 11:23:46:565::[1884] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError. 2014/09/05 11:23:46:565::[5564] WER element [suppressModal] is set to value [true] 2014/09/05 11:23:46:565::[5564] WER element [P4] is set to value [unexpectedError] 2014/09/05 11:23:46:565::[5564] WER element [P7] is set to value [unexpectedError] 2014/09/05 11:23:46:565::[5564] WER element [P6] is set to value [unable to select Source Engine process to start, see debug level logs for detail] 2014/09/05 11:23:46:565::[5564] WER element [P6] is converted to [C6F06531] 2014/09/05 11:23:46:565::[5564] Error: Unable to select Source Engine process to start, see debug level logs for detail Type: 88::UnexpectedError. 2014/09/05 11:23:46:580::[5564] Catalyst execution finished: 09/05/2014 11:23:46. Return code: 30088. Exception caught: UnexpectedError. 2014/09/05 11:23:46:580::[5564] PERF: TickCount=54950540 Name=RunSetup Description=End function

Bump!

Hi all, I'm in the process of upgrading Adobe Reader utilizing SCCM 2012R2 with SCUP. On most PCs, we have version 11.0.0 and I'll be using the SCUP-imported software update to upgrade those to 11.0.7. However, other PCs have 11.0.04, 11.0.02, and other various versions. The Adobe update for 11.0.7 that was imported from SCUP seem to be failing on these. Is there an easy way to upgrade PCs with versions > 11.0.0 without having to uninstall and reinstall Reader? Can anyone advise?

After reviewing netsetup.log during the actual OS deployment, it doesn't look like it's attempting to connect to the domain at all. It is simply joining a default workgroup. It's in the task sequence, however, and works with a network-based deployment. I need to figure out a way to make this work when using stand-alone media that isn't too burdensome.

I just realized -- this log contains info AFTER the image and when I went in and joined the domain manually. It actually works when I do it post-imaging. I'll have to see if I can get a log where it doesn't successfully join.