Kevin79

Anyone?

Nothing that I see.

SCEP is not currently installed. SCCM uninstalled it when it tried to run the upgrade. There isn't anything to uninstall now.

I having an issue with SCEP on a few of my Windows XP machines. They all had SCEP installed on them with SCCM 2012. I upgraded my environment to SCCM 2012 SP1 so there was a new version of SCEP. The computers were set to automatically update the SCCM and SCEP clients. Most computers updated fine. I have 3 though that won't install the new version though. SCCM uninstalled the old version automatically but when trying to install the new version it fails. When I try to install it manually, it either asks for the path to a file (epp.msi or FEPClient.msi) and no matter where I point it to, it says that the file is not a valid installation package and won't let me continue or it fails with the error code 0x80070645. I search Google but didn't find anything helpful. Does anyone know how to fix this?

The only thing that pops out is "\\?\M:\SMSPKGSIG\<package name>.<version> could not be located. This is in the distmgr.log file on the secondary site server. I see messages on the primary site server saying that it is sending the package to the server but nothing else referring to the secondary site.

I am using SCEP on my clients and am having an issue with the definition package. The package updates fine on my Primary site and distribution points but my Secondary sites all say "Distribution Manager successfully processed package" and the status is "In Progress". Why doesn't the status change to Success? This is in Monitoring > Distribution Status > Content Status > [Package name].

I have an issue with new computers not being assigned to sites. If I look at the computer details, the only listed after "Agent Name" is SMS_AD_Security_Group_Discovery_Agent. I have AD System Discovery set to run a full discovery every 2 days and delta discovery every 5 minutes. It seems to run but the delta's don't pick up new computers. If I run a full discovery manually (Run Full Discovery Now) it finds the computers and then add the computer to the site. I don't want to have to run it manually all the time though. How do I find out why the delta isn't pulling in new computers?

How do I fix this since I already have SP1 installed?

Yes, SP1 is applied.

I am constantly getting the below error message in the smsdbmon.log file. What does this mean, is it important and how do I get rid of it? It is always the same error message and happens a lot (45 times in a minute).

Assuming we decide to go with two completely separate systems, how do I configure the boundaries and such so that there won't be a conflict? Is there a way to have it so that clients that come to the US won't be managed by the US system even though it is in the boundary?

With a CAS, will they still need to transfer their packages over the WAN to the CAS server when they create new packages?

Ok, back to this topic.. sort of. I have a standalone WSUS environment that most of my devices are using (I haven't had time to fully test using SCCM). They are configured to use my WSUS servers with group policies. Can I somehow make them use SCCM to get updates to the SCEP definitions while using my WSUS servers for all other updates?

Not that I see. Each boundary consists of an IP range and is only assigned to one site system. I don't know if this matters but each server listed in that picture is just a DP and not a secondary site. I can post screenshots of the boundary group configurations and such if you need.

Ok. I don't think a secondary site will fly though... I'm sure the other IT department will not want to be a child off of our site.

Any idea where I would look to see why it is using all of those locations for HOL000F? The boundary it set to use just the surrey-sccm server.

There is about 2500 clients total. We don't manage users with SCCM yet, but there are less then 3500 users.

Does this mean it is downloading from all of these locations or could connect to any of them?

Was it the CAS.log file or a different one?

Question for all of you guru's. I have two IT departments that are from two old, separate companies. The IT departments work separately and manage many locations. There is a history between the two departments and we don't really get a long very well. (Yes, I know. Grow up and work together but I don't see that happening any time soon). Anyhow, we have SCCM up and running now with 1 primary and multiple DP's and secondary sites. We also use SCEP for antivirus. SCCM is 2012 SP1. They now want to start using SCCM to manage their software packages while keeping their current antivirus (Symantec). Would it be best to create a CAS and make my primary part of it and then setup their primary under the CAS or create a primary for them and keep the two completely separate? If I do a CAS, what can they change on our servers and what can we change on theirs? How would SCCM handle laptops that go between their site and ours? In general, what is the best way to do this and what are the 'gotcha's'?

Is there a way to do both Itanium and IA64 at the same time though?

I don't use ADR for monthly updates so I want to see all of the updates available but I don't have any Itanium or IA64 servers so I don't care about those.

Is there a way to do it in the "All software updates" view?

Is there a way to exclude updates for Itanium and IA64 processors from the SUP view of all updates?

Some of my DP's are on Secondary servers but a hand full of them are just DP's on Windows 7. How do I update the DP's and Secondary's after I update the Primary?