SCCM 2012 and PXE

I have a client assigned to site PR1 and I deploy a pxe task sequence to my imaging collection which this machine belongs too. I can see the task sequence in the deployment tab of the properties for the client.    I also have verified the
deployment is pxe enabled.     But I get a pxe abort here is my log.
The pxe point we are hitting, because of helpers, is in site PR2.   So my question is if a client from PR1 with an advertisement PXE's to a distribution point assigned to PR2 will it not run? (a deployment to unknown computers works just fine)
Jroth
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777370" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
SMSPXE 8/1/2013 9:36:36 AM 4348 (0x10FC)
04:7D:7B:EE:2A:84, D36D0401-4AEE-11CB-986D-DF25BCD5D5DB: no advertisements found SMSPXE 8/1/2013 9:36:36 AM 4348 (0x10FC)
04:7D:7B:EE:2A:84, D36D0401-4AEE-11CB-986D-DF25BCD5D5DB: No boot action. Aborted. SMSPXE 8/1/2013 9:36:36 AM 4348 (0x10FC)
04:7D:7B:EE:2A:84, D36D0401-4AEE-11CB-986D-DF25BCD5D5DB: Not serviced. SMSPXE 8/1/2013 9:36:36 AM 4348 (0x10FC)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777370" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
SMSPXE 8/1/2013 9:36:40 AM 4348 (0x10FC)
04:7D:7B:EE:2A:84, D36D0401-4AEE-11CB-986D-DF25BCD5D5DB: no advertisements found SMSPXE 8/1/2013 9:36:40 AM 4348 (0x10FC

as Torsten mentioned "make sure that both boot images are deployed to the PXE-enabled"
you may have missed the make visible to PXE check box when creating the image deployment. it will still see your task as a deployment, just not PXE visible.

Similar Messages

Database instance for SCCM 2012 and WSUS on a single primary site server

I am going to install SCCM 2012 and its SQL database on a single physical server. This is going to be a single primary site server. The default SQL instance will be dedicated to SCCM 2012 with no other named instances to be added on the SQL server down
the road.
During the WSUS server role installation, there is the Database Options page asking for using (1) Windows Internal Database, (2) existing db server on this computer, or (3) an external db server.
Since SCCM 2012 doesn't share db instance with others, how should I handle the WSUS db that's going to be hosted on the same SCCM/SQL physical server? Do I really need to create a separate SQL instance just for the WSUS db?
Thanks and regards.

Even though you can do it, it is the best practice to have SCCM 2012 and WSUS installed on separate instances.
http://technet.microsoft.com/en-us/library/hh692394
When the Configuration Manager and WSUS databases use the same SQL Server and share the same instance of SQL Server, you cannot easily determine the resource usage between the two applications. When you use a different SQL Server instance
for Configuration Manager and WSUS, it is easier to troubleshoot and diagnose resource usage issues that might occur for each application.

SCCM 2012 and Reverbed appliances

There is a requirement to have the Riverbed WAN acceleration appliances installed instead of Distribution Points.
For the fresh setup of SCCM 2012 that we are working at the moment. The initial proposal was with one Primary Site Server and number of distribution points
however client wants to go with the Reverbed appliances and not to use distribution points.
Would like to know and get the confirmation from Microsoft that if Reverbed appliances are supported fully with SCCM 2012 and if any recommendations on this.
Thanks.
Gurudatt

Hi,
If you want an offical answer from Microsoft if it is supported and recommended you should really open a support case or perhaps an advisory case with Microsoft Support. You will not get an offical statement here and for Microsoft to fully support it would
mean that they would have tested it as well.
There are some information regarding that it will work on riverbeds page
https://splash.riverbed.com/thread/2723
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCCM 2012 and collection settings

Hi all,
I am migrating SCCM 2007 to SCCM 2012 SP1 CU3.
All my 1200 collections are migrated to SCCM 2012 and the incremental option is enabled on most of my collections (about 1100).
Now I found out that my collections are updating very very slow.....
I read an article that best practice is to enable a maximum of 200 collections with the incremental option.
So i ran a powershell script to disable this option on my collections....
Now it seems that collection updates are faster again...
Do I need to disable the incremental option on all collections and enable the schedule full update eg. very 30 minutes ?
I hope someone could share his experience with this....

I ran this test this weekend since it has been a while since I have do this. Short version, yes I’m getting confused between CM07 and CM12. CM07 this work perfectly for User and PCs. In CM12 this only work perfectly for Users. If you want
to make this work for PC you need to do the following.
PC
Add the PC to the Security Group.
Wait of the Security group to replicate to the PC’s local DCS.
Reboot the PCs
Wait for the Discovery Data(DD) collection Cycle to occur, (default is every 7 days), However I recommend making this daily and in some cases hourly.
Once the DD data is in the CM12 db. You need to wait for the Collection to update (default is every 7 days)
Then you need to wait for the PC to retrieve it’s Machine policies. (~1 hour)
User:
Add the User to the Security Group.
Wait of the Security group to replicate to the PC’s local DCS.
Logon to the PC. With newer OS , just unlocking the PC will
do the trick.
Then you need to wait for the User Polices to retrieved.(~1 hour)
http://www.enhansoft.com/

SCCM 2012 R2 PXE not working because DHCP Option 43 is configured to AVAYA

Hello!
We are having some issues with PXE and OS Deployment with some computers.
We tested computers DELL, PXE and DHCP works without any issues. But we tested some HP computers and we received the error PXE-E77 Bad or missing discovery server list
We investigate that error and found that is related with the Option 43 Vendor Specific Info is enable on the DHCP Server, the solution that we tested and works as expected is create a new scope on the DHCP and without enable the Option 43.
That was a temporary solution for the issue, nevertheless we need to use PXE over our network, and we cannot remove the Option 43 on the DHCP configured for AVAYA, so we need a solution that can coexist with PXE and Option 43 on the DHCP.
We will apreciate any advice on this issue.
Thank in advance.
Manuel
Manuel´s Microsoft Forums Threads

The easiest way to deal with this problem is not to use DHCP scope options. Implement IP Helpers instead. It is straightforward to configure and is the only MS supported way anyway.
http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part_9487.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM 2012 R2 PxE can't boot - your pc need to be repired.

Dear All,
These days, I upgraded SCCM 2012 to R2 , after that PxE can't boot , and shows a blue screen that your pc need to be repired, same issue like this:http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-task-sequence-fails-with-bcd.html
And, i have also re-configed the pxe more times follow by this acticle , and still failed.
And, after I replace the \RemoteInstall\SMSTemp\2014.01.08.12.31.26.01.{xxxxxxxxx}.boot.bcd to \RemoteInstall\Tmp\x86x64{xxxxxxx}.bcd, and the PC can boot to the winpe well. that means the pc using Tmp folder's BCD store
to boot to WinPE, and not using SMSTemp's.
I check the PxE process:http://technet.microsoft.com/en-us/library/cc722358(v=ws.10).aspx
PXEBoot.com downloads Bootmgr.exe and the BCD store, and I think PXEBoot.com should download BCD store from SMSTemp folder, and should not be the Tmp folder.
So, my question is that why te PXEBoot.com download BCD from Tmp folder ? And how can I change it to download BCD from SMSTemp folder. ? I have been getting to crazy about this fucking problem.
Nemo

Reinstalling WDS and the PXE was not the answer, at least not for me, but I dunno about the original poster as he kept quiet.
For now I am trying to get SCCM2012 R2 running as this is the topic for my final projekt.
But I am stuck here, the problem is the same as the original poster mentioned.
Even thougt DHCP options are set to my CM and smsboot\x86\wdsnbp.com, pxe keeps loading boot\... and fails.
Making a copy from smsboot to boot and renaming the file fixes it in a dirty way.
The WDS-service has never been configured manually, after rolling back to a fresh Server and installing CU1 first nothing changed about that (PXE worked at all at least) und reinstalling the living dead out of the roles and features fixes nothing.
The remoteinstall folder gets populated everytime, with the SMS related stuff and the wds related stuff, I guess (boot, SMSboot, ...).
I tried various variations of the start path, TFTP still loads from boot instead smsboot.
The Images have been temporarily replaced with the one from our old site.
I renewed the whole site, this bugs me since 2012 R1 and R2 is the second site too.
I would really appreciate it if someone could help with an working solution.
Let me know if you need some more informations, site is described below.
In case this should get another Thread, let me know.
Thank you guys :)
Hyper-V Environment, Windows Server 2012 R2 Standard on all three Hosts (Gen 2),
Followed mainly the MS TLG for SCCM2012 for this, supported by windows-noob.
Have a nice day.
Little Edit right here: renaming the file only helps with the 89 error thing, but it doesn't help booting the sccm image.

