Ports for 2012 R2 - Agent Install

Hello,
I am getting blocks from our Firewall for ports 20639, 11180, 16614, 44503 (as examples) when trying to install an agent.
I thought (obviously mistakenly) that the following are required.
Can someone point me to the new list for 2012R2 please?
Thx
John Bradshaw
RPC endpoint mapper Port number: 135 Protocol: TCP/UDP
*RPC/DCOM High ports (2000/2003 OS) Ports 1024-5000 Protocol: TCP/UDP
*RPC/DCOM High ports (2008 OS) Ports 49152-65535 Protocol: TCP/UDP
NetBIOS name service Port number: 137 Protocol: TCP/UDP
NetBIOS session service Port number: 139 Protocol: TCP/UDP
SMB over IP Port number: 445 Protocol: TCP
MOM Channel Port number: 5723 Protocol: TCP/UDP

Communication is established by Agent. You need inbound port 5723 open on MS for regular monitoring after installation.
All those other ports you have listed are granular port settings, but this can all be accomplished simply by enabling remote administration and file & print sharing on agent. These are only required for setup to push installation files and
run the setup package.
If you manually install SCOM agent, you does not require to open the above list ports
Roger

Similar Messages

Ports for 2012

Hi,
We are getting blocked on Port 21594 when trying to do and Agent Install (2012R2).
I cannot find this port (or range containing this port in any documentation).
Has anyone got an idea about this, or better still, a link with the details about opening this port??
Thx
John Bradshaw

Hi,
For Agent push from the SCOM MS console you will need:
Keep in mind that you can closed this ports after the initial installation, but you won’t be able to repair or upgrade (Cannot remotely manage) agents from the console.
RPC endpoint mapper                                    Port number: 135
Protocol: TCP/UDP
*RPC/DCOM High ports (2000/2003 OS)   Ports 1024-5000            Protocol: TCP/UDP
*RPC/DCOM High ports (2008 OS)              Ports 49152-65535        Protocol: TCP/UDP
NetBIOS name service                                     Port number: 137
Protocol: TCP/UDP
NetBIOS session service                                Port number: 139
Protocol: TCP/UDP
SMB over IP
           Port number: 445           Protocol: TCP
SCOM Channel
Port number: 5723         Protocol: TCP/UDP
For Management Server deployment I would recommend having RPC enabled:
RPC endpoint mapper                                    Port number: 135
Protocol: TCP/UDP
RPC/DCOM High ports (2000/2003 OS)   Ports 1024-5000               Protocol: TCP/UDP
RPC/DCOM High ports (2008 OS)              Ports 49152-65535          Protocol: TCP/UDP
SCOM Channel
Port number: 5723         Protocol: TCP/UDP
Please also go through the below article:
System Requirements: System Center 2012 R2 Operations Manager
http://technet.microsoft.com/en-us/library/dn249696.aspx
Regards,
Yan Li
Regards, Yan Li

SCCM 2012 SP1 agent install via WSUS

