firstcom

How do you handle Java deployments/upgrades?

I already get the MSIs from the executables. That's what I use...

Yes please!

Good morning all, Can I get some detailed feedback on how folks deploy Java 8 updates? I've got mine set up as an application with supersedence rules to remove old versions. However, the new install often errors out with code 1603. I'm trying to deploy Java 8 Update 65. The install works fine when msiexec is called from the local command line on the PCs, but not when it's deployed from SCCM. It's set up to run as Administrator, etc. The command line I'm using is: msiexec /i "jre1.8.0_65.msi" AUTO_UPDATE=0 EULA=0 NOSTARTMENU=1 SPONSORS=0 WEB_ANALYTICS=0 WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H /qb If you're using some kind of script, please share the script. If you somehow managed to get it to install as a simple application configured within SCCM, please share your parameters and details. I'd appreciate any input and assistance that anyone can provide. Thanks all!

Hello! We are trying to deploy wake-on-lan functionality within SCCM 2012 to all of our networks. I've tried various scripts, and even manually enabling it on the network adapter. A majority of our desktops use a RealTek PCIe GBE Family Controller driver, but when we enable "Wake on Magic Packet" in advanced settings, a few moments later it reverts back to disabled. The BIOS has wake-on-lan enabled, but the network adapter simply isn't having it. Has anyone seen this before? We really need to get wake-on-lan functioning. Thank you!

I'd love to hear from those of you that have a similar set up as our environment. We have an external WSUS server and two SUPs -- one as a primary and a disaster recovery SUP. Best practice suggests using one database for multiple SUPs, but obviously in a DR situation we'd want a completely separate database in our DR datacenter - so that can't apply in that scenario. I was told it was a best practice to let SCCM handle all WSUS administration, but I've also read articles stating that WSUS needs to be pruned and cleaned up regularly. I don't think these articles were users that utilized SCCM in combination with WSUS, however. Within SCCM, I have set it to expire superseded updates after one month. Our WSUS server has around 14,000 total updates. In SCCM, I have divided our update groups into OS or product, as recommended by best practice guides. We fall within guidelines of having 1000 or less updates per update group, with the largest having around 600-700. However, I'm curious if the WSUS side of things is being kept to best practice with this scenario/environment. Should I be pruning it and performing clean ups, or should I let SCCM handle it entirely? Thank you!

Peter, The problem is when PCs are shut down, etc... You can only set a single "available" time/date. So while that'll work in a perfect world where all PCs are powered on, if some PCs are powered on the next day then I don't want that traffic pulling during business hours. Wake-on-LAN is not an option. I don't want it deploying (transferring, installing, or ANYTHING) during the day. How do I achieve this?

Hi, We're running into an issue where deployed applications are being downloaded (but not installed) before they are supposed to. Maintenance windows are configured and the applications are not set to disobey the maintenance windows, but we're seeing network traffic spike and applications being downloaded according to CITaskmgr.log. What could be causing this to happen?

When PXE booting and imaging a PC, it fails on numerous (perhaps all) applications with the error of 80040104, failed find CCM_ApplicationCIAssignment for AdvertID = "xxx" If I find and disable that particular application, it seems to just proceed to the next application. The applications in question all show as distributed. I've attempted to re-distribute and it shows success. distmgr.log shows no warnings or errors. I've even tried to delete an application and re-create it from scratch, and they still bomb. Does anyone have any suggestions?

The AI is only installed on the CAS. ConfigManager doesn't even let you install it on the primary. I even tried to remove the role completely from the CAS to see if that would help since we don't fully use ConfigManager for AI, but it's still giving a database replication error.

I'm in a situation where I have a ConfigManager environment that's unusable and in need of troubleshooting, however I have an immediate need to image some PCs. I do have a thumb drive from a prior task sequence offline media image, but it's failing at a specific app. Is there a way, within the PXE session (perhaps on the F8 DOS screen?), to set something to force it to proceed on error with any application?

This replication issue is still an issue for us, and it has now rendered our ConfigManager environment unusable. Is there /anyone/ on these forums that is familiar with resolving these issues?

Any tips?

Hi, We have a CAS (FCC) and a Primary Site (HQ1). Our primary site has all of a sudden gone into maintenance mode, and I can't figure out how to resolve the issue. After looking at Google, I found that I needed to look at rcmctrl.log due to a failed replication between our CAS and Primary server. In that log, the only thing that stands out is a message that states: Error: Replication group "Asset Intelligence Knowledge Base" has failed to initialize for subscribing site HQ1, setting link state to Error. $$<SMS_REPLICATION_CONFIGURATION_MONITOR><07-27-2015 10:16:33.489+300><thread=4664 (0x1238)> Can anyone help me figure out how to resolve this and get things working again? We really need full access to our ConfigMgr environment. Thank you!

I'm having trouble with SCCM not updating deployment status and compliance. I have some applications that I've deployed the past few days and that are clearly installed on PCs, but when you look at Deployments on the Monitoring tab, they're showing no data and compliance is at 0%. What would cause this?

Hi all! We have a SCCM 2012 R2 environment and I'm trying to generate a report of certain model PCs that we have in each of our 40 locations. The problem is, there isn't a report that drills this down. The Hardware 09A report under Asset Intelligence is probably the closest thing, but I'd like to figure out a way to add the Active Directory group that the device belongs to. Can anyone provide step by step or a good guide on how to accomplish this?

Still stuck on this issue! Bumping this post to see if anyone has thoughts... Has anyone seen this before?

