SCCM 2012 secondary server

Hi All,
I am trying to install secondary site server from primary site server. All the prerequisites like .NET 3.5, 4, RDC, BITS are installed. Primary site server name is added In the local admin on the server. But still the installation is getting failed.
I got mcafee enabled on the machine. Is it blocking bootstrap file
Log:
******************************************************************************** $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
Starting SMS_BOOTSTRAP. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
Microsoft System Center 2012 Configuration Manager v5.00 (Build 7804) $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
Copyright (C) 2011 Microsoft Corp. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
Set current directory to E:\. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
INFO:Action:<Install>. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.412+0><thread=1F2C>
Successfully read E:\SMS_BOOTSTRAP.ini. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
Started for the first time. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
Current time: Tue Mar 11 16:56:49 2014 $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
Looking for the .PKG file... $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
Found E:\SMS_BOOTSTRAP.pkg. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
Elapsed time since startup: 0 days, 00 hours, 00 minutes, 00 seconds. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
Processing the .PKG file... $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
Validating E:\SMS_BOOTSTRAP.pkg... $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
E:\SMS_BOOTSTRAP.pkg passed validation check. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
There is enough disk space: 1574MB required, 952704MB available. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.427+0><thread=1F2C>
Temp directory is E:\4n9i849i.TMP. $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.443+0><thread=1F2C>
Decompressing E:\SMS_BOOTSTRAP.pkg... $$<SMS_BOOTSTRAP><03-11-2014 16:56:49.443+0><thread=1F2C>
Decompression successful. $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.669+0><thread=1F2C>
Elapsed time since startup: 0 days, 00 hours, 00 minutes, 16 seconds. $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.669+0><thread=1F2C>
Running SMS Setup... $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.669+0><thread=1F2C>
Successfully parsed E:\4n9i849i.TMP\\SMSSETUP\install.map. $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.934+0><thread=1F2C>
E:\4n9i849i.TMP\\SMSSETUP\install.map build number "7804" is correct. $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.934+0><thread=1F2C>
Started "E:\4n9i849i.TMP\\SMSSETUP\bin\x64\SetupWPF.exe /script E:\SMS_BOOTSTRAP.ini /nouserinput" as PID 8016. $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.934+0><thread=1F2C>
Waiting for PID 8016 to terminate... $$<SMS_BOOTSTRAP><03-11-2014 16:57:05.934+0><thread=1F2C>
PID 8016 exited with code 0. $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.016+0><thread=1F2C>
FATAL ERROR: SMS_SITE_COMPONENT_MANAGER is not running, setup must have failed, bootstrap procedure aborted!
$$<SMS_BOOTSTRAP><03-11-2014 17:19:43.016+0><thread=1F2C>
Deinstalling myself... $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.016+0><thread=1F2C>
Deleted E:\SMS_BOOTSTRAP.pkg. $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.078+0><thread=1F2C>
Deleted E:\SMS_BOOTSTRAP.ini. $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.078+0><thread=1F2C>
Deleted E:\SMS_BOOTSTRAP.EXE. $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.078+0><thread=1F2C>
Deleted temp directory <E:\4n9i849i.TMP>. $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
Deinstalled the SMS_BOOTSTRAP service. $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
Deinstallation complete. $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
Bootstrap procedure unsuccessful. $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
Stopping SMS_BOOTSTRAP... $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
SMS_BOOTSTRAP stopped. $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
******************************************************************************** $$<SMS_BOOTSTRAP><03-11-2014 17:19:43.359+0><thread=1F2C>
******************************************************************************** $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.078+0><thread=DD8>
Starting SMS_BOOTSTRAP. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.093+0><thread=DD8>
Microsoft System Center 2012 Configuration Manager v5.00 (Build 7804) $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.093+0><thread=DD8>
Copyright (C) 2011 Microsoft Corp. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.093+0><thread=DD8>
Set current directory to E:\. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.093+0><thread=DD8>
INFO:Action:<Install>. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
Successfully read E:\SMS_BOOTSTRAP.ini. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
Started for the first time. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
Current time: Fri Mar 14 15:53:13 2014 $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
Looking for the .PKG file... $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
Found E:\SMS_BOOTSTRAP.pkg. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
Elapsed time since startup: 0 days, 00 hours, 00 minutes, 00 seconds. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
Processing the .PKG file... $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
Validating E:\SMS_BOOTSTRAP.pkg... $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.109+0><thread=DD8>
E:\SMS_BOOTSTRAP.pkg passed validation check. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.125+0><thread=DD8>
There is enough disk space: 1574MB required, 952700MB available. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.125+0><thread=DD8>
Temp directory is E:\s3jvf81y.TMP. $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.125+0><thread=DD8>
Decompressing E:\SMS_BOOTSTRAP.pkg... $$<SMS_BOOTSTRAP><03-14-2014 15:53:13.125+0><thread=DD8>
Decompression successful. $$<SMS_BOOTSTRAP><03-14-2014 15:53:29.707+0><thread=DD8>
Elapsed time since startup: 0 days, 00 hours, 00 minutes, 16 seconds. $$<SMS_BOOTSTRAP><03-14-2014 15:53:29.816+0><thread=DD8>
Running SMS Setup... $$<SMS_BOOTSTRAP><03-14-2014 15:53:29.816+0><thread=DD8>
Successfully parsed E:\s3jvf81y.TMP\\SMSSETUP\install.map. $$<SMS_BOOTSTRAP><03-14-2014 15:53:30.066+0><thread=DD8>
E:\s3jvf81y.TMP\\SMSSETUP\install.map build number "7804" is correct. $$<SMS_BOOTSTRAP><03-14-2014 15:53:30.097+0><thread=DD8>
Started "E:\s3jvf81y.TMP\\SMSSETUP\bin\x64\SetupWPF.exe /script E:\SMS_BOOTSTRAP.ini /nouserinput" as PID 5480. $$<SMS_BOOTSTRAP><03-14-2014 15:53:30.113+0><thread=DD8>
Waiting for PID 5480 to terminate... $$<SMS_BOOTSTRAP><03-14-2014 15:53:30.113+0><thread=DD8>
PID 5480 exited with code 0. $$<SMS_BOOTSTRAP><03-14-2014 16:14:06.991+0><thread=DD8>
FATAL ERROR: SMS_SITE_COMPONENT_MANAGER is not running, setup must have failed, bootstrap procedure aborted! $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.022+0><thread=DD8>
Deinstalling myself... $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.022+0><thread=DD8>
Deleted E:\SMS_BOOTSTRAP.pkg. $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.084+0><thread=DD8>
Deleted E:\SMS_BOOTSTRAP.ini. $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.084+0><thread=DD8>
Deleted E:\SMS_BOOTSTRAP.EXE. $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.084+0><thread=DD8>
Deleted temp directory <E:\s3jvf81y.TMP>. $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
Deinstalled the SMS_BOOTSTRAP service. $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
Deinstallation complete. $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
Bootstrap procedure unsuccessful. $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
Stopping SMS_BOOTSTRAP... $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
SMS_BOOTSTRAP stopped. $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
******************************************************************************** $$<SMS_BOOTSTRAP><03-14-2014 16:14:07.365+0><thread=DD8>
Regards, Pratap