Hi guys,
I'm having got an issue when I try installing the agent via WSUS. When I try installing manually everything seems to work.
Here are the infos from the ccmsetup.log:
==========[ ccmsetup started in process 2252 ]========== ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Running on platform X86 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Updated security on object C:\WINDOWS\ccmsetup\cache\. ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Launch from folder C:\WINDOWS\SoftwareDistribution\Download\Install\ ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
CcmSetup version: 5.0.7804.1000 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Ccmsetup command line: "C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe" ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSJoinedToADDomain ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Local Machine is joined to an AD domain ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetAssignedSiteFromAD ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
DhcpGetOriginalSubnetMask entry point is supported. ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Begin checking Alternate Network Configuration ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
spNamespace.Open(sNamespacePath), HRESULT=8004100e (e:\nts_sccm_release\sms\framework\ccmutillib\ccmiputil.cpp,1109) ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Finished checking Alternate Network Configuration ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetADSiteName ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Current AD site of machine is DE-Zeilarn ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Attempting to query AD for assigned site code ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=2887256160)(MSSMSRangedIPHigh>=2887256160))))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=172.24.8.0)(mSSMSRoamingBoundaries=DE-Zeilarn)(mSSMSSiteCode=XYZ)))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Verifying Site Compatibility for <XYZ> ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=XYZ))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7804.1000' for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Site Version = '5.00.7804.1000' Site Capabilities = <Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="31"/></Capabilities> ccmsetup 08.02.2013
13:45:47 196 (0x00C4)
LSIsSiteVersionCompatible : Site Version '5.00.7804.1000' is compatible. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Site <XYZ> Version '5.00.7804.1000' is compatible. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetAssignedSiteFromAD : Trying to Assign to the Site <XYZ> ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Got site code 'XYZ' from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieving client operational settings from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=XYZ))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
OperationalXml '<ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
HTTP is selected for Client. The current state is 0. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
The MP name retrieved is 'mysccmserver.mydomain.tld' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="31"/></Capabilities>' ccmsetup 08.02.2013
13:45:47 196 (0x00C4)
MP 'mysccmserver.mydomain.tld' is not compatible ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieved 0 MP records from AD for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Received client operational settings: <ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Http port 80; https port 443; select first cert 1; sslstate 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Certificate Issuers = ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FromAD: command line = SMSSITECODE=XYZ ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetManagementPointsForSiteFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
SslState value: 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Detected sitecode 'XYZ' from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPPORT:    80 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSPORT:    443 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSSTATE:    480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSCERTNAME:    ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FSP:    ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMCERTISSUERS:    CN=root-ca ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMFIRSTCERT:    1 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Creating CCMCertStore ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMCERTID:    SMS;FB0F35392A7FF68D2FA9C97D0CD54A3E0057964E ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
No MP or source location has been explicitly specified. Trying to discover a valid content location... ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Looking for MPs from AD... ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieving client operational settings from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Received client operational settings: <ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Http port 80; https port 443; select first cert 1; sslstate 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Certificate Issuers = CN=root-ca ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FromAD: command line = SMSSITECODE=XYZ ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetManagementPointsForSiteFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current directory 'C:\WINDOWS\SoftwareDistribution\Download\Install' is not a valid source location. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
DetermineInstallSource(), HRESULT=80004005 (e:\nts_sccm_release\sms\setup\ccmsetup\ccmsetup.cpp,4426) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Failed to parse '"C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe" ' with error 0x80004005 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::~CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
A Fallback Status Point has not been specified. Message with STATEID='307' will not be sent. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::~CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
ParseCommandLine(), HRESULT=80004005
My boundaries and boundary groups are configured, I can see the objects in the Systems Management Container in AD, but still the agent install via WSUS will not work. Any suggestions?
Cheers
Sebastian Bammer

see my latest post. It looks like a bug in the setup. It selects a certificate but still it presents information that iis on the mp does not accept. Check your iis logs. Manual install works for ssl only sites. I haven't got any other methods yet. I will
keep you updated.

DPM 2012 Manual Agent Install Fails