SCCM 2012 _ PXE error (no advertisement found)

Hi
i have an error, always happen with PXE deployment on SCCM 2012 SP1_CU4
i tray to uninstall DP ,WDS and delete Reminstall, recreate Boot images
nothing no advertisements found
save me
Mahmoud

Hi,
Quote: i import computer info in to Device collection
So could you pxe boot successfully after deploy the task sequence to the device?
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012 OSD PXE, OS System disk is D:/ !

HI !
SCCM 2012 st.OSD PXE, OS System disk is D:/ !
Deploing OS, resulting
in system drive
is D:/. How to achieve this
would be C :/?
cenubit

Ok.
What are the steps and conditions
are followed
to establish a
new Reference Image ?
cenubit

SCCM 2012 and Windows 8.1 OSD

Dear all,
I am planning to upgrade my current site (2012 SP1) to either SP1 CU4 or R2. This is to support Windows 8.1 OSD
My Question is :
i) is it worth just upgrading to Cu4 to allow this? or would it be better to schedule the full upgrade to R2?
from what I have read R2 is a more substantial upgrade
thanks in advance

I believe that it is best practice to deploy the latest version of software, unless there is a specific reason not to do so.
You are right. The upgrade to R2 is more substantial than just applying the CU. You have to, for example, uninstall ADK 8.0 and install ADK 8.1. However you might as well do this upgrade now rather than later.
I have described the R2 upgrade process in detail here
http://www.gerryhampsoncm.blogspot.ie/2013/10/in-place-upgrade-sccm-2012-sp1-to-r2.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM 2012 and .PCK files - how exactly are they used?