Hi,
What's the version of your SCCM 2012?
If it is SCCM 2012 sp1 CU2, please have a look on the following KB.
http://blogs.technet.com/b/configmgrteam/archive/2013/07/02/known-issue-secondary-site-installation-failure-with-cumulative-update-2.aspx
Best Regards,
Joyce Li
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.

Similar Messages

SCCM 2012 secondary server installation failing

I am trying to install the SCCM 2012 secondary server remotely and when i check the configmgrsetup.log and i see below error. I tried to check the registry at HKLM\software\microsoft\sms and i see a site code as DRW but i had given a site code DFW.
I checked the permission on the servers, the OU everything seems to be fine, can someone please suggest:
INFO: Attempting to load resource DLL... Configuration Manager Setup 8/23/2013 12:51:28 PM 16652 (0x410C)
ERROR: Connection strings not initialized Configuration Manager Setup 8/23/2013 12:51:28 PM 11464 (0x2CC8)
CSql Error: Cannot find data for connection type: , cannot get a connection. Configuration Manager Setup 8/23/2013 12:51:28 PM 11464 (0x2CC8)
ERROR: Failed to connect to SQL Server 'master' db. Configuration Manager Setup 8/23/2013 12:51:28 PM 11464 (0x2CC8)
INFO: Prerequisite rules for secondary site fresh installation are being run. Configuration Manager Setup 8/23/2013 12:51:28 PM 11464 (0x2CC8)
INFO: File C:\Windows\smstsvc_test_1.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:51:28 PM 11464 (0x2CC8)
INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:51:34 PM 11464 (0x2CC8)
INFO: smstsvc_test_1 Return result <0> Configuration Manager Setup 8/23/2013 12:51:34 PM 11464 (0x2CC8)
CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on FTWEISSCCM12S1.eis.equifax.com Configuration Manager Setup 8/23/2013 12:52:26 PM 11464 (0x2CC8)
CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on FTWEISSCCM12S1.eis.equifax.com Configuration Manager Setup 8/23/2013 12:52:27 PM 11464 (0x2CC8)
CWmiRegistry::GetValues: Failed to get values from SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL Configuration Manager Setup 8/23/2013 12:52:27 PM 11464 (0x2CC8)
CWmiRegistry::GetValues: Failed to connect to registry on machine FTWEISSCCM12S1.eis.equifax.com. Error code: 2 Configuration Manager Setup 8/23/2013 12:52:28 PM 11464 (0x2CC8)
INFO: Checking Installed SMS componants on:FTWEISSCCM12S1.eis.equifax.com. Configuration Manager Setup 8/23/2013 12:52:31 PM 11464 (0x2CC8)
CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\SMS\Setup on FTWEISSCCM12S1.eis.equifax.com Configuration Manager Setup 8/23/2013 12:52:32 PM 11464 (0x2CC8)
CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role on FTWEISSCCM12S1.eis.equifax.com Configuration Manager Setup 8/23/2013 12:52:32 PM 11464 (0x2CC8)
CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\SMS\Providers\Sites on FTWEISSCCM12S1.eis.equifax.com Configuration Manager Setup 8/23/2013 12:52:32 PM 11464 (0x2CC8)
INFO: File
\\FTWEISSCCM12S1.eis.equifax.com\admin$\smstsvc_test_2.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:52:34 PM 11464 (0x2CC8)
INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:53:12 PM 11464 (0x2CC8)
INFO: smstsvc_test_2 Return result <1> Configuration Manager Setup 8/23/2013 12:53:13 PM 11464 (0x2CC8)
INFO: File C:\Windows\smstsvc_test_3.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:53:14 PM 11464 (0x2CC8)
INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:53:22 PM 11464 (0x2CC8)
INFO: smstsvc_test_3 Return result <0> Configuration Manager Setup 8/23/2013 12:53:22 PM 11464 (0x2CC8)
INFO: This is a local site system. There is no need to check for the Admin$ share. Configuration Manager Setup 8/23/2013 12:53:24 PM 11464 (0x2CC8)
INFO: Checking Windows Cluster. Configuration Manager Setup 8/23/2013 12:53:27 PM 11464 (0x2CC8)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e Configuration Manager Setup 8/23/2013 12:53:29 PM 11464 (0x2CC8)
INFO: WMI namespace root\MSCluster not exists on FTWEISSCCM12S1.eis.equifax.com. Configuration Manager Setup 8/23/2013 12:53:29 PM 11464 (0x2CC8)
INFO: File
\\FTWEISSCCM12S1.eis.equifax.com\admin$\smstsvc_test_4.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:53:30 PM 11464 (0x2CC8)
INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:54:08 PM 11464 (0x2CC8)
INFO: smstsvc_test_4 Return result <7> Configuration Manager Setup 8/23/2013 12:54:08 PM 11464 (0x2CC8)
INFO: File
\\FTWEISSCCM12S1.eis.equifax.com\admin$\smstsvc_test_5.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:54:10 PM 11464 (0x2CC8)
INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:54:48 PM 11464 (0x2CC8)
INFO: smstsvc_test_5 Return result <7> Configuration Manager Setup 8/23/2013 12:54:48 PM 11464 (0x2CC8)
INFO: File
\\FTWEISSCCM12S1.eis.equifax.com\admin$\smstsvc_test_6.exe does not exist. No zapping needed. Configuration Manager Setup 8/23/2013 12:54:52 PM 11464 (0x2CC8)
INFO: test loop count:0. Configuration Manager Setup 8/23/2013 12:55:30 PM 11464 (0x2CC8)
INFO: smstsvc_test_6 Return result <0> Configuration Manager Setup 8/23/2013 12:55:30 PM 11464 (0x2CC8)
INFO: FTWEISSCCM12S1.eis.equifax.com is a 64 bit operating system. Configuration Manager Setup 8/23/2013 12:55:35 PM 11464 (0x2CC8)