Hello Everyone,
Using DPM 2012 SP1, I've been stuck on an issue for some time now in trying to get a DPM agent install accomplished on a certain server. The DPM server resides on a parent domain and the server that I am having an issue with is on a child domain. Other servers
on the child domain have installed the agent without issue when doing it manually.
Here is the command I use (as an administrator):
net use X: \\DPMSERVERNAME.parentdomain.com\c$
cd /d X:\Program Files\Microsoft System Center 2012\DPM\DPM\agents\RA\4.1.3465.0\amd64\1033
DPMAgentInstaller_KB2991995_AMD64.exe dpmservername.parentdomain.com
The installation proceeds through the Microsoft License Terms, begins to install and then backs out. The error message that is generated states: "DPMAgentinstaller failed with error code = 0X80070643 error says: fatal error during installation"
In researching the 1708 error within the log file it lead me to the fact that maybe the firewall on the target server was the issue. I
ran this suggested fix on the target server:
netsh advfirewall firewall set rule group=\"@FirewallAPI.dll,-29502\" new enable=yes
netsh advfirewall firewall set rule group=\"@FirewallAPI.dll,-34251\" new enable=yes
netsh advfirewall firewall add rule name=dpmra dir=in program=\"%PROGRAMFILES%\\Microsoft Data Protection Manager\\DPM\\bin\\DPMRA.exe\" profile=Any action=allow
netsh advfirewall firewall add rule name=DPMRA_DCOM_135 dir=in action=allow protocol=TCP localport=135 profile=Any
The issue still persists.
The MSDPMAgentinstall log file says the following at the end:
Property©: Date = 1/7/2015
Property©: MsiNetAssemblySupport = 4.0.30319.18408
Property©: MsiWin32AssemblySupport = 6.1.7601.17514
Property©: MsiRunningElevated = 1
Property©: Privileged = 1
Property©: USERNAME = Windows User
Property©: DATABASE = c:\b1e38ee30069ed00e510\DPMRA.msi
Property©: OriginalDatabase = c:\b1e38ee30069ed00e510\DPMRA.msi
Property©: SOURCEDIR = c:\b1e38ee30069ed00e510\
Property©: VersionHandler = 5.00
Property©: ROOTDRIVE = c:\
Property©: EXECUTEACTION = INSTALL
Property©: ACTION = INSTALL
Property©: UILevel = 5
Property©: CostingComplete = 0
Property©: OutOfDiskSpace = 0
Property©: OutOfNoRbDiskSpace = 0
Property©: PrimaryVolumeSpaceAvailable = 0
Property©: PrimaryVolumeSpaceRequired = 0
Property©: PrimaryVolumeSpaceRemaining = 0
MSI © (68:E8) [09:38:14:119]: Note: 1: 1708
MSI © (68:E8) [09:38:14:119]: Note: 1: 2205 2: 3: Error
MSI © (68:E8) [09:38:14:119]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708
MSI © (68:E8) [09:38:14:119]: Note: 1: 2205 2: 3: Error
MSI © (68:E8) [09:38:14:119]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI © (68:E8) [09:38:14:119]: 吰瞒
MSI © (68:E8) [09:38:14:119]: 吰瞒
MSI © (68:E8) [09:38:14:119]: Grabbed execution mutex.
MSI © (68:E8) [09:38:14:119]: Cleaning up uninstalled install packages, if any exist
MSI © (68:E8) [09:38:14:119]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/7/2015 9:38:14 ===
Any ideas where to turn next?

I do not have a Program Files\Microsoft System Center 2012\DPM\DPM\ProductionAgents\RA\4.1.3313.0\amd64
file path on the DPm system.
Rather Program Files\Microsoft System Center 2012\DPM\DPM\ProtectionAgents\RA\4.1.3313.0\amd64
Still, I ran the DPMAgentInstaller_x64.exe
from that file path and the agent did not install.
Also, on the DPM server I have added the target machine name to the DPMRADmTrustedMachines
group. I also made sure that the domain service account is in the same group. Still no luck.

SCOM 2012 SP1 Agent install issue

Dear all,
Wheni try to push SCOM client , getting below error. Any idea what would be issue ?
The Operations Manager Server could not execute WMI Query "Select * from Win32_OperatingSystem" on computer XXX.XXX.XXX
Operation: Agent Install
Install account: XXXXXX
Error Code: 800706BA
Error Description: The RPC server is unavailable.

Looks Firewall issue only , i have opened below ports , is there any mandatory ports required for SCOM agent installation ?
443
TCP
445
TCP
135
TCP

Can you specify the port for default services when installing OEG?

Hi everyone,
The default installation of OEG 11g uses 8090 port for management services, and 8080 for the virtualized services that you register in the gateway. After installation, you can change the ports by editing gateway's Profile Repository in Policy Studio. But is there a way to specify the port number before/during the installation?
Thanks,
Iris

Hi -
here are the steps to change the listening port (in 11.1.1.6)
- Connect to OEG using Policy Studio
- Click on "Edit Active Configuration"
- Under "Services", find the default services, and you'll see a listener for port 8080 there. Right-click to edit this.
- Change the port from 8080 to your desired port. Note that if you've installed the software and running it as a non-root user on Linux, then it will not have permission to bind to a low-number port (like port 80 for instance)
- Now deploy your change (for 11.1.1.6 hit F6 or click on the "deploy" button which is towards the right of the toolbar in Policy Studio).
- You may also choose to version your configuration at this point (click on "version" which is beside the "deploy" button and enter a comment about your version).
Now verify that OEG is listening on your new port. You can see it bind to the new port by looking at the trace [Connect a browser to port 8090 on OEG, login as admin or another user who has rights to view the trace, then click on "Trace"].
It's a usual practice to configure a new listener on SSL (e.g. on port 443) then to delete that pre-configured port 8080 listener, if you want to only receive traffic over SSL.