Ok, no one, not even Microsoft engineers can seem to provide a clear and definitive answer on this topic, everyone's understanding of the .PCK file with relation to SCCM 2012 is clear as mud.
I understand what .PCK files are...in the SCCM 2007 world, and how they work, all that jazz, what I don't understand is how/when/why they would be used by SCCM 2012...it seems that sccm 2012 would only need these .pck files during a reassignment of a shared
DP in a migration scenario...even that surmise is sketchy since I've watched very closely the DP content conversion process and at
no time did the server access the .PCK files to populate the single instance store.
I am going to do some more testing on my own, my ultimate goal is to permanent delete the contents (not the folder itself) of the SMSPKG folder, essentially all the .PCK and .DL$ files to save space on my server.
If any soul out there knows..not guesses...the purpose of the .PCK file in 2012, let me know please, don't just copy/paste other people's posts as an answer, explain in clear terms each step of the process that 2012 would utilize a .PCK, or if the answer
really is that 2012 does not use .PCK files at all, let me know.
I have a single primary site with 16 secondary sites in my SCCM 2007 environment, I'm migrating to a single primary with 16 distribution points...so even if .PCK's are used to populate secondary sites, I should not need them since I won't have any secondary
sites once all of my DP's are migrated...yeah?
Thanks!
Terry

