firstcom

Hey ej! In my prior post I explained that other apps like the SolarWinds WOL tool works fine - I was able to use it to wake up the same PC I am targeting with SCCM. It works with SolarWinds but not with SCCM. I've tried both Unicast and Subnet directed, and tried both UDP ports 9 and 7. No luck. :/ Any other ideas??

Hi all, I'm trying to get SCCM to work with it's internal "wake on LAN" functionality. I have PCs that work with wake-on-LAN using other tools, such as the free tool from SolarWinds, but when I attempt to deploy something with Wake-on-LAN enabled in SCCM, it doesn't actually wake the PC up. The configuration options in Site Properties are pretty limited and I didn't think this would be a complex thing to set up. I choose to enable WOL, enable wake-up packets only, and to send them via Unicast (the target group mostly uses static IPs) -- I did try subnet as well but it didn't work. Reviewing logs, I checked wolmgr.log and wolcmgr.log. The only thing out of the ordinary that I notice is a line stating, "Warning: The xxx*.WKP file is missing wakeup instructions. This file will be ignored and deleted." Anyone have any ideas??

This hot fix resolved the issue! What a pain! Glad it's resolved, though! I'd suggest to any SCCM administrators to investigate the aforementioned KB and consider deploying it 100% to their environment. It's a tricky one that required a good eye to catch!

Update #2: I performed a manual "Update Scan" and then "Update Deployment Scan" on one of the impacted workstations after applying the patch, and it seems to be processing updates now! I'm waiting for everything to complete to check for sure.. Please be aware of this issue!!! It's very sneaky. SCCM will report that impacted PCs are in compliance when, in fact, the bug is the client being misled into thinking all updates are "not required"! The patch for this bug was NOT considered a security update OR a critical update.

So I found KB3112343 today, which actually describes my issue spot-on. Unfortunately, the patch and a reboot didn't resolve it. I'm really hoping someone on these forums have seen or experienced this!

After uninstalling WSUS, re-installing, and re-syncing, I've deleted all ADRs, deployment packages and software groups. Initialized a re-sync. The impacted PCs are still experiencing the same issue. Garth, et al - any advice on where I can look next? This is, needless to say, frustrating to experience. Thank you!

I am now in the process of deleting all ADR's, deployment packages, and software groups and forcing SCCM to re-sync across the board. We'll see if that works!

In UpdatesDeployment.log, I can see updates getting added to the targeted list. In UpdatesStore.log, I can see it querying the status of updates. In WindowsUpdate.log I can see lines that say "Added Update { ... } to search result.. I do see occasional warnings that say ISusInternal::GetUpdateMetadata3 failed, hr=8007000E

I can initiate a Software Update Scan, SoftwareDeployment scan, etc and watch the logs process the request...

WindowsUpdate.log does suggest that it's connecting through my configmanager server. I've been reviewing WindowsUpdate.log in C:\Windows, and UpdatesDeployment.log and UpdatesStore.log.

An update on this issue: I re-installed our WSUS environment last night. It re-synced with SCCM. Everything seems to be up and running and 100%. Logs look good. However, the problem persists. * On one example PC, it shows no updates available when you check through WSUS. However, when you check online, there's 80 - some of which are security/critical updates, which is what we target. * When you pull up this specific PC in SCCM reporting for updates, it shows up blank. * WindowsUpdates.log suggests "Found 0 updates and 91 categories in search" and "0 updates detected" Does anyone have any clue why this is happening? Windows should not be showing as compliant and the reports for this specific should not show as blank. Updates ARE available.

Also, if you install some of the recently released updates manually, they DO install.

Hi all, I've come across some workstations in our environment that don't show as out of compliance in SCCM, but when you run a Compliance 5 - Specific computer report on it to view updates, they are blank. If you go in to view installed updates on the PC, they aren't up to date or show as failed. Has anyone seen this before and know what steps can be taken to troubleshoot? Thank you!

Some of our applications pull things down when installed when a network connection is present. Otherwise it doesn't. So I'd like an easy way to differentiate when an image is happening over a network PXE or when it's offline media.

I was wondering if anyone knows of a way to have a task sequence only execute a task if the task is happening over a network connection and not if it's being done via offline media?

I believe I figured out the issue -- I needed to enable anonymous access to PXE. This somehow got unticked and seems to be the culprit.

So I've added logging parameters to all of the applications. It bombs on the first one and doesn't even produce a log file. It almost seems like the applications aren't even making it to the PC... I do not see an appenforce.log anywhere on the workstation to be imaged.

Thank you! This script/method looks pretty solid. I'll give this a shot. Do you run into errors during Java installation? That's the issue I've been having -- occasional errors/failures during installs.

I apologize -- we are on SP1 CU2. We upgraded to it recently and I forgot about it completely. I'm doing additional testing with more verbose logging on the applications now. It almost seems like it's ANY application in the capture task sequence that's failing.

Anyone have any troubleshooting tips for something like this? Any assistance would be appreciated!

Hey anyweb! Sorry for the delay in my response. I had taken a few days off but I'm ready to tackle this issue again. We're running SCCM 2012 R2, CU5 This one has just mystified me completely. I've not had any issues with applications deploying in other task sequences at all. I can try and insert one of these applications into a task sequence that I know works next, but that still won't give me many definitive answers -- especially since I've already built out a new task sequence for this capture process. Any ideas? It'd be very appreciated!

Hey all, I've got a mysterious one here... I'm trying to go through our capture task sequence over the network to update our base golden image, but it keeps failing when installing some applications. The configuration for these applications look okay. I've tried to rebuild a completely new task sequence and everything. I've attached some example logs -- can anyone tell me what they see or point me into the direction of some other logs to help me determine what's causing these failures? Programs install fine, but applications seem to be bombing... Thank you! smsts 1.log smsts 2.log smsts.log

With the answers so far I've read various solutions but nothing that stands out to me as a consistent and concrete deployment method. I'd love to hear details from others on how they deploy Java.

I have looked at all of the log files that I've read about and haven't found anything that indicates a problem. Then again, many of the articles out there in regards to replication aren't always the most straightforward. I'm still getting emails with alerts periodically about replication being down, even though the link shows as active and green. I wasn't aware that everything had to be done on the CAS, but I can adjust going forward. Can you provide any guidance on the errors and replication issue?

Hey all! I was looking over our ConfigManager environment and noticed something unusual. When I came into the company I'm part of, they had an existing ConfigManager environment with a CAS and two primary sites -- one that they use often, and the other acts as a DR server. Very rarely have I had to sign into the CAS. However, I noticed something that seems unusual. Before I go into this, I'll say this: The link between all servers show as active, with no errors. However, when the replication link analyzer is run on the CAS or the primary server, it suggests resetting queued replication messages on the SQL server. If you do it, it says it's successful - however, it repeatedly suggests having to do it. Everything else besides that shows up as green and good on the replication link analyzer. If you finally choose to skip resetting queued messages, it suggests there may be some messages stuck in the transmission queue on the primary site. Has anyone seen this before? How can I resolve it? On what could be an unrelated note, under the monitoring tab for database replication, *everything* shows as green on the primary server. On the CAS, everything under every tab shows as green except for "Secondary Site Data", "CloudDmp" and "Secondarty_Site_Replication_Configuration" -- I've tried to google research this, but haven't come across much. If anyone has seen or knows anything about either one of these items, please respond and let me know!