SCOM 2012 R2 Agent Deployment - Uninstall Old and Install New

By chance anyone come up with a scripted method for removing an existing SCOM 2012 SP1 agent and installing a new 2012 R2 agent? While I've come across a few scripts I'm trying to kill a few birds with one stone. This is a cross-domain attempt where the
SCOM servers sit in one domain and the member servers are scattered across multiple domains. Member servers range from Windows Server 2003, 2008, and 2012. In most cases the servers have the 2012 SP1 agent installed and in some cases there are multiple management
groups from previous SCOM standups. In addition there's a separate DEV SCOM 2012 R2 environment to manage DEV/QA servers. Active Directory Integration is configured and I have the necessary security groups created. There is a group policy created which is
filtered to just that security group. So the plan is to simply drop the servers into the correct group and have the agent installed via group policy start up script. ADI should have DEV servers appear in DEV SCOM and PROD in PROD SCOM.
Although there are ways to facilitate agent deployment via the console I need to perform a staged migration against a ton of server so as to not impact the existing production environment. So I'd rather do this remotely to pre-selected servers. This process
should involve removing the existing agent, installing the new one, and if possible removing any existing management groups. So far I've come up with the following:
Uninstall SCOM Agent:
%WinDir%\System32\msiexec.exe /x <path>\MOMAgent.msi /qb
Install SCOM Agent:
msiexec.exe /i \\path\Directory\MOMAgent.msi /qn /l*v \logs\MOMAgent_install.log USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> MANAGEMENT_SERVER_DNS=<MSDNSName> ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER=<AccountUser> ACTIONSDOMAIN=<AccountDomain>
ACTIONSPASSWORD=<AccountPassword>
Remove Management Group via Script
http://gallery.technet.microsoft.com/Remove-a-Management-group-336c849a/view/Discussions#content
I'm guessing this wheel has already been invented or maybe there's a better way. So I'm open to ideas or suggestions.
Any responses appreciated.