I'm also unable to create Secondary site due above error in configuration setup log.
INFO: Attempting to load resource DLL...   Configuration Manager Setup   23/Mar/15 3:11:26 PM   5020 (0x139C)
ERROR: Connection strings not initialized   Configuration Manager Setup   23/Mar/15 3:11:26 PM   8752 (0x2230)
CSql Error: Cannot find data for connection type: , cannot get a connection.   Configuration Manager Setup   23/Mar/15 3:11:26 PM   8752 (0x2230)
ERROR: Failed to connect to SQL Server 'master' db.   Configuration Manager Setup   23/Mar/15 3:11:26 PM   8752 (0x2230)
INFO: Prerequisite rules for secondary site fresh installation are being run.   Configuration Manager Setup   23/Mar/15 3:11:26 PM   8752 (0x2230)
INFO: File C:\Windows\smstsvc_test_1.exe does not exist. No zapping needed.   Configuration Manager Setup   23/Mar/15 3:11:26 PM   8752 (0x2230)
INFO: test loop count:0.   Configuration Manager Setup   23/Mar/15 3:11:33 PM   8752 (0x2230)
INFO: smstsvc_test_1 Return result <0>   Configuration Manager Setup   23/Mar/15 3:11:33 PM   8752 (0x2230)
CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on    Configuration Manager Setup   23/Mar/15 3:11:36 PM   8752 (0x2230)
CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on    Configuration Manager Setup   23/Mar/15 3:11:36 PM   8752 (0x2230)
CWmiRegistry::GetValues: Failed to get values from SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL   Configuration Manager Setup   23/Mar/15 3:11:36 PM   8752 (0x2230)
CWmiRegistry::GetValues: Failed to connect to registry on machine Error code: 2   Configuration Manager Setup   23/Mar/15 3:11:36 PM   8752 (0x2230)

SCCM 2007 Secondary to SCCM 2012 Secondary Site

we are planning to upgrade SCCM 2007 secondary to SCCM 2012 Secondary Site, As per the TechNet document that I understand i can't do in place upgrade of Secondary site. I can do only upgrade
of 2007 DP to 2012 DP,
This is what I plan,
1. Install a SCCM 2012 Secondary site
2. Enable DP sharing in 2012 and share the DP of 2007
3. Upgrade the 2007 DP into 2012 DP on 2012 Secondary Site.
My question is,
1. How to copy the DP package to 2012 Secondary Server DP, it will happen during the upgrade or we need to use Export/extract Content feature in SCCM 2012
2. How the client migration will happen? Do we need to distribute the 2012 client prior to DP update or we can use client push to upgrade old client.
3. before share the DP, do i have to remove the MP, PXE role on the 2007 secondary?
Thanks for your support

I have already few packages available in that DP that I am going to migrate
The second shared DP that I want to migrate to 2012, but it is not working.
Do I need to specify any thing in reassign distribution point wizard, because I only select the site code where I want to migrate the 2007 DP, and all other option I leave default and client on next.
This is what I am trying to do.
I have build a SCCM 2012 Primary and Secondary Server and I am trying to move the DP from exiting SCCM 2007 Secondary Site DP to 2012 Secondary Site.
I set a source hierarchy for primary server with enable shared DP then I am trying to reassign a DP.

Is there a way to change an existing SCCM 2012 site server intranet FQDN name to lowercase?

Does anyone know if there is a way to change the intranet (not internet) FQDN name of an existing SCCM 2012 site server to all lowercase letters? You used to be able to do this in SCCM 2007.

I had a problem with WSUS updates not working via SCCM 2012 R2 during an operating system deployment. When examining the c:\Windows\WindowsUpdate.log I found the following errors:
WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <****:8080;****:8080> Bypass List used : <(null)> Auth Schemes used : <>
+ Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
WARNING: GetConfig failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
After a LONG time researching this error I found it was related to the fact we were using a WPAD proxy implementation and apparently this doesnt cope well with uppercase characters for the WSUS server URL. I changed our GPO to be using lowercase lettering
but when examining the WindowsUpdate log again it still showed as being in uppercase. In the end I found that despite what your GPO setting says, this can get over written by the SCCM site server's own published WSUS location. You can check this by entering
the following command:
wmic /namespace:"\\root\CCM\SoftwareUpdates\WUAHandler" PATH CCM_UpdateSource
Unfortunatelty in SCCM 2012 there is no GUI way to amend the intranet FQDN used for the WSUS location so I then turned to directly editing the database (which anyone will tell you is not recommended, but by this point i was DESPERATE!).
In the end it solved all my troubles so if anyone finds themselves in this situation, you can fix it by going to the SCCM database and within the table 'WSUSServerLocations', change the WSUSServerName to be in lowercase letters.

Windows 8.1 system with new Office 2013 install not pulling down any Office 2013 updates from my SCCM 2012 SP1 server

Hi,
I've just setup a new Windows 8.1 system and added to my SCCM 2012 SP1 server and all is good and it pulled down all the correct Windows updates and pulls down automatically the FEP updates that are distributed from SCCM 2012 daily.
I just installed Office 2013 on this system and have activated it as necessary. The problem is that the system doesn't seem to be pulling down any of the Office 2013 updates that have distributed thru SCCM. I have other systems with
Office 2013 installed and they have pulled down Office 2013 updates in the past when I published them.
If I look at the Office 2013 updates in the SCCM console software section, I can see that for example it shows that Office 2013 SP1 (x86) is needed by one system and installed on 8 other systems and shows as downloaded and deployed.
I've restarted the new system multiple times and also tried to force a software update check from the Configuration Manager applet but nothing seems to happen.
What can I check to try and determine what the problem is?
Thanks in advance,
Nick

Yes, the 8.1 system is a member of collection where the update deployment is targeted.
Are there any specific logs I should check in the client? If I check the WindowsUpdate.log I can see messages about the machine pulling down the FEP updates but that's all it appears to be doing.
in CCM\logs, focus on the updatehandler and updatedeployment, to begin with
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Is the distribution point role required on an SCCM 2012 site server?

I am wondering if the distribution point role is required on an SCCM 2012 site server.
We have an installation of SCCM 2012 SP1 with a site server, and two remote DPs.
I would like to remove the DP role from the site server, and stand up another server (2012) at the same location, making it a DP and also have it hold the WSUS content.
I was successful in creating the DP on the new server. I distributed all of our packages to the new server.
I then removed the packages from the DP on the site server, and removed the DP role from the site server.
After making these changes, we lost the ability to deploy packages, either from the new DP server, or from the previously existing DPs that were at other locations.
Deployment status in the SCCM console showed that clients were “waiting for content”.
I found that adding the DP role back to the site server, and distributing packages to it corrected the problem.
Deployment resumed after doing that. Is it necessary to have packages on a DP on the site server?
We want to virtualize the server, and would like to make it as small as possible to facility restores.

Hi,
Have you checked the log file distmgr.log? Maybe it can give us some clues.
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.

