Home
%3CLINGO-SUB%20id%3D%22lingo-sub-587548%22%20slang%3D%22en-US%22%3EReleased%3A%20Exchange%20Server%202013%20Service%20Pack%201%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-587548%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CDIV%20class%3D%22resources%22%20style%3D%22width%3A150px%3B%22%3E%0A%3CUL%20style%3D%22list-style-type%3Anone%3Bfont-size%3A1.2em%3Blist-style-position%3Aoutside%3Bcolor%3A%233b79cc%3Bmargin-left%3A0.5em%3B%22%3E%0A%3CLI%3E%3CA%20title%3D%22Download%22%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fdetails.aspx%3Fid%3D41994%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EDownload%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20title%3D%22What's%20new%22%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fjj907309(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EWhat's%20new%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20title%3D%22Release%20notes%22%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fjj150489(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ERelease%20notes%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FDIV%3E%0A%3CP%3EExchange%20Server%202013%20Service%20Pack%201%20(SP1)%20is%20now%20available%20for%20download!%20Please%20make%20sure%20to%20read%20the%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fjj150489(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Erelease%20notes%3C%2FA%3Ebefore%20installing%20SP1.%20The%20final%20build%20number%20for%20Exchange%20Server%202013%20SP1%20is%2015.00.0847.032.%3C%2FP%3E%0A%3CP%3ESP1%20has%20already%20been%20deployed%20to%20thousands%20of%20production%20mailboxes%20in%20customer%20environments%20via%20the%20Exchange%20Server%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fb%2Fexchange%2Farchive%2F2014%2F02%2F19%2Fexchange-on-premises-tap-program-accepting-nominations.aspx%22%20target%3D%22_blank%22%3ETechnology%20Adoption%20Program%20(TAP)%3C%2FA%3E.%20In%20addition%20to%20including%20fixes%2C%20SP1%20provides%20enhancements%20to%20improve%20the%20Exchange%202013%20experience.%20These%20include%20enhancements%20in%20security%20and%20compliance%2C%20architecture%20and%20administration%2C%20and%20user%20experiences.%20These%20key%20enhancements%20are%20introduced%20below.%3C%2FP%3E%0A%3CP%20class%3D%22note%22%3ENote%3A%20Some%20of%20the%20documentation%20referenced%20may%20not%20be%20fully%20available%20at%20the%20time%20of%20publishing%20of%20this%20post.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1738070245%22%20id%3D%22toc-hId-1795175687%22%3ESecurity%20and%20Compliance%3C%2FH2%3E%0A%3CP%3ESP1%20provides%20enhancements%20improving%20security%20and%20compliance%20capabilities%20in%20Exchange%20Server%202013.%20This%20includes%20improvements%20in%20the%20Data%20Loss%20Prevention%20(DLP)%20feature%20and%20the%20return%20of%20S%2FMIME%20encryption%20for%20Outlook%20Web%20App%20users.%3C%2FP%3E%0A%3CUL%20class%3D%22arrowlist%22%3E%0A%3CLI%3EDLP%20Policy%20Tips%20in%20Outlook%20Web%20App%20%E2%80%93%20DLP%20Policy%20Tips%20are%20now%20enabled%20for%20Outlook%20Web%20App%20(OWA)%20and%20OWA%20for%20Devices.%20These%20are%20the%20same%20Policy%20Tips%20available%20in%20Outlook%202013.%20DLP%20Policy%20Tips%20appear%20when%20a%20user%20attempts%20to%20send%20a%20message%20containing%20sensitive%20data%20that%20matches%20a%20DLP%20policy.%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj150512(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ELearn%20more%20about%20DLP%20Policy%20Tips%3C%2FA%3E.%3C%2FLI%3E%0A%3CLI%3EDLP%20Document%20Fingerprinting%20%E2%80%93%20DLP%20policies%20already%20allow%20you%20to%20detect%20sensitive%20information%20such%20as%20financial%20or%20personal%20data.%20DLP%20Document%20Fingerprinting%20expands%20this%20capability%20to%20detect%20forms%20used%20in%20your%20organization.%20For%20example%2C%20you%20can%20create%20a%20document%20fingerprint%20based%20on%20your%20organization%E2%80%99s%20patent%20request%20form%20to%20identify%20when%20users%20are%20sending%20that%20form%2C%20and%20then%20use%20DLP%20actions%20to%20properly%20control%20dissemination%20of%20the%20content.%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FDocumentFingerprinting%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ELearn%20more%20about%20DLP%20Document%20Fingerprinting%3C%2FA%3E.%3C%2FLI%3E%0A%3CLI%3EDLP%20sensitive%20information%20types%20for%20new%20regions%20%E2%80%93%20SP1%20provides%20an%20expanded%20set%20of%20standard%20DLP%20sensitive%20information%20types%20covering%20an%20increased%20set%20of%20regions.%20SP1%20adds%20region%20support%20for%20Poland%2C%20Finland%20and%20Taiwan.%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fjj150541(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ELearn%20more%20about%20the%20DLP%20sensitive%20information%20types%20available%3C%2FA%3E.%3C%2FLI%3E%0A%3CLI%3ES%2FMIME%20support%20for%20OWA%20%E2%80%93%20SP1%20also%20reintroduces%20the%20S%2FMIME%20feature%20in%20OWA%2C%20enabling%20OWA%20users%20to%20send%20and%20receive%20signed%20and%20encrypted%20email.%20Signed%20messages%20allow%20the%20recipient%20to%20verify%20that%20the%20message%20came%20from%20the%20specified%20sender%20and%20contains%20the%20only%20the%20content%20from%20the%20sender.%20This%20capability%20is%20supported%20when%20using%20OWA%20with%20Internet%20Explorer%209%20or%20later.%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fdn626158(EXCHG.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ELearn%20more%20about%20S%2FMIME%20in%20Exchange%202013%3C%2FA%3E.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH2%20id%3D%22toc-hId--814086716%22%20id%3D%22toc-hId--756981274%22%3EArchitecture%20%26amp%3B%20Administration%3C%2FH2%3E%0A%3CP%3EThese%20improvements%20help%20Exchange%20meet%20our%20customer%20requirements%20and%20stay%20in%20step%20with%20the%20latest%20platforms.%3C%2FP%3E%0A%3CUL%20class%3D%22arrowlist%22%3E%0A%3CLI%3EWindows%20Server%202012%20R2%20support%20%E2%80%93%20Exchange%202013%20SP1%20adds%20Windows%20Server%202012%20R2%20as%20a%20supported%20operating%20system%20and%20Active%20Directory%20environment%20for%20both%20domain%20and%20forest%20functional%20levels.%20For%20the%20complete%20configuration%20support%20information%20refer%20to%20the%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fff728623(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EExchange%20Server%20Supportability%20Matrix%3C%2FA%3E.%20This%20matrix%20includes%20details%20regarding%20Windows%20Server%202012%20R2%20support%20information%20about%20earlier%20versions%20of%20Exchange.%3C%2FLI%3E%0A%3CLI%3EExchange%20Admin%20Center%20Cmdlet%20Logging%20%E2%80%93%20The%20Exchange%202010%20Management%20Console%20includes%20PowerShell%20cmdlet%20logging%20functionality.%20Listening%20to%20your%20feedback%2C%20we%E2%80%99re%20happy%20to%20announce%20that%20this%20functionality%20is%20now%20included%20in%20the%20Exchange%20Admin%20Center%20(EAC).%20The%20logging%20feature%20enables%20you%20to%20capture%20and%20review%20the%20recent%20(up%20to%20500)%20commands%20executed%20in%20the%20EAC%20user%20interface%20while%20the%20logging%20window%20is%20open.%20Logging%20is%20invoked%20from%20the%20EAC%20help%20menu%20and%20continues%20logging%20while%20the%20logging%20window%20remains%20open.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fmetablogapi%2Fimage_6884397B.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-metablogapi%2Fimage_5F00_6884397B.png%22%20target%3D%22_blank%22%3E%3CIMG%20width%3D%22624%22%20height%3D%22120%22%20title%3D%22image%22%20style%3D%22background-image%3Anone%3Bpadding-top%3A0px%3Bpadding-left%3A0px%3Bdisplay%3Ainline%3Bpadding-right%3A0px%3Bborder-width%3A0px%3B%22%20alt%3D%22image%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fmetablogapi%2Fimage_thumb_1C4C2FCD.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-metablogapi%2Fimage_5F00_thumb_5F00_1C4C2FCD.png%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fmetablogapi%2Fimage_058CE844.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-metablogapi%2Fimage_5F00_058CE844.png%22%20target%3D%22_blank%22%3E%3CIMG%20width%3D%22418%22%20height%3D%22441%22%20title%3D%22image%22%20style%3D%22background-image%3Anone%3Bpadding-top%3A0px%3Bpadding-left%3A0px%3Bdisplay%3Ainline%3Bpadding-right%3A0px%3Bborder-width%3A0px%3B%22%20alt%3D%22image%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fmetablogapi%2Fimage_thumb_27784AC8.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-metablogapi%2Fimage_5F00_thumb_5F00_27784AC8.png%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CUL%20class%3D%22arrowlist%22%3E%0A%3CLI%3EADFS%20for%20OWA%20%E2%80%93%20Also%20new%20for%20Outlook%20Web%20App%20in%20SP1%20is%20claims-based%20authentication%20for%20organizations%20using%20Active%20Directory%20Federation%20Services.%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fdn635116(EXCHG.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ELearn%20more%20about%20the%20scenario%3C%2FA%3E.%3C%2FLI%3E%0A%3CLI%3EEdge%20Transport%20server%20role%20%E2%80%93%20SP1%20also%20reintroduces%20the%20Edge%20Transport%20server%20role.%20If%20you%20have%20deployed%20Exchange%202013%20with%20a%20supported%20legacy%20Exchange%20Edge%20Transport%20role%2C%20you%20don%E2%80%99t%20need%20to%20upgrade.%20That%20configuration%20is%20still%20supported.%20But%20we%20do%20recommend%20that%20future%20deployments%20use%20the%20Exchange%202013%20Edge%20Transport%20role.%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fbb124701(EXCHG.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ELearn%20more%20about%20Edge%20Transport%20in%20Exchange%202013%3C%2FA%3E.%3C%2FLI%3E%0A%3CLI%3ENew%20communication%20method%20for%20Exchange%20and%20Outlook%20%E2%80%93%20SP1%20introduces%20a%20new%20communication%20method%20for%20Exchange%20Server%20and%20Microsoft%20Outlook%20called%20MAPI%20over%20HTTP(MAPI%2FHTTP).%20This%20communication%20method%20simplifies%20connectivity%20troubleshooting%20and%20improves%20the%20user%20connection%20experience%20with%20resuming%20from%20hibernate%20or%20switching%20networks.%20MAPI%2FHTTP%20is%20disabled%20by%20default%2C%20allowing%20you%20to%20decide%20when%20to%20enable%20it%20for%20your%20organization.%20MAPI%2FHTTP%20can%20be%20used%20in%20place%20of%20RPC%2FHTTP%20(Outlook%20Anywhere)%20for%20your%20Outlook%202013%20SP1%20clients%20while%20Outlook%202013%20RTM%20and%20older%20clients%20continue%20to%20use%20RPC%2FHTTP.%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fdn635177(EXCHG.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ELearn%20more%20about%20deploying%20MAPI%2FHTTP%3C%2FA%3E.%3CB%3E%3C%2FB%3E%3C%2FLI%3E%0A%3CLI%3EDAGs%20without%20Cluster%20Administrative%20Access%20Points%3CB%3E-%20%3C%2FB%3EWindows%20Server%202012%20R2%20introduces%20failover%20clusters%20that%20can%20operate%20without%20an%20administrative%20access%20point%3A%20no%20IP%20addresses%20or%20IP%20address%20resource%2C%20no%20network%20name%20resource%2C%20and%20no%20cluster%20name%20object.%20SP1%20enables%20you%20to%20create%20a%20DAG%20without%20an%20administrative%20access%20point%20on%20Windows%20Server%202012%20R2%20from%20EAC%20or%20PowerShell.%20This%20is%20an%20optional%20DAG%20configuration%20for%20SP1%20and%20requires%20Windows%20Server%202012%20R2.%20DAGs%20with%20administrative%20access%20points%20continue%20to%20be%20supported.%20Learn%20more%20about%20creating%20a%20DAG%20without%20an%20administrative%20access%20point%20%3CA%20title%3D%22Windows%20Server%202012%20R2%20and%20Database%20Availability%20Groups%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fb%2Fscottschnoll%2Farchive%2F2014%2F02%2F25%2Fdatabase-availability-groups-and-windows-server-2012-r2.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3Eand%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd638137(v%3Dexchg.150).aspx%23CT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FLI%3E%0A%3CLI%3ESSL%20offloading%20%E2%80%93%20SP1%20now%20supports%20SSL%20offloading%2C%20allowing%20you%20to%20terminate%20incoming%20SSL%20connections%20in%20front%20of%20your%20CAS%20servers%20and%20move%20the%20SSL%20workload%20(encryption%20%26amp%3B%20decryption%20tasks)%20to%20a%20load%20balancer%20device.%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Flibrary%2Fdn635115(EXCHG.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ELearn%20how%20to%20configure%20SSL%20offloading%20in%20Exchange%202013%3C%2FA%3E.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH2%20id%3D%22toc-hId-928723619%22%20id%3D%22toc-hId-985829061%22%3EUser%20Experience%3C%2FH2%3E%0A%3CP%3EWe%20know%20the%20user%20experience%20is%20crucial%20to%20running%20a%20great%20messaging%20platform.%20SP1%20provides%20continued%20enhancements%20to%20help%20your%20users%20work%20smarter.%3C%2FP%3E%0A%3CUL%20class%3D%22arrowlist%22%3E%0A%3CLI%3EEnhanced%20text%20editor%20for%20OWA%20-%20OWA%20now%20uses%20the%20same%20rich%20text%20editor%20as%20SharePoint%2C%20thereby%20improving%20the%20user%20experience%2C%20and%20enabling%20several%20new%20formatting%20and%20composition%20capabilities%20that%20you%20expect%20from%20modern%20Web%20application%20-%20more%20pasting%20options%2C%20rich%20previews%20to%20linked%20content%2C%20and%20the%20ability%20to%20create%20and%20modify%20tables.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fmetablogapi%2Fimage_1B765A94.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-metablogapi%2Fimage_5F00_1B765A94.png%22%20target%3D%22_blank%22%3E%3CIMG%20width%3D%22554%22%20height%3D%22382%22%20title%3D%22image%22%20style%3D%22background-image%3Anone%3Bpadding-top%3A0px%3Bpadding-left%3A0px%3Bdisplay%3Ainline%3Bpadding-right%3A0px%3Bborder-width%3A0px%3B%22%20alt%3D%22image%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fmetablogapi%2Fimage_thumb_193C6289.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-metablogapi%2Fimage_5F00_thumb_5F00_193C6289.png%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CUL%20class%3D%22arrowlist%22%3E%0A%3CLI%3EApps%20for%20Office%20in%20Compose%20%E2%80%93%20Mail%20apps%20are%20now%20available%20for%20use%20during%20the%20creation%20of%20new%20mail%20messages.%20This%20allows%20developers%20to%20build%20and%20users%20to%20leverage%20apps%20that%20can%20help%20them%20while%20they%20are%20composing%20mails.%20The%20compose%20apps%20leverage%20the%20Apps%20for%20Office%20platform%20and%20can%20be%20added%20via%20the%20existing%20Office%20store%20or%20corporate%20catalogs.%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fmailapps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ELearn%20more%20about%20Apps%20for%20Office%3C%2FA%3E.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fmetablogapi%2Fimage_06C6D01B.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-metablogapi%2Fimage_5F00_06C6D01B.png%22%20target%3D%22_blank%22%3E%3CIMG%20width%3D%22459%22%20height%3D%22222%22%20title%3D%22image%22%20style%3D%22background-image%3Anone%3Bpadding-top%3A0px%3Bpadding-left%3A0px%3Bdisplay%3Ainline%3Bpadding-right%3A0px%3Bborder-width%3A0px%3B%22%20alt%3D%22image%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2FTNBlogsFS%2Fprod.evol.blogs.technet.com%2FCommunityServer.Blogs.Components.WeblogFiles%2F00%2F00%2F00%2F31%2F06%2Fmetablogapi%2Fimage_thumb_6471CB52.png%22%20original-url%3D%22http%3A%2F%2Fblogs.technet.com%2Fcfs-file.ashx%2F__key%2Fcommunityserver-blogs-components-weblogfiles%2F00-00-00-31-06-metablogapi%2Fimage_5F00_thumb_5F00_6471CB52.png%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CH2%20id%3D%22toc-hId--1623433342%22%20id%3D%22toc-hId--1566327900%22%3EUpgrading%20to%20SP1%2FDeploying%20SP1%3C%2FH2%3E%0A%3CP%3EAs%20with%20all%20cumulative%20updates%20(CUs)%2C%20SP1%20is%20a%20full%20build%20of%20Exchange%2C%20and%20the%20deployment%20of%20SP1%20is%20just%20like%20the%20deployment%20of%20a%20cumulative%20update.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--77136512%22%20id%3D%22toc-hId--20031070%22%3EActive%20Directory%20Preparation%3C%2FH3%3E%0A%3CP%3EPrior%20to%20or%20concurrent%20with%20upgrading%20or%20deploying%20SP1%20onto%20a%20server%2C%20you%20must%20update%20Active%20Directory.%20These%20are%20the%20required%20actions%20to%20perform%20prior%20to%20installing%20SP1%20on%20a%20server.%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E1.%20Exchange%202013%20SP1%20includes%20schema%20changes.%20Therefore%2C%20you%20will%20need%20to%20execute%20the%20following%20command%20to%20apply%20the%20schema%20changes.%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3Esetup.exe%20%2FPrepareSchema%20%2FIAcceptExchangeServerLicenseTerms%3C%2FP%3E%0A%3CP%3E2.%20Exchange%202013%20SP1%20includes%20enterprise%20Active%20Directory%20changes%20(e.g.%2C%20RBAC%20roles%20have%20been%20updated%20to%20support%20new%20cmdlets%20and%2For%20properties).%20Therefore%2C%20you%20will%20need%20to%20execute%20the%20following%20command.%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3Esetup.exe%20%2FPrepareAD%20%2FIAcceptExchangeServerLicenseTerms%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CH3%20id%3D%22toc-hId-1665673823%22%20id%3D%22toc-hId-1722779265%22%3EServer%20Deployment%3C%2FH3%3E%0A%3CP%3EOnce%20the%20above%20preparatory%20steps%20are%20completed%2C%20you%20can%20install%20SP1%20on%20your%20servers.%20Of%20course%2C%20as%20always%2C%20if%20you%20don%E2%80%99t%20separately%20perform%20the%20above%20steps%2C%20they%20will%20be%20performed%20by%20Setup%20when%20you%20install%20your%20first%20Exchange%202013%20SP1%20server.%20If%20this%20is%20your%20first%20Exchange%202013%20server%20deployment%2C%20you%20will%20need%20to%20deploy%20both%20Client%20Access%20Server%20and%20Mailbox%20Server%20roles%20in%20your%20organization.%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3EIf%20you%20already%20deployed%20Exchange%202013%20RTM%20code%20and%20want%20to%20upgrade%20to%20SP1%2C%20you%20will%20run%20the%20following%20command%20from%20a%20command%20line.%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3Esetup.exe%20%2Fm%3Aupgrade%20%2FIAcceptExchangeServerLicenseTerms%3C%2FP%3E%0A%3CP%3EAlternatively%20you%20can%20start%20the%20installation%20through%20the%20GUI%20installer.%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CH3%20id%3D%22toc-hId--886483138%22%20id%3D%22toc-hId--829377696%22%3EHybrid%20deployments%20and%20EOA%3C%2FH3%3E%0A%3CP%3ECustomers%20in%20hybrid%20deployments%20where%20Exchange%20is%20deployed%20on-premises%20and%20in%20the%20cloud%2C%20or%20who%20are%20using%20Exchange%20Online%20Archiving%20(EOA)%20with%20their%20on-premises%20Exchange%20deployment%20are%20required%20to%26nbsp%3Bdeploy%20the%20most%20current%20(e.g.%2C%20SP1)%20or%20the%20prior%20(e.g.%2C%20CU3)%20Cumulative%20Update%20release.%3C%2FP%3E%0A%3CP%20class%3D%22alert%22%3ENote%3A%20We%20have%20learned%20some%20customers%20using%203rd%20party%20or%20custom%20transport%20agents%20may%20experience%20issues%20after%20installation%20of%20SP1.%26nbsp%3B%20If%20you%20experience%20installation%20issues%20consult%20%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2Fkb%2F2938053%2Fen-us%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKB%202938053%3C%2FA%3Eto%20resolve%20this%20issue%20with%20transport%20agents.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1052840702%22%20id%3D%22toc-hId-1109946144%22%3ELooking%20Ahead%3C%2FH2%3E%0A%3CP%3EOur%20next%20update%20for%20Exchange%202013%20will%20be%20released%20as%20Exchange%202013%20Cumulative%20Update%205.%20This%20CU%20release%20will%20continue%20the%20Exchange%20Server%202013%20release%20process.%3C%2FP%3E%0A%3CP%3EIf%20you%20want%20to%20learn%20more%20about%20Exchange%20Server%202013%20SP1%20and%20have%20the%20opportunity%20to%20ask%20questions%20to%20the%20Exchange%20team%20in%20person%2C%20come%20join%20us%20at%20the%20%3CA%20href%3D%22http%3A%2F%2Fiammec.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20Exchange%20Conference%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3EBrian%20Shiers%3C%2FSPAN%3E%3CBR%20%2F%3ETechnical%20Product%20Manager%2C%20Exchange%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-587548%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20Premises%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esetup%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

Exchange Server 2013 Service Pack 1 (SP1) is now available for download! Please make sure to read the release notesbefore installing SP1. The final build number for Exchange Server 2013 SP1 is 15.00.0847.032.

SP1 has already been deployed to thousands of production mailboxes in customer environments via the Exchange Server Technology Adoption Program (TAP). In addition to including fixes, SP1 provides enhancements to improve the Exchange 2013 experience. These include enhancements in security and compliance, architecture and administration, and user experiences. These key enhancements are introduced below.

Note: Some of the documentation referenced may not be fully available at the time of publishing of this post.

Security and Compliance

SP1 provides enhancements improving security and compliance capabilities in Exchange Server 2013. This includes improvements in the Data Loss Prevention (DLP) feature and the return of S/MIME encryption for Outlook Web App users.

  • DLP Policy Tips in Outlook Web App – DLP Policy Tips are now enabled for Outlook Web App (OWA) and OWA for Devices. These are the same Policy Tips available in Outlook 2013. DLP Policy Tips appear when a user attempts to send a message containing sensitive data that matches a DLP policy. Learn more about DLP Policy Tips.
  • DLP Document Fingerprinting – DLP policies already allow you to detect sensitive information such as financial or personal data. DLP Document Fingerprinting expands this capability to detect forms used in your organization. For example, you can create a document fingerprint based on your organization’s patent request form to identify when users are sending that form, and then use DLP actions to properly control dissemination of the content. Learn more about DLP Document Fingerprinting.
  • DLP sensitive information types for new regions – SP1 provides an expanded set of standard DLP sensitive information types covering an increased set of regions. SP1 adds region support for Poland, Finland and Taiwan. Learn more about the DLP sensitive information types available.
  • S/MIME support for OWA – SP1 also reintroduces the S/MIME feature in OWA, enabling OWA users to send and receive signed and encrypted email. Signed messages allow the recipient to verify that the message came from the specified sender and contains the only the content from the sender. This capability is supported when using OWA with Internet Explorer 9 or later. Learn more about S/MIME in Exchange 2013.

Architecture & Administration

These improvements help Exchange meet our customer requirements and stay in step with the latest platforms.

  • Windows Server 2012 R2 support – Exchange 2013 SP1 adds Windows Server 2012 R2 as a supported operating system and Active Directory environment for both domain and forest functional levels. For the complete configuration support information refer to the Exchange Server Supportability Matrix. This matrix includes details regarding Windows Server 2012 R2 support information about earlier versions of Exchange.
  • Exchange Admin Center Cmdlet Logging – The Exchange 2010 Management Console includes PowerShell cmdlet logging functionality. Listening to your feedback, we’re happy to announce that this functionality is now included in the Exchange Admin Center (EAC). The logging feature enables you to capture and review the recent (up to 500) commands executed in the EAC user interface while the logging window is open. Logging is invoked from the EAC help menu and continues logging while the logging window remains open.

image

image

  • ADFS for OWA – Also new for Outlook Web App in SP1 is claims-based authentication for organizations using Active Directory Federation Services. Learn more about the scenario.
  • Edge Transport server role – SP1 also reintroduces the Edge Transport server role. If you have deployed Exchange 2013 with a supported legacy Exchange Edge Transport role, you don’t need to upgrade. That configuration is still supported. But we do recommend that future deployments use the Exchange 2013 Edge Transport role. Learn more about Edge Transport in Exchange 2013.
  • New communication method for Exchange and Outlook – SP1 introduces a new communication method for Exchange Server and Microsoft Outlook called MAPI over HTTP(MAPI/HTTP). This communication method simplifies connectivity troubleshooting and improves the user connection experience with resuming from hibernate or switching networks. MAPI/HTTP is disabled by default, allowing you to decide when to enable it for your organization. MAPI/HTTP can be used in place of RPC/HTTP (Outlook Anywhere) for your Outlook 2013 SP1 clients while Outlook 2013 RTM and older clients continue to use RPC/HTTP. Learn more about deploying MAPI/HTTP.
  • DAGs without Cluster Administrative Access Points - Windows Server 2012 R2 introduces failover clusters that can operate without an administrative access point: no IP addresses or IP address resource, no network name resource, and no cluster name object. SP1 enables you to create a DAG without an administrative access point on Windows Server 2012 R2 from EAC or PowerShell. This is an optional DAG configuration for SP1 and requires Windows Server 2012 R2. DAGs with administrative access points continue to be supported. Learn more about creating a DAG without an administrative access point here and here.
  • SSL offloading – SP1 now supports SSL offloading, allowing you to terminate incoming SSL connections in front of your CAS servers and move the SSL workload (encryption & decryption tasks) to a load balancer device. Learn how to configure SSL offloading in Exchange 2013.

User Experience

We know the user experience is crucial to running a great messaging platform. SP1 provides continued enhancements to help your users work smarter.

  • Enhanced text editor for OWA - OWA now uses the same rich text editor as SharePoint, thereby improving the user experience, and enabling several new formatting and composition capabilities that you expect from modern Web application - more pasting options, rich previews to linked content, and the ability to create and modify tables.

image

  • Apps for Office in Compose – Mail apps are now available for use during the creation of new mail messages. This allows developers to build and users to leverage apps that can help them while they are composing mails. The compose apps leverage the Apps for Office platform and can be added via the existing Office store or corporate catalogs. Learn more about Apps for Office.

image

Upgrading to SP1/Deploying SP1

As with all cumulative updates (CUs), SP1 is a full build of Exchange, and the deployment of SP1 is just like the deployment of a cumulative update.

Active Directory Preparation

Prior to or concurrent with upgrading or deploying SP1 onto a server, you must update Active Directory. These are the required actions to perform prior to installing SP1 on a server.

1. Exchange 2013 SP1 includes schema changes. Therefore, you will need to execute the following command to apply the schema changes.

setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

2. Exchange 2013 SP1 includes enterprise Active Directory changes (e.g., RBAC roles have been updated to support new cmdlets and/or properties). Therefore, you will need to execute the following command.

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Server Deployment

Once the above preparatory steps are completed, you can install SP1 on your servers. Of course, as always, if you don’t separately perform the above steps, they will be performed by Setup when you install your first Exchange 2013 SP1 server. If this is your first Exchange 2013 server deployment, you will need to deploy both Client Access Server and Mailbox Server roles in your organization.

If you already deployed Exchange 2013 RTM code and want to upgrade to SP1, you will run the following command from a command line.

setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms

Alternatively you can start the installation through the GUI installer.

Hybrid deployments and EOA

Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the most current (e.g., SP1) or the prior (e.g., CU3) Cumulative Update release.

Note: We have learned some customers using 3rd party or custom transport agents may experience issues after installation of SP1.  If you experience installation issues consult KB 2938053 to resolve this issue with transport agents.

Looking Ahead

Our next update for Exchange 2013 will be released as Exchange 2013 Cumulative Update 5. This CU release will continue the Exchange Server 2013 release process.

If you want to learn more about Exchange Server 2013 SP1 and have the opportunity to ask questions to the Exchange team in person, come join us at the Microsoft Exchange Conference.

Brian Shiers
Technical Product Manager, Exchange

214 Comments
Not applicable
@Brent Alinger [MSFT] - Please provide a link to the guidance that you mentioned in the below response. Cheers

@ABDL - Regarding OWA Apps on 2012 R2, yes there is a change in behavior in Windows 2012 R2 which requires a Web.Config change for many OWA Apps. We are working on a KB article for this issue and will have this guidance posted within the next week. Unfortunately the article was not ready for publishing prior to the launch of SP1. It is never our preference to force customer changes to Web.Config and we are working with the Windows team to make this seamless for those who want to deploy Windows Server 2012 R2.
Not applicable
@Brent Alinger [MSFT]: Great, thanks for the update!
Not applicable
Nevermind, figured it out. The upgrade broke the SMTP tie-in for Symantec Mail Security. Exchange Transport would start and then stop immediately on the 2013 mailbox server. Uninstalling Symantec Mail Security fixed it, so it probably just needs to be re-installed.
Not applicable
Hello Exchange Team.

When can we expect to see the Exchange 2013 SP1 help file available for download?
Not applicable
After upgrading to SP1 does not start the transport service. The logs error
Microsoft Exchange could not start transport agents. "C: Program Files (x86) EAExchDomainKeys EAExchDomainKeys2007.dll" because of an error "type not found."
After disabling the agent transport service start successfully.
Not applicable
Plenty of my customers at http://emailmigrations.com have been waiting for Exchange 2013 SP1 before starting their email migration project. Good news it has arrived, and I am looking forward to testing, and then deploying it.
Not applicable
internal Managed Availability Mails are still being copied to configured Journal Mailbox - will this ever be changed ?
Not applicable
Do we have any hope to get these Public Folder limitations on the level which they should be in year 2014? Or are we all forced to keep Exchange 2010 still in organization?

http://technet.microsoft.com/en-us/library/dn594582%28v=exchg.150%29.aspx

10000 folders in PF store, is not an enterprise limit :(


Neither I have not seen fixed for cross forest migration and Public Folders. Any plans on that?

Not applicable
Not applicable
We have been on SP1 for about a week and a half. The system seems very stable and responsive. Previously we had an issue with RPC crashing and SP1 seems to make that much better. We do have one issue with SP1 and that had to do with Caching plain text emails. We have setup the systems to pull full items now as a work around. We have a ticket open and MS was able to reproduce the issue yesterday. Hopefully they will find the issue and can resolve.
Not applicable
Regarding broken Transport Agent issues, I can confirm the CFG files in the GAC are all broken. The first line in each file contains multiple hyphens (-------) which makes the entire XML invalid. Removing the first line, or fixing it by removing the multiple hyphens and making the line end with --> fixes the problem.
Since our agent was compiled with reference to Exchange 2013 RTM public DLLs, the following files should be edited:
"C:WindowsMicrosoft.NETassemblyGAC_MSILpolicy.15.0.Microsoft.Exchange.Data.Commonv4.0_15.0.847.30__31bf3856ad364e35Microsoft.Exchange.Data.Common.VersionPolicy15.0.cfg"
"C:WindowsMicrosoft.NETassemblyGAC_MSILpolicy.15.0.Microsoft.Exchange.Data.Transportv4.0_15.0.847.30__31bf3856ad364e35Microsoft.Exchange.Data.Transport.VersionPolicy15.0.cfg"
Microsoft, please note: those are not the only broken files - all other files in the same hierarchy are broken as well (C:WindowsMicrosoft.NETassemblyGAC_MSILpolicy.*.Microsoft.Exchange.Data.***.cfg).
I hope the above information will assist in releasing a quickfix ASAP.
Not applicable
@Brent Alinger [MSFT]: Thank you. If the issue gets confirmed, can you please also confirm that removing the broken XML comment line is a proper workaround? We did comprehensive testing with the policy modified this way and tests were positive -- it's just we don't know if the comment is of any importance and removing it will break the next Exchange update or something.
Not applicable
Upgrade servers from CU3 to SP1 broke all sounds in OWA.
Files with sound present in correct folders (owa/prem/15.0.847.32/resources/sounds/calendar_notify.mp3 for example), but IIS don't get it to client:
GET /owa/prem/15.0.847.32/resources/sounds/calendar_notify.mp3?UA=0 HTTP/1.1
Response HTTP/1.1 400 Bad Request
Not applicable
when will I be able to download Exchange Server 2013 with SP1 from Volume Licencing Centre so I can install it on Windows Server 2012 R2?

thanks
Not applicable
THANK YOU!!!!

Although, I'm still going to wait a few weeks to hear back from other people first, so please, please, please everyone post your production experiences here if you decide to deploy it.

If no issues and everything looks like it's clean, then I'll start updating everyone immediately. I feel like after waiting a year, we are hopefully looking at a good, stable update that clears up the previous CU issues. The last update where the config file was modified to timeout 480 times really caused some pain. Same with all the URL directory rebuilds due to IS going bonkers. Hopefully we won't see any more of that and we're back on track with a fantastic Exchange experience for both the end users and admins.

THANK YOU for releasing this update!
Not applicable
@Jetze Mellema: Sorry to hear that Connection filtering is still not supported. But I have already made some other agents in C# for Exchange and I think I am going to make one which check against a block list and then set the spam confidence level or a x-header if it is listed. Shouldn't be to much work with this ......
Not applicable
One concern in upgrading to SP1: Is it necessary to remove security update for CU3 (KB2880833) before upgrading to SP1? I recall that there were serious problems at CU1->CU2 upgrade with these security updates which eventually lead to failed upgrade.
Not applicable
Before going and start upgrading, it would be beneficial to stop just for a moment, and remember back to the year 2013, and all those not so successful update and rollback stories...
Not applicable
@AN, you may have run setup from PowerShell session which will call the existing setup file. Please run setup from a normal command line in the path you extracted the SP1 files instead and you should have better luck. :)
Not applicable
@ Chris & Jordan, the modern PF access issue from Windows XP clients is fixed in SP1

Please check KB http://support.microsoft.com/kb/2926248 for major issues that are fixed in SP1
Not applicable
@RossSmithIV - Thank you for your answer! Today we'll start upgrading CU3 servers to SP1.
Not applicable
Does it support Office 2010 on XP workstations?
Not applicable
When can we expect to see the Exchange 2013 SP1 help file available for download?
Not applicable
@Stig Vidar Hovland: Unfortunately not, the Connection Filtering Agent is still not supported on Exchange 2013 CAS. You could deploy an Exchange 2013 Edge Transport server with SP1 to perform this task.
Not applicable
@Tony, the Edge Transport role in 2013 SP1 is managed through Exchange Management Shell until you create an Edge Subscription with the internal servers. IIS is not a requirement for ET to operate so there is no place to render EAC on the box and you end up with a system running far fewer processes.
Not applicable
@Everyone bumping into some issues, please use the Exchange TechNet forums where we can interact better. Comment sections are very hard to try to help with technical issues. Love the enthusiasm, but don't want to miss helping if it gets lost in the other comments.

@George & Brook, do either of you have 3rd party transport agents installed?
Not applicable
@Tony, the download page leads you here for details if you look at the details section. http://support.microsoft.com/kb/2926248
Not applicable
@Stanthewizzard An in-place upgrade of the operating system of a server with Exchange installed is not supported. I'd recommend to restore from backup or roll-back with setup /m:RecoverServer. See for more information: http://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx
Not applicable
Released: Exchange Server 2013 Service Pack 1
nice work
Not applicable
I suppose there is no concern, but shold this say Service Pack 1 or Cumulative Update 4 for Unattended Setup?

C:Windowssystem32>setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup

Not applicable
We are already running Exchange 2013 CU3 on win 2012 RTM in production. I would like to upgrade to Exhange 2013 SP1 and also Windows 2012 R2.
Since, in-place upgrade of Win 2012 to win 2012 R2 is not supported if Exchagne 2013 is already installed.
Do you think if we keep running win 2012 would there be any issues in future?
Not applicable
@Ericdukece: You need prepare domain by Ex2013 SP1 distributive. You must install SP1, no need for RTM (every Exchange 2013 CU#SP# distributive is a complete version of Exchange)
Not applicable
Hello! MAPI over HTTP will support publishing through TMG?
Not applicable
We're also having issues with custom-developed Transport Agent built with reference to Exchange 2013 RTM public DLLs, as mentioned in other comments here. Any status on this? Maybe a workaround for customers (like editing XML files for compatibility)?
Not applicable
when will I be able to download Exchange Server 2013 with SP1 from Volume Licencing Centre so I can install it on Windows Server 2012 R2?

thanks
Not applicable
Thanks have been keeping back a couple of projects waiting for this, while none of my customers use it I'm glad to have back the Edge role as it is a nice options in smaller deployments.
Not applicable
Is connection filtering (ip block list providers like zen.spamhaus.org) supported on single server environments with this update? Like it was in Exchange 2010?
Not applicable
Thank you Mr. Brian.
Not applicable
Installing now. Will see how it goes. As an FYI... Been running CU3 on 2012R2 with Domain Functional of 2012 R2 and it runs fine to be honest.
Not applicable
@ Медведовский Алексей – yes, you can publish MAPI/HTTP using TMG, just by adding the /mapi path to your publishing rule. You cannot however currently do this with UAG, there’s an update planned for UAG to add support for MAPI/HTTP.
Not applicable
GFI_Customer: They (and other vendors) are likely experiencing the same Transport Agents issue that we do. I have posted to the Exchange Server Development TechNet forum, maybe that'll shed some light to the issue.
Not applicable
@Qaiser.Khan, as mentioned in a previous announcement (the URL escapes me right now) Forefront Protection for Exchange 2010 was the last major version and a 2013 version is not to be released. Edge in 2013 SP1 retains the same Antispam features Edge in 2010 SP3 had, but A/V is handled by the 2013 mailbox role's anti-malware agent, a third-party on-box solution, or perhaps Exchange Online Protection.

@stanthewizard (do you have a cool staff and hat?), Upgrading AD would have to be answered by the directory services team, but generally they allow in-place upgrades of DCs and it should not affect Exchange. Jetze is correct that any server with Exchange installed on it cannot have an in-place OS upgrade happen and remain in a supported state. You would have to remove Exchange, upgrade, re-install Exchange.
Not applicable
Improvement (oh no): "Test-SmtpConnectivity" showed me that my own receive connector AND the Default Frontend use the same binding "0.0.0.0:25". After deactivating my receive connector, I could start the "Microsoft Exchange Frontend Transport" service.
Not applicable
@Korbyn, you're welcome. Our sustained engineer team is very good about making sure important items found (in this example) in post-SP1 builds we are running are what we call back-ported to SP1 builds. This is where the .32 in the version # comes from as there are a number of revisions were additional changes are made before we finally release an update.

@Chris, yes see this article http://support.microsoft.com/kb/2918951/
Not applicable
@AmbersEd, were you in a Exchange Mangement Shell session when you ran that command? I see you were in the C:WindowsSystem32> path. If you were in EMS, then it calls the default setup installed with the last update. Please try running the SP1 setup from an elevated command prompt (not an EMS session) and browse to the directory you extracted the SP1 files into before running the command.
Not applicable
Has SP1 been deployed internally at Microsoft and on Office 365? I believe it was mentioned after CU2, that this particular change release management process was going to be happening, and I'm curious to let our O365 customers know where they're at, and what confidence level we have for our On Prem clients. Thanks. K.
Not applicable
@Eddy1968, check if you have to copy newer versions of (I think) ESE.exe and ESE.dll from the 2013 SP1 server to the DPM server. DPM always needs the latest versions to be able to checksum the same version EDB.
Not applicable
@JB-RI, I believe the specific external meeting forwarding issue you mention was resolved in CU3. http://support.microsoft.com/kb/2902929
Not applicable
@Burak, just different ways of packaging the same bits.
Not applicable
Can't find this answer. I have an exchange 2007 going to 2013. I have my 2012R2 servers ready. Do I prep the domain with the sp1 binaries or the rtm binaries? Do I install rtm exchange then update to sp1 or is there a slipstreamed exchange 2013 that includes sp1 that I should be using.