Wow! 4 days and no responses, not good Microsoft SCOM Community. So here's a status on this issue.
As stated I have Active Directory Integration configured which means:
I see the OperationsManager container in AD: dev_scom
I see the HealthService SCP and separate OU's for each of my management servers.
I have an ADI security group containing my management servers and scom action account.
I have an Agent security group which will contain servers the scom agent will be deployed via group policy.
I also have an AD LDAP query set to target the SCOM agent group.
(&(objectCategory=group)(name=DSCOM_ADI))
I finally get the script to install via the following steps:
Reference:
http://technet.microsoft.com/en-us/library/cc754995.aspx
http://technet.microsoft.com/en-us/library/cc770556.aspx
http://blog.coretech.dk/msk/install-a-scom-2012-agent-silent/
1. Launch Notepad ++ and enter the following:
msiexec /i
\\server.yourdomain.com\opsmgragent\%Processor_Architecture%\MOMAgent.msi USE_SETTINGS_FROM_AD=1 MANAGEMENT_GROUP=DEV_SCOM MANAGEMENT_SERVER_DNS=YourSCOMsrvr1.yourdomain.com ACTIONS_USE_COMPUTER_ACCOUNT=0 USE_MANUALLY_SPECIFIED_SETTINGS=0 ACTIONSUSER=svc_dscom
ACTIONSDOMAIN=yourdomain ACTIONSPASSWORD=YourPassword! AcceptEndUserLicenseAgreement=1 /qn /l*v c:\scom2012r2mmainstall.log
2. Save the script to a name of your choice. For me it's installdopsmgragent.cmd. Watch the extensions as you may end up saving it as installdopsmgragent.cmd.txt.
Note: Make note of this steps in the reference articles listed above:
"In the Add a Script dialog box, do the following:
In the Script Name box, type the path to the script, or click Browse to search for the script file in the Netlogon shared folder on the domain controller."
It's been a while since having to use a startup script so it took me a minute to figure this out. "getting too old 'fer this..."
3. Copy the script to the Netlogon folder which is located in the following directory on my Windows 2012 server: E:\SYSVOL\sysvol\yourdomain.com\scripts
4. Launch the group policy management console, create a new policy, edit it, and navigate to the following location:
Computer Configuration > Policies > Windows Settings > Scripts (Startup/Shutdown)
5. Double-click Startup to open the Startup Properties window.
6. Click Add and browse to the location of the script which you copied to the Netlogon share.
7. Click OK to close the Startup Properties window.
8. Close the Group Policy Management Editor.
9. Link the policy to an OU containing the servers.
10. Add the SCOM Agent group to the Security Filtering area of the group policy. I also remove Authenticated Users.
Note: make sure you have a few test servers in your Agent security group.
11. Drop to a command line and run gpupdate /force. You can also use gpupdate /force /sync but you will have to reboot the box you're running this from.
12. Log into one of the servers you have slated to deploy the agent to, drop to a command line, and run the same gpupdate command.
13. Follow this with a gpresult /r command to ensure that you see the policy applied in the Computer Settings area.
14. Reboot the server and you should see the startup script run.
15. Log into the server and launch the Control Panel.
16. If all went well you'll see the "Microsoft Monitoring Agent" icon.
17. Launch Event Viewer, navigate to the Operations Manager events node located under Applications and Services Logs and validate the logs.
17. If all didn't go well check the error log located, for me, on the C:\scom2012r2mmainstall.log
My issue: I don't see the management info in the Agent properties.
I installed this last night and waited until the next day still no changes. Event logs show the following:
Event ID: 2011 The Health Service did not find any policy in Active Directory
Event ID: 2003 No management groups were started. This may either be because no management groups are currently configured or a configured management group failed to start. The Health Service will wait for policy from Active Directory configuring
a management group to run.
I see the HealthService is Running in Task Manager on this server and of course I don't see anything listed in the Management Groups registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\
I don't want to manually add the management group info. Checking as I may have missed something in one of the switches.
Any responses appreciated.

Unicode Kernel Diagnostics Agent install on non_unicode kernel System.

We have some ECC 6.0 ABAP systems that do not have a unicode kernel. The diagnostics agent setup guide for Netweaver 7.0 says you should have a unicode kernel DVD for the diagnostics agent install. I was hesitant about using a unicode kernel for the SMD agent and a non-unicode kernel on the ECC 6.0 instance. I tried installing the agent with the non-unicode kernel DVD and got an error that would not let me continue. Anybody have experience with this?

Carl,
David is Right, SMD is itself an SAP Instance(to be considered a seperate system-SAP Note:1365123) with its own exe. So it shouldn't be a problem.
Regards,
Jagan

How to install SCOM 2012 R2 agent on workgroup Linux machine.

Hello Experts,
Please help in installing SCOM 2012 R2 agent on WorkGroup Linux machine.
Please provide links for steps process so we can proceed easily for installation without much searching.
Thanks
Richa KM

Hi
The beauty deploying SCOM agents to Linux Systems is that it does not depend on Kerberos. If the Linux Systems is Domain joined or not does not matter. In both cases the authentication occurs using certificates which are signed by the SCOM Servers. You Need
just to make sure that:
Port 22 (SSH) and 1270 (WS-Man) are open / reachable
DNS works both ways and pointers (reverse look up) is configured.
Make sure the Linux System Name is same as DNS if not check
http://stefanroth.net/2014/02/03/scom-linux-agent-deployment-signed-certificate-verification-operation-was-not-successful/
Make sure you Setup the RunAs account properly
http://stefanroth.net/2012/03/15/scom-2012-linux-monitoring-lab-part-1-setup-suse-11-1/
If you consider these points everything should work fine...
Cheers,
Stefan
Blog: http://blog.scomfaq.ch

SCOM 2012 R2 Agent Issue: Error 25211.Failed to install performance counters.. Error Code: -2147024809

