WSUS 4.0 and SCCM 2012 SP1 Sync Errors

SCCM 2012 SP1 is installed on a Windows 2012 Std server with the WSUS 4.0 Role installed.
All other links I have found list a 2008 R2 Server with WSUS 3.0 SP2 hence all the "fixes" revolve around hot fixes and patches/settings for WSUS 3.0 or 2008 R2 systems.
WSUS is set for port 8530/8531
SCCM SUP is set for ports 8530/8531
Both are on same machine (single site SCCM 2012 SP1 System)
What does Bad Configuration, SUPs present but no default SUP
mean and how do I fix it?
Recent entry in my WCM.LOG states:
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.401+420><thread=6052 (0x17A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.454+420><thread=6052 (0x17A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.481+420><thread=6052 (0x17A4)>
Changes in active SUP list detected. New active SUP List is:~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.489+420><thread=6052 (0x17A4)>
SUP0: SCCM2012.xxdomainnamexx.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.496+420><thread=6052 (0x17A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.503+420><thread=6052 (0x17A4)>
Bad Configuration, SUPs present but no default SUP $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.510+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.525+420><thread=6052 (0x17A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.535+420><thread=6052 (0x17A4)>
Waiting for changes for 11 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.543+420><thread=6052 (0x17A4)>
Wait timed out after 11 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:04:54.569+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.577+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.585+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.592+420><thread=6052 (0x17A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:04:54.714+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.721+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.728+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.734+420><thread=6052 (0x17A4)>
Randall

Here is my WCM Log from this mornings "re-attempt"
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:22.156+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.179+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.181+420><thread=5540 (0x15A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.194+420><thread=5540 (0x15A4)>
No SUPs are present $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.199+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.220+420><thread=5540 (0x15A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.224+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.226+420><thread=5540 (0x15A4)>
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:37.356+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.388+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.493+420><thread=5540 (0x15A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.541+420><thread=5540 (0x15A4)>
Changes in active SUP list detected. New active SUP List is:~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.543+420><thread=5540 (0x15A4)>
SUP0: SCCM2012.MORTONGENERAL.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.546+420><thread=5540 (0x15A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.550+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.553+420><thread=5540 (0x15A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.559+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.562+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.593+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.596+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.611+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.614+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.617+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.620+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.634+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.637+420><thread=5540 (0x15A4)>
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.640+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.761+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.798+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.813+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.823+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.826+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.840+420><thread=5540 (0x15A4)>
Waiting for changes for 23 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.843+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.846+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.849+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:07.863+420><thread=5540 (0x15A4)>
Waiting for changes for 23 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:07.866+420><thread=5540 (0x15A4)>
Wait timed out after 23 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:30.913+420><thread=5540 (0x15A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.917+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.920+420><thread=5540 (0x15A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.923+420><thread=5540 (0x15A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:31.041+420><thread=5540 (0x15A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.045+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.048+420><thread=5540 (0x15A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.051+420><thread=5540 (0x15A4)>
Randall

Similar Messages

SCCM 2012 SP1 - SUP Error

Hi guys,
i upgraded my SCCM 2012 test Environment to SP1. I have only one Primary Site Server which holds all Roles. Everything seems to work fine except the SUP Role. If i try to synchronize the latest Updates it says that it cannot find a WSUS Server
and i should check WCM.LOG.
Within WCM.LOG i can find the following Messages:
Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 08:56:44 3620 (0x0E24)
Trigger event array index 0 ended. SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:07:56 3620 (0x0E24)
SCF change notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Setting new configuration state to 1 (WSUS_CONFIG_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Changes in active SUP list detected. New active SUP List is: SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
SUP0: CM01.TEST.LOCAL, group = , nlb = SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Updating active SUP groups... SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Bad Configuration, SUPs present but no default SUP SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Default SUP not specified SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Setting new configuration state to 0 (WSUS_CONFIG_NONE) SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Waiting for changes for 47 minutes SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
So in General this tells me that it can find a SUP but this one is not specified as a DEFAULT SUP. How can i tell SCCM that this is my Default SUP? (I only have this one and it is configured to sync from Microsoft Update site). I have never seen
this before so i guess this is related to SP1?
PS: I also installed the 2 necessary WSUS Updates before i upgraded to SCCM SP1.
Thanks in lot in advance.
Stefan

None of your solutions apply to WSUS 4.0 on Server 2012
None of the specified patches applies or will run on a Windows 2012 Std server. They either report that WSUS 3 SP 2 isn't installed OR that the patch isn't applicable to the server version installed.
Here is a excerpt of MY WCM.LOG
I have a fully patched Windows 2012 Standard Server, Fully updated SCCM 2012 SP1 installed, and am connected to a fully patched SQL2012 Server on another fully patched Windows 2012 Std server.
Ports 8530 and 8531 designated on both the WSUS 4.0 Role and SCCM 2012 SP1 system (both are on same server)
SUP0: SCCM2012.xxdomainname.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.496+420><thread=6052 (0x17A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.503+420><thread=6052 (0x17A4)>
Bad Configuration, SUPs present but no default SUP $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.510+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.525+420><thread=6052 (0x17A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.535+420><thread=6052 (0x17A4)>
Waiting for changes for 11 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.543+420><thread=6052 (0x17A4)>
Wait timed out after 11 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:04:54.569+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.577+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.585+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.592+420><thread=6052 (0x17A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:04:54.714+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.721+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.728+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.734+420><thread=6052 (0x17A4)>
Randall

WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

Hi,
I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
wsyncmgr:
Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
1/9/2015 12:00:00 PM 3668 (0x0E54)
WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Remote configuration failed on WSUS Server.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
Regards,
Malwinder

WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
It's not only a matter of installing the console, but also those hotfixes on a remote server ...
Torsten Meringer | http://www.mssccmfaq.de

SQL 2012 SP1 and SCCM 2012 SP1

Hi,
I am installing SCCM 2012 SP1 with SQL 2012 SP1 in Stand-Alone mode. But I am receiving error:"the service broker endpoint cannot listen on port 4022 because it is in use by another process"
I saw in SQL (SQL Server Configuration Manager) that I am using port 4022 without dinamic port.
Thaks.
Lessandro Zampieri - http://lezampieri.com

Thanks for the reply.
C:\>netstat -ano
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 780
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:4022 0.0.0.0:0 LISTENING 4664
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 528
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 836
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 900
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING 624
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 624
TCP 0.0.0.0:49217 0.0.0.0:0 LISTENING 616
TCP 0.0.0.0:49219 0.0.0.0:0 LISTENING 4184
TCP 0.0.0.0:49389 0.0.0.0:0 LISTENING 2056
TCP 0.0.0.0:49627 0.0.0.0:0 LISTENING 5060
TCP 127.0.0.1:49390 0.0.0.0:0 LISTENING 2056
TCP 127.0.0.1:49628 0.0.0.0:0 LISTENING 5060
TCP 127.0.0.1:57593 0.0.0.0:0 LISTENING 4664
TCP 192.168.100.30:139 0.0.0.0:0 LISTENING 4
TCP 192.168.100.30:445 192.168.100.20:49420 ESTABLISHED 4
TCP 192.168.100.30:445 192.168.100.20:49421 ESTABLISHED 4
TCP 192.168.100.30:445 192.168.100.20:49422 ESTABLISHED 4
TCP 192.168.100.30:445 192.168.100.20:49423 ESTABLISHED 4
TCP 192.168.100.30:4022 192.168.100.30:61430 ESTABLISHED 4664
TCP 192.168.100.30:4022 192.168.100.30:61496 ESTABLISHED 4664
TCP 192.168.100.30:49627 192.168.100.40:55914 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55915 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55921 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55922 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55926 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55927 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55928 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55929 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55930 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55967 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55992 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55998 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56001 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56002 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56009 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56077 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56211 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56656 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56687 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56817 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56891 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56946 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56959 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57027 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57072 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57223 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57240 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57248 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57268 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57292 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57293 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57294 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57311 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57312 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57314 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57320 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57340 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57342 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57343 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57369 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57372 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57379 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57385 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57386 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57387 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57388 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57389 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57390 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57391 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57392 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57393 ESTABLISHED 5060
TCP 192.168.100.30:61430 192.168.100.30:4022 ESTABLISHED 4112
TCP 192.168.100.30:61496 192.168.100.30:4022 ESTABLISHED 4112
TCP 192.168.100.30:61537 192.168.100.10:49158 TIME_WAIT 0
TCP [::]:80 [::]:0 LISTENING 4
TCP [::]:135 [::]:0 LISTENING 780
TCP [::]:443 [::]:0 LISTENING 4
TCP [::]:445 [::]:0 LISTENING 4
TCP [::]:4022 [::]:0 LISTENING 4664
TCP [::]:5985 [::]:0 LISTENING 4
TCP [::]:47001 [::]:0 LISTENING 4
TCP [::]:49152 [::]:0 LISTENING 528
TCP [::]:49153 [::]:0 LISTENING 836
TCP [::]:49154 [::]:0 LISTENING 900
TCP [::]:49155 [::]:0 LISTENING 624
TCP [::]:49156 [::]:0 LISTENING 624
TCP [::]:49217 [::]:0 LISTENING 616
TCP [::]:49219 [::]:0 LISTENING 4184
TCP [::]:49389 [::]:0 LISTENING 2056
TCP [::]:49627 [::]:0 LISTENING 5060
TCP [::1]:49390 [::]:0 LISTENING 2056
TCP [::1]:49628 [::]:0 LISTENING 5060
TCP [::1]:57593 [::]:0 LISTENING 4664
UDP 0.0.0.0:123 *:* 948
UDP 0.0.0.0:500 *:* 900
UDP 0.0.0.0:1434 *:* 3000
UDP 0.0.0.0:4500 *:* 900
UDP 0.0.0.0:5355 *:* 124
UDP 127.0.0.1:51181 *:* 4132
UDP 127.0.0.1:51338 *:* 124
UDP 127.0.0.1:55475 *:* 900
UDP 127.0.0.1:59835 *:* 1628
UDP 127.0.0.1:60840 *:* 3596
UDP 127.0.0.1:62010 *:* 1816
UDP 127.0.0.1:62390 *:* 4112
UDP 127.0.0.1:64129 *:* 624
UDP 192.168.100.30:137 *:* 4
UDP 192.168.100.30:138 *:* 4
UDP [::]:123 *:* 948
UDP [::]:500 *:* 900
UDP [::]:1434 *:* 3000
UDP [::]:4500 *:* 900
All things are correct?
Att.,
Lessandro Zampieri - http://lezampieri.com

Sccm 2012 sp1 sms_object_replication_manager error

Hello,
Since the migration of SCCM 2012 to
SCCM 2012 SP1, I have a
critical error on the error component
SMS_replication_object_manager 6004
Here is an excerpt of the log with
cmtrace objreplmgr.log on:
+++Completed processing CIN notification files SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 16:26:07 5240 (0x1478)
+++Begin processing changed GCA objects SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 16:26:07 5240 (0x1478)
STATMSG: ID=6004 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OBJECT_REPLICATION_MANAGER" SYS=NONETTE.GI.LCL SITE=G10 PID=5964 TID=5240 GMTDATE=mer. mars 20 15:26:07.982 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 16:26:07 5240 (0x1478)
Since two weeks
I can not find a solution.
Have you ever encountered this kind of problem?
thanks
jonathan

Here is what i get in the log objrepmgr.log
Successfully deleted Deployment Type ScopeId_1C06030C-B11E-4DE4-BCB4-B3D6166AF786/DeploymentType_61745739-f711-4601-815d-e62afa43b1d6/1 SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:41 5240 (0x1478)
*** delete vCI_ConfigurationItems where CI_ID=16927079 SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
*** [23000][547][Microsoft][SQL Server Native Client 11.0][SQL Server]L'instruction DELETE est en conflit avec la contrainte REFERENCE "CI_AssignmentTargetedCIs_CI_ConfigurationItems_FK2". Le conflit s'est produit dans la base de données "CM_G10", table
"dbo.CI_AssignmentTargetedCIs", column 'ActualCI_ID'. SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
Failed to delete Install Policy Type ScopeId_1C06030C-B11E-4DE4-BCB4-B3D6166AF786/RequiredApplication_a804a167-8077-4407-a5c3-eba81430cfcc/1 SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
STATMSG: ID=6004 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OBJECT_REPLICATION_MANAGER" SYS=NONETTE.GI.LCL SITE=G10 PID=5964 TID=5240 GMTDATE=mer. mars 20 11:46:42.185 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0 SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
+++Begin processing changed CIA objects SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
***** Processing Application Assignment {079743EE-F252-49F6-88C5-67760F061078} ***** SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
Deleting notification file C:\Program Files\Microsoft Configuration Manager\inboxes\objmgr.box\16777339.CIA SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
CI Assignment {079743EE-F252-49F6-88C5-67760F061078} has 1 Targeted CI(s) SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
Successfully deleted policy for CI Assignment {079743EE-F252-49F6-88C5-67760F061078} SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
Successfully deleted BGB policy for CI Assignment {079743EE-F252-49F6-88C5-67760F061078}, BGB Policy ID = {079743EE-F252-49F6-88C5-67760F061078}/RunOnce SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
STATMSG: ID=5802 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OBJECT_REPLICATION_MANAGER" SYS=NONETTE.GI.LCL SITE=G10 PID=5964 TID=5240 GMTDATE=mer. mars 20 11:46:42.816 2013 ISTR0="VLC media player 2.0.5_Tous les utilisateurs_Installer" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=414 AVAL0="{079743EE-F252-49F6-88C5-67760F061078}" SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
Successfully processed Application Assignment {079743EE-F252-49F6-88C5-67760F061078} SMS_OBJECT_REPLICATION_MANAGER 20/03/2013 12:46:42 5240 (0x1478)
thanks

WSUS Update KB2938066 and SCCM 2012 R2

Looking at the newly release WSUS update KB2938066 and wondering if I need to apply it to my SCCM WSUS component. If so, what type of impact on the SCCM clients should I be aware of?
Orange County District Attorney

As the update is about securing and hardening WSUS and also the communication with WU/MU, I would definitely apply this update.
The client-side is going to be tricky, depending on the configuration of your windows updates. Jason did a very good post about this here:
http://blog.configmgrftw.com/the-wua-dilemma-in-configmgr/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2012 SP1 - Patch error

Hi,
I am getting the below error in WCM.log when i try to sync with microsoft website.Please help
Log:
DB Server not detected for SUP DCMPSTPV01.devswad.net from SCF File. skipping.~ $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:08:39.994+00><thread=800 (0x320)>
Sync failed: WSUS update source not found on site SCW. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:08:40.006+00><thread=800 (0x320)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2136 TID=800 GMTDATE=Wed Jan 29 14:08:40.006 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source
not found on site SCW. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><01-29-2014
14:08:40.007+00><thread=800 (0x320)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:08:40.008+00><thread=800 (0x320)>
Setting sync alert to active state on site SCW $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:08:40.008+00><thread=800 (0x320)>
Sync time: 0d00h00m00s $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:08:40.018+00><thread=800 (0x320)>
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:08:45.056+00><thread=800 (0x320)>
Next scheduled sync is a retry sync at 29/01/2014 15:08:40 $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:08:50.208+00><thread=800 (0x320)>
Thread terminated by service request. $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:10:15.206+00><thread=800 (0x320)>
SMS_EXECUTIVE started SMS_WSUS_SYNC_MANAGER as thread ID 3660 (0xE4C). $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:11:19.045+00><thread=7148 (0x1BEC)>
Log level 2 $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:11:19.048+00><thread=3660 (0xE4C)>
Next scheduled sync is a retry sync at 29/01/2014 15:08:40 $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:11:22.063+00><thread=3660 (0xE4C)>
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:12:00.746+00><thread=3660 (0xE4C)>
Next scheduled sync is a retry sync at 29/01/2014 15:08:40 $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:12:05.857+00><thread=3660 (0xE4C)>
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:12.973+00><thread=3660 (0xE4C)>
Next scheduled sync is a retry sync at 29/01/2014 15:08:40 $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:30.358+00><thread=3660 (0xE4C)>
Wakeup by inbox drop $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:33.831+00><thread=3660 (0xE4C)>
Found local sync request file $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:40.027+00><thread=3660 (0xE4C)>
Starting Sync $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:40.028+00><thread=3660 (0xE4C)>
Performing sync on local request $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:40.028+00><thread=3660 (0xE4C)>
Read SUPs from SCF for DCMPSTPV01.devswad.net $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:40.036+00><thread=3660 (0xE4C)>
Found 1 SUPs $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:40.680+00><thread=3660 (0xE4C)>
Found active SUP DCMPSTPV01.devswad.net from SCF File.~ $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:40.680+00><thread=3660 (0xE4C)>
DB Server not detected for SUP DCMPSTPV01.devswad.net from SCF File. skipping.~ $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:40.681+00><thread=3660 (0xE4C)>
Sync failed: WSUS update source not found on site SCW. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:41.903+00><thread=3660 (0xE4C)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2640 TID=3660 GMTDATE=Wed Jan 29 14:14:41.904 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update
source not found on site SCW. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
$$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:41.905+00><thread=3660 (0xE4C)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:41.907+00><thread=3660 (0xE4C)>
Setting sync alert to active state on site SCW $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:41.907+00><thread=3660 (0xE4C)>
Sync time: 0d00h00m01s $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:42.186+00><thread=3660 (0xE4C)>
Next scheduled sync is a retry sync at 29/01/2014 15:14:41 $$<SMS_WSUS_SYNC_MANAGER><01-29-2014 14:14:42.392+00><thread=3660 (0xE4C)>
Regards, Pratap

Paul i got it, but when i select remote SQL server. I get the below error
Log@
2014-02-03 12:16:04 Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
2014-02-03 12:24:13 Success   MWUSSetup          Detected that setup was launched through Server Manager
2014-02-03 12:24:15 Success   MWUSSetup          Validating pre-requisites...
2014-02-03 12:24:15 Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the
file specified.)
2014-02-03 12:24:15 Error     MWUSSetup          WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
2014-02-03 12:24:42 Error     MWUSSetup          ExecuteQuery: Failed to execute SQL query SELECT SchemaVersion From SUSDB..tbSchemaVersion WHERE ComponentName= 'CoreDB' (Error 0x80040E14)
2014-02-03 12:24:42 Error     MWUSSetup          ExecuteQueryGetSingleResult: Failed to execute query SELECT SchemaVersion From SUSDB..tbSchemaVersion WHERE ComponentName= 'CoreDB' (Error
0x80040E14)
2014-02-03 12:24:42 Error     MWUSSetup          CheckDbConnection: Failed to run SQL query SELECT SchemaVersion From SUSDB..tbSchemaVersion WHERE ComponentName= 'CoreDB'. Assuming SUSDB
of incorrect version... (Error 0x80040E14)
2014-02-03 12:25:16 Success   MWUSSetup          Initializing installation details
2014-02-03 12:25:16 Success   MWUSSetup          Skipping Asp.Net install since not running on win2k3...
2014-02-03 12:25:16 Success   MWUSSetup          Installing wYukon using ocsetup
2014-02-03 12:25:16 Success   MWUSSetup          Windows Internal database is already installed on this machine
2014-02-03 12:25:16 Success   MWUSSetup          Installing WSUS...
2014-02-03 12:25:24 Success   CustomActions.Dll Unable to get INSTALL_LANGUAGE property, calculating it...
2014-02-03 12:25:24 Success   CustomActions.Dll The system language ENG is not supported. Using English resources...
2014-02-03 12:25:25 Success   CustomActions.Dll Successfully set propery of WSUS admin groups' full names
2014-02-03 12:25:26 Success   CustomActions.Dll .Net framework path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319
2014-02-03 12:25:34 Success   CustomActions.Dll Creating user group: WSUS Reporters with Description: WSUS Administrators who can only run reports on the Windows Server Update Services server.
2014-02-03 12:25:34 Success   CustomActions.Dll Creating WSUS Reporters user group
2014-02-03 12:25:34 Success   CustomActions.Dll WSUS Reporters user group already exists
2014-02-03 12:25:34 Success   CustomActions.Dll Successfully created WSUS Reporters user group
2014-02-03 12:25:34 Success   CustomActions.Dll Creating user group: WSUS Administrators with Description: WSUS Administrators can administer the Windows Server Update Services server.
2014-02-03 12:25:34 Success   CustomActions.Dll Creating WSUS Administrators user group
2014-02-03 12:25:34 Success   CustomActions.Dll WSUS Administrators user group already exists
2014-02-03 12:25:34 Success   CustomActions.Dll Successfully created WSUS Administrators user group
2014-02-03 12:25:34 Success   CustomActions.Dll Successfully created WSUS user groups
2014-02-03 12:25:34 Success   CustomActions.Dll Succesfully set binary SID property
2014-02-03 12:25:34 Success   CustomActions.Dll Succesfully set binary SID property
2014-02-03 12:25:34 Success   CustomActions.Dll Successfully set binary SID properties
2014-02-03 12:26:40 Success   CustomActions.Dll CopyADMFile:The system locale ENG is not supported. Using English...
2014-02-03 12:28:50 Info      IISCustomAction    Performing Setup Action, Command /Install
2014-02-03 12:29:10 Info      IISCustomAction    Command /Install Succeeded
2014-02-03 12:31:26 Success   MWUSSetup          WSUS Installed Successfully
2014-02-03 12:31:26 Success   MWUSSetup          Setup completed successfully
2014-02-03 14:32:57 Success   MWUSSetup          Detected that setup was launched through Server Manager
2014-02-03 14:32:58 Success   MWUSSetup          Validating pre-requisites...
2014-02-03 14:32:59 Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
2014-02-03 14:32:59 Error     MWUSSetup          WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
2014-02-03 14:33:45 Success   MWUSSetup          Initializing installation details
2014-02-03 14:33:45 Success   MWUSSetup          Skipping Asp.Net install since not running on win2k3...
2014-02-03 14:33:45 Success   MWUSSetup          Installing WSUS...
2014-02-03 14:33:47 Success   CustomActions.Dll Unable to get INSTALL_LANGUAGE property, calculating it...
2014-02-03 14:33:47 Success   CustomActions.Dll The system language ENG is not supported. Using English resources...
2014-02-03 14:33:48 Success   CustomActions.Dll Successfully set propery of WSUS admin groups' full names
2014-02-03 14:33:48 Success   CustomActions.Dll .Net framework path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319
2014-02-03 14:33:50 Success   CustomActions.Dll Creating user group: WSUS Reporters with Description: WSUS Administrators who can only run reports on the Windows Server Update Services server.
2014-02-03 14:33:50 Success   CustomActions.Dll Creating WSUS Reporters user group
2014-02-03 14:33:51 Success   CustomActions.Dll Successfully created WSUS Reporters user group
2014-02-03 14:33:51 Success   CustomActions.Dll Creating user group: WSUS Administrators with Description: WSUS Administrators can administer the Windows Server Update Services server.
2014-02-03 14:33:51 Success   CustomActions.Dll Creating WSUS Administrators user group
2014-02-03 14:33:51 Success   CustomActions.Dll Successfully created WSUS Administrators user group
2014-02-03 14:33:51 Success   CustomActions.Dll Successfully created WSUS user groups
2014-02-03 14:33:51 Success   CustomActions.Dll Succesfully set binary SID property
2014-02-03 14:33:51 Success   CustomActions.Dll Succesfully set binary SID property
2014-02-03 14:33:51 Success   CustomActions.Dll Successfully set binary SID properties
2014-02-03 14:34:36 Success   CustomActions.Dll CopyADMFile:The system locale ENG is not supported. Using English...
2014-02-03 14:36:36 Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
2014-02-03 14:36:36 Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
2014-02-03 14:36:36 Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
Regards, Pratap

SCCM 2012 SP1 - PXE error

Hi All,
I am trying to do a OS build via SCCM task sequence for esprimo c720. PXE boot is working fine but after the windows screen it goes blank and restarts in which i have tried below troubleshooting steps like
1. Updating the relevant drivers on the boot image
2. Verified drivers are getting installed manually and also standalone image is working fine
3. Enabled Command support and did IPconfig (Gave Windows IP configuration) and diskpart (gave disk space) which is fine i think
But when i try to ping the SCCM primary and DP server. It throws error as
PING TRANSMIT FAILED:GENERAL FAILURE. So i concluded the network adaptor with esprimo c720 has some issues. Is there any steps i need to try further. Please help
SMSTS Log:
<![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="1092" file="fwopen.cpp:146">
<![LOG[uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,185)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="1092"
file="tspxe.cpp:185">
<![LOG[Failed to download pxe variable file. Code(0x00000001)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSPxe" context="" type="3" thread="1092" file="tspxe.cpp:185">
<![LOG[PxeGetPxeData failed with 0x80004005]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSPxe" context="" type="3" thread="1092" file="tsmbootstraputil.cpp:1415">
<![LOG[HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1416)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSPxe" context=""
type="0" thread="1092" file="tsmbootstraputil.cpp:1416">
<![LOG[TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2623)]LOG]!><time="19:25:26.222+480" date="04-14-2014"
component="TSPxe" context="" type="0" thread="1092" file="tsmediawizardcontrol.cpp:2623">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSPxe"
context="" type="0" thread="1092" file="tsmbootstrap.cpp:1078">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1183)]LOG]!><time="19:25:26.222+480" date="04-14-2014"
component="TSPxe" context="" type="0" thread="1092" file="tsmbootstrap.cpp:1183">
<![LOG[Exiting with return code 0x80004005]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSPxe" context="" type="1" thread="1092" file="tsmbootstrap.cpp:1195">
<![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,515)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="1092"
file="environmentscope.cpp:515">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,337)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSPxe" context="" type="0"
thread="1092" file="environmentlib.cpp:337">
<![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,549)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSPxe" context="" type="0" thread="1092"
file="environmentlib.cpp:549">
<![LOG[Execution complete.]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="872" file="bootshell.cpp:690">
<![LOG[hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSBootShell" context="" type="0"
thread="872" file="environmentscope.cpp:515">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSBootShell" context="" type="0"
thread="872" file="environmentlib.cpp:337">
<![LOG[this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSBootShell" context="" type="0"
thread="872" file="environmentlib.cpp:549">
<![LOG[::RegOpenKeyExW (HKEY_LOCAL_MACHINE, c_szSMSTSKey, 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,258)]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSBootShell"
context="" type="0" thread="872" file="utils.cpp:258">
<![LOG[RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSBootShell" context="" type="2" thread="872" file="utils.cpp:258">
<![LOG[GetTsRegValue() failed. 0x80070002.]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSBootShell" context="" type="2" thread="872" file="utils.cpp:279">
<![LOG[End program: ]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="872" file="bootshell.cpp:722">
<![LOG[Finalizing logging from process 856]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="872" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="19:25:26.222+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="872" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="19:25:26.591+480" date="04-14-2014" component="TSBootShell" context="" type="1" thread="872" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="19:25:26.591+480" date="04-14-2014" component="TSBootShell" context="" type="0" thread="872" file="tslogging.cpp:584">
Regards, Pratap

Hi,
Major possible reasons for the error message PING: Transmit failed. General Failure are:
Misconfigured Firewall
Outdated Network drivers or firmware
DNS and other socket issues
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 SP1 + WSUS + Server 2012 + SQL Server 2012

Hi all;
I installed SCCM 2012 with Sp1 for my site server and everything is going well.. And than i installed the WSUS role on my Windows Server 2012 and SCCM 2012 SP1 it gave an error message which is "Fatal Error: The schema version of the database is from a newer
version of WSUS than currently installed. You must either patch your WSUS server to at least that version or drop the database." My database server is SQL Server 2012... Do you know any pathc for WSUS or SQL Server 2012 doesnt support WSUS yet???
Thank You...
MCT

Normally if you are going to install SCCM 2012 SP1 +Windows 2012 with SQL 2012, Then you better use the SQL 2012 sp1.
also when you are installing the WSUS version 6.2 which come with server 2012 make sure you leave the default settings as it is. it shows in the below article.
also when you are giving the path to save the WSUS contents make sure the drive you going to create the wsus folder and the place where you going to download the updates is having free disk space and its formatted with the NTFS volume. Also the service account
you are using for this configuration should have the admin rights to the location of the wsus folder you going to create,
Thanks
Hasitha

SCCM 2012 SP1 WSUS/Software Update Point Synchronization error on CAS.

Hi All,
Good day to all you.
I would like to seek all your help on this issue that i have encountering.
My SCCM 2012 SP1 CAS are having a synchronization error in WSUS/Software update point. The CAS have intergrated WSUS role in it. The last good synchronization was on July 16, 2014. No error log found on WCM.log and WSUSctrl.log
Error:
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall).
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
Sync failed. Will retry in 60 minutes
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
below are wsyncmgr.log:
Setting sync alert to active state on site C01 SMS_WSUS_SYNC_MANAGER (0x1690)
Sync time: 0d00h01m14s SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Starting Sync SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Read SUPs from SCF for MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Found active SUP MYHQKUL990707S.sdb.com from SCF File.
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:20.750 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:20 PM
5776 (0x1690)
Synchronizing WSUS server MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:21.763 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:21 PM
5776 (0x1690)
Using account sdb\SCCM-Admin to connect to WSUS Server
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Synchronizing WSUS server myhqkul990707s.sdb.com ...
SMS_WSUS_SYNC_MANAGER 440 (0x01B8)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER
440 (0x01B8)
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source:
Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
All response is much appreciated
Thank You

Hi,
I recommend you look at the IIS 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.

SCCM 2012 SP1 - Evil Folders in Reporting Services - What Are They and How to Remove Them

Hello All,
There are a lot of sub-folders in the http://CentralSiteSCCM/ReportServer. They are like:
<dir> Config_Mgr_CEN
<dir> Config_Mgr_CEN.OLD.0
<dir> Config_Mgr_CEN.OLD.1
<dir> Config_Mgr_CEN.OLD.10
<dir> Config_Mgr_CEN.OLD.100
<dir> Config_Mgr_CEN.OLD.1000
Only <dir> Config_Mgr_CEN is properly populated with the correct set of the default folders.
Would you be so kind to advise on:
What are they?
How to remove them?
What to do in order for them not to appear any more?
Thank you very much in advance!

Hi Mike,
I ran into an issue when I did the SP1 upgrade where a majority of our reports were duplicated. I created a script to delete these duplicate reports and I've adjusted it to work for your situation. You can find the original thread here, if you're interested:
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/dc9aa3b4-cea9-4a07-87ca-2795a2dbc04e
You'll need to know your SCCM site code and the server name to run this script.
# SCCM2012SP1-RemoveDuplicateSSRSFolders.ps1
# This script will connect to SSRS on a specified server and delete all folders that end with .OLD.*
# Used for SSRS cleanup after SCCM 2012 SP1 installation
# Script must be run from an account that has access to modify the SSRS instance
# 3/22/2013 - Mike Laughlin
# Resources used in writing this script:
# Starting point: http://stackoverflow.com/questions/9178685/change-datasource-of-ssrs-report-with-powershell
# API Documentation: http://msdn.microsoft.com/en-us/library/ms165967%28v=sql.90%29.aspx
# Previous script: http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/dc9aa3b4-cea9-4a07-87ca-2795a2dbc04e
# Define variables
$SiteCode = ""
$serverName = ""
# Set the value of $noConfirm to $True only if you don't want to manually confirm folder deletion. Use with caution.
$noConfirm = $False
# Safeguard
If ( $SiteCode -eq "" -or $serverName -eq "" ) { Write-Host "Enter the required information for the SiteCode and serverName variables before running this script." -ForegroundColor Red -BackgroundColor Black ; Exit }
# Connect to SSRS
$ssrs = New-WebServiceProxy -uri http://$serverName/ReportServer/ReportService2005.asmx?WSDL -UseDefaultCredential
# Get a listing of all folders in SSRS
$reportFolders = $ssrs.ListChildren("/", $True)
# Find all folders containing .OLD.*
$foldersToDelete = $reportFolders | Where { $_.Name -like "ConfigMgr_" + $SiteCode + ".OLD.*"}
# Quit if no folders are found
If ( $foldersToDelete.Count -eq 0 ) { Write-Host "No folders with .OLD.* found. Quitting." ; Exit }
# Show a listing of the folders that will be deleted
Write-Host "The following folders will be deleted from SSRS on" $serverName":`n"
$foldersToDelete.Name
Write-Host "`nTotal number of folders to delete:" $foldersToDelete.Count "`n"
# Get confirmation before deleting if $noConfirm has not been changed
If ( $noConfirm -eq $False )
$userConfirmation = Read-Host "Delete these folders from" $serverName"? Enter Y or N"
If ( $userConfirmation.ToUpper() -ne "Y" ) { Write-Host "Quitting, folders have not been deleted." ; Exit }
# Delete the folders
$deletedFolderCount = 0
Write-Host "Beginning to delete folders now. Please wait."
ForEach ( $folder in $foldersToDelete ) { $ssrs.DeleteItem($folder.Path) ; $deletedFolderCount++ }
Write-Host "Folders have been deleted. Total number of deleted folders:" $deletedFolderCount
Standard disclaimer: While this script worked just fine for me in my environment, I make no guarantees that it will work anywhere else. I've attempted to make this script as user friendly and generic as possible, but it may require slight tweaking to work properly.

Can I have an SCCM 2012 R2 server and a SCCM 2012 SP1 server in the same site?

We are currently using SCCM 2012 SP1/MDT 2012 Update 1 to deploy Windows 7, and to migrate existing XP installs to Windows 7 (using the offline USMT functionality in MDT). We are moving forward with Windows 8.1, and understand that
we need to upgrade our SCCM infrastructure to SCCM 2012 R2/MDT 2013. We also understand that this will cause us to lose the ability to migrate XP machines, since MDT 2013 uses a newer version of USMT that doesn’t support XP.
What do we need to do to continue to support our XP migrations, and enable deployments of Windows 8.1?
Can we have two SCCM servers in the same Site running different versions of SCCM? Do we need a separate site?

You don't explicitly need ConfigMgr 2012 R2 to support Win 8.1. SP1 CU3 will suffice although managing a few things like boot images is a little more difficult: http://blogs.technet.com/b/configmgrteam/archive/2013/10/21/how-to-enable-windows-8.1-deployment-in-sc-2012-configmgr-sp1-cu3.aspx
You could create two separate site hierarchies, but that would be painful and involve tons of duplication. There would be other issues also if the systems are located on the same subnets and in the same AD forest.
The best option is to get rid of XP. EOL is in less than 30 days!
Next best is to stay on SP1 CU3 until you get rid of XP. I know that sucks, but keeping XP around is the root cause of this and many other coming issues in any organization wanting to keep it around.
Jason | http://blog.configmgrftw.com

SCCM 2012 SP1 - Build and Capture - ReCapture impossible

Hi all
i upgrade my SCCM 2012 RTM to SCCM 2012 SP1 yesterday. Today i started a recapture of my Windows 7 and Windows 2008 R2 Base Image.
For that i have 2 VMs located in different SCCM Collections. And a Build and Capture Task Sequence is deployed to the collections.
Before SP1 the behavior was:
- Reset Required PXE Deployment in SCCM for the VMs
- Start VM
- VM boots with PXE
- VM installs and capture the Installation
And that i could do all the time so often as i want.
Now with SP1 it is the same procedure but just for one time. After one success Build and Capture Task, the vm is unable to do the task sequence again. The VM is booting into the PXE and then i can see in the smsts log:
There are no task sequences available to this computer
But there are. The Task Sequence is set to "Always rerun".
The only "fix" is to completely recreate the computer item in sccm.
What is here wrong? Is this a known bug?
best
JBAB

Hi, your problem is that when you deploy the task over the collation you only specified "media and PXE" was available to and probably the machines that you try to capture already had the sccm client. You can try to deploy the sequence task to a collation
including the the option "configuration manager, media and PXE", or you can also deploy the task sequence to de "unknown devices" collation and delete the objects of the two virtual machines in configuration manager

Deploying Office 2013 through SCCM 2012 SP1 leaves Office 2010 Tools and Sharepoint behind

I apologize in advance, but I have searched similar topics to this, but I haven't seen an answer yet that describes where and how to accomplish this. I'm also a bit new to SCCM and I'm still finding the nuances.
Scenario: Running SCCM 2012 SP1. Office 2013 32bit is added as an application and deployed properly with an accompanied .msp file stored in the source folder. The configuration is to have Office
2010 uninstalled silently. The deployment runs flawless and the user doesn't know otherwise. Success in anyone's book, right?
Except... Office 2010 Tools and SharePoint Workspace 2010 are left over. Manual uninstallation is not an option. This is for hundreds of PC's in several global locations.
I've seen it hinted to write a script. That's fine I suppose, but what do I write, where do I store the script, and can I have SCCM2012 automatically run it before the installation of 2013?
Our favorite IT tool Google hasn't quite returned what I'm looking for. Does anyone here have ideas or perhaps have experienced a similar issue?
Thanks,

1st, save the following content as a XML file on a server share, named as "config.xml".
<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="SETUP_REBOOT" Value="Never" />
</Configuration>
Run the following script during or before the installation of Office 2013:
"C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config \\servershare\Config.xml
For more SCCM specific topics, we'd recommend you to visit the SCCM forums at:
http://technet.microsoft.com/en-us/systemcenter/gg191847
Max Meng
TechNet Community Support

Deploy Java Updates using SCCM 2012 SP1 and SCUP 2011

What is the best way to deploy Java updates using sccm 2012 SP1 and SCUP 2011?

I didn´t find Kent´s blog useful when talking about Java. I can deploy Adobe products fine, but I have to import Java manually because not having Shavlik certificate. So with that said, I have the fallowing problem;
I have full offline installer unpacked, .msi file and Data1.cab. When I´m importing these binaries to SCUP, I only can point to .msi. Doing that, installation fails in client side fails because of lack of data1.cab fine, which is the main file.
Should I use some other downloaded files of Java? I couldn´t find any Java-update-file only type of files to download.

WSUS 4.0 and SCCM 2012 SP1 Sync Errors

Similar Messages

Maybe you are looking for