Boot an ESX 5.1 VM to my SCCM 2012 (WDS) server?

Hi folks,
I just got my SCCM 2012 server installed, configured a distribution point, published new boot.wim to distribution point.
I am trying to test booting up a 'bare metal' ESXi 5.1 VM to my SCCM 2012 (WDS) server, but fails with attached error.
Configuration Manager is looking for policy.
Anyone have a suggestion?
Thanks, romatlo

Thank you so much for responding! I must admit that this is my first install. :)
I could not find that option, so I deleted/recreated my task sequence, then found it as part of Deploy option.
I deployed the task sequence to unknown computers but I still get that message and will not boot up correctly.
I've pasted last part of my SMSPXE.log in case you see something definitive.
I did not have my WDS server role installed when enabling PXE on my DP, maybe that messed me up.
Thanks again, I may snapshot my VM here and start over on install if there is not a clue.
<![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6346">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: device is in the database.]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: No boot action. Aborted.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: Not serviced.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">

How does WSUS work when an SCCM 2012 R2 server is newly installed? Should WSUS be installed and configured on same server?

Let me clarify.
We had a functional WSUS server delivering our updates to ours workstations. The location of the WSUS server was pushed out by Group policies.
Later, an SCCM 2012 R2 installation was installed. The original WSUS server was removed. Now WSUS type services appear to be broken.
I tried to start WSUS on the SCCM 2012 R2 server and it does not start. (I assume its not configured).
I want to get WSUS running again but am not sure how to do this safely in conjunction with our SCCM 2012 R2 installation. Do I just reinstall WSUS on the SCCM server and configure? Or is there other preferred methods?
I was not involved in SCCM's installation, so I do not know what was done.
Geoff.

Update functionality is provided via the Software Update Point
https://technet.microsoft.com/en-us/library/gg712312.aspx
... which requires WSUS to be installed - it basically takes control of WSUS.
Any existing group policies defining WSUS servers should be removed so that the SCCM client (which I assume is installed on computers already) can configure accordingly. Otherwise you will have group policy and SCCM client over writing one another to configure
the update server

SCCM 2012 Secondary Site Migration

we have to migrate more then 50 Secondary Site to SCCM 2012 Secondary Site. Since we have to low-bandwidth connection for the remote site we prefer to go with SCCM 2012 Secondary site inside of DP.
I know we can migrate SCCM 2007 Secondary to SCCM 2012 DP and SCCM 2007 DP to SCCM 2012 DP.
But is there a way i can move the distribution point package from SCCM 2007 Secondary to SCCM 2012 Secondary Site?
when i try to migrate migrate SCCM 2007 Secondary Site DP to SCCM Secondary Site 2012, it uninstall the 2007 Secondary site and upgrade the DP to SCCM 2012 under the 2012 Secondary site.
But my requirement is to move the old SCCM 2007 secondary site package to SCCM 2012 Secondary site DP, is there any tool to manage this activity?
or what is the best practice to do this migration.

Hi,
You could use prestage content in SCCM 2012 to send packages to remote DP.
Configuration Manager 2012: Content Prestaging and Remote Content Distribution
http://blogs.technet.com/b/inside_osd/archive/2011/04/11/configuration-manger-2012-content-prestaging.aspx
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.

ERROR: Failed to update prerequisite results into the registry; error = 1 for sccm 2012 secondary site installation

Hi,
We try to install sccm 2012 serondary site in server 2012. It always failed.
I used the rereqchek tools to check system enviroment locally. All passed.
The primary site installed in server 2012. Both server had granted the administrator permission.
Anyone can help to check the below Configmgrprereq.log
ï»¿<01-16-2015 08:47:55> ********************************************
ï»¿<01-16-2015 08:47:55> ******* Start Prerequisite checking. *******
ï»¿<01-16-2015 08:47:55> ********************************************
ï»¿<01-16-2015 08:47:55> Commandline :
"D:\Microsoft Configuration Manager\bin\x64\smsexec.exe"
ï»¿<01-16-2015 08:47:55> Check Type: Secondary site
Site Server: DPServer.ms.com,
SQL Server: DPServer.ms.com,
SQL Named Instance: ,
Install Folder: d:\Program Files\Microsoft Configuration Manager\,
Setup Source Folder: D:\SCCM2012\Source
ï»¿<01-16-2015 08:47:55> INFO: Executing prerequisite functions...
ï»¿<01-16-2015 08:47:55> ===== INFO: Prerequisite Type & Server: SITE_SEC:DPServer.ms.com =====
ï»¿<01-16-2015 08:47:55> <<<RuleCategory: Access Permissions>>>
ï»¿<01-16-2015 08:47:55> <<<CategoryDesc: Checking access permissions...>>>
ï»¿<01-16-2015 08:47:55> INFO: CheckLocalSys is Admin of <DPServer.ms.com>.
ï»¿<01-16-2015 08:48:08> DPServer.ms.com;    Site server computer account administrative rights;    Error;    Configuration Manager Setup requires that the site server computer has administrative rights on
the SQL Server and management point computers.
ï»¿<01-16-2015 08:48:08> <<<RuleCategory: System Requirements>>>
ï»¿<01-16-2015 08:48:08> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
ï»¿<01-16-2015 08:48:08> INFO: Check Lanman service: <DPServer.ms.com>.
ï»¿<01-16-2015 08:48:22> DPServer.ms.com;    Check Server Service is running;    Passed
ï»¿<01-16-2015 08:48:30> INFO: OS version:0, ServicePack:0.
ï»¿<01-16-2015 08:48:30> DPServer.ms.com;    Unsupported site server operating system version for Setup;    Error;    Configuration Manager site systems can only be installed on systems running Windows Server
2008 SP2 or later.
ï»¿<01-16-2015 08:48:34> INFO: Failed to get Active Directory membership information for computer DPServer.ms.com with 0.
ï»¿<01-16-2015 08:48:34> DPServer.ms.com;    Domain membership;    Error;    Configuration Manager site server components must be installed on computers that are members of a Windows domain.
ï»¿<01-16-2015 08:48:40> INFO: Free disk space on target \\DPServer.ms.com\d$\. = 510158 MB
ï»¿<01-16-2015 08:48:40> DPServer.ms.com;    Free disk space on site server;    Passed
ï»¿<01-16-2015 08:48:47> DPServer.ms.com;    Pending system restart;    Passed
ï»¿<01-16-2015 08:48:50> INFO: The server DPServer.ms.com is not read-only domain controller.
ï»¿<01-16-2015 08:48:50> DPServer.ms.com;    Read-Only Domain Controller;    Passed
ï»¿<01-16-2015 08:48:50> INFO: Check FQDN Length for site server: <DPServer.ms.com>.
ï»¿<01-16-2015 08:48:50> DPServer.ms.com;    Site Server FQDN Length;    Passed
ï»¿<01-16-2015 08:48:50> <<<RuleCategory: Dependent Components>>>
ï»¿<01-16-2015 08:48:50> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
ï»¿<01-16-2015 08:48:57> DPServer.ms.com;    Microsoft XML Core Services 6.0 (MSXML60);    Warning;    MSXML 6.0 or later libraries are required for Configuration Manager console and Configuration Manager site
server installations. MSXML 6.0 is available for download at http://go.microsoft.com/fwlink/?LinkId=215744
ï»¿<01-16-2015 08:49:03> DPServer.ms.com;    Microsoft Remote Differential Compression (RDC) library registered;    Error;    Microsoft Remote Differential Compression (RDC) library must be registered for Configuration
Manager site server installation. Details at http://technet.microsoft.com/library/cc431377.aspx#RDC_for_Site_Servers.
ï»¿<01-16-2015 08:49:03> INFO: Checking Windows Installer version on DPServer.ms.com.
ï»¿<01-16-2015 08:49:13> INFO: Path of Windows Installer is <\\DPServer.ms.com\C$\Windows\System32\msi.dll>.
ï»¿<01-16-2015 08:49:19> ERROR: Failed to determine Windows Installer version from path:<\\DPServer.ms.com\C$\Windows\System32\msi.dll> .
ï»¿<01-16-2015 08:49:19> DPServer.ms.com;    Microsoft Windows Installer;    Error;    Setup failed to verify the Windows Installer version, or the installed version of Windows Installer does not meet the minimum
requirement. Configuration Manager requires at least Windows Installer version 4.5.
ï»¿<01-16-2015 08:49:19> INFO: Start Checking InstallSQLExpress on site server: DPServer.ms.com, SQL Server instance CONFIGMGRSEC
ï»¿<01-16-2015 08:49:28> INFO: SQL Server Instance Names value was not found
ï»¿<01-16-2015 08:49:28> INFO: IsPortUsedByAnySqlInstance port 1433.
ï»¿<01-16-2015 08:49:39> INFO: TCP port 1433 is not in use by any other SQL Server instances.
ï»¿<01-16-2015 08:49:49> INFO: Sql express: OS version:0, ServicePack:0.
ï»¿<01-16-2015 08:49:49> ERROR: Cannot install sqlexpress 2012, not meet OS requirement: Windows server 2008 sp2, Windows server 2008 R2 sp1 or higher.
ï»¿<01-16-2015 08:49:49> DPServer.ms.com;    SQL Server Express on Secondary Site;    Error;    A SQL Server instance is already installed on the secondary site server using the instance name CONFIGMGRSEC,
or the specified TCP port is being used by another SQL Server instance, or OS version is not Windows Server 2008 sp2, Windows Server 2008 R2 sp1 or higher. Setup is unable to install SQL Server Express on the secondary site.
ï»¿<01-16-2015 08:49:55> ERROR: Failed to connect to registry of DPServer.ms.com
ï»¿<01-16-2015 08:49:55> DPServer.ms.com;    Existing Configuration Manager server components on site server;    Error;    A site server or site system role is already installed on the computer selected for
site server installation. Remove the site or site system role from the computer, or select another computer for site server installation.
ï»¿<01-16-2015 08:49:55> DPServer.ms.com;    Firewall exception for SQL Server (stand-alone primary site);    Passed
ï»¿<01-16-2015 08:49:55> INFO: SQL Server computer <DPServer.ms.com>
ï»¿<01-16-2015 08:49:55> INFO: SQL Server named instance <>
ï»¿<01-16-2015 08:49:55> INFO: Install SQL Server Express on secondary site, skip checking.
ï»¿<01-16-2015 08:49:55> DPServer.ms.com;    SQL Server service running account;    Passed
ï»¿<01-16-2015 08:49:55> INFO: Install SQL Server Express on secondary site, skip checking.
ï»¿<01-16-2015 08:49:55> DPServer.ms.com;    Dedicated SQL Server instance;    Passed
ï»¿<01-16-2015 08:49:55> INFO: CheckSQLCollationSecondary
ï»¿<01-16-2015 08:49:55> INFO: Installing SQL Server Express; skipping
ï»¿<01-16-2015 08:49:55> DPServer.ms.com;    Parent/child database collation;    Passed
ï»¿<01-16-2015 08:49:55> INFO: Checking .NET framework versions 3.5...
ï»¿<01-16-2015 08:50:05> INFO: .NET is installed
ï»¿<01-16-2015 08:50:05> DPServer.ms.com;    Minimum .NET Framework version for Configuration Manager site server;    Passed
ï»¿<01-16-2015 08:50:05> INFO: Checking .NET version required for installing SQL Server Express for Secondary Site.
ï»¿<01-16-2015 08:50:05> INFO: Checking .NET framework versions 4.0...
ï»¿<01-16-2015 08:50:10> INFO: .NET is installed
ï»¿<01-16-2015 08:50:11> DPServer.ms.com;    Minimum .NET Framework version for SQL Server Express edition installation for Configuration Manager Secondary Site;    Passed
ï»¿<01-16-2015 08:50:11> INFO: CheckInstallSourceVersion <D:\SCCM2012\Source>
ï»¿<01-16-2015 08:52:29> ERROR: Could not read install map from \\DPServer.ms.com\D$\\SCCM2012\Source\SMSSETUP\install.map (result 2)
ï»¿<01-16-2015 08:52:29> DPServer.ms.com;    Setup Source Version;    Error;    The product version in the source folder specified for secondary site installation does not match the version of the primary site.
ï»¿<01-16-2015 08:52:29> INFO:CheckInstallSourcePath <DPServer.ms.com>
ï»¿<01-16-2015 08:52:55> ERROR: Failed to call GetResultByRunningService
ï»¿<01-16-2015 08:52:55> DPServer.ms.com;    Setup Source Folder;    Error;    The computer account for the secondary site must have Read NTFS and share permissions to the Setup source folder and share. We
recommend that you do not use administrative shares (for example, C$ and D$) because they require the secondary site computer account to be an administrator on the remote computer.
ï»¿<01-16-2015 08:52:55> INFO: Enter CheckSecSiteSqlOnSameMachine.
ï»¿<01-16-2015 08:52:55> INFO: Installing SQL Server Express, skipping SQL Server check.
ï»¿<01-16-2015 08:52:55> DPServer.ms.com;    SQL Server on the Secondary Site Computer;    Passed
ï»¿<01-16-2015 08:52:55> INFO:CheckSupportedFQDNFormat <DPServer.ms.com>
ï»¿<01-16-2015 08:53:04> INFO: NetBIOS <NZWHKVMAS020>
ï»¿<01-16-2015 08:53:04> DPServer.ms.com;    Primary FQDN;    Passed
ï»¿<01-16-2015 08:53:04> INFO:CheckMachineAccountHasADAccess <DPServer.ms.com>
ï»¿<01-16-2015 08:53:30> ERROR: Failed to call GetResultByRunningService
ï»¿<01-16-2015 08:53:30> DPServer.ms.com;    Verify site server permissions to publish to Active Directory.;    Warning;    The site server might be unable to publish to Active Directory. The computer account
for the site server must have Full Control permissions to the System Management container in its Active Directory domain. You can ignore this warning if you have manually verified these permissions. For more information about your options to configure required
permissions, see http://go.microsoft.com/fwlink/p/?LinkId=233190.
ï»¿<01-16-2015 08:53:30> INFO:CheckRemoteWMIConnection <DPServer.ms.com>
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    Remote Connection to WMI on Secondary Site;    Passed
ï»¿<01-16-2015 08:53:44> INFO: Check required collation of Sql Server.
ï»¿<01-16-2015 08:53:44> INFO: LangID <409>
ï»¿<01-16-2015 08:53:44> INFO: NOT primary site or CAS install, skipping check for reqired collation of SQL Server.
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    Required SQL Server Collation;    Passed
ï»¿<01-16-2015 08:53:44> ===== INFO: Prerequisite Type & Server: SQL:DPServer.ms.com =====
ï»¿<01-16-2015 08:53:44> <<<RuleCategory: Access Permissions>>>
ï»¿<01-16-2015 08:53:44> <<<CategoryDesc: Checking access permissions...>>>
ï»¿<01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping check for sysadmin role on SQL Server.
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    SQL Server sysadmin rights;    Passed
ï»¿<01-16-2015 08:53:44> INFO: Skip testing, no expand primary site specified.
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    SQL Server sysadmin rights for reference site;    Passed
ï»¿<01-16-2015 08:53:44> INFO: The rule 'Site server computer account administrative rights' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping Windows integrated security check.
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    SQL Server security mode;    Passed
ï»¿<01-16-2015 08:53:44> <<<RuleCategory: System Requirements>>>
ï»¿<01-16-2015 08:53:44> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
ï»¿<01-16-2015 08:53:44> INFO: The rule 'Unsupported site server operating system version for Setup' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:53:44> INFO: The rule 'Domain membership' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:53:44> INFO: The rule 'Pending system restart' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:53:44> <<<RuleCategory: Dependent Components>>>
ï»¿<01-16-2015 08:53:44> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
ï»¿<01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping SQL Server version check.
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    SQL Server version;    Passed
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    SQL Server Edition;    Passed
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    SQL Server Tcp Port;    Passed
ï»¿<01-16-2015 08:53:44> INFO: Checking if SQL Server memory is limited.
ï»¿<01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping SQL Server memory check.
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    Configuration for SQL Server memory usage;    Passed
ï»¿<01-16-2015 08:53:44> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
ï»¿<01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping SQL Server memory allocation check.
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    SQL Server process memory allocation;    Passed
ï»¿<01-16-2015 08:53:44> INFO: Installing SQL Server Express, skipping SQL Server case insensitive validation.
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    Case-insensitive collation on SQL Server;    Passed
ï»¿<01-16-2015 08:53:44> INFO: Check Machine FQDN: <DPServer.ms.com>.
ï»¿<01-16-2015 08:53:44> INFO: getaddrinfo returned success.
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    Validate FQDN of SQL Server Computer;    Passed
ï»¿<01-16-2015 08:53:44> INFO: The rule 'Primary FQDN' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:53:44> ===== INFO: Prerequisite Type & Server: MP:DPServer.ms.com =====
ï»¿<01-16-2015 08:53:44> <<<RuleCategory: Access Permissions>>>
ï»¿<01-16-2015 08:53:44> <<<CategoryDesc: Checking access permissions...>>>
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    Administrative share (Site system);    Passed
ï»¿<01-16-2015 08:53:44> INFO:CheckSiteSystemtoSQLConnectivity <DPServer.ms.com>
ï»¿<01-16-2015 08:53:44> INFO: Installing secondary site, skipping SQL Server connectivity check.
ï»¿<01-16-2015 08:53:44> DPServer.ms.com;    Site System to SQL Server Communication;    Passed
ï»¿<01-16-2015 08:53:44> <<<RuleCategory: System Requirements>>>
ï»¿<01-16-2015 08:53:44> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
ï»¿<01-16-2015 08:53:44> INFO: The rule 'Check Server Service is running' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:53:52> INFO: OS version:0, ServicePack:0.
ï»¿<01-16-2015 08:53:52> DPServer.ms.com;    Unsupported management point operating system version for Setup;    Warning;    Configuration Manager site systems can only be installed on systems running Windows
Server 2008 SP2 or later.
ï»¿<01-16-2015 08:53:52> INFO: The rule 'Domain membership' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:54:05> INFO: Windows Cluster not found on DPServer.ms.com.
ï»¿<01-16-2015 08:54:05> DPServer.ms.com;    Windows Failover Cluster;    Passed
ï»¿<01-16-2015 08:54:05> INFO: The rule 'Pending system restart' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:54:05> <<<RuleCategory: Dependent Components>>>
ï»¿<01-16-2015 08:54:05> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
ï»¿<01-16-2015 08:54:05> INFO: The rule 'Microsoft XML Core Services 6.0 (MSXML60)' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:54:10> DPServer.ms.com;    IIS service running;    Warning;    Internet Information Services (IIS) is required for some site system roles. You have selected to install a site system role that
requires IIS. Install IIS on the site system to continue setup.
ï»¿<01-16-2015 08:54:39> ERROR: Failed to get WEBSVCEXT from Remote Service on DPServer.ms.com.
ï»¿<01-16-2015 08:54:39> INFO: Failed to get IIS BITS Server Extensions state on DPServer.ms.com.
ï»¿<01-16-2015 08:54:39> DPServer.ms.com;    BITS installed;    Warning;    Background Intelligent Transfer Service (BITS) is required for the management point and distribution point site system roles. BITS
is not installed, IIS 6 WMI compatibility component for IIS7 is not installed on this computer or the remote IIS host, or Setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. Also, check
if IIS/BITS services are running properly. Setup cannot continue until BITS is installed and enabled in the IIS settings.
ï»¿<01-16-2015 08:55:08> ERROR: Failed to get WEBSVCEXT from Remote Service on DPServer.ms.com.
ï»¿<01-16-2015 08:55:08> INFO: Failed to get IIS BITS Server Extensions state on DPServer.ms.com.
ï»¿<01-16-2015 08:55:08> DPServer.ms.com;    BITS enabled;    Warning;    Background Intelligent Transfer Service (BITS) is required for the management point and distribution point site system roles. BITS is
not installed, IIS 6 WMI compatibility component for IIS7 is not installed on this computer or the remote IIS host, or Setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. Also, check
if IIS/BITS services are running properly. Setup cannot continue until BITS is installed and enabled in the IIS settings.
ï»¿<01-16-2015 08:55:08> DPServer.ms.com;    IIS HTTPS Configuration for management point;    Passed
ï»¿<01-16-2015 08:55:08> INFO: Stand-alone primary site or secondary site. Skip checking firewall settings for SQL Server
ï»¿<01-16-2015 08:55:08> DPServer.ms.com;    Firewall exception for SQL Server for management point;    Passed
ï»¿<01-16-2015 08:55:08> DPServer.ms.com;    Administrative rights on management point;    Passed
ï»¿<01-16-2015 08:55:08> INFO:CheckV4ClientNotInstalled <DPServer.ms.com>
ï»¿<01-16-2015 08:55:36> ERROR: Failed to call GetResultByRunningService
ï»¿<01-16-2015 08:55:36> DPServer.ms.com;    Client Version on Management Point Computer;    Warning;    You cannot install the management point on a computer with an earlier version of the Configuration Manager
client installed. Upgrade the client to the current version, remove the client, or select a different computer for the management point installation, and then try again.
ï»¿<01-16-2015 08:55:36> ===== INFO: Prerequisite Type & Server: DP:DPServer.ms.com =====
ï»¿<01-16-2015 08:55:36> <<<RuleCategory: Access Permissions>>>
ï»¿<01-16-2015 08:55:36> <<<CategoryDesc: Checking access permissions...>>>
ï»¿<01-16-2015 08:55:36> <<<RuleCategory: System Requirements>>>
ï»¿<01-16-2015 08:55:36> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
ï»¿<01-16-2015 08:55:49> DPServer.ms.com;    Unsupported distribution point operating system version for Setup;    Warning;    Configuration Manager distribution point can only be installed on systems running
Windows Server 2003 or later.
ï»¿<01-16-2015 08:55:49> INFO: The rule 'Domain membership' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:55:49> INFO: The rule 'Windows Failover Cluster' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:55:49> INFO: The rule 'Pending system restart' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:55:49> <<<RuleCategory: Dependent Components>>>
ï»¿<01-16-2015 08:55:49> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
ï»¿<01-16-2015 08:55:57> DPServer.ms.com;    Microsoft XML Core Services 6.0 (MSXML60) for distribution point;    Warning;    MSXML 6.0 or later libraries are required for Configuration Manager console and
Configuration Manager site server installations. MSXML 6.0 is available for download at http://go.microsoft.com/fwlink/?LinkId=215744
ï»¿<01-16-2015 08:55:57> INFO: The rule 'IIS service running' has been run on server 'DPServer.ms.com', skipped.
ï»¿<01-16-2015 08:55:57> DPServer.ms.com;    IIS HTTPS Configuration for distribution point;    Passed
ï»¿<01-16-2015 08:55:57> DPServer.ms.com;    Administrative rights on distribution point;    Passed
ï»¿<01-16-2015 08:55:57> ***************************************************
ï»¿<01-16-2015 08:55:57> ******* Prerequisite checking is completed. *******
ï»¿<01-16-2015 08:55:57> ***************************************************
ï»¿<01-16-2015 08:55:57> INFO: Updating Prerequisite checking result into the registry
ï»¿<01-16-2015 08:55:57> INFO: Connecting to DPServer.ms.com registry
ï»¿<01-16-2015 08:56:09> INFO: Setting registry values
ï»¿<01-16-2015 08:56:16> ERROR: Failed to update prerequisite results into the registry; error = 1.

ï»¿<01-16-2015 08:48:08> DPServer.ms.com;    Site server computer account administrative rights;    Error;    Configuration Manager Setup requires that the site server computer has administrative rights
on the SQL Server and management point computers.
Actually the administrative permission had been granted.

SCCM 2012 Secondary site Client Communication for SUP

Hi,
We have an SCCM 2012 Setup and here is the design CAS-->Primary-->Secondary site servers.
SUP is configured for Secondary site too. Boundaries are defined with IP Address Range and is proper.
Some clients are comminicating to Secondary site for updates. Downloading successfully and installing the software.
But some of the clients are communicating to primary site for updates and retain with the status "Downloading update"
I have checked the locationservices.log and it is fluctuating between Primary and secondary MP.
2 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:35:59 AM 768 (0x0300)
Executing Task LSSiteRoleCycleTask LocationServices 4/5/2013 11:51:59 AM 4200 (0x1068)
1 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:51:59 AM 4200 (0x1068)
Executing Task LSSiteRoleCycleTask LocationServices 4/5/2013 11:51:59 AM 5648 (0x1610)
2 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:51:59 AM 5648 (0x1610)
I have also checed "DataTransferService.log" and found more errors.
Error retrieving manifest (0x800704cf). Will attempt retry 7 in 1920 seconds. DataTransferService 4/5/2013 11:51:59 AM 5576 (0x15C8)
DTSJob {141CB5AE-8EF2-464D-8D8C-68B868EE7F7B} in state 'DownloadingManifest'. DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
Failed to send request to /SMS_DP_SMSPKG$/1fd86ee1-ece0-41ae-a2b8-5a2b305746d4 at host xxxxxxxx.xxxxxxx.com, error 0x2efe DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
[CCMHTTP] ERROR: URL=https://xxxxxxxx.xxxxxxx.com:443/SMS_DP_SMSPKG$/1fd86ee1-ece0-41ae-a2b8-5a2b305746d4, Port=443, Options=192, Code=12030, Text=ERROR_WINHTTP_CONNECTION_ERROR DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
Raising event:
instance of CCM_CcmHttp_Status
ClientID = "GUID:0DA907D5-1709-4B10-B627-61E289FD7149";
DateTime = "20130405062159.643000+000";
HostName = "xxxxxxxx.xxxxxxx.com";
HRESULT = "0x80072efe";
ProcessID = 4260;
StatusCode = 600;
ThreadID = 4200;
DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
Successfully sent location services HTTPS failure message. DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
Error sending DAV request. HTTP code 600, status '' DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
GetDirectoryList_HTTP mapping original error 0x80072efe to 0x800704cf. DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
GetDirectoryList_HTTP('https://xxxxxxxx.xxxxxxx.com:443/SMS_DP_SMSPKG$/1fd86ee1-ece0-41ae-a2b8-5a2b305746d4') failed with code 0x800704cf. DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
Error retrieving manifest (0x800704cf). Will attempt retry 7 in 1920 seconds. DataTransferService 4/5/2013 11:51:59 AM 4200 (0x1068)
my query is how some of the clients are communicating primary site server for updates even though the boundary details are properly configured and Secondary site is configured with sup. Also need to know (as per the log "DataTransferService.log")how
come the clients are communicating SSL port for updates. Plz help in resolving the issue.

Hi Kent,
Thanks for the reply.
Primary and secondary sites are connected over WAN and we have around 2000 clients which are reporting to Secondary site.
Considering the WAN bandwidth utiliztaion and number of clients on secondary site we have configured the SUP role.
Not all the clients are with the above error message around 40%-50% of the clients are with above stated error message.
Plz let me know what is the error message indicates and do we need to reffer any other logs for indepth analysis.
Locationservices.log is with fluctuating connectivity
2 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:35:59 AM 768 (0x0300)
Executing Task LSSiteRoleCycleTask LocationServices 4/5/2013 11:51:59 AM 4200 (0x1068)
1 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:51:59 AM 4200 (0x1068)
Executing Task LSSiteRoleCycleTask LocationServices 4/5/2013 11:51:59 AM 5648 (0x1610)
2 proxy MP errors in the last 10 minutes, threshold is 5. LocationServices 4/5/2013 11:51:59 AM 5648 (0x1610)
how come the clients are communicating SSL port for updates. Plz help in resolving the issue.

SCCM 2012 Secondary site some client's are scan hardware inventory for more than 30 days

Hi,
In our SCCM 2012 environment we have secondary site configured which connected with 8500 computers, on those 5500 machines scanning hardware inventory and send latest inventory details to Secondary Site Management Point, but remaing 3000 machines are not
sending latest hardware inventory for more than 30 days. I verified clients log found it is generating report on inventory agent.log however it is not available with secondary site Management Point.
Are anyone experienced this issue, please share your thought how to fix this issue.
Thanks in advance.
Madhan

Yes i did verify but the client isn't listed on both log files. Also i couldn't open IIS log because of it size has more than 800MB. currently this site has connected with 8500 machines do you think these many clients are supported by secondary site server.
If you can't open the IIS log then how do you know that the Client's IP is not listed within them?
5000 is the max for a secondary site. You will need to secondary sites at this location.
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigClientNumbers
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2012 on Server 2012 and WSUS 3.0 SP2 on Server 2008

We are installing SCCM 2012 SP1 fresh into our development environment - the primary site server and the database (SQL 2012) are both being installed on Server 2012.
We have an existing WSUS box on a Windows 2008 (not R2) server - the WSUS server version is 3.2.7600.256. We have set this up as the software update point.
For the purposes of this discussion, these are the server names (obviously obfuscated):
Primary site server: sccm.domain.local
Database server: sccmdb.domain.local
WSUS server: wsus.domain.local
On the primary SCCM server, I've installed the WSUS user interface (Install-WindowsFeature -Name UpdateServices-UI), in order to work with the remote WSUS server.
Updates synchronization appears to be working fine, but when I try to setup client distribution via SUP, I'm getting the following error in the Application event log:
Log Name:      Application
Source:        SMS Server
Date:          8/6/2013 11:03:11 AM
Event ID:      6613
Task Category: SMS_WSUS_CONFIGURATION_MANAGER
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      sccm.domain.local
Description:
On 8/6/2013 11:03:11 AM, component SMS_WSUS_CONFIGURATION_MANAGER on computer sccm.domain.local reported: WSUS Configuration Manager failed to publish client boot-strapper package "9D5353E5-DA80-48C3-97DE-C9C528F73A2D" with version "5.00.7804.1000"
to the Software Updates Point.
As well as this in the WMC.log:
PublishApplication(9D5353E5-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions do not match.~~   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String
sdpFile)~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String sdpFile)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile) $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013
11:03:11.787+240><thread=3704 (0xE78)>
ERROR: Failed to publish sms client to WSUS, error = 0x80131509 $$<SMS_WSUS_CONFIGURATION_MANAGER><08-06-2013 11:03:11.803+240><thread=3704 (0xE78)>
It would seem obvious that this is because of a mismatch in versions between the WSUS server version on wsus.domain.local, compared to the UpdateServices UI on sccm.domain.local.
Is there a way around this, without having to upgrade the WSUS server to Server 2012?
Thanks for any thoughts you may have!