Hi All,
I'm trying to deploy SCOM 2012 R2 agent onto a domain controller and I get the following error "Product: Microsoft Monitoring Agent -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.)."
I've installed the agent successfully onto 4 other domain controllers with out any issues.</p><p>The domain controllers are all VM's running on VMWare and are Windows Server 2012 R2.
I've rebuilt the Perfmon Counters based on this article: https://support.microsoft.com/en-us/kb/2554336?a=wsignin1.0
I've also enabled verbose logging on the msi installation:
InstallHSPerfCounters: Custom Action Data. C:\Program Files\Microsoft Monitoring Agent\Agent\
InstallHSPerfCounters: Installing agent perf counters.
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
Any help on this would be great.

Hi Stefan,
I've successfully installed the agent. The server needed a reboot after fixing the corrupt perfmon counters.
I know have a issue with the agent on the domain controller. It kkeeps on greying out and have used hslockdown to allow the local system access by using the following command.
HSLockdown.exe "ManagementGroupName" /A "NT AUTHORITY\Authenticated Users"
Further digging into the issue I see in the SCOM Management Server the following error "The entity servername is not heartbeating"
Written a SQL query to gather more information. SQL query I used is:
SELECT
ME.FullName,
HSO.StartDateTime AS OutageStartDateTime,
DATEDIFF (DD, hso.StartDateTime, GETDATE()) AS OutageDays,
HSO.ReasonCode,
DS.Name AS ReasonString
FROM vManagedEntity AS ME
INNER JOIN vHealthServiceOutage AS HSO ON HSO.ManagedEntityRowId = ME.ManagedEntityRowId
INNER JOIN vStringResource AS SR ON HSO.ReasonCode =
REPLACE(LEFT(SR.StringResourceSystemName, LEN(SR.StringResourceSystemName)
– CHARINDEX(‘.’, REVERSE(SR.StringResourceSystemName))), ‘System.Availability.StateData.Reasons.’, ”)
INNER JOIN vDisplayString AS DS ON DS.ElementGuid = SR.StringResourceGuid
WHERE (SR.StringResourceSystemName LIKE ‘System.Availability.StateData.Reasons.[0-9]%’)
AND DS.LanguageCode = ‘ENU’
AND ME.FullName like ‘%SERVER NAME%’ –Change name here or leave %% for ALL SERVERS
ORDER BY OutageStartDateTime
This gives me the following reason behind the failure : "The heartbeat from System Center Management Service is missing."
Have I missed anything? The agent is running fine, however SCOM is reporting that the heartbeat is missing.
Any help on this would be great.

Error 25211. Failed to install performance counters while trying to remove a 2012 SP1 agent from system.

I have a system that has the "Repair and Uninstall" options grayed out from the Management Server (2012 SP-1) and if I go to the system itself, I have tried repairing the Agent Installation (Does not work successfully) and I now am trying to "uninstall"
the agent from the system.   I keep getting about 1/2 way through the uninstall and an error opens that "Cannot install performance counters".    The system is Windows 2003 Standard Edition SP2.   The system also
has a SCOM 2007 directory locally that cannot be deleted because a log file is in use. There are no other agents locally on the system through "Add / Remove Programs" within Control Panel.
A little history.
We have two Environments (2012 R2 and the other 2012-SP1). Some system were "Dual-Homed".   This one was not. I am trying to uninstall the SP-1 agent so we can move it to the R2 environment. It previously had MOM
2005 agent tha was uninstalled and it appears to have had a 2007 agent installed at some point, but only the trace directory that I can find.
I have tried rebuild commands for performance counter and it appears to be functioning correctly.

Hi,
Can you see the agent under pending management? You may upgrade the agent through the console.
When you upgrade an agent, the Operations Manager installer service runs and is not removed until after the completion of the upgrade. If the agent upgrade fails, you might have to re-install the agent because the installer service was not properly removed.
If you attempt to upgrade the agent again and it fails, you should re-install the agent after you have completed upgrading all features of Operations Manager.
After rebuilding performance counter by following the link below, you may try to uninstall the agent and check the result:
http://support.microsoft.com/kb/300956/en-us
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

After change port for TCPIP PORT for default SQL Server instance (MSSQLSERVER), sql service and sql agent service did not started again