Thanks for the reply Torsten, that would make sense if my primary site had any .pck files at all (my sccm 2012 site that is) only my DP's have .pck files. I have no child sites in my 2012 hierarchy unless DP's are child sites (I thought secondary sites are
child..) When my DP's require a package they get them from my primary site, not other DP's. I have no 'Pull' DP's setup.
If SCCM 2012 uses a 'single instance store', which contains 3 folders itself that seem to contain compressed versions of the package files, then there should be no need for another folder that also contains compressed files...just a thought.
Terry

SCCM 2012 and 2012 sp1 client cache not cleaning itself

I work on a University campus that deploys 100's of software titles to lab computers. Since last summer, we have been using Config Man 2012 and upgraded to 2012 SP1 in early Jan. Recently we started noticing 160GB hard drives filling up in locations
that get most of our software. When looking into it, the ccmcache folder has 50GB+ of data in it even though the cache size is set to 30GB. I looked at the folders in the cache and many of them are from last summer when the apps were first
downloaded and installed. NONE of these apps are set to persist. My understanding is that they should have been cleaned up automatically after 24 hours as space was needed. Either way, shouldn't the cache folder be at or smaller than the
cache size setting?
I have talked to others that have seen similar problems with 2012 of the cache folder growing beyond the max, but they don't have the software load that we do, so they are not filling their drives. If I manually tell Confi Man client to delete the
cache files, I free up 50GB or more, but manual intervention isn't a great option.
Any ideas on where to troubleshoot this issue or what settings might be messed up that allows for this?
Thanks

How much of this is software updates? Like in 2007 software updates are not counted against the cache size:
"You can configure the location and amount of disk space that Windows Configuration Manager clients use to store temporary files for when they install applications and programs. Software updates also use the client cache, but software updates
are not restricted by the configured cache size and will always attempt to download to the cache"
https://technet.microsoft.com/en-us/library/gg712288.aspx
http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Any major changes to the database for SCCM 2012 and Reporting?

I'm in the process of migrating my custom reports from SCCM 2007 to SCCM 2012. I wonder if all the tables / views in SCCM 2007 are the same in SCCM 2012 for my reporting purposes? So far everything I've migrated over appears to work without a problem.
Orange County District Attorney

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
The SQL schema for SCCM 2012 has been released here.
https://technet.microsoft.com/en-us/library/dn581978.aspx
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCEP going out to the internet after being migrated to SCCM 2012 and saturating facility MPLS.

I was unaware of the fact that SCEP was gonig out to the internet to pull down 120 megs worth of data each time a client is migrated. I'm trying to determine the easiest or best way to avoid this. I've done some research and it looks like bundeling the SCEP
policy with the migration package might work. I also saw some tool that you can use to add a SCEP update rollup to the package. Ultimately if i could just get the exact URL the clients are going out to our networking team could apply QoS to this URL. Unfortunately
though it appears in the MPCMDRUN.log to go to go.microsoft.com/fwlink, but on the networking side in pathview i seen the client ends up going to Akamai.
I'm assuming MS offloads their web traffic to Akamai and that first link is redirected, if that is even the right link. Does anyone know a way i can prevent this while still getting the client up to date. This entire time I thought the clients would pull
what they needed from the SCCM 2012 env. I'm using ADR to push the definitions and that seems to be working fine except for 2 situations. One a client is migrated, or 2 the client comes online after being offline for more than 7 days and goes out.
Either way if someone could provide me with the URL for throttling or a better method for deploying I would be very grateful. So far we've migrated about 8 thousand clients and have about another 10 thousand to go. The majority of the clients have local
pull DPs, and if further details of my infrastructure would be helpful please just let me know.
Thanks,
-KR

Jorgen,
I appreciate you pointing out the setting and that has helped partially and I was able to track down the URL that is being used by the clients for QoS by networking. Now management has pushed back with why are the clients going to the internet at all. I
can understand why. If were deploying all the patches why can't the clients pull their SCEP engine from the SUP/WSUS server. I see it finding it in the MPCMDRUN.Log file but it still goes out to Microsoft to pull the 120 meg file. Do i not have any other options
for pushing the engine to the clients, if ADR is working for current clients what am i missing. I'm sure its something obvious, but my migration is on hold up until I can keep the clients from going to the internet for their new engine and deltas.
Any help you could provide i would very much appreciate. Thanks again Jorgen.
-Sam Kachar