Can anyone advise or provide input?

5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Running rule: IsSiteActive. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Running rule: <IsSiteActive SourceSiteCode="FCC" TargetSiteCode="HQ1" ></IsSiteActive> 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for High_Priority_Site from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Collection_Membership from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Medium_Priority_Site from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for EndpointProtection_Site from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for General_Site_Data from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for CI_Compliance_Rule_Details from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for CI_Compliance_Status_Details_and_History from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Software_Inventory_and_Metering from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Status_Messages from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for MDM_Site from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for MDM_SiteSpecial from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for CFD_Site from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_1 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_2 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_3 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_4 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_5 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_6 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_7 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_8 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_9 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_10 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_11 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_12 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_13 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_14 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_15 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_16 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_17 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_18 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_19 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_20 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_21 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_22 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_23 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_24 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is in progress for Hardware_Inventory_25 from publisher HQ1. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : Initialization is failed for replication group Operational_Data. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : RLA detected no re-initialization for the group Operational_Data in last 24 hours. 5/15/2015 9:37:37 AM: ReplicationLinkAnalysis Information: 1 : BCP in failed for Operational_Data for tables DrsSendHistorySummary. 5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : All links are initialized between subscriber HQ1 and publisher FCC. 5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Getting results of rule: IsSiteActive execution 5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Loading result Xml from rule:IsSiteActive 5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : rule:IsSiteActive has some dependent rules 5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Working with parent rule:IsSiteActive -> dependent rule:DoesFileReplicationRouteExist 5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Appending result xml 5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Rule IsSiteActive result: failed. 5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Rule: IsSiteActive failed. Stopped running replication link analysis rules. 5/15/2015 9:37:38 AM: ReplicationLinkAnalysis Information: 1 : Completed replication link analysis thread.

We use SCCM 2012 R2 and have a "Central" ConfigManager server (site code FCC) as well as two primary servers: our main server that we use for almost everything (HQ1), and a disaster recovery ConfigManager server (DR1) that we'd like to replicate from what we do on HQ1. So the hierarchy is: FCC / \ DR1 HQ1 Under the monitoring tab, in the Site Node Status, it shows a red "X" between FCC and HQ1. It's apparently been this way for some time, but I'd like to get it resolved. When you hover over it, it shows for "Global Data Replication Status" that HQ1 to FCC and FCC to HQ1 is green and active. However, for "Site Data Replication Status" for HQ1 to FCC, it's red and shows a failed status. When I right click and run a report for errors, nothing really stands out as problematic that's recent that would explain the communication/replication issue between HQ1 and FCC. When I run the Link Analyzer tool, I see errors about "Site is NOT active, so not calling the DrsActivation procedures on DRSSite queue" and errors about the "IsSiteActive" rule being false. 5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : All links are initialized between subscriber HQ1 and publisher FCC. 5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Getting results of rule: IsSiteActive execution 5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Loading result Xml from rule:IsSiteActive 5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : rule:IsSiteActive has some dependent rules 5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Working with parent rule:IsSiteActive -> dependent rule:DoesFileReplicationRouteExist 5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Appending result xml 5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Rule IsSiteActive result: failed. 5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Rule: IsSiteActive failed. Stopped running replication link analysis rules. 5/18/2015 2:27:06 PM: ReplicationLinkAnalysis Information: 1 : Completed replication link analysis thread. I should note that everything seems to be working just fine with our primary server, HQ1, and even our central server, FCC. However, this warning has persisted for some time. Replication to DR1 hasn't been working, however, which I suspect may be related. Can anyone tell me where to look to figure out why we're getting this warning/error, or how to resolve it? Thank you!

Hello! This post is the first part to a two-part question. We use SCCM 2012 R2 and have a "Central" ConfigManager server (site code FCC) as well as a "main" ConfigManager Server (HQ1), and a "disaster recovery" ConfigManager server (DR1) that we'd like to replicate from HQ1. So the hierarchy is: FCC / \ DR1 HQ1 Under the monitoring tab, in the Site Node Status, it shows a red "X" between FCC and HQ1. It's apparently been this way for some time, but I'd like to get it resolved. When you hover over it, it shows for "Global Data Replication Status" that HQ1 to FCC and FCC to HQ1 is green and active. However, for "Site Data Replication Status" for HQ1 to FCC, it's red and shows a failed status. When I right click and run a report for errors, nothing really stands out as problematic that's recent that would explain the communication/replication issue between HQ1 and FCC. Can anyone tell me where to look to figure out why we're getting this warning/error, or how to resolve it? Thank you!

I'll have to look into the roll-up to see if that has been applied, as well as Exchange logs... I did check event logs on the Service Manager server and didn't see anything that stood out. I haven't checked Exchange yet because it seems to be Service Manager related - it's the only thing we've had trouble with email-wise, and it catches up upon rebooting the Service Manager server. Timing doesn't seem to be consistent, but it does seem to last a good week or so upon each reboot.

Hi! Sorry for the delay in getting back. We do not use SCOM at all. Just SCCM and SCSM. For SCCM we do not use notifications of any kind, either.

We have Service Manager installed and configured to send email notifications when tickets are placed or updated. We also have it emailing for high priority tickets. At random, usually about every 1 to 2 weeks or so, these notifications stop getting sent. Once we reboot the server, it "catches up" and flushes out all pending emails and notifications. Does anyone know why this would happen?

Update: I tried another PC and it seems to be working okay so far. Weird!