Hi
-when i install default instance MSSQLSERVER i added a domain account as a service account,
- when i change port for TCPIP PORT , and after sql service and sql agent service did not started again.
it thrown error
The SQL Server (MSSQLSERVER) service failed to start due to the following error:
The service did not start due to a logon failure.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
but when i add domain\sqservice account in administrators group these services started,
1) here why this change behavior happened
2i changed the port 1500
adil

HI
the sql instance service is running with domain/sqlservice account ,
- i stopped the sql service service
- when i start it not started again and i found below error message
Domain and account: MOJPORTAL\spsqlservice
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this.
If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed,
check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7041</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2015-04-24T17:12:58.326973300Z" />
<EventRecordID>2177</EventRecordID>
<Correlation />
<Execution ProcessID="520" ThreadID="4044" />
<Channel>System</Channel>
<Computer>PORTALSQL1.mojportal.com</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">MSSQL$xSQL</Data>
<Data Name="param2">xxxL\spsqlservice</Data>
</EventData>
</Event>
adil

VMM Agent install fails on Windows Server 2012 R2 Hyper-V

Hi,
We are unable to install VMM 2012 R2 agent on Windows Server 2012 R2 server either from VMM console or manually on the hyper-v server.
Error on VMM Console:
Error (410)
Agent installation failed on chsicoecdh03.casper.com.
Fatal error during installation (0x80070643)
Recommended Action
Try the operation again. If the problem persists, install the agent locally and then add the managed computer.
==================================================================
Error on Hyper-v server:
MSI (c) (E8:D0) [16:53:24:726]: Windows Installer installed the product. Product Name: Microsoft System Center Virtual Machine Manager Agent (x64). Product Version: 3.2.7510.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success
or error status: 1603.
Also, I suspect may be issue with WMI then checked WMI repository and it is in consistent state. winmgmt /verifyrepository.
Please help on this issue.
Any help would be appreciated.
Thanks
Kumaresan Lakshmanan

So, I've managed to research this some more since Thursday and I've come to the conclusion that Hyper-V does a horrible job of supporting Qualcomm NIC cards. That's the only thing I can conclude as far as where the issue is originating. I've read many
post and walkthroughs but nothing that has helped. The issue wasn't with any settings in the domain controller. The issue was that there really is a slow connection originating at the domain controller that is a VM and has network connectivity through the
virtual switch from Hyper-V. So, next question is, how do I get the DC to have better connectivity through the NIC that Hyper-V won't give it? If hyper-v would allow passthrough, this would be so much simpler. VM-ware is looking really good at this point.
Im disappointed in MS right now.

How to install sp2 for sql server 2012 , where sql server 2012 instnce is installed in cluster mode

Hi Everyone,
I want to install sp2 for sql server 2012, My sql server 2012 instance is installed in cluster mode.
Please suggest the best practice to install sp2 , what are prerequisite and recommendation.
Please share installation guide for sp2 in cluster instance, if any one have.
Thanks All
Aditya

Did you searched a bit before posting question.
Please read
https://support.microsoft.com/kb/958734?wa=wsignin1.0
http://blogs.msdn.com/b/john_daskalakis/archive/2014/09/05/how-to-install-a-service-pack-at-a-sql-server-2012-failover-instance-best-practices.aspx
http://blogs.msdn.com/b/jason_howell/archive/2012/08/28/how-to-patch-sql-server-2012-setup-with-an-updated-setup-package-using-updatesource-to-get-a-smart-setup.aspx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

HT3625 I have a 2012 macBook Pro 13" and the option "Use audio port for" does not appear at all in the sound menu. why is this? im running mountain Lion 10.8.2

I have a 2012 macBook Pro 13" and the option "Use audio port for" does not appear at all in the sound menu. why is this? im running mountain Lion 10.8.2

Because line-in has been removed.
It does allow for an Apple headset with mic., but I don't know if it would work with third-party ones.
You'll need to use a Griffin iMic or similar to use line-in via a USB port.
The same goes for the 15" retina, the newest MBA and the new iMac (whenever it finally arrives).

Ports for 2012 R2 - Agent Install

Similar Messages

Maybe you are looking for