SCCM 2012 and SQL 2008 R2 Sync problems

Hi
I installed 2 servers for SCCM 2012:
-1 with SCCM 2012, FEP, WSUS console admin
-1 with SQL Server 2008 R2 complete install, WSUS complete install
When I made or the system mades the synchronization, it shows this error in SMS_WSUS_SYNC_MANAGER:
Error 6703:
WSUS Synchronization failed.
Message: Failed to sync some of the updates.
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates.
And in the wsyncmgr.log appears:
sync: SMS synchronizing updates, processed 3336 out of 3368 items (99%), ETA in 00:00:06 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:14:11.663+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3360 out of 3392 items (99%), ETA in 00:00:06 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:15:11.669+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3383 out of 3415 items (99%), ETA in 00:00:07 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:16:13.206+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3412 out of 3444 items (99%), ETA in 00:00:07 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:14.152+300><thread=4640 (0x1220)>
Synchronized update 3a572bd0-5976-4abc-b2d8-955008c5466f - Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.131.558.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:18.227+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3446 out of 3463 items (99%), ETA in 00:00:04 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:14.400+300><thread=4640 (0x1220)>
Synchronized update 3eeb75c2-81aa-4cc0-9b7a-237a6a0bf737 - Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.131.574.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:47.964+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3482 out of 3484 items (99%), ETA in 00:00:00 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:19:15.587+300><thread=4640 (0x1220)>
Synchronized update 74e86346-9384-4304-9625-2c865738c552 - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.131.574.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.659+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3508 out of 3508 items (100%) $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.662+300><thread=4640 (0x1220)>
Sync failures summary: $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.664+300><thread=4640 (0x1220)>
Failed to sync update 1ba2d28f-75fe-49d7-9cb4-cd39b8706f48. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.666+300><thread=4640 (0x1220)>
Failed to sync update 8a042978-e6d7-4ae6-b3ab-687d8f9bcd9c. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.669+300><thread=4640 (0x1220)>
Failed to sync update a3aff37b-ad3b-4dde-9464-767a516c76e5. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.671+300><thread=4640 (0x1220)>
Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.421+300><thread=3536 (0xDD0)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=GDVSCCM1.gdar.local SITE=CRP PID=1908 TID=3536 GMTDATE=mar jul 24 14:20:06.423 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates"
ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.425+300><thread=3536 (0xDD0)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.501+300><thread=3536 (0xDD0)>
Setting sync alert to active state on site CRP $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.503+300><thread=3536 (0xDD0)>
Updated 173 items in SMS database, new update source content version is 36 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.526+300><thread=3536 (0xDD0)>
Set content version of update source {6A4B4446-1B80-4CF4-838D-405D3847A8E3} for site CRP to 36 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.572+300><thread=3536 (0xDD0)>
Sync time: 0d00h19m46s $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.575+300><thread=3536 (0xDD0)>
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:06.651+300><thread=3536 (0xDD0)>
Next scheduled sync is a retry sync at 24/07/2012 10:20:06 a.m. $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:11.940+300><thread=3536 (0xDD0)>
Why is this behavior?
Thanks
Doc MX

Hi
Today I think I discovered what was the problem:
I used an user in the domain for deploying the role of SUP, but I forgot to put that user in the group of SQL Admins of the SQL Server.
I done that and after reseting the servers, the error for sync with SQL didn't appear again, al least from this morning until now, before this change every hour showed the error 6703.
Thanks to all for your comments.
Doc MX

SCCM 2012 and WSUS Synchronization error. Message ID: 6703.