Not really. As mentioned though, even the separate WSUS server is probably overkill. In ConfigMgr, WSUS is used to handle the update catalog and that's it. Clients do *not* report status to the WSUS instance and do *not* download updates from the WSUS instance.
No management is ever done in WSUS.
So, in reality, once a month, clients connect to WSUS to download the delta update catalog (delta compared to what they currently have) which usually comes out to about a few hundred KB (yes KB, not MB) -- this download is done via BITS. The server also
syncs the catalog from the WSUS instance, via the SUP, in a similar fashion. If you are using SCEP, the frequency will be greater, but the deltas will be much smaller.
EULAs, as needed, are also stored in WSUS and accessed by clients -- these are also quite small only a select few updates requires them.
That's it. Standing up a dedicated WSUS instance means having a server sitting there doing almost nothing else.
If you are concerned about load on the site server, then you should create a separate site system that contains the MP, SUP (and WSUS instance), and DP. Then, for HA purposes, you can simply build a second site system with these three roles also and HA will
essentially be automatic (from a client functionality perspective).
Jason | http://blog.configmgrftw.com

Inplace upgrade SCCM 2012 R2 server OS from 2008 R2 to 2012R2 and SQL 2008R2 to 2012

Hi
Is it possible to do inplace upgrade?
I have Windows Server 2008 R2, SCCM 2012 R2 CU1, SQL 2008 R2, WSUS and MDT 2013.
Can I upgrade to Windows server 2012 R2 and SQL server 2012?
Are there any catches which I must know before upgrade?
Do I start upgrade with OS and then SQL?

The in-place upgrade of the operating system is not supported...
For a complete list see:
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_UpgradeInfrastructure
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2012 migrate server A to Server B.

Right now I have BACKOFFICE running Windows 2008 R2 server which has SCCM 2012 SP1 installed and is in production. I did a newly installed of another primary stand alone SCCM 2012 SP1 on SCCMSERVER running Windows 2012 R2. My question are
1. What is the best way to migrate all of BACKOFFICE ConfigMgr 2012 database or roles into the new SCCMSERVER. What tools or steps can I use to do this?
2. When can I safely uninstall ConfigMgr 2012 off BACKOFFICE ?
Thanks for your help,
Voev

The steps are the same. You set up a source hierarchy and then create migration jobs.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM 2012 secondary server

Similar Messages

Maybe you are looking for