Hi,
I am facing issues with synchronising updates in WSUS server with SUP in SCCM 2012. I am using web proxy, which has full access to all microsoft update websites. I have configures SUP for both intranet and internet clinets. I am posting some logs below
that may help to resolve the issue:-
wsyncmgr.log-
Synchronizing WSUS server SCCMSERVER.domain.com SMS_WSUS_SYNC_MANAGER 11/1/2012 11:56:35 AM 3824 (0x0EF0)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 11/1/2012 11:56:35 AM 6368 (0x18E0)
Sync failed: UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS SMS_WSUS_SYNC_MANAGER 11/1/2012
11:58:04 AM 3824 (0x0EF0)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CDCTIBCMSCCM.India.TCS.com SITE=I1P PID=2648 TID=3824 GMTDATE=Thu Nov 01 06:28:04.549 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
WCM.log-
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Successfully got update categories from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully got update classifications from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully got update languages from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:21 AM 4016 (0x0FB0)
Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Id>1403f223-a63f-f572-82ba-c92391218055</Id>~~ <Id>041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591</Id>~~ <Id>84f5f325-30d7-41c4-81d1-87a0e6535b66</Id>~~ <Id>bfe5b177-a086-47a0-b102-097e4fa1f807</Id>~~ <Id>8c3fcc84-7410-4a95-8b89-a166a0190486</Id>~~ <Id>cb263e3f-6c5a-4b71-88fa-1706f9549f51</Id>~~ <Id>5312e4f1-6372-442d-aeb2-15f2132c9bd7</Id>~~ <Id>7f44c2a7-bc36-470b-be3b-c01b6dc5dd4e</Id>~~ <Id>dbf57a08-0d5a-46ff-b30c-7715eb9498e9</Id>~~ <Id>fdfe8200-9d98-44ba-a12a-772282bf60ef</Id>~~ <Id>ec9aaca2-f868-4f06-b201-fb8eefd84cef</Id>~~ <Id>ba0ae9cc-5f01-40b4-ac3f-50192b5d6aaf</Id>~~ <Id>90e135fb-ef48-4ad0-afb5-10c4ceb4ed16</Id>~~ <Id>26997d30-08ce-4f25-b2de-699c36a8033a</Id>~~ <Id>a4bedb1d-a809-4f63-9b49-3fe31967b6d0</Id>~~ <Id>4cb6ebd5-e38a-4826-9f76-1416a6f563b0</Id>~~ <Id>558f4bc3-4827-49e1-accf-ea79fd72d4c9</Id>~~ <Id>6964aab4-c5b5-43bd-a17d-ffb4346a8e1d</Id>~~</Categories> SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012
11:52:21 AM 4016 (0x0FB0)
Subscribed Update Classifications <?xml version="1.0" ?>~~<Classifications>~~ <Id>e6cf1350-c01b-414d-a61f-263d14d133b4</Id>~~ <Id>0fa1201d-4330-4fa8-8ae9-b877473b6441</Id>~~ <Id>28bc880e-0592-4cbf-8f95-c79b17911d5f</Id>~~ <Id>cd5ffd1e-e932-4e3a-bf74-18bf0b1bbd83</Id>~~</Classifications> SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012
11:52:22 AM 4016 (0x0FB0)
WSUSCtrl.log-
WSUS registry key change notification triggered. SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
System.Net.WebException: The request failed with HTTP status 403: Forbidden.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~
at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Failed to set WSUS Local Configuration. Will retry configuration. SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Waiting for changes for 57 minutes SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Urgent Help Appreciated.
Thanks,
Deepak

STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CDCTIBCMSCCM.India.TCS.com SITE=I1P PID=2648 TID=3824 GMTDATE=Thu Nov 01 06:28:04.549 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
System.Net.WebException: The request failed with HTTP status 403: Forbidden.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~
at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Those errors are unrelated to ConfigMgr. The first one is a name resolution error; the second one tells that the servers is not allowed to connect to the proxy.
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2012 and PXE

Similar Messages

Maybe you are looking for