From d05cff6fc792a4a23dc4c615116b3000c0d0e089 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Wed, 23 Oct 2024 16:32:52 -0700 Subject: [PATCH 01/16] Edits to MCC monitoring page --- windows/deployment/do/mcc-ent-monitoring.md | 83 ++++++++++++------ .../images/mcc-ent-cache-node-summary.png | Bin 0 -> 11749 bytes .../images/mcc-ent-key-metric-charts.png | Bin 0 -> 51903 bytes 3 files changed, 57 insertions(+), 26 deletions(-) create mode 100644 windows/deployment/images/mcc-ent-cache-node-summary.png create mode 100644 windows/deployment/images/mcc-ent-key-metric-charts.png diff --git a/windows/deployment/do/mcc-ent-monitoring.md b/windows/deployment/do/mcc-ent-monitoring.md index fd1e2c5e51..356df8fdeb 100644 --- a/windows/deployment/do/mcc-ent-monitoring.md +++ b/windows/deployment/do/mcc-ent-monitoring.md @@ -14,48 +14,79 @@ appliesto: ms.date: 09/04/2024 --- -# Monitor Microsoft Connected Cache cache node usage +# Monitor cache node usage -Tracking the status and performance of your MCC cache node is essential to making sure that you're getting the most out of the service. +Tracking the status of your MCC node is essential to making sure you are getting the most out of the service. - +For advanced monitoring, navigate to the "Metrics" section under the "Monitoring" tab. Here you will be able to access more sampled metrics (hits, misses, inbound traffic) and specify different aggregations (count, avg, min, max, sum). You can then use this data to create customized dashboards and configure alerts. Overall, this section is designed to cater to your specific monitoring needs and preferences. -## Cache node summary +Between the two monitoring sections, you will be able to gather essential insights into the health, performance, and efficiency of your MCC nodes. -The Cache Node Summary box on your Azure portal +## Basic Monitoring + +### Cache node summary + +The preset monitoring data for MCC is displayed on the Overview page in the Azure portal. Below are the metrics you will find in the "Cache Node Summary" dashboard, along with their descriptions. Please take note that this dashboard only reflects data from all cache nodes the last 24 hours. The filters that are displayed below the dashboard only affect the data shown in the "Key Metrics" charts. + + +![Screenshot of cache node summary in the Azure portal interface.](../images/mcc-ent-cache-node-summary.png) | Metric | Description | | --- | --- | -| Healthy nodes | The MCC service will periodically request heartbeat messages from your MCC node to determine if it's functioning as expected. | -| Unhealthy nodes | If the cache node doesn't respond, it is labeled as unhealthy. | -| Max in | The maximum egress (in Mb/sec.) that your node has pulled in at any given time. This statistic isn't dependent on the time filter near the charts. | -| Max out | The minimum egress (in Mb/sec.) that your node has pushed out at any given time. | -| Average in | The average ingress (in Mb/sec.) that your node has pulled in over its lifetime. This statistic isn't dependent on the time filter near the charts. | -| Average out | The average egress (in Mb/sec.) that your node has pushed out over its lifetime. | -| Cache efficiency | The percentage of all requests that your MCC node receives that are ultimately delivered by your MCC node. An effective node is generally expected to have an efficiency >95%. | +| Healthy nodes | Your MCC node will frequently send heartbeat messages to our backend. If your node has responded in the last 24 hours, it will be labeled as healthy. | +| Unhealthy nodes | If your node has not sent a heartbeat message in the last 24 hours, it will be labeled as unhealthy. | +| Max in | The maximum ingress in Mbps (Megabits per second) that your node has pulled from CDN in the last 24 hours. | +| Max out | The minimum egress in Mbps that your node has pushed out to devices in your network over the last 24 hours. | +| Average in | The average ingress in Mbps that your node has pulled from CDN in the last 24 hours. | +| Average out | The average egress in Mbps that your node has pushed out to devices in your network over the last 24 hours. | +| Cache efficiency | The percentage of all content requests your MCC node receives that are ultimately delivered by your MCC node. An well-performing node should have an efficiency > 90%. | -## Charts +### Key Metrics -### Filters +The two monitoring charts on the Overview page more visually represent the usage of your MCC node, as well as the types cached content delivered by your node over various time intervals. -- Will only filter the data shown in the two charts, scalable from 1 hour to 30 days -- Can view data by individual cache nodes or the average of all your active MCC nodes. + +![Screenshot of key metric charts in the Azure portal interface.](../images/mcc-ent-key-metric-charts.png) -### Outbound traffic +#### Filters -- The egress (in Mb/sec) that your MCC node is pushing out at specific time intervals +Both filters displayed will only impact the data shown in the 2 charts below. -### Volume by Content Type + - By time: View data from the last 1 hour to 30 days + - By cache node: View data from individual cache nodes or the sum of all your active MCC nodes. -- The volume of content that your MCC cache node is distributing, broken down by the hostname used to download said content +#### Outbound Traffic Chart -## Additional metrics +This chart displays the egress in Mbps that your MCC node was delivering at specific timestamps. The value in the chart's key represents the average egress over the specified time period. -### Custom metrics +#### Volume by Content Type -- Navigate to the "Metrics" tab in the left-hand toolbar -- Configure chart as desired using the provided metrics +This chart displays the amount (in GB) of each supported content type that your MCC node is delivering at specific timestamps. You can find the complete list of supported content types here: [Microsoft Connected Cache content and services endpoints | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/delivery-optimization-endpoints) - \ No newline at end of file +The content types in the key are sorted from highest to lowest volume an each have a distinct color. The bar chart is stacked such that you can visually compare total volume being delivered at different timestamps + +## Advanced Monitoring + +To expand upon the metrics shown in the Overview tab, navigate to the "Metrics" tab in the left side toolbar of Azure Portal. + +Listed below are the additional metrics you can access in this section: + +| Metric | Description | +| --- | --- | +| Inbound | The number of content requests your MCC node receives over a specified period of time. | +| Hits | The number of times your MCC node fulfills a content request by pulling from its cache. | +| Misses | The number of times your MCC node is not able to fulfill a content request by pulling from its cache | + +### Customizable Dashboards + +Once you select the charts you would like to track, you can save them over to a personalized dashboard. This dashboard enables you to configure the chart title, filters, range, legend, and more. You can also use this personalized dashboard to set up alerts that will notify you if your MCC dips in performance. + +Some scenarios where you would want to set up these alerts: + • My MCC node is being shown as unhealthy and I want to know exactly when it stopped egressing last. +A new Xbox update just released last night and I want to know if my MCC node is helping deliver this content to my client machines. + +## Additional Metrics + +Once the content has left the MCC to be delivered, the node cannot track whether the content has successfully been delivered. To access client-side data, you can refer to this page: [Monitor Delivery Optimization | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/waas-delivery-optimization-monitor) \ No newline at end of file diff --git a/windows/deployment/images/mcc-ent-cache-node-summary.png b/windows/deployment/images/mcc-ent-cache-node-summary.png new file mode 100644 index 0000000000000000000000000000000000000000..596b382728342dae1cbc9637de2c4aa8aa0d6d92 GIT binary patch literal 11749 zcmd_QS6Gux+b#?$@CYJSRH_O{2c<|eK}EXKduR%Xbfij2q6i`&AYHmh2@oI<2ps|< zAiehz0UYFS-Dsl7#P^K zwVoI;Fq}rwe;@pFiXI1QN37EmMqeY%#|#yNJR5Z5jPs*sj~E!L;@OU#Gtup{-ddKv z3=Et?e*>eok>DQ&2FYOUCyz|t*y0z?hMG()oNT9`RXK#AfQR|>2C*m)D|0h zj-Fiqk8zX#G~Ljc#~?&RL@J4lbYsHO$|?ga%~-g)q7lnAbD93=A<6G(e_LkNq05|Z zF)$xor^k1HcGKgxkATedBeh)f=VsIR()3Wq3-|CpELoxVq z=T_AgLtM<5D=w_vpygzx?>b+Z=@8@!J*$=h`vJI4jh}fi>s)Gb_+YO2NzT5+oAseZ zB|iG!#Scy8_;ZgWOpKPtmZlGsT4h1{;K!BKzi^D`M6@KLH6b8AYhq;dXneW6n_koHojvP z){I!fMRcYLfR3rzx%^0exLireaStY_Q07!sW;5y~2Dm+#ATX&yUAcL}Nc}rmth0It zx=$o3NK>@U7fs3}UC*P#5`-K@p}7n5ZKXtd;j2`$N{E>D?H&5yj&-YP2C~F&nZ$OZ zHqRi?8)frB>k%CM;Dezj_`%i9>yHZw2Q}6tDjNi}sZmXZX@RX@b zBj4PuGO8hN=*foInP5HmMcf|G)QgMwA93*3mS3>}yL=%N)sLo{!`&jxxP6oExO%1q zu{?g6jcW~wL6rsWdUqUC9H-HQgrjMPz@Jb;)s2b(x1f)3JN%%ptd>&aLZ}i!-XH|hXNEzG$qOJbWAeo|1hP%3{iCd9qd+A(8A)cyPKf;)Wxk+54zqW44E(= zYVho=Hsg|lY>=NXb@G8pAb|%g?tA+)Lm5wRTuREB@Qr^8v1{>uz0IbrA5p!vCajDm zuM=a&m7$g=k*f1A2TVkFdlEM$kK$M_hAq)7Ci@Ej-=5b!DKZcEjWTVvr2eNqT4 zjAwsFV{p;|b!&dm;)$wwN`%h+wW9*TkY-YG#*ELN6LUr>Mp!J}EpPvKP|9g=Gwb+9A*+~5PX7v|m z&p^*vcA#gTxll=?9p1zjZT7C3#+#Gwh|+ML55dY4sE7W>eCg$N!&dJ}XF6@mL)g?J zr_iQ8xl=Cmt>z)gpj~OL`rGiVr4SRhE>Q9xniH{v#(!MBXbNl1+S-=wI({4d6Q-Yo z`uMEt~`^OKXF|TEyXsn{W^V>(&k(?V!>Qu`7`1TzzMtA4g1{pDUK&I{E z$PeEmP8=zGX9vhfTG}?wU2#ZntUq*YyyjbZ1dz0+C=K@ZffXI5$mATn!c2n6?gBwS zyeR9FtG)a~zdoI7AOaAW0?(0MK3)n(1&uVpLE2H4q%ZAaJ~2i9YsX3!KDH4yaDWAk zdQg>gnAehFWYozpW2Y@ePR~fK$bhAJV;woj)kO&ve)@r@zgl)*$z@F>q%GEw zD#1e-;n0I@B({)`eDo?Y(T>=7IF%y+5c?Ru(u0}x8=n0fXpQgwfZq7*JS%Ant$#(z z6ei#n=5yHStCQW-8weyx%Rhb0kve?wU>vH7F?1rX_o0(J#IEvreU3nc(eF9*KAzhN-KFtT3gqn6exp5y;y+gQzMLXsHQmL zM#5iEFk!-^na&)0G--b}`#mvRs$W$| z9Bnn#l=j^=;yG~!E7Ls7K>*o8#BU~TBwt<2h^y`lG+@XpqQ zU8|DqE*8h;qxN{xi{1#xv_&lP`W` z#G$fY7;>})a8_}EiVLhJgg^s9Y_uXAvR6%7iv=MGfE;`$pg-czTqjBp&LVi>iYhY) z>V88GDsj2f%!DbEU;m)<*J-hmIazv#mcCu-j)xT%&RjlQ{ENJTkYjh$s~D@YD~}7D z+`NYzd~b}yd0RI!+p)@d-nbZNh^KEAq@QDlklZ~HjsHBMO>_zQzBnNOlQjQ;ycWvLU)&|iF8D*YdL zntZ?Y+f()t`jdxOO(rdLssDo3|4l9a1B?I9IQM^S7O2P-BvC_5L_|whw^~?i9Es13 ze}nrBNO*hbe~S1ZBiL<>nJi~;AW~R-_}_55m&?sX^)E^I#FZK!-wFwg?8(&G64hPY z2l2njKPQZ^8u`wm{1Q8JSxP8VxQ=)4&@f~(aYm*V|F$mv48DZ*rZ^8ZQqhK`*l|^~ z@T%dT<&@j;_=Ypf_!p};`SpUWxEl%!Hx{ zArNP+o@eB2NEsq&OA)dFyFtq~ngmRuXJ8l51*IaPg^}i_OY--dO^rm$Y2J7y^plsU#r70>BZLcx%R9z zP`g44rtT|{I$IYrlV^L=WEEaUD2>(51U|pTZ)fSqPiQLWZX^xW)Sj1o=pXo|BU-Jc zd$W1M{m(ifB+a8>p<>zHuC|@`%<6h3_tvC%c`X3kQ#e2UqxITk=$~=#S%Tcx!1v!z zYwppq(rwCBT8jer&@My5k+%n#>m)$g4{kNZ!b?*|jrKuxUVPv`Bq{i7*4lE%-Dr|zcYLE{PsV04 zAg{e9i?V8K)Rinserj5oiLhLoIFH0&n_MPFpOKT*_5J|YN8rwv+S}?!cd9nxy)(iW zcwO(|f0PO@_fYiQGiUo2wyT`mX~99@*6S0OZzbIW09^r?xf;=zmJM z^$pbOkT7^;AxsIkO@&;uR5aa=*{qJ4RneI-p}?DRh4e>cos1Pe++J4SirXOACQDY` zaiEsPSJ2FPX+CB@zqMTRpj1 zqu=c;EVe4DB7z&H6{W(C`^%z8{yZasWz87htuLU>*)dKuk&-}79&Va=j#cvws45<< zaK3#p#aJhzB>6T6s)%#c|0~a7;W-M#6E|Zjus0>VyMU?^u&8(N+H3wN$4TC{JwUhh z-m3NUJgVTMpM7|@tK8iwHDy~;Zq5y*#wA)qKzV{^h}hNWV4=&g~UX@Mizrq{(GMJ{r%jkV$F%o z2_@#UO8U<(gW7b`iI#i?NAA;;#zWRLzwXtBi{N(c8^(_8<)>N-r@aO?ik!Qy40bKB z6sWMD%Uf<1{CEhw#yHX;!PQ^OQZ7koQ;sO80!%+btI^ktJ3}7pf$5i^3O~K-EUw zpZ-|B!@jvBU%l{F#Sf~L{Fw;SORBB}hO0CQYPvVLyRIeX9A5s&Q@UhWyDIrMcQIuqD?~nj}ySLn?4sNb{(h!ek#UwH)Q>Ll1@#Dd*3a(dduqTKsXQl42aj8 zz1)^#tmzhY0y)u>zL04}5jdBTmTy<=W>!m38_6t~x|6lIRIE7a(KYXlh;)_g>*xBW z+bn@`Dqjde;*w5JHg{#Kz|&F}CZd4Fw#}>-%?I1P?>Fv{H?7GRK#Jw4nX?aLpRdc` zEDht_zTab+iE{HBR+ zN$jM)yUqIn3hQ-Z*>Z8iW$>UNi)Aw+MB+rl{k>V;4RH-#F1T7xfxTZHl4olUP`i?j zYN&ErTvGsCRkn{{tIRLl^$T*l)RzkVT4xq#pzC+9mdrJ_uq1__@ z)+on4@kE#q2VK;D8?Y0RHpq}n;IQ1ly7i&0osIP)mdxeT5rZX}^TDchrbOY2xbnQJ z@_)|yL}w6Q>HZOs$}~|C>NHKXs__CF#9i2KQa=wtQnTRitncr?Jrk_mq4W;ss2962 zRevgo{M+_pV9;llEas@pCeQjV$HZT{WPI)j+ zwEM#Zz|66i2T?IJnv6?&@?fwBO-VN&>V(mqQgl42_cH)%#n_blEJMQv1k0Z18JKYM|+_Dmv z0i5?yEuJpoP?yNUuz!0KV9LnFku5utqUiDOPMCV2i}!3?wV`QdvDe-nz|)UmlVI+2 zpxT#~uUd88oj9?PvU^%&npVI}s*O*#ID2G?$SPs3WKpber!?cYVtJElR%SAvsP_Bd z$9v!RiBmtRfis{Bh4Q>6OM!t$m8eVaYkG=&-6xpiGq zheFe(w2u-=;w(`6X z!`U{M*_HWNE}6cjdVLI@qN>ioiEjvBCIte*5`5A7dABw@Of)qEmAgB~XqVWo^+yAC z)26p|<~k2SAex_MNQL~1yn0RIA9b&k!f$%v^9urpym$+ltuS_bWm^f$%0FQaYPvJ+ z*)2D#M&s(mYLmNE{tj|K=g~@36D^yi5i@w6j1rKgYy7 z_SSkbVH%E)1B1_(-ne+c+S{#tgXRDg>|8JcA%oN#=Hd$jxDzLc3QB=PN_S<7@+GAJ z;UX%bLOLVgx3a#n-kxljwZba6-CtYVstWu?-=W8256Zvg?{?3qP(=H??$qi>KFL|q*4w|LGP0KVvcaE|0q0(G(5 zm5LL_$&%UIG}lkRdXpwkEvghfxHreA>rq!_8GD-#Eeg-rE}EIT^pnvG+{buUGf1#_ z?CoM^F7(*%DSsH1^}c_2EupwIrd2n%zh@v_cH833!_f5N=V`W6SP#n!6_-|pG%Ai# zCzhRDRc)sIj4LF5C5z0UzY9bGCM8x~_jX}>Amh%R@6V?`^9FT}W0xIcS}L{&E~?az zT`0yxkbFi8d7aD?3gs5_EOSpHRisRUstHe$QbKHV1J|#yb;wS9+zn1IOfek_!&|a9 zvQ0A~H2imk198M$fWN8pkPQF4{J;&21PEtUt~mp&@&2|bmSXFw!(?r|sQGw)#s7Cv zFk{)7yC4c40^W9^(`+2WJTJ=}weHJI@*6lVmw4Se^P20&>@Vs~r3Vs<^ z{d|BK4NxGd!(?Y!+haldcEi52K*$c3ID1;((5WY=R{rg1tKuxFB`w`NX!x0^{-)AO z?fp0p)yZde1PtP%+A1+@AuxH7#HoJYWuO3U#p{7&RO4>0x2bci$JS8^>19#8dpkKQ zMLdzSd_4KspIGBwd0R8=%D`bq^B4U~g`brx{b$?0T;`Y%xxlx$`(tpeL`F9b6R6ty zBtFXPzG64v=gzW6wiKyS?2^&QKpnzD29>UJW4)#A+-tp>n*1wQ zt#np+GbZZ)5$CAU*0uAa=$^d`5mf{z~)4OF@n>qjG3hf8k%w#8R~s5tcg90B7qq5$?*kt=j0)gM* z-}=94GXMYaZt8z5XaA4(@&B^<9rT;Wt)>K4R@Twc(XA*}lsgqGu&C^)FZdOb-KG*> zv^ZPy4!~{#)DbPE2L{37vZ_?_zqgac=?C?WyTA8p`u}qO4Kc^Q>DrAXg_LPyr~I7E zoJkE&TerLMwf~9)MaLrJPjPG8>FZ3(<&_QrIsPZ>xWGUW;>!+D@qYQc4HxrKSgB5e zRP=WAt1Xye&7XHHiz4Mwa$ZN}1k{GU{Nil5L~bf@jpH8eC4u)5p=l~eC@EeS`o)KB zia9EgSW%`wa@$REw=o#9kE@Oud+*f@axDzLXG&0i4QwptXg7VbV)oO=H_hlkko2@6 zsP!7wlHeoGZE)Cn`s)>W8Ge47&rNXsT&un*{#s{~TiGx1KXZLRi2ze(pS#x~?nk9Z zVKypLs!6Ix6~)mgI#*?u_Ds{xay9H7u)Z?H-c@EYkeLEr=LA&-L@*9yV7rU zA%!`bbI=lG#H4@MH7>S6sicKkX4Tk}Q!zMx>twB}DsPO=d*{Ipz)|(ro|`e?4wx-l zTFt!uz$ejZv6(%HCmgV|+O zWp9oNFXTM#oI|?%ceTh8H;@6T&L7}G*6QO^^5RVg8BUXgng5Cn2~42xGXg%nl*edz znYPywBtFPkS54UJ0IIrku@lq|Dpb*}9-S^T4CpKEy6Og5 z%glrZQu-Rr@9gV?bTz*dV%VF|l+D91Wp z@UiiIiI+QxX-3aEy(yQSy^1OMB%2m%3Y8`wafo6cBsBs z+U0*xuF7bhiwf?GiE|GCnqobI!I~3asNoMZn!mqX(*iwcGR8XI4A% z*KZLsI0BFF4gHsIxxTKgI+VN^d>P(!X}`0}GSpFFgk~?#Rzp^k4N+Mc@2O>z6z&ON>lcQsqxptE-*2YH^w+F(C*X z+FDw5bJ)Use*40IMULkGh#V5&CAQJ-yqZ0AikIDH#l!OakEP4HmQZ-RgEf14X+nqT zv$<5@wj*r@M4D_2sTiu@x_58Cc{i1GOVH~`1i$rgsl zAWuC5UL9#oQB$_{LAM4EC<hJ&rT{` zK_ES?u{Fuvp{xNz)t>zG>Vfs^HP?DIZ_mip%>}KDKNhYiisS zA6m)+D%gsam1?-6XOxyP>2?h#=eszdO2`|WLB1b@W*iQFDFpajw`8==%HXsvGkFao zxVQ#uLSY0=cixX}Xx%se88cfFl%;*_*x>xc^~$eVr6P)@!`~m^!GT5h`GfU;No=!Sd+Po2}_-*V0)wE_b zKuBo>xdz88nOlg+TWpp7mQ-9gKRHeoq{Z7l>#8{I7Q(8WEx z+3-O4Yw*bepnRBq5G;ua8~q8u72P?A>)M-fUzLI5HCr&me^Hf^Q zcV4a_x~h@_oId*&M!)}=$kVgyf_u%`wTN3Y`g09~gg9V!b6B^LR)22F_Z(H?P0cX# zS*c03GDu@SU<&IywPCb^%W+dGuF;bn;PaWQa5;h2yf^o${t0(**!kAynPg))LOtFyOUx_zyPEp!=5d>^eG$S zAQ#3n6b1buCz_@j=DR7v~y{H)GY zri=Kps4blj*it`%?=?+Dyxd-Ck!-fPFmYR(uG^TV8xcg4mD0;zv#)61)Y-7>9qDDy zAMeNh>;oJuvTv8Zo)O}1E`~Tf39C<8af0_=L^6uVi}Huq?m1K>edcQ3ZIst*xs$;T z386#lLDQSI=DO1?XWiZj2i(`6@GVTWKI*;c3|Y9hLi(v^37K9F`m0@-i_}HCY0J3P zLV&V|*TRhEpj-sx)_po;hMgQ9?TiHLKFGb=$tCcG53z$+xaks3x@5TW1V`d~6Z}*Y zXZnGU8{O;5>puVeB<$FJ?ms$*s@|Df_eN;Of}9gx+(4Q^p2xGLSI$S2Rgpquo2&C) zLFoJ4z`;@Od3W!)EZ9b@Wp4V)r_%9;M>_T!X*^14(VLmH#yojFucmpamk;CIKgbTY zn{urrDvm09e5HPxy_McHfkas13{{fdYW(`j&Wn?Z$ic_THnl==zd5|%*KDVtLCf?m zl5x|*g$61G72?;u4!!2kbf)5I{dbSo$r#nG0edIkHVt_)hN{JO6e z3S2Iik>eXjTz-Qc83$$FuY|$*lwkCo@{UcKjZ1+M-=FQ3D4Odd|Hq;cX_5|ez?0aC zYl=h7j;^+%<%iSpZ(U32$B*gbQ$Lw}X`zd%H zKoZ!CpC%i9{ryQ1v-q>yb_YN61`?1uM YaK>T~@X~lXy$A+vb-gDQkL|<$KS+=yJ^%m! literal 0 HcmV?d00001 diff --git a/windows/deployment/images/mcc-ent-key-metric-charts.png b/windows/deployment/images/mcc-ent-key-metric-charts.png new file mode 100644 index 0000000000000000000000000000000000000000..b1d05e6103139bef459935e9c4bfeffd5aa30ae7 GIT binary patch literal 51903 zcmdSBXHb(}6fPR1i3lhNNbk}?x^xify-SxSok;Hi0a1GIO?n6Eorv^~^p2R&dkqkh zocP^2XYT!V=iXoEyfc}1zsY3nti9KI)?RBplSnNMMS>@kPXGV_fwIy&9RL6e2LQmR zfBXpj4rq!AioRiZ=qSDg)J{_GqaU#BWYuK>fckj+2TN@9Gu|g9BM$(8jOE`8Ls^IU z3;-C_Q+_9_=WBknj{AYc7KM9eIz!;HToRVn0OOc$kkv9h;x7DlSQm1{a58~|Jx7lF z_*;mxtj(C~=g=d9lH>+ep9MtzZXT<{jCld4LpB_=5x_UKods2J2X9J3u(V(3qbCLc zzUw(6E&dy6F&AU~H;9Tz`R^|CJAwGW0UM>xKTQAtc{!E;?%(Z|@ctXTAYjM%HwYv31r6u^ku@JP4 zmQRjaYFAw}Zg#rl58*cJcHiC%hIO6qtp4}C2sy0-+k*jdb}=ZX7JnjBGIc(MKekz* z-`O9G3ydFB?mr4to_s$`AePxr%W()ys4cd~S7C4ulu}zPvyVlK0BHT9X9>~aGGi?* zbO)$Jrl?_xTKS=u|2wm+3ZNu)f&P{4o?kCB`^1~wx_~;aZ}_?HxoXhfhZ>j;|0gdp z6)gAukCX|d0Dw$nSPDR;s)>5ywRf&^&`x9ds`5R4-CZTb4zRQ^S72XIa(q=9BM-1VWg!z+ke9Sa~Jxdya_^s$c3Uw6iu_` z6;Uirj5iGt@Yg`#|JMMk;cBJ0NYK%b@c=1SdCXK*h zZrAWqGji*XV8zl$6aWo zre@A3}LxA!kCT1Do8XRY+f?UuxT zy~3x6_(0)9v1bi7RKy-Ye@P{Oqx%qvw7AqhFk>c6!iyEyJ^2xRmICGK^Qw% zM%gJ{R4*Z8Ygd_bu+aG$)mn}JaxSr5K=b_T3q;@fpwTX`X-a8#vj{iSnCgDN6YXaH z)}>EGtp!;hs_=zB3Q}@Xt_`?S6FJkoj>V?#OI?8OW!Ecmp2% zad@GTDBZ9%aG*-5>_dB<^!59|>$&+QV8B|gcz{TzT<8EfxN?xkIR625y=}J15Io;= z+96V#5sl!@1;s#}^& zzXQkq_Y>o8s)difqG;M}zH32>jt$?Nd_TfJ11Edt`5^0vvIR4|&#qEY&18Ef{hG_X z+|=S`h&<6kbvWFofoF!_8Rs`>vV;lZ*m-lmUFwNpt`#ZrF|Y)+?>=5pRn@Waa1gN1 z$YQje#~F~QnRJZp@og1u0c=_F;idHjaw*d`EWqaG5txk=QGE@EGs6<{ij^iW`vz&tTGOs5&RMgK zl#CD2-bknpr(Lhj=^5c|rCYwzgzx4>OL^pyl6bp_(U~&IMEwq^=R^dswgfut_gKJ% zntL=ftDYMW)^SP-C+AkUKRH>JTe6xI`?hDhxt{l?y>oxZJAgG#Bd6^cy2evou5;HT zyeniepNNO@IVs9DN+k_NsR~#S*u<+Axj_bl??;AqCvzdTPU$>m_j`Rrit(WMbc~-k zXwa=l;Z^}ZOE&5os*L(MuiWORIE0@h2C6M9n(<=*Dm@1MUE~KYOl~B8?`^WJ9t^=k zP>|QI6GIFFyGH_l8`GQ}gp=O@mw{TiA~jtu+;?(_&)4T+5jeoI_*fB*REoLvhJtA1 z&z!r6k<$y^062v-ES>h*vE9V!D@pnhBVE zs|1@-x3Fdv^I!%o6IP!0nkP{XjDjj9lJ2Utbo78aKBqgFf-)l14^Eo`-5+m)K&yj@ zVz$BK^}u@7DZ*vVEYw5>1bIAiNzMa8Jrwx7dKlZ?$z;OWcRIojsQ6 zwQAwcRR>+#2=ZzK3??`* zz_&tgQRHac5#@5DX5nu+U-wbcz-F$Od#PkD#5L>@w(R{LF7DsJVR?$LHOD6LKVgs#tm@o-1Ic=;E#grs>qkzc*`*JS$6yg zr2@a9jj27?wI8mJQdqNYB*l(1rYdQQC2WrV0LJ2;^!6h8zs7ic`b3-cI`tJZ=ld%J zQGW2v{yAjmj*Fe{_O^&9kqEGa@h_-UXG1D04c*$)%D1tVi)31Xih4m1_$|uytoqMN z&3Kl+*%IV|F|yZ!E-f`yT)lA0e5&#u4B}9Uf;-F>#frl=Uf?GEXi(54zj$+CRYvaN zsn!%z2B|Z%AyR6SK7;xaUuW?;*j@Hxa~bt~;k#K${l4?X)#ll7ZF(bnt5gp&o&BA> z*}^9__YoN>!)@un)n;8oCMBx`)RI`68-bl{*N5d*al5osDo88|7kSirvzYOV6155( zKiP)aV#$}}UVMw6W5lM!fg5w#;QP!8E`V3d1F1@qqgjAnd`BYv;AY$NrM3wATc3R+ z-g|`{CH`=Kb;q+W&;)3KH-?XM_Ia|T@M)BG1u-bw$L-=)BT(2UtV=xDzTm^YBA#MH zC>`iw)6fF+oR(H2s!Su7@$P5nm*|B5xqdl9247tffb>n6G!#2|P}Wtt8)7&VFT!RF zqOY)QHigrTiN1*x4z%-4Uof5a7N^?uO&8)RB+zT|ws8YnO!%i81hptv%l_I%TZoQf zP)oZ8*g4lKSL{kiWSSLte=O1^`E-O+4T3!ahLe!Lwgy_BIR6NqjB$=lzli@RZUOFj z)0%}LkhGP-$wpXqVq2tFL_Me!P?^sNtGDMbRd6=CjVv7{xom=n2?fb=A zOlG;^<&d&+te%U!sUtsJ!oXH~d%-G?*ABCX%Wv3CelTA9E!iw%_F5)X{|Sx`&Jyw% zoRUUdEtlm7!f6h00Y_Nu7%3`~3-efVtLd9B5(D{o0$wk&O;7Zt^7sjhSs(s}7SN2< z-}%jgJR94Yu~JH>k1@TaOYeODoPk>dpY>Tyd^95r_S{z_gC)Q3x}2bjEhghS2yqP( ztgq!S3T?@6hDRp@^;m;fi*GJ^q_1r~#HUP-M2d>8PUI#R`G^7qEvrAiqHRfpp|iUxA-KT^Ry{w-=I$c=T$V;+ry2B8$WPSX2xJ zsNUAil`}L51V$+Dx3<|xhr{OTUv%JFseih4T$Thj@&VqQRdPF>nUG}Abf)oHI{ab{ ztMqia3fGPV9DR3Rc4n_B$`pcRE9-9Te$g5J^vM_^G6ib#DB2H2B-Y28YoY^e{1(^w ztAYIjlr#O*N$!%nTalNu6y7L2Zt@m{c&tl;svfv~I_mh!uPE&>|6>uJ5lYm^`TCE* zrJ5P}9_~^vZe^u4^25w76f>pbP<^Al_hBJQcZEnaBnf~v4g;c@r_rFK` zHDX7vfDjtS^~R&y>lkSwRvL-?`vEOFbm~OhCR#DpF5RA~TM=>l^yukVYMHI&TFMtc zTO`&ShV<7d)0b~7uSd-_E?d_EZpN~CK_uOOP6I%sImo+mu?q|~hAwyNR&=U5K=^N7 z4ad~hY!cp#6wac&>7u_;u!q**7foKqe;R%xtu4y;wm(Ct|7A{vPJ94Bip=BG?=L)j z$VS`#WO1etLf^9}a`B>Nr7$buefPZd)KB*q0`O=RCPEs!I!Qzg{3y`rS$Hq|6BS7j z)&dd{RL(BI2kXUJ(+aHuMqYr7tYtsLCu-v`rB}J; zbJ2yrzcEoo;YK3n9eb6ZlVL*xfW07(_AD=+s5a;B3g2C`; zk+i3$$kD%zfuevAVr~z30K+v^SEGO&RG?gd?u(G~#pp_BS4Qp?eEBl|JrnP$)~`B5 zR#tFfb~Ekm{G`c4ro>3hvgBdvu3YxHbg*}?@2kTqT)w8=@`?6b;ql2D&}I8HQJ?&nt_EM#8t7LjHvWiUQ)aZv z{B85;9^`c6RPVDi>doI=@T+bZTpzqO<}DvMqwV1Y!L>Hb#RCP6oSbD^u9%Pm`v=$C zvPaUf0mHbt8nF9ACPL~rKgWc3R|*X6WY;=fd?@n^bSN|s&5|S2F4G>Vw=q_wHvu=g z_a2Dl#?&bkazhn=YL~BCa|7OszpjXIH<-7&WyRkUt&-E{1C!Ucje&`R>mjVD3mvIQ zAHraX;#n%yBEQV4X@^nMeL=y(MEW;EL7BNpgFe;2@^JyURwuxH_w3+ z@X@BQ^=-6SCqY)*hq3%q5zRHpyX;(}U1Fow_}my3om5l$n$5NQqxr#HF76HGj&n|0s=>g9uAARXsg)Y1y#*liT8>3wft%b_g!-;THz6RT zndvJL%I5+)?6X@WF7YuWGUxF&R~MVkKa{oT-qbCL z0>k^Ow32XFrD)ovT1MKyaSw>TrC!ZhkA<9)Q?I$Rvdi6#ddTAbDX7=JNF%=^w{rAm zw^qnx_EKZfmF8hCbg+&_oTa&PYw|zUQJXh8QCuvqbBy73)wSzw6)s)aQmQ4Dh|yxu zM%H?^ccRD0MkIGhn!u6a>F|;QL00_c*nxtgtNQc)Vc&TL~WZmEmK{@twky2T$}b<59*N^JH1=62J;2$<^R zK2EOWAFrs@F5weC_;084wj^xuU9Kt2?pAEN{}E9f-W8;te_%gzFj6#rygmz*2LV z_Rv-uvBvXL@mkI6Ctf7|ie-ixzU)m7K^IJ~R_$3$8r8;djdE@OQO4pbda@2s-Mr|;Nt=v6b6mpU^IS*a5?ILuB)WX z*KS=Vx{%qjZ>kdu{5&6QB)*HCwYCr)gk*Uh9DlfwBQak(m7b_v*c8X){W2zVb%Q~m zWU#R5m`z+LL0Tl&XD>cD+Rce+w|i2<1+r+t;K8j);b-q6zv?DrkJ!S~ExF&C60c`m z%|n^PFV|fsil=UVgIh1b1Q_2lUJL;Pyyer-7__OXtq)ukG|4Rm{s1RSoty-jkB|85 zC9Tiq-#q)ma|t`%Ja;e=hTUHf8Hj^B{TBy`#4EkWec{=Nro64uhSms>|Bt^vjShVf z2t*ab@2a7v{-{mXmY<@{dySBFa%UryJZozeI4&@(G-?{^YUQ;8;p!zIK6i||3NQ1mJa|V6fGVS(TEi< zlw0_1r$&;n#?lI1oE6ADh?*R{DX%MQgXI?q_S@7%ble>5RYn*y8?IG(Hl zcdZ@WoSt68_3mpXnPk_H$Btki@;%J5RV6(=7IglF!qwW)*?hX}?JqFh)T%6KbwKg! z&^1*vL($Y!=M4~99dy;O_^LX+-P5Y;O(SQdPj+)KDi8up15ImbRUCQ+FKq7jmr5Qr zXpgrv+v(+6oa*Xx@M)Lv?we+{R3>}jjUAmIdinL*!Tph^bwc@4yPj?XZGMTN!C+hX zj*m{2S;ypBE9&Q*)}EKZCu!_!;0U8D`!?dI_7NQmG1tKaT!%M0orY(5;4R@->UZUb^bF9?c<(<@N61?HL3EcZNklZmx zRK9FEp0SI0CjbD5CU^{Hz&2DhHQ|54h?LJ$4J~M-LBBdrdq`+$C&_-$s8`u_1~|32 ztZCA!qK$-TZ^!jbo9E4)+J&6h&VB?^Xhq#rqBS4Z7wcr7`zcR|R>(`KoAMer{s_WZ z?0<7_Z#87x+|e!4)DtbmgOtMC7U5ZPE9J`!b-0DrUn{@2JziO6+-=80Gu73Bq!887;$EcA-Ge;ajO2M6yEFPF< zt_D3T-vxxH9EhkwWnWL4l__yEG1jE``$a;zzC{a%;XIv+P{m-O8dXFVL5Di>??l#M zG!-gVXvdA}k&GMr;O31pIx3V?Q|lR!dfi)z@p|Bi{Jom&MfP-M7$WBpcT9$w7rLAu zEBo81(qpU;Y1b3r42*dM7T?LqI%_f3PP)67n? zg58+3NP9H-p4_Qq;`-!2<2@GrRCn=H)-p8V_^Tk1*RSQs(0mKq{fm|>rX&3k)vRMG z>LV^mEi>^T`4X{9OI9&|ld$_^>BwPk5Z_i1p81C@cxkMlY3)jYFY9%?dMC+1TX!~Z zn*`jH&19jt5L~A~N0;BY*_*sD#=De{a7;$f!!Okj>7JJL>?uimbVtyz%2PIK5NLov z)tW75{Y%n@+&F|!df>24)^~2GL7J@6ZgGRHUAM~{<}UTJ<}Oz`02|=|V%4=|Sm%-Y zEbV&L8<%`!Z(?zEKA3atV~r}m#I-4|@po|EiVdh_8!y&|c0H({_M6XNNNizQdf6X3 zQ$udkH=y1?JPu(F^B1A}bsiw|%(F`(g9@Jf_DSh7zPv82o>AbIUVpX%RxrDe^M81YWAf7zgYC^O zHvQ$PU#W2L1e23+1$U(}sNDnAgTP&Cg0&X-b^nB}_$_@OWo@NdY4zVG-NZnc*d2

%MAGf*ROrS^FXxm?1IK}F;pgcanvRoXd zx;BQa)>tq7w8W$v=X3evMO`H&JspdJiW?6lAZ&jtrKZr*PElF5)zL5rJqb13m6zhC24|CUt?#;-@wf9o{ zkn7#QwRHFQ-E~t@J(#${h7~JMsrTyE5d%x2;yi<9L>9u{qjZr-%&%YYenHHQ;&kD5 zVioh*QZKIq`kS2;4P%g=B*BdNCxZjY!Ptg|6eo_9E7NRgSfma2l^y!9$2d?XueO^b44SJ zv!B8laBWGIrrBZR^f})m;dquHOd^;OSm|}FZTQXfY#Ero|3QjhY}2*P!$po>0T_ovvn%Dj!{QceC?FB5{6O zcRo`R@CAXa>eiF1!66q;3zKti@RawZ*hDGQ5H1jOxle9x;m7@9&xcb{=)2wbg!sie zU-10Iy!E|z0P^|^xm@W(&(>_34bs}&D9>pZXaJfXxgIv`v+%vkRz*nrjqwJP-?lq; zv-aq1?&lNvdmdbF=kiQJ8`DApk4}YyW;-wTNtxi@hoY9NL3SIpcz_R=rRok24$_E+ zvG7Qe-HCj#%|39)L*e7cSE6)t?_?9y>HmJU*Z2@jSEhN>V24~DjTK8I4r!y+lA4k!$a_>&EnrK&2T zZ0mvM^RI_3Q^CzOLjx0=YA?|!V(3)oH&^q{T$=YVRXtk-e57;oHy?PD+aRs`G|;x* zv(kU}OB{_DjG|NSiopMfkoX}$&9B7u;Dq-c+|JCWX_&^*{rac^+Udh7iIO;cKmP44 z%;(-T>mslf;}j?;b-gtxx~^Q9H01IaaHD+zT5Wu6^?79+%_BH|`7{C#GL$bF@NxNK z8w4ut(Vr28pf*6!61V5U(Gvuk4CLu{lIy3ijz&f@slyK@2fZzL$AkHSKIW&^EzN^N! zf+8LGw_w-^E-^ApnF?*I;MGJl$09{5F)`6@GUpsd^z!CnI$LC4GNik^Yi8!sP5iYj z@q@*RFY;G=QMQ!t%EgUM-1o5~$S!ZrM$e~r*1#&9w>CYVnCeZGkJzwPc7Wn&u0}}G z-k)Afrp+LqooXX6x5+}A8^p5DyoZ9+>jJ9mPPV0rCIL9;qG$iz{SxrKf4R|aD*PPM zgK(7{iu1fx?KVek?EO}ZS4glp3W5`*aGRuYqZutFO3FwVMKlFOtKn#=K4=AgI)%Df zy*Vy{OQ?8?t>3y?!*323OU85q$OSzx?cz(nl!S&jEsXDn(iB`>YIITWu6>Wg%YnU8fjFq@qQ_Bw= zNYdw2u;s~6eT4W%px7~SYdascA7mx$94nB-g0=ZXgpqM+2FpmsOds9d=3_1FxWa>A z|0jfvEua|7Dp1YzgOJ7j>tdI^_1jx(Mb{SlEzOOUvc>N|5sBweJg*O%$X~D0XcJyA zzJ2OYCtQYAf5-}U)h>~FSG#(uYR+J?jrpHAXnHOsAq8-dc^aiaOSq^iVAJ#j|HHoQ zRT^gVeUqI4p4_|e!;E}`n)m!V-6>y?5yO2vnD@!lkoUevuZ>rK*w}Cqn7sT?)WrZT z`{zH40nTN*I=i1!>-B>W5713L68_g$(+A0a-Hb6m)W^JP+Qe^C`3!v;TSTJtF|o}d zw#7wNjMW+XQ&o4<*I|Z(ee*wIA%TsGDl%9-x7U@Vs>qCGS(>?)b}eotuZQqCg}wK_ z&O^_nTb{Zo3QpVJLG_z(WQGrvK2%!LwSxcv zOH8{5pKWi;CTT<{9nF1`xC)4-fv=uf8p-kY*b zqAbWe2&9(wBf+~0!vXOX*@dW(-W~rM=PO!C!u7CNp4}E{7(c$&HNeuO+vKvG4fn$x z2oJEa+?^Ilk9Vc&u^;W;*!AsT@{H{z#|D~`sSvGp@Sz`Bn;FA&Z@LvjqDIICr zzfDTj*B5Ojt9y4u-`y6r*Pg~P**zJv2mk{&*f{kw^J^a!ug{0N`BZ>xjq5#B|3501S~56aS)P zr*sj|di|l^&;E^WP+gU6$>(=z&lalJKXJ`NsV{Su@?c#f= zeE4Si`r*^?#c!992O`%lCEA3{fBdtk=l^JFKk$fWHPZ&aeGHS!z)gEiBqU3lsSrtj zEAxCu)N%7<*`F2@5EA>pO5#sX&_ISpZ~Jm|kvydEa{&_?ps3yV9{(@iT7=wxhV%c0 z1vjC={+YqO_fNV7(`=zNj?N2+NL+GM9~pI8UVM(YGgd$p1AYvR@L@4q5-tgOgKafb znC`zxE(WC7W&f56t+0;;n>AbM?S!^7PscBPDqfATFsRAcVEx#)@P^6g?ODwyCdN>1 z^#trWeQfgt5)Z~o)%@4y|H%jmZSd)1C~*9suMbVk<~F`fZoSzTV*39JW9LNy&cBgza(TI$k?WeI$1#)ePqfre6{FWr(n-nLt&cW#-41|4^IW;wX_=i3an=(@4PzHj=ri zu}sMtEN}6D^Ws10*S&%T2=njyPnhlOsdE#4W-&CoDDQ^HQu{g_Q1Pl8%kTUb3S=;r z%F<-EU#!%M)=;0F<1?PVd{!(5dh5vK$tBTZ{f*8fqJ@cauOaY)1C0&Z$sf8X`WTVc zTXv6vf(CAx+>UXT>lDIcERct%khPufRp?F*I{tlLVq$sr;14zo!UtXfkFG<(7WwtZ z-s%PGn8JEg6OMqF>Po92@8}FLKWr_jAzS+tTV~!lztJheo?`q(-YvgFlo<#xi~UdA zCkoHx6Q#Kb`fp?Z`IclQH}C4tWzLlqS)N*+uJ_@z68w{>V@qtHSF(RC_d%zBz{jbf zq@-8{ZT*cgT0hGFHd1#~=aKmPR;KMMmg6PEv28viU3tQ z57n~SOVJo`yl$Uy?MZD{h7Y^L)z`vm+&B?7TBa6fNIaK>N#o$pd#`_d!Y2j3I-$eE zO2~4ksAuWgzLPmEPXzhOdIhv*+ry(C?mNI)Z#zs@O_H$EV4mb-ba*=ky}?|p`O0Z$ zKkv$;aN4kvBDg!JMtha~IQj&`<2y^`aP-x_@7Q{3>`+!!(QbF4tKZeZr=j`w7eqg^ z(klEij{5P5eGKcnc1eWc5Qpn5Dm>Rkt98gpTf0~^tt*a?VfWYU`odP8RYDf3_O7xx za@s@f%4GU-2}vmI6f&^k-HDhUSXSOH78VnY)SzTC8mc7aznzt5mDCM7sNBuP67+;O?8QLIUgt|N7@$>7ux-Y5(qd5J5?;_|QPip*K4eQQYn79r- z$V0QTOmvjW%N8DI8h22LhqrYv4HOl&&I=(u44XIW)JEsr`?r!Qi0CN79&%oRwUKAy5>A0F)ZBX1rB3X+&}?i%fkkW$9$ z#KLGP!w@xpPpv$KjKLxj*LxJ12~7b3Fy#8!#oN3RyKk(#Hnh^&Zae&u7ubn5hA*PO zDN}PH6!j8^^9Dws!$dBB?{{Q?`@rhn38+ly8p#(R{;o}I3V zq;NCYh)3n^odr`=wU!o_s&cY^vt0}4r*)j-4^`+h$mOT(?<9(a0<3c{mlu9O4dpNO zG89*LT%qM3Pgp6^T>?FCI8<|rT@;Z_-=Lkd-%H27fi_y~tqecdgz;`(?Jbx=(yckq zjI^qsCgMj-ip$cz`P$PSDClxV(X&@`r#QT&XSoz(RLzv>N5N?Shg`rPCnIg-p7Rm< zNE)IpYOM0oI%QhtTtICxz`IVnfApeP8nn2(7;dM_k@6j-IzK@NCXaJnUmcj*WIy>CVI;nK@r-$AuR^IEXUq zWnCZk?TY&~x$F$u8MV3VwxZrE$mpxXZfFD3gorN&Hy4Ip9gv(-5}&;MOH6R>^rm}e z)kL_gA*Di}W$m|}W22+Q6%Hw$va+z3fVrk{bau4X;QB%GW`I4t8%L!2CiNcapGzoK z1XeHWl$}D}*qeYagU>v1zi|LHh5Wu;m`hYHP{lA~j?YEfTv9$o$E#tuY|>KU=gUrB zNd}hp4N`a0BTx5NIzhq#loxPz<5b-Hv>O^dnNzZUGa7@^QIyL-OPOru_Mfv zdXWc}sq@S_yq8Nml7ckdc5PmZpLRcgJ|c9263P3J*IRQExi2NZaO#`XYakJ#)bFO8 z6si>64EoR&6i*aRI6rsDTrf?rv)6?Kn zRtjko-~8~@=FlAF^8Swp*Nl-h%34-XOS0~lY9e*?32WbNnGCO!dAD`}QJU zS1IrSiAHIEBz-ukqN7V_eRWDj{U`9s^HpR)5U10tr0Vb04^$GqHq6WTcYT)K65`EC z%6Q0){0@*^R@qno4LIo?7yhF4l?5+|{!5pjdGR5$e6K!-{RZt3>7Em5WzyOC^vG5D zdqgh$-oz(%#6gf^m@L16sWvCQLqUiYMJ*fbnC1I7aHmhvhUp0+pZn68$LPs((lQG$ z)AlbfnjqPG+R(DEGW-}9S@H3ak>aqYTV?#&b6y}|M&O40TF{4E(00)tR&HbRvzg%< zckB+oks&5L6L$`Eax*h*Lp$Qb*)PpvkW{uHohN1%#3zSWR%Byw6nc9j}+?p_8$6^A;_ z7s<)xYY9YT`Q_l}LyMt3?M;iEhSLd#lM7DUS~fVMwLR3jy=6&iDl$?;%Gk;aZiltV z1)8k4YXSB-SN@_&Jr^v_5SHj!kLdaGptnvdnL@ z6!>YZW^JW*cKHbrwLR|VBzO%ZCzP0hf*>i4)KMoT84t;YAFL8WEb3P^f8RY~B0d>M z9dG5r6)v1Faf}QZ=N&&|X?j(P!wqKiIO=Y=iWvA(f3qd|Fx-V)v!A*t0S^z_Wl@%`!-=u41(&WW^O(kIj$i;EJIp-6>(Qi(W> zKmg?L3uC~$2*+v8anyt0#gtqwdKwmb8s{qI)#&gAOt&~_I(mlobhUOkvJm*SSox{T z0}1e=lamGzLjt3|limu8kMJlh8FzLF-1&-< zPe#6j^0i)(jybFdrjI0k6G(5qOq1%$wz=Y{a#&r9Wq$1}<>%HgO4=o~-7N&Y3~0l5 zW;}ceJ$>g+Osu)-C*zLuJGOuC+H}~JF%uJR5^*GCNd7r|jM?pg`k;W%1+ylO+ECd> zz<}tJqth6382SFzT4>?6IbP(K_-NWeVyh1cKd zug{^#fc`#}G55_AOg9TM%?YK>1P=x+_rgt_n4qh@93S3b?n5#ot|EBuQWE2YoQGe zGff!oag-+*u~8BX+^THRw-y;IPr z)6HPMVzO~Gwo_NbVw5@4#$MOZqg0mgZJ2D}*|6{F=Ym+TqPhU(2s#5v#yfyf9`#3N zrftm^l*{7Gob;LIUcqJVrGtjc30!^%et&R5QG2@X$XGPg3P z#>UNVr-fy5o9C)6hzNx(xUy^rB#3kb>MHj9N=sIGVIrL5mwPLIUsUEWMc_`oP_t!P zVOrqM%=X0gPI>B*#-%JJPR9%NbBM?NMon^lZu zC>A6TCDePZ8&f0B_~Jra^aap>h;9F+8eCKH;GM?rF{SM^Sf>E%a-s;VCH#LEUSYshl zcK?;HRe@~1XD||PV1G-QR2?%lPQLIhx;l&N!rZ1?Nd{-_zBC$+=qH3s_FYnsUFkYu{Iw(=+i921Jj_ei4h!08a+X~0gc2@?u7xF zYWpv5qQ|Qwoq-`U7$eK1;sIy7dtoD0Jsxc)`kyKgyCYbGRQO z!Q3`Bmvo!g()oJTN6_rqoGj=a}-BbT+Q0B9h;iTP0q0SW0$`NW(Gk5 z=F+IvuTaSIDx`*}hrD77j&gY3l9{-O&O6SXJf`1#ei!=32^P?AjK8^!iqL+k>~>db zbD`~s?ci?i$=aEXwE*qypz&0WI4Ye@Z-Oeh>Y0?T3=t03GGw#0rpSy|VW$bdW-f8& z_R3judy@;zbpEK34J%GEOrZ>^7=h}JL{eKblh7MsWGf}9_2kDZ%MUj~O=M{4q@BE& z{_tBv+xmhBg%o<~ltP0dU7FD+K^HNJnqC5L$ z(dkf65>?H`5$W-Rt+GDHbj^_6vW!A$8>__n2d!ozH*rtKq8RZJ<87+>gvSA}M8O&j zp&ioGK`+zcFrwYfPSo&HaUA}b`|;`C{&;`DAYWhCdoM*{x^ZyuVP1h#c|Z$jqaN=* zncNede8Yk1Qww~#ALI@@I?6kmuZPo;vn7@IX=BvtXrL0?>Y3+Rgzr8+v@m2A6Zo7Q z&I;%!o5O0I9MiE&a$`Hl=^|BqQ`nOw9p?^Q=N(wlrO_{JzFPYJ%GUi7TW^`@6csew zwlVujE-?xnZOhQ6wIb+Kb+X%kf$_G6ET)ieafeK7Wq~my4u>hPr`Q%&!E!^V$%--< zd)~2}*(l)BxxK|<8o5w+_f=Tj!E~tN^&OxD=K5DwcDL#y4k)pU2tRr zEXw`>2t*0VYkY_8jBcHPl*^P}VGiKCwS=;Fvc9II`B%#im2VOe(JgXk@1)=5-MXWC zb7n*4YErG=mH5x5dY@_%$$GENTiXesTJIBsN!6nxgsWNTpW@7KoHbpk=}*X%;WX2> z>L?UB!nT^8)>IlA#!mz&&Ajq-+;7{jHMC!x>H-y z9PlHyFA3Xd!E3#-eT~uQqB;PU6rnH(EJ!O&+zUQ%S*&|?$y(I4;o1u@qmPP zY!7-nVa#HGXTzUwR~gJCgxekD1iow8 zhHLu-7vHWje6=i!kgIdv@P{BV(G26l-$%5<;pA#*Ibw~lkAl4K;X4%?NZaRqvdAmr zMkL6XlJ|YNUg>xQMvyPYPxGi_4r{(7D_%ZW3oeH&%Z&GP!tiRs$U=hlt5TNiPzl+z z3ghLGWurFQA~5{tkJI-ZDlaPGt2Tn!q3k9R-t0VqQZflzsnz_4bvY!G!dT)om`Ev& zn(Vgil0@RjRLSDFMpvH7d!cC2@l@fs`+Dp5+bb7Q*AaE^H7@Cm9uB?+ELvT`()_fg{q@lcjF!r=UcmsyM$D-JF4;Q4L_GG8#SUB{a(8jj6d^gpP0gT2+@|!cd~fI zbgcS;?|l^JhpHSCi%00Z=#i1_{ZieN2@C^7F0s$*pTArK`h*9371*LUdWB-Vmi~$K z6@Fou10-53J?6rM0ca5(Wd9qdQbIj?1^^murM zn&oAjiaOXgB$`|eND+-~FBMQlx_w0-^DlnVYR99SYa3B4ReORQbEnHaHGtDxv86o z(zc)*MOn^7Nu<+5^Oa&0XgaSvcc%UkO|(lCHI9wPFfERMhipumwSC$%^wtPH$_Z4J z$-B8_iW*j>QB`7EbnLm(7;&H|{7Ti0D-g`+0}WEXuVfX?re@dwGcUf~HAm}uP^^dM ze6+8H{`-3ZwIj+q1)!*w-8jJF|LS*4Q@y{xqI}UN&7UVx^8f62f!*Gw|cr!+AxrJ0?Xwa`g&zXZb#lVgpqdW@=1 zWI+Q0JKaIk^Cg)DOPUHJwJ5Mhov*x@iPEOz5$kMdK z9e0@@b6gy(m|pl*$Ua~9s@^k^mrIlK#v#Q9By200{%Rd!v@KhL4y~&`|5?8*aIobj z!Mi=p!4*=1%j{7;UnZHY{F0H;bm*bUaUd!2poHs6y}}0{_Q?oyUh+%Ii4;c9RP0{*e60G?OCuw#?{$sk#2jh5;xielqKSf$;c*Q$ zTMov1pAgDXX-(Hy%QcF2QEzEmX_v9l8LnXEwkbD}K32FVb0ZCNm=GI(Yh_`pm;oMn zU6D8jz~+vZ&+WJ!zhSl}g*9I5(Vy}o^6L!9?V9~toCsRuARP$}0bFo3Q7PUrEHp)_ z>4_7%ne$zT#nrgTWi@FMk4p4xW=_OBt0`)HLVSV#-Oa@hKT{7}Ibb7wRQo*fv{RLp z0oM2mKK73Lkk!`$gV}-r8}UjNs&JoLfDu$YWi^*)>6LA&hTjWQZn|r2s0<4*Va#N< zdhua$!~Ec4T35i{py6#N ztC(pOLuhp(+i)E}!^Binh~(NAm2DxywfYRdaZ4F~xs@wycG;8Rg`#Gx3qPT|ug=}o zb)SAGnZF-rDPdg>osUa)t>t=XW)-5T`R9V}cCF>C7sKkPN{KkwzCg=*EqhbI&j`mN zBLYAXo�F9=abf9yeh_gA>!IsA87v)bz&)-O6npeqcx@f>u@W#m0M3aD5r1i1YP( zU!;v!IGUiU@?GTRNXw6yt+$jCCxi|EgR-~ailbq-Hi1A05S&18cj-WIm*DO$!QFyu zfB?Z8cL{EdH0~ila1ZY8?mm_0dDoe9&Npk;%pa((hOVmn-uv3Sq5~i~ho8w@S@C3y zZr0<1I7cu&#WHPYY3i2F#0+_o704#+iXd(o4Mp<}P#OW%#d}cNn^#}$sLjmL=5CV@ zFOOJtmwM21if5URQSiCGfSabko^NyU1zzRjlbcA?nW6s%rBhA8++Jp~2Jn-~j%0GA zGq?J<=(754=u{{3M7$wv(jw@yj5aek`&5hX!jc?XfcDyr$Zx_xD)JK?9YhaD94s%w z`F%^KrIFi@oe5G&XDFK^#@vZrC3~e)@G^VFys&inyo-?9a$z1HTf*bsRTG$OuQYS$i*ZcN zQ#rSBaBOXfkuhY!1D~hN?K!tFHOIZ)qXkSlF@&%BMKDxu$U%%uo3v-EEq+$Ng4TSTWX9@aj;D#1(B-Wfx%HD~d*0QJz0bwimhqtRrUL_f zozIR9-_En#AD5l6bdLRbWcw7EJ;q3sr~U0sDR5hbEZ^ynL@v56W{=b|1)j0PD?er zJFej#>8q}y#5*Qzh{DyeMFR)H+MNPmEwFuiN%q`n_j^2bzGQ&bog@kIyGr9t|4AgG z^1;<=@g2o*VyJN<-eIjw*r<^k(VrT5U@md?lm|2p!7`~MzO*yCp4it^QL^u3_`JgpyFVMxDg!{?MtUnTP^P=;{#dY2e|6EcTg_zNn%c> zrp7lMWjyga&$IhVb^ZVm@D9`eApR-TwCIcbkv{q1`vg2B8S-FZ(Qv&yd_uG&mB>Dw zc-KLEsX5-SjMZAECEjvr-^%)%;?ZbXlUvhlH3^re0=Y-DcFk#jgV^- zR4+@+yp(VmLv%D9kVCR$@A}nlJNsP>Z7w|IwMwo`G9}n}q0}kldp#{Jo`;{yua+QWwHc zOnsi;;H0G=aU9bL)JxN?;z4T~h@nMzY-;Bloda&$^VzKQkd1zam0!!h{Ud_s9 z%5=_Qy}@P_z${x~_NUYBfratJ^E|lr=5rfVKr~*z6@^ifp<|^c+YOe8HBcQ2nZn|> z1jZtjTm!#EZJ%-`72Jda;)73#-`nA1MCwWA9HB^w?2{qxt{*ra<2`M#w&Gviu{sB#IiGohe2@VVm>nU2|RRRMBqY%r!z}P#{w5qTd0u_JN?8AeM7H+ zWeV_0k*4iB`_?&hP3q|w<;kUDB(KGTZHdT}3EQM0k9G^mUt4Q!5fC8v*jY+#8~Y5k zHpkoR6dCRL`pvMfFy?eN7e740stXQ7O`!@#+rv{Sy<;660#GeQ@7q@$nq-ah>~)SC`|4~46w`S6lJRP!BV#Jo zcS47VV1AO|5L{Jhpt2(xpJ%jCxTK}I>?9G zmQ<1uLEb3&g#)s{kzBf=WkRkh`y=9`<(Iq?%%j)U7O*fsr-74@It$nHDaS+T{QQ6g zu1iG9-zDlKugU4nD`Of^OW$mJ3i}l+PZe%FB6wdfn0uS7dF$vl+_%Dnmqu8^h#G2O@HUy?}-=*_)1@aAhRpZA) z0iF}SN|&k+G0kX0;rkh3L9@vh4p!ns_{+ChQ5bqlJLK`PNe)0Xp{m*Ji)x#~Eq_?FgfYPyXe z8#<}!^A;&D$mFq@(=^~GUI(CB4dA|KyAw_p{5-Kz4eW=1fi$KQN1(&1-mK^+t6*WOVbCpUmDXgkN1UQz~!9o4LyHSiz$m4_2tBm zuGn*;R9H7HsU5KP*hY1qidzu)4w)#CqvMYXsc$OU!KJKemlth`bR5}CTgr2KWeZIW zdg{lrfLtujxaY$ftGnHL0BD&T{52AD1MN`r#8x3hs=B#Avqzo_Ppz`tjAX1TQsst5Q883@J;nUHey| z^g*3nUPEOVmyG`)LB0f3vly$%XtxzRfARCsX!*%}p+Lz5oTB5Q%QnP2L|LpYZR*Qb z4V4f?8d(T}YPGw5ve9k96An0B%GJ$31o&INHD74QF~1brFD7afHGf$m7y%yFi|rO~ zgc9fSqc2i42hOzP0N){|z0Gi1Y>9d(Y7~ygyX&LMM5JLfM5!)rN`7hk>H2i>oxaw` zhJkmsak$;f6WRQgc9Q^Z_?!i(%l{glf8DkEs(Tfo-#@TZZ%7GfI5g|NuT z&6x1{*^hX)lqkfE>W2rq!Fb4~_lXA$Y;2yLf$?NR_G&SBa(*%L+}Eq*Agy%0mXK^+ z1N7F6bv8B&{iYF=X;H=m(sjc`JX;65M@Y~O$!TC6D@Pfkw^pWLw4js@KH(_JwAaJE zONCkho=l2-gZ)X{ml(YAHf$obhH^yEreU1IOMeezs}UqNd52JBuB=tC*@Hv-SmDrM zWF&j0tOo@g(dK^QAS1PjVAEBK@GYT+R|KaC490lw`%8M|B=)FQv^Luse_6Y}@2}DC zecSkW6qP~WS%eXpJ;c53|&@Q$_q_w^5J7@PAq@t z;dB+{F~F0*he+?Kme0(1f+#YjXtJ88lDPL=wjT=BQ4Hw7nw$=8PKGpaZsV42=!Cye zXjX`#Zy%sOKW}tTNH_+xiNSZyTb*5)>Giwf47wo&{?sSI^#n>CETDuBLK(LXTYELFMs@}_MY{L*r=rhGvZK3gUd$jZ z8&aHG`Q+$UqY0bg`v)tlR-+#(sceL=FV_(IdiF2y@JIxJ--zJepK4u4GLUfA+-62* z)T$L43_%^1A02^m}jQdJBE-AlM zoh2y*lnG*}-7LAJmzlD4mT55Y0&usxmoEyUF%xhHrX1^sn^In_3J2q2U(Xmg)WXoxg-*^p?L8_;|mt1&T>-~ni*m5 zfjjd_RTfY}(kyK^|Idsf>3OdB+>Cbt5(genFyTw%vyIWmQbD!*;9M{-}%;qrK|a)X&otzA>J-$s=j(%Elc!IQ?2?Ceh3yx6)Wq5(1a zSk~^s7p>8XyQADC1ZgcAYD7enE7Htv-rw8$?9=2;lug}4a8SLW)e~-TZ`8r>s;*gn z;ABQZ#V3I6Rauy=e$%*8e^+Eyoc>3~%`G?TRfL{b;r3$`G;v@L(WQD{%w=0=E~to6 zjXqm@m^O3NE3R?jxZ${^*6OiJ8)7P0R?M?mjMD?R6mgWd=>qa|+e%Y|B;hf^dw9Q$ z7a@Xh-ZbO!y>|0N*6rW9C#X#Ty@8m&2Qm zR#uZyLTPB*bZ(_r$Ze0j*vTdMvr_I4Nj_=X%cjZCc zE1!%suAg-5F<;JGIj@tRuVAz6(sWRVFPAmlRVSlH-7g)Tq5a8pfNG4LWl#s*9%R)J zBeEAtx!w_?=XjM#xaoPDBRk^?*bQwhp5Saa;6BBW4}Tqy07EZg6_AkAM_=m+Z+Bs2 zO<^2%#Zsl89%|gJ!LT#zr9J2ndZ_&5F_Brn$@yJD91V?~$cw_QZ?koV@D2;9{xDP2 zjgZIGY?9ou(~s+4E)zkY#iQ)G3yj2^D+*0b^&y9`K}Pk_VvlDoCF_iW{5|;e zZ=L$2pUO2kw7E9Sam?T&UM}YCGU;Zv)M&agh$I@VO8wO|rJ;)Q&@!GBZ+(xCD_ks^ zw{rT1EG&#t=}{{QhuI9t+}`4m_kWJgK9Ts_HhIWZ<=a|uC#xOzr#!kcb(&oXrF|H_ z31YVz(${Eus%o{CdI|?x9VSH?m8_JDt^ouq`wfa%XNtYn4)6JsQ+ecDxUIadMM_f}2TxoAQQw}nrm%)Z|T##8h=!pF2I+b1clz?JA-getROEchCvMd~L zr%S6={#j)N*HDEsF6IQJua&=Xdd>zU8C2-mPh*Mmv(4T_r(;!#NI~GZ-Lj#Nk>l%1 z`M%7%gQ@Gc~TYoA|hoqh0h2Jlc3k2qFTxC zLC1%0dBi0Ad5-=x3|J>m2PZ;Z96~j-SstfNigvyxgwx3+#A-FlG))YL`&(O**%U5s1(VpzMUe2-CB9`Mu5U}fipABLInW@7=;lIHf<|Ni^ zvY(h>!|B@uwYd^1^axKO$_*pAj6i6}rMt4!wZ1!)o zLJR6VZDg3pVB8gJU(4O5IP}`h7{iBg@%wk92rN@r*Qs8F(*MMzf*(!Joa#fa_yyg@ zl)xGYZ%S?5jdMg2ix(x>CfY{~WR<=~3=f!=y042%++&5+KVwzTj8YejN(Pq2LO(Mf z%Nl(Q=}UJldXe+HD{|*;drlFFTxrxGQV8#eDQma(<<=$x(l4LO7)EugzYS4MMrOfI ztW2dtA2n5oN|sGWh;nLWrKE{#-GTsBc3i4mssGFM_0o;|Nn+;pr=?94SZ;Ve1i>?| zxpx#a=Y7Mt%#Z!L5C1VlhEx!*k3cE@Pn4A1;A`!o>)ES#!-jTaoPXVri!JIwf{<2l z1={)hUy)1IebayMKKeEX-gWakY4%}e&9g%?L`dx7ge(3ttYG<1=R-u4XyYSuoDSTd z422$;fA9L`I}As7c51-7gX)RprB?8E6$S9VtXn!-(s||};m^`u_W|SDJjWL8Fwy2< z)(8u$U~_nOwp~mCXlGgXya$posc5*o4g?bEf|lU25eJLLsG;pKH?>Z^e0(1=c$Y@s#MFYRd*?nM|q z94w;!bm5jpzy|Q^Xd|M~6~G+V<-6&_eTz%w2p!NVOZ4N1y`*ExF&7J4#S4E^oBopImO z3>fN%eF_1Jvwb}(ZKs!GVr7ck6X+7yY)W3&+z{B)!F!{$F~37z)v~JJ<48yh>VM-u z^~`%2Rk5!?^1fY*G8`wC4Znyq5v`=w#%_v@%gjBsXV{NRMHS7<-L0YniYyBOn{ll~tvmt9>V6@Y3qhto<_z^ZqhR)UQ2>$oXeE7p(rLQaiEj0Lv#~R6n0?GAVi##BQ zQb3=eTrF{&g^&i4h>e;P?zY&3i}XS16?ax$LMl22;Np*nJb|*9e(R`o@ZdiBDB<@T zUDIY#&vLGEqojXV?CokJr(sk5`r%#1WOGFF9hQ>uEbXbZX(sIJj@B{P%iC?yDM6Ek zqquoYyJF6HXh8{0zMXI`dKqk$qb<$B2O}auXd(@8Um#%i!0p^m3zZX8`daZ@#e+%9 zfV>bhiz&(s#Ep$6&AmHk@F zYwuxX3RXrl9#+n@7Nxn_pj9+%-Hs7!FDK5Cy_y3(;f@jWpzx zE`>ea<1>Nt6i&+Ev*FbB0CbLtukZej(Io;CM1!pqF;cr^T3nLmdjYR{du^x6HB$|U z)NLv8anZJ0XUk_7cy>_w)A~3EG-QRlTo&9%Mm(voC7hY!1(HXfXi#|*+9G&x-c2g9 zzrZ%6bouSnFn9U)4}Te&LV*!4_AEbj&PYB~yYhPuVSsg{3f$FlZ=9{AO%(Eq(+{1P z_}HTz&zN|#el|GLWd(#JN|cA2KHK4O_I48SXPvFaex83(FUDN$-p*($e{$1SNeoXL zE3B}M&ed!G(c&StP$Qdapg(x3%`o-i>lF(B9prZHxVl*-_5N)sLT+tgMZ$iiIRTq zbiCzV;NxvF95N-_ghrlp5@A)c5ET5ZRyX8seI^=^;JH(Lp`Th4Qmjl1+3!Z7si*-p zO7_Kky0kQBG;!26=<8^V9MaaTxCpEpL*5F#)!af@&?WRgSZzZD)?vBf{Z5kORx+M@ zGAlDCVjQZX<#xeLMj(;fZwEO(kk$0;)VXk8uGIL*MZUc(b`=Vvs#S^$;rtdV_(r{CH!vR!YkCIN>{ zub#jE`5zy*6b+emhiUU7Jv#e+kTtg`n&FS)=WH3-RjL@OM_Q)#0y z@u(ImC4HM-$Us`&pxUXgK#ooXD?a0VqB#l>taOJ7vR(Q}V1-(oH<%G)s}P>ay82LqPW)ZqtI%F5Folg}-9WUTdwuW6f?yR9QPn`7WmwIA(>OUn zEIQEqcbr~}1*gjuII4z2cVU~ee~#!no6WWpL;7mxRAZc~AYM5T7;~9SjL#e>Sf610N~!8BBm6S#7Cc)mnVpaKNxV!w z>9_v7xnLCp3PuID`dUnGs||212E9mDu@%33diELgl9~cRcSr4Vknsx@9@V>8G(Svt zP{_LabJjCtl%-FBxPEa1WllVz4c*{*JNHm+ExJcjVck~Elbf$!fo0PL8KxjyB}jw> zxsP4aZS^(#c9^JNod4of1Rq;$z6SJ<}ve4Ba(#UHS6( z_yZVkQ;Jic;OCa&S05Wsil>JdV}QFvRQcC3X(4a== zvd+2HS6Ih8^Bhplk>MUz^k3#7YXs2%Z5Q?c4a%|?dzg@t+f7KsgGHF#Ec?Ol$9U;* zkkl{asEyZsF2nF;FbdY&KNj2JZ8a_UUiaZTEsEuQ-;!g~Rxo=A5i9S(17Vf7m%&J~ zJz--8fknq#64TtsXcXLJ9!II+ZWXz<57S_(@sK z(GYIlzRx-c+zYP~$REd{A_aocsSXIyk(TB$Bl4T)MKVEDlj-<-y3hOT5bju zFrAQq9sDbnSW`86L<|I!I@zg0#7&d{B|8Ym^eSVczM;-}(J`>CS8Txx72(PO=h3Gf zagi-J@f@@uJ5t%?b4poq170z5(c-LRArD&^1JOM)tG1bPg4Onq**98Zl^7N+ee#4c z^!0#Hmrp7AN4u_-!N@WTR9+()OVod;=)xPx4PVgTn%8R)OghX1;r7k~{rEt7$angy zRLHF8ZBP#g2WE4mqSFXKVG3=dsnLP7^@f4p-`y1TZ)pb2-_neTXft1jemIlRVP5+1 z&Cc#%TYN?Uz~du9Hm#&~+^i^|QleZ-W9LNKITa`+Rh*xqk~F3s5X6LZfo0jE-1Zdqu79Vye(>=v~tczh|Go#gU zLW1!$>X;3MKa;fgs_y;YI9=r^(qEj;6xC21S4q=XPYv@w`F%PJdatTx(IJ8;so_E5 z_yhzbFWx{ti{^Ukj;@?fvDV?1ID>=yP&NC%m;S3zQ>7$S52-k5&JrAp1q=bBp2I1= ziRi(b22I{uryFBO(+7JAhb9+ow{_VBspkr_$3;^b!ze;SIGFH+CFAUF)D;68p$|%4 zM4p@G5xCEr5MM7;3Ro-z zQ$Rd8DhCXT4(S-UIT!tt6ZD33AoO zZuXdnRE-8Kj7%W9Q1kOutqo5R>q_@2HB64w9Q}3J^0}SpOEoizH$uC*7K|)Y2bh#p&HpZ zF_Q!^|H0hgASz@$VjH{P;1d~~CJF2ol3WyK`vQ^++s`KQ)e+v0M~S0rG%!p?P)R$k zRumM%L?_ZsYm~wSBy^D-C`7|teEm4_TZCD}K-w^=oJv)u>c}Y_r8x+`j8LZPwJgG{ z6Z?}GP=6zg1O}&h?LEJmla@Tl>8wA*eE4L0%g6ax)Cua~bXg7q4A?ZNHunE)Lx}wE zZ3x-_XBz^?4$6PEA#8S(v7+cPE%1*yDmk8ph?&|!G*kICF2$Wt^S1%$bz;I}Hu6%UXt)*}byX(Ir za9!3gOhoDZyl>x!#@H5w0WPrwN|t!l$6jzhBJ$Xj7BUI+^&Z!IOVicaYSu8nzI!tp zUPVg!P=kZsyfenAH=Z)WqGC|iL&wYo)-eyAfjlkc=3#_XtC)?jqdYl?+Nz|hNU3`U zyGx8sozJ_R;_>lK8r?q|$RbNS(nUc4=Oz_viqfT_ZvJKHqk5?qP=h8DPC2!WX8yOJ z#4XB~ojh+2)V?~ia9*AR7#a9eNdoUXY~$2ktxmfChClzx#N$3~TYn04mh{|4+4LA} zGyO`i9jYE;JePuKMBoZgdPZP+!+-3NXb!QS!dJ8Ars8$%>BFwJi<`O(7X0apbRJHf zx-EOi1YAZ1*z!o-<@?0bl{r9H`ofG(gguf{zNPr_P-lBeYi7R>*&#i^tl! z?%Q1kKfha`c5yaHUp4R-CH^nlEPfo^ups7MMbm0=SkZ8mZ;(tg6kEaY*1*vwCW>0i zd(juy!>*h+)!zod?~;LTpYG+JjFmVLo2S}W%G3@tKraUw|8ma>E4y-1+R4N zz^B-el~b8fHFO__AGusn$nHcC59SIv`IkS=S#Pki51%QM3D1sQUrlBqH%W#A)`|VB zW99r&pcHo*Y2*jS>Q~y|JboS-l~@` zDk^$Qi2(erk3iWVCdm|x4K4*8L$hnTe;5GHDXbLpdena-;#BxKnHYc=F|cXFVJ<7H zeMYbdJ)g<+{2`pn_f#0s)P;fzPb(iaxZ%-B<#c(S0I~4s)Tx7X>F;Z0zMM6s*glLxqk4VFN5m`ybMVh@(sUlU`CNXAC`1I9$AT+2%n!Dx!2Yb3 zc|5nG3GB}p{vCIULcm1-&$>c|t>O8fZ6(DAa9@`XxI8-N_n&{Ox27jf&zrc>dYJ_2o z8i@K!Ibyicf2mI^0IFjv+w=oH>=nFMLteQSnBVzO3G7B$C{}fmtFW(@bDQw>xr_@{ zc9cyFuv8@p_Wb;l3@OelecL}B>ND{LfNxl4qfM3$>I&<=Qb=z2m4yG~uj(#+XZs#$ zfS)SUGw01kMq&+=mj-BOlBegoCLe!=1UrPsEiEOYpcI{ng>eb3=tFdw*^AoDKRhja z^kDj43&ezCaN6b16(G2M+XJ}C3$*?DQ+$CrANA*F2tSF?ttu%`=(mk`z5iLS=V~lA z;|x`;ld}K>^9_5YyXM5$%+^ac0rl1h(;Cy9)JldtU3iLfXAJ;c9<$tc`2c8ULT;*}Gl-E691i$F1pK>$FVW)q48pHsqXA!ECv`i1fj_ zNuqAgyG`ikITJCY;`1@d@!bgWHR-UF466@6R5S;~3&u%03W=uU5-uEfyjPuKTPf*5 zK~UMw%o}kx8zIP*$gC{|-d)i+(!NR}5}MbyH$J5Cdld>uO)f8M*-qz>1;qP@dWcdq z9@V}Ly@6`XSzujcy&wJtv>`mp@j6%Jc=2fGSg=XM)!;*_H!}lo@&f;`gI=}}o0GQ3 zoCztZKSg@}sLpp(%S!T(!y~#`5g-5zNg%Jg^esCJ{PbP+f`oA;P$;iS@ptX(R-<)+ z%da^c`VLh&pq_qcf`|JIJ-T=cns@a;)<#}LZ2bu#luw%JnJ*JpPH zHaB%_2fG#HK9f0Uz`2Em30-{%!z=gIYS5s@D|2-*AXGKKQa7kdI#&>TQdRfp2pyyk;u0L8O4tl)-T6{={S~P#_ zAN>?4&ED>Lvp^$=|Vf5+>4$s!PT z%$HQ{qv{OqP>pZqR78r->~D3I6ml+hzqr3d;d9z<1MW$qwHJ=A!#B}wL*OZsYL8mV;+KUdCnI&Uo&eFrmK?kZXAvqD3qI56 z50h`f>+Psz70?res~}-jQJvf8k3R0%HPC|@Xv2{qM0ukfbjb)9nD7p?lpN`tb&nb@ zhm3X@X@nGt4Y!#x@bqWscnAo>CA=9lgC`Il@%PMb8 zBT;tS&w%{MRIRb+V>Y8iIFuEh5mmF2*B^p~!Pz=IYWZiJgtT~sfz*`p+z14hDYi3c zUV^e0u_VW}eC-ZOiY?F@t7dxlUE(FT_#?vP z1g84WMt%Sp6odJ~9H3D|!2?IgN7s?hiD1gC^|xJ4ZZ*uCLxE~LBQSbp8xY@r?9PUY z`<2%Pv1^5I^ah$D^joJ{BYnb>;PJt|^qAP!{e$&hEwC+62a$|eLAwrK<*R)WD7K^r z@9CT%s5)ZwEp9yKt*8eJFugTlH>A$x}e>f6ukibpUHM z9=#iDUG5L%V61z9q@@bL@g368Tcd}y@&5&-^y9NIa{xb57{14i#h$=4D>B!tU4UtO z;P%z)qvX-u_*=t<09Cx*m~`I;m1!{DnV5&R5$YxzD)oW^{x8ms~IU&qeFJ1 z=q@8e{JjIQc9~omrrW7|pUeCa77g5MQpkV|Ezj8ws>S~A{!9A* z>c2#w_-mlj-fC&|8)TYV0WevBTYoq*UC6V9UxeJk=SxJ z-|{^7j!%Yg_n=aFHa603nvV zeUM=2=)F5D8@DTprBN4LQ`T@x-ei5fN^0R`G3uY(JN`1(7UkSDCO6|qmh!#AFVGALbCBAi4)_#{SXk{UfAH8<*EFNC<94x%-voM#Phaz|nGL^jyNB zB9AFS6iA`Y!%69~8D4trDZg zF-l+EOj8TRtxGdhLdst-P1{nz#OA>#tgq!eF63ECN9DT?+&Ov& zJB$)Ttwyp#L2PQ;F8?hSt{!|{gajqu8MREuxPQJ6myooZvp52o@bWAzeBsQwCV*5} z_Yft)yzy(>8DGazoe2a3)uvFyjb!;aYZ#yVkrZJPF!jzz+AywxU^C=>hZAIWFhl%X zl%DM!^sXllABeohFdWthgrnPSewUP@5L@x{?B1 z*`y}D09DLsW^!z&R|zBzzHXm4Y1vd?5XOCwP*k^9v>&B2{*mbTNi5q)3I-J}MG;^& z1IV@~peuzGly+0Y2fGNMXF7CaECG8V$Gx#jzdQnZT{O*TX_rb>=Bb)UN^}X2gDjgx z;s#vTcril$#TUc78m@uYclnwum0OC8iaH^a!NpMZ0hb_=l#%Vt+~a4NTx zr&P&#gEU1vSNq^yP5O%%eLwWLOoACHH`i)U)xAG1MG;(s_ZmaHOJ~_d6n7+L(k2Ub+58e~O_^`YbFu$zAk-^kO&5Z$ax|K4Rq|Z~c9Vr?`afjim2+H{ zoNs&?Jq?t0DOz!1b@%8DT+J_W@+1PKP(?3iL9gC|w94vT8)ctlTFE>cFaNZSx&xDz zOt#yNUjgg?)4sW>bJWBTB&W)iOqOl!9eNfhEq9YR&*-unondW|-A9_bnAJ?{IgDgb zwcTJ|>@90(0Or^EvNrMu0{C3N5{d>omICpp<`2+~o1cE6Ob@u&D7l_pv>G|*b;6m1 z$e}ROW+RJ8N&si9cOvvrVFlO$J1u%k1u{HDoNsDgNq3l`dfETGa0axJNzZw4I9*B@ zRB8CBg(7c=d5Rb}CK60tBLW}4Tv5MrZqRCkHFb$71|6zQ`n^zd-`@bd|N6NgYH#hY zr+W20Hf;d#U7Lg$A3M(#qmo4v! zL0VsI43_-${S7`e;osLhkBAvm<+!<{2y%tv$q6p|Tb=-K=`yl&eG&9C8$1o%?7WG+ zu{Z%%Vs-PY(?iW)CJ{sBLrV8ssS7V)LACdyo#Xw-Z=gvNf2DyXLPjA<@HvQpl(sBNJ9HUWHySgI8i0AFj@s zgA#t$6Se&qGLatclZRMZ#=wbRQj;C@r+JP&CtNpItA+LGG@W9GYITu&sRJ@q2J zNh!7jG&=ilIeh@-@gM3+pe5AaC* z;=Mrx^HUlhQ0)|+T^}E?PTy$lOH0Gi(|DG+U zxD`9p{tLm+FiEy5IWSiO_-vk(2F@@ZCwA@x&f2kWZx6A(H}gGwj?&KK&C#INk#W@j zAW@|2elRfJN-npQJs80BNJZgz>j?fNvuxxrBXyTAD-i#8Nn3-_(n#KisWjOTK-bkOI|JCk-r9hc#UE|pmKg<|b?#OIIq zG@MuIUcFKu}t#1m7p$5*kw_40q5$o*t%2GXj8?jTgy5CTjI-}t^ z?y)uz`TY7Y#nBm*YZv5+ccVWZK}G#M_ehZ+aS@GFpWEBl)?D)OSfBgWtnJcJm>*pE zIp%WFo#=%xBvbpVLyo^V;^|C1SSTsZ?bTOKRVmlIsj6N>=NWf!AlI9+Ftf3_8zS@} z7zGcwll6#Hzra9v3;%%6hQuf|qnD`Ncr&c;v+&5a4sjW^<6~NGF132;SSe?c1ui$s zCC0NNlbwE_3y`Kqk6D&7CS%Bv zyuy~os~3;MmYJfF>B#)zS3QsSp=>Yd z;*jMk=?nB&%pt4BIjO{iP1p*&x9!uei8r^W^YGe-{A--dI6W+ip%nk;oL85V`-Y*k z!SaQ=tVZ4BNK0_+P#mir&ZfQ6zDUTfRFet9O61f)nVrgm zX|_F7RRsamjt>yyj06M;I#ZO0b{cZ zFYr<6aw+0O-~)+Zs&Yr+Me&a<2|uUMZwSESYju>T_z%02qKDU%Od6{963pFk$0sHSr}U1M!~y5xr?QyNz+6#HJ<~y>+0J zug+~_bZ#~}$O>P_>G+RKSv?IYUp)Rq-&CaxtovftY2+XFE=?20do@wbIMM%vpkfFi z$Ml2jWlwbFKc=FTQFFQ14gnHGqb;&`mH>EZG1SdrszsWOtIciV{mO1^o5jWR%RqKa zoWrKTX~{Qa0}bZUjQZ~6rz0$omaHcv>)EsHKIQ>Ev;MFG2-xiZkwUS_8bYC24!S{d zb_Y#sp2=w^JYCz7m{91ilLGQhsK47MPf2>BXucVH6{yiXVI*%jLb+9RxFO;x_dL4w8>nr$ zcJ!o8OrJss0;-u6^{xTbL|}pTULD$O2K}G%OzA}+6^B^cBk5hCJ;$R;wv{iC`qHqy zQIt-;8>T<7_W*JbpcD@upWj=*^Z^~Ewy{lXITeqJg)x_(a|uwX`!~|x&ubCerfu8^ zSY)gt*zAoWm_=7LPgOIh8`|H(KF_Aro8Q&$4SRIvA09|%keHnYBIK1#=Dj2K=|;1e~7qN^n@ahP$QUm!*p_t2_HA#fE0xNuek_TS_XbZ$i#wz z-&Za9%4fea9w|xxTTvphGQ_qj-|Hfe59ks)K3aNk2MwZN#bLQTAGsS;O^+1~#Eb%{ z5sjhG3mLBn%`s31$b8?(21+TP&1gMIk#iLD;cN~xd{;Jmyf&eFBe>F!GR@#Szx0s! zyOk_V{!e^l8X)Q09|_imPVr*RSdVVyQD}WZIxnere-BFOb}=kz!vaEe|ITgYb4kz( zM_wSBckRCgbVj$6B}WTzH*U8BXUV7%rypz+tbRKW<#g8&u)?xRuX$?VC6(CN{ff`?PX9eRE$jD#KwlJDBPo zCj`c?J7r>q$Oah&pq~lb!ZhX~H3?OJnIuC1J(d4pIY^T20Vwn~zwbr{X1JG$-nL)5iTQSs4jAFC?vwtsozwfSE^}oDm2<8hpI)l#ssa`QklfSZblyVf z`zYQ(FfJ98w2N9h{)V362NLR$1pO5SSzmZw=G)HemMl)9xO*(Rd%jo)+b?^Uhq9(S z?eLdvLrd@f1Y6$GLJ%Cj!ozqbY;ISt^hmlj?`VX8;9&~BW&X3G zSVzM^pU=9Am0U9P0s7bs*9M!u{q2+|5SDJ3VuC$~I^NVl*S|uLQ8u>6x^#6Bdtf)+ zQML`XTIv6KD@b0^=gx*-QQyloLjIxLGgnO%KBb0~F>+(6fN#LoNK(>jqD;G+pMq#J z1EQ;_!W&gV)JN`}?CZeGiDePue((P<;`SdDz4*ULDMs3NV8ilv zQ3{fXIaK1_5+8e{Ff6;sgK7tuvQ)VvB8G#bnBGZ=agjo-DbLvFoUi$FwOA}FsOg6O zuiD-+s*Y~k79|jZLjnZX;O_1g+}+*XT@yUW!rk57CAbE64Z+>rZjo>AbN9LLo!8!v z_tu}aU{$MDYu2ne$LOPv-ZiH?KQllV6HSDaWOlZZaJ9d-dl`C@C%Yi|&@OxTF4T4U z-q2104nRk4;Ht&l=;g&ga&1d1?V}k8S#<@_@BKBrYg%gmrMnZhw&L@DXKpb1O=lMl z#zYKS><`RbgAQRef#mlorXfBvHreV3y#qQAj`aXhSbL(3#knyp8a&^JiMKwfxM5zh zv)*gPm*biv^y&I1KZ4nF6b0;T!;NZOp{Km$@3NKuhDgv@VER)TsQ>W&Z@#xr^!`{P z;b!9N!y|hm2jqc8+2n*7DN*b#iJTa@ST4SNd_q^n{?aZO`6M;aa}NQYN~}A$gS_9K z2`CVltp^F!1qAFka9(_Zy`Gy|huzZw>Q7;xPc~&Rq4|xo#;*!Pa7HS^C|4_H`4fc+}a&Ei4854)~9~j z$Z4G$$r;7_6Gt!pufvJXY%>Tko%fjzy=yMAZKqQeLp>pmYaZWP+|!Bcv9k4bKr~-F zgpF6Pogoy7=-eMw$BH!MUv4TyXh|oZ0oMn_UwAm&${9yh(JhQ@gQK~*)OD=~fe0GIYPJQIW>p(6~^pJjNs%urcl$gMo<`#7-;M z7aqm^Il7zw2uHV3ObVl|IV823a!HcaE9W6WP|t^k%JQYKF2(AjLTe>r?>1eT>GfdoU71Dn4xoT&XVzJ_4#N^svy8YCuaOak=|fY<$4mKbp5uYliu zi#(Xv2z}wMq8ak$^q6ET=% z{yl^qPL#ZL87Kk6jOE`JhUQB50nCj$H70gDSy;i~-3y9q8etZMz;6^Y-MIGv8N z4wbAU;2mBUI;(E7ltt1Ddsrse>)YKMfPVU<%{VD0_)(2naS$#dA96e(j~^Bx7}^0o zx}2XCdhv@3ycw>jy>dN>NS(U-q%S}sJV=N&vB`(A-IgaAU_=_%0#+CcIG0i`njVY* zB{GRd5lb84EE9K0#HD3t-1eugo@LO@<7WOljzZrLPTP{?QeLed_OijlG8kVW2%_R% zltEu$kd-m^KN}cZ!8fGrCj)(gcg1oqgqBZFQSEVA?L4WQ_d!+7L##d+GRitV(0rRGZW*WLe2%L5pEE)7NmjzJr8D_ zoIwWu2I$U(G72T5VyP*4;(|#H@K&9u>4{dU%Z~SfUb;`lnY8$GtwgwIL$87 z_u@=Y_ZJ4Nq34szPfus@)McU;yR8AG0748#j)}(%F9vH#&SkD`hYp>p=piQ7ZRr02 z;_8)|UI{Fm8La-j(%jdd?aQ#eZSRH>i=$N!FGaHI-*b0RZ!Oo9eE=G=`K13SAUg%t zuLHzlvH*boG%%{e`*g>^hV!ttvJJ$6R>K*e){@yr}IIpNXazpBz&{F(Vp}&Se%Rd*J*pi4qloHGlPoyE&X`GIW zkSlx^8M;nYDm&811<7RJ#!?Td|9g^f%c0-{0IM`J-x7WRv%_!+^Ly((d%Ea0bP_}U z+hWP&qh4>|k(q>0_MrBUmlcoXo0k>7Yh)D1r`dd23_8>RB_{s$kX|%c7^p=^`3t`} zYlt7%p94F#fHrl7hn0kUtd;r-P_F^#GYx{AY zyA;g-R+HVC zZS}I10{)Lgn?uxZCBFc7yU;;shCFW-JG7Dh@>+~&T8C91-3!>A$wO*OjEg>;Uq$Z) z2qV5ySM2BPa~mhaQf^_8YiyAlH1l$#yyu$Z0^yRKmBNcek55N#=Y-((vy$9hvm($k z53Pt301<#WV)9NK|2Ukwqskaon&h}47&)W;td|cSr?5*Hyk$2!I3z)#QfoRm(XMm{ zXA&ZUdDfE&qP|FQ1BoEdeN^^m;TA?&!4!xy=uQpZx-V0v3jF%D1WE(psKk> zBGNP;)O|MdO5}#tW!}~~wOvsEzWCOYHJl2_^aEx@Q`=va6X#BhN7#LS;A9p>0RroV zhBb#msZA=yTfLcbl;tWwJDB0OM5+We6Q*A{VP+`L=yQ20AXspzFn%k z=~)l!`631veQza8CEH~M5cJ1P{!=y-KkP|JN8R+-O{(a*i6I(rQYyR2tqMYN_h$&% z{_r}2uQ{!JDU-e&fG#z6QtrVfzB6e54|Iav^A|d~0Fpk4Oo^i3#>xXu8zzh1WK;kN zW$f4KEL;tz@~Y?7(=OiqRiVC}L~y|^kh2#4nuT|oSwAX?o4+}B3P+b>J*jj!>;PzW zj{w6D;LHJCL}OZ)K)B(}xq3lSxeYlKuNJjBKn0*HH_|6;C7^D&m^`IIK9}M3=xmw# znL@#n^MIkL&QfDDN)gx>aeaYz5P0bj=e3{Qw4P-S_+ZgxGUiCP1jMuIS$Wm_{ z$fAa=Q)xIZ$?%9oT1JsE+=e~3S<{^)TGDMcl8~_3^k%6)h933Rme{UHt^=|#Hmj5P zJh2pz3MH(+Rw$L_JizkiOB;@5V;zWMf;fZku zY3xLvE8}%mdlxsqkK6~h)Nk>)W7G%2)>8ISYAZL9e2LT9ZR2B-f2C_o*8Z3+emZ?F z#&#L5-1O{e!=A6!7=W9vb4=9edp4nSIp4dEoBh?m#HgIx8F$Z!9C66r$yNpccwTqM z&%LdTP?qXQ*KM~{7Xd?bma#puL%w|-n7Y{t?xmFre}Rb1-YB5PrPH+G6JnwlGX$JlAzwA zGixLXNOKIIhHLsiA4OQfWy2x!aUeuS+9r=y5NS#`Mdgp!ZxsEoF%n(A#?!aof-Ra~ zPp97tf`LT~RSWa;{_2{pu$7?6O?eJgkxk1gXPPPs9yLLYw>nw1YgBXMBTjQ_8iN*_DxL zwS(6PK#N0ku66rc((nH#QB?YC!Oiq3SpKk3^Y7FElNekmIN|fV&73BfMMQ;^?~ll+ z@39-gt@s~pc`n8Ph-Vr7rF>Dt?3ywD4%pQZE8|4?iG}o@VZ*{WNJ%&R1pgR1o)ItI z>eP~8;#vn;A$`KmBiKU^wrcpZ;4y_gm6vs9`|G60@6AwGj?~kIZp@%no+45w8lRGo zZK!w*@V$ecs_&0(nIlqVFOn+XIYN-d>JBxC)fgI+X`(LS^q!S0Buf=8I!RTT)a-ag z+af*hupGs86;Nt!#lm_&a$8sjQdDib`p~i&;H^mIhEAE*iKe=vU!!8v;r>eqA%ga^R~#>; zrO%{(YlYbmk~oK~^nl8RA@0&(g^>Ba(@%cT)5D_*#Y`lZJuTBo!%M`Aj=uD93v9Hg z7z{Nb$!|!My!U@Ukz*Lw#Sf)x{Nf^~EbIztetfTP7+4qY@n!DlyA`TcG&q5#Y+ieK zcrM+$Rr@PF+Na2AGc#>MEJVOkj*)@~Jmw3GhP=V6SwWLn=_oP*bNa3tzqsx04}=(B zqeF3;(?JMNTb_N~{XAMH8G>hUy^n9*faHDeyPNfTevnh55nB%D;{9MZ`eF^$qMWz+ z?jjg+dh7LuFKr=`$g={tnK}}MLV%?Tn1s=-qZ^FSCK%S}1a@T&2VztiBldUH$;#w? z1IJIo39v?-Iqx4;>nB}N!wP=In157wvp3BW267=YXfXr7FJ`WC7FAw;Wp&RGO~{h4 z79z-+Ur5NoF1Gc*p)U9yg0v!W#th`IAQ@Ln-~m@FFmlio5dj(+TwMatW(J{cS&aeS zgdA@55wvC{Dcq9{o)wJJ-YtW-;CTo#Ogd`%VtzL;Cm8-WbrX|_g3bR5brjPaU?4#8 z(DnJ8dM7=~S^>-|7bI==S}q!Cv{c(n?$I}qCy46ww}~t)?+QAk0ga&gM^TvuxViBV zC6)JSYV{4-mR!~l@)inLq!_vND@0fu5yFND#Rv_~U#Xus_)j0(1ehJCJ z`LKvO#q$^!kBRmwWQBvw0TH1 zL)Jd;#6Z>E56EI0l_@%CkYOsR6EY=oAE!2igYD{lW5iw3$dyr0Gvc(NHQ)s`aNfK} zeJ-Iox%Dk^tecD}FKU4au^fJT(EzcTFG^DZS%XAunssMnnZy4wi=G<&PjM0T(T~l3+EN-$qdzl; z_&og8^uJwA8}aJ{ij9*=DySf$&+yMDVgtzKR@HPjb0QZFb^BR6@g;tTouUx=Soc>q?J@dLBohlx46L4LO7tYr ztYp6K1(lF!18C>p8lP6J*ENu-iqs+K1iW+;L&mt>)1xy!?tZK(+VqQQY!eZ&YT{uowT5^>y=8TwB44ak^YT&f{{vc zM$@5v3`VgUoFU-{Ba*zGln$Vwh*kh+q=GqdSiQ z1vM}Z`-J{Y82n|Ms^WJNL|%@^FrCLP-_~77_?JHc&l?z+$lrw+SX9m4yr_W}D#F`B z2|OJ+*>4a0-w$tsVSv!nJ74=futRJ1c?H04(FoY)m?;ow%Ri6WHwg@&onf-t{w`;VYBK69HOa^ zjpDaohIfFtWof2HGu3LXY+T)emsJ39UW?c9Mpk5wVL6!Cm&@3Znr5ZgjPBv)Adgtr_U~_rVS~s@pNOL&WjvbG07P8vRoBOI0Zl~^fJE;oyhq4 zWY7~8x>xeuetlbp zm1!&siQ}6NK1ckz`hcA^T@j%07=kyAPdiYP?6liLtg6wN)>KxvsrS zBiS~LMOo0WZ@Q{p-J#{~-gO8~oih{qCX+VE*{)n%!f8Vr)2WTJ{aKEC0DAg*Tq>RX z1w9|1>?Bz#R z<=JAbOiehboz2%^*rsKx;^0))kPO+5`p&u$1sEFypXGeW_?P9#xSuL-1t*p)1UfZ( zVZ4r6AG^-TTh-^!1E$4ZLGTU?=uv@(oX$=rQODG@g!7gtZ=}>)+$mO%Z}%QSoK?2I z`mx0rm_S>uD*A{lxcgyC@_IYR-S)hLPUFaZbvox25>H)9dLCeOeSWO@D2l#`&Sme| zG`^7WuC12@k58_8b5MrY@|7M6h2+Rk(MQ1l3H05oq-S>NhlQf`?1LSzWc~qT)vq;# zHVmLGSyA+L!Qf>^<>lpfxQpgkI|}tH)7^N@;HP%WXsG(N$C`)n)Y0X~1J{v^B}Q7g z1)iVvYe;NA7SY1PmTK}gstV0;CazPH8Ae_yf+V~36oKJDe`-KSdTOA$X~d=Qmj;Bf zt%_J5M0^qGGzs{OfZ|d~y;(Vz-QW|^G3r#qfq(|_;!X8W|HTTbg=v4=_2|dv2yTa3 z5jfw@1l)8QI@>x}IK94qJCZLYW8gaybuSn%0t|A1Fdpmd5k2U04L zt{tVv+Ng%{W&XRWW$N((`s1@TZJiaiN1(Tic<9|ifbJ=#^_TrmH6;!Wwc7veJ}J=+ zzoKv%GmmF{te5(6Kw%*49F5Msfy$0JjPzh0s!I~@venbq$|1PfAv)7}J|?;ym*ID! zf$J`p*j|1A9t6U?hq{dstmY=fQjV%&GYUuK)g4o)3C?)3*WEH zsJ-qUnvy=rp97J=Ds;E;QKgyNa?0Y8lw{y(X|^#h$#6q{(>=UadsYWxUs<7sE=^GA zz72WnDZi);BB<#>8@o8)Y!%yj;!n-A^f4`+n3-R!XwtQ;K|Iu~^V3c%Lv}E2Ja_<;U$6lqm&$nE`Y%+z38hsyy zApkVbDlYTJr79!(YDVa#fLp4se>I<(R$i*^Whb^=+Cb4~CM_=P9$(zrXZFGUbpn7W91g5*d zB$I9w;d-WD6W$`yH&TCMf8A5dLeiekuYmvT;j zqME0q{t0}q9uC;gUrKz2%6t>7O1bdp;B~1-E8pkq^9Um4t3UTwk!FP{=5XLrbgq>h zLA<42B0+y0K=iWzahiEVpe|+z$(zcStQQ5@$qM}T#m~IbdN-U-%ZCpGq~jG+?8qs< z?>ArY5-%^J6mNB%mhTva8w7|g+8aG4DrpA2cB`-FBaGXpU0!c=L-wzFmQ#1sMxQza zc1>PrS-2sg{MTI`yKP&afB&8BCvPR&x81NWSsYMWeN&_SpEpQClD8wk<-g!^r8b+pTKv(5pc^?a z&fA}@mn!{Q(FQLo2tEe{3_9e2G4ncYe1}%jhGGHZb&sZpkx_u~t>_*1Q{Jw0Pimhn`C|P&- zLOUgD-O^`{n`u`PWGa1{WG&7KO8j*{q+Ie{_mPE#j^KIUaAoy;ablw28hgfe>Ly;@ zG-iQR;>Gph=iJuk6kZme=g;Pmi>vFp7A7xZq&0McM*T+_*Ta|DQ^DrQH&1cCwz2gi zOHK%ye5sq)nMc6SB5K5NKh)Wwq3$m~TD7C*prmfh-bTxXV)m^AH66~BSAUfM9USB_+`_X2S%B%bJ!aBZwWYEa{>|>*gF9&@b?{eAo2%Joc zYM9mKJ16|v%G(3{NiQ9fr^tPx3|kuSoq}?Yj?QP=bj<|>L^-j)gNOkV+jEXO9Z&1D z1Icg+6|x;!BSL9sKKlRSYt{d5OY10QCS2b%$$4{>9B9*uR26cZtUIn7ZDNCm96hg? zaj(5oLYAC6UZB`eo4o6Spz|yx6dppaKX0;r(zQ+#z4N}~BDiiL#*}%yrt!tl?PGH0 zaqMaOf}v^DFRQWF;@A4f)moHI7prkMx^M7K z5Z>e2ao}$47p0!!KE8}m0CiYIC#;~xUh|&mXVf;eTJ_aiuV9Jgw1}xc!c<6MNx2?LJ?-LwgZEG zi;q!L+fhWxWL9pRMe(#@Ug*j-SL}9HyvveYCr3JnDtiKK1KP$$aH)wJzz-H4lfw%u zF9TrQ&k?xzTIgTd&<4WoJzo)z7-~;1msw8|O}0e3Be4B>T9pk0Wh&b&($|bc*X+mG zR=-iHRw(4|`pumTG22PsdAhr;>JxFP+EcAx*Jr%ABH~7DOP1!K`M%grSJb-=37?24 z^@qc~*m^jfzFObw3z}Xi8NYfw7x=99#Bnt%mk95$cvYBc6E3EaE%+Ba@0}mmiia7q zH|YsXcwKJjPZiA9+M8CyW@$=b_-NV6+=!7@c^@3x`sU7Waz$Zh@>=4FBfX@v&8I1C z1zDxdwkAX!tAu{;Yhp6R!%VHWJUP&KzSlvxwm-k!Kk~GP`M@SyBTi0N>ch}c`Rg8# zvZIWrg1W`TAT1y!D-}K;OTcGUxjXVj(R}dqbU)`~XR@71Th{hjyBP7rwFIHV6sn+9FA|x(uC+t*(8^7LRKSF{VRi^8*7J?Fwqo z*YPYEB8^yM2ScAvv(47aD5afGF2NT^FdWIMjnB?~joKldJP;q&=Q~mz?AN}BI?_qu zt%r^?ecDv4VN0EZtg;?z5Ic(MHbki;k zd+?lYE|E?ZljlO1V(VC~5_nF4;59DyHUhpDB0tFPM{Z_aiyD#*GyVoa0PH?~210@@KlOY|&&1A<5L>(+3Q(y`Z9IePD_Ggy zk8_BAx#T3}`YML-i^h{;OTF9nvVnKLm56SLi_x_p3N^lA|N5xw7nFnb5$HG;s^el{ zvCnwWbY$|+D??19te1D!@vH5r%VX zAMY~L6%OvGca2xlTD)CGBIt+BWM3^_PM5WQ!KZcHPe*iY7BfV>Bt6vtVA&tRYUy zRehb%>-&NEGs)8|llj9o&CwA^T3Hoo7mNd(PdQlNs_MH-bQqHKEvEt6b!<@^d)H-9 zl<6JIAE6oML0TdFmf-TLQ+0=IaQx9GLal>?L_S__-Z{EGT6zwV2isP zi`k1FH*Lre5QVi1NDB(s8~k7x*SG~YojmYL3Ma!YiPF$WBRD|DC>D6|ZKkcou$HIW z=k-WwMM zu%5u6H`}=VPEEsPZRT5>7CrPX-h$zvO(yDl-AGzc>rhTea!3`Y_bA;&uNrIJ0ONmy z!Lu$u8uGJoG1T5>(T^DkBpckGt59T!+C++paC^7wvWotJ&Pa+QE$fKL{d6W$5s^{; zi$Y4OHqVs#O9IAjt(%plrG?=)!+p{DMv00Bhhl`j^}tLv4Qz(|`OTK#K|@qMM0*E3 zwHjB;lW*&%rhTNL(x&XbSr3y3+zyO5bvRmjSvhRCVm@i}epIPskx4Jl*2ZLnA1*3z z>J8skKEEWxp###m#%nxK3+mil-!E5=2IAmg{bSAbu~m~dQT-ZE?Bamo|0=TI;^x$ zp6k9Htw$R@VLS|EvsR=Lza7XvRInB;@p|gtEe=B=;fIY-8O2PEwQPV9`~|M|n6=gl z1t&W^bWxtNR^2x6AB97$Gil-oUGXkaZk&SgEvVmVY<-dB=0fn99Xx@%>1B}sJ+~Rt z#;jUGZ?|FgY-_Gsp%a_eZpI^KrJ1d_s;5mf4 z`b6r#{^Tkw^7A_bYpIA$^}5u4X}5f?Y0u=;)Qr+@k-3FM`}8-?;EUL-B9H#;y7E{K zb8z&!=`OB75-G83PU~U$Tkg9R~C9nATyi_MogI@CjNV=MP@0Y&LGPApcEBA4xelkhu z!1SJbt^!q#ZQr=X)UDVbB~997Z|@u;S^vJxizHQ$FbK-2)n)(f$>q;?`F>bohSY|; z?xsDLiR`S9)C{WE`?%<<){lA64~*8`X8+hpbbYSNRwzSnG&M8%PQi4Co_9Z+rd(L< zf${>F72F(O-ke75qa=+5Lfy_(zGUv#Ata&`L7M|nIm>cPC5o&$P8HS89JZ zO8`1#wJONWgu1Y%Y4AvGFJLHeMm61o}okbqq#HlbiN# zi&&JqG0~DTy^;k21jxxxUo0Hz(Xz_mqks-pj+PU$774ieD%laG(JnaoVNptVxeQ$F zBbJmBw(sF>Nx^8ywI``4t$sYXd{x#IC5c5TOZat83m(LW|R{pwEtH=Z{(sB`HmdHnHtoWV$GhJ#!+h=EWB^`T@ zSqN?phOne>SUvWpNvKiqyJ()6>1sHq+8!cGcwB_u*syW(>?ieS!w>MEJWe4iu|MT> z7HygxH8p1waB2(~Qzwq}-j*czNR>-?XdHSzwxO+~=jEUzgtz%3()FEMS4;4TYJBRD zY=LPf@sRrwF&TA4)eH4|q$B3O*{s@L%n*Z<(b}1=#ys$V^!rU5$>{7(2Ok>%^_Yd+ zJnfxkMpye3bq!NL%vEO#cb^ti;xDRvvkB;&;H^m~Vjjcgc`5xh3|TgCITcKHYtqiN zKCiP#tmq8mS$nnna4{Q?gf(fGvQq@gblZ`wiyT8qWa%H!G}-FY{T$liVnTkI-1M7W zohD|&ZsV?cz=r8)P4JNIyZ=~jsQQp}+d1m$+h~HV%BYIN#EJH=5cWVdSbwiJ7h^`W zbM{JzwRe}ErFj{nK{+qIlGz5a{i&vk!5OyN*deAZk7HGdZ?BIbFALETJa7MbhTxT? zaNm6;e&Xfuxg8fk$Qv9Ld+Kj51Lp@h)5&+M3#e+<-j`doQz3TaHh_z6eG5Wj)x;Fm zA#9PCo@DK?isRZZVgD0*d38Og8uI5=m;HUi84;DBc-%dV=a)c&23QE(@!;NZ^YsZ+ zahnwoU!e~v%5x&_4;r@Q!a5{b!@iC7PWX&nLt$&GXos)T=>>`LNfaA)C#Gb&jV`ql z(Hyb@UAca-B7B*!Y~;@?u5dDS#L4#O8kthqL)$rJU#oTkjIT)Iu;O3Xa}9&+|AJ&~ zHZ2ko{NJnCgG`uFiFXeUoFy>GD#~)^G*pw4ROqyXKdWeY98jEaUHO-f)aFq$FhtM0 z{{j14+;rfQI-S}X=-k`q0J@DL{aQvVMI&&}A7uH7X8Dx__iE6=#_- z=~3rkqfG}#ZIbSqNDZ;5%ekpkOV)8DyXZ7A&^MQsXW$RAIMQa$set2?ZOmRCE zi*ziLMOa%}d)>IicswPAvo6>w4&(bYJneX|*5M>lKwv6L#fnRm@Wc-*I z==a8d$w-O%I@IxF-g~9HeU*voBKc$MAcCi;kJndYB$|GE?R1%Zv2!J3qbU=Z<@Yjf zXYoMbFpPU2DYVC}9Pc^_yGUmi3_TtrOszD4M|(QG{XhZIjKqFFDyWW-XnNcokwb<~ z`C~;(s)9hmL+aU^x*^_}K|4u<;4}WxB*xf}xh zA*p!)rxD>ofcI5$&e};OqT1Bqdj#!pUCl?-`y%CCaVXc#`FYYQ~3^~Sw`SXBMg~k6qKi`gXlN2QOO zlM9Vw5Kh;?EqG*yR=}jXPUk^i%=E~B_5A%yoS(&a;B05Ieh1fJP8_%?$XevF#3s*^ z4k~^Z@BW5mRH>i~T^donj;k3(2j{^Dc>VdXm-ql*WUxI_#uA&;W-YDDJBIr5(MK$- zOVOmI!+P5#g9(wYbziWSG~g2X8^K?R!6u}oxIi-wynfkbze5VC>fgQ0{yyac)0Ro} zMMcojJUe{{wkoW7@lN=hJ|{EJblM5BSB+rq2$BQbu_lsB@lSdZx`0c^W;g%AvC_Ru z+u*OzAH03(X$S#4T;QA>Oo6z(Ots=Tw#14`cr<0-7~z;&8jeFWE9Lna>t`njt-M^}#(uik}z-KC+`g zVPnDLAL7J3f_WQEYm1mdbK0kKBZCn@D7;0;>EF_Po6YgIy!1VKW(`_Mz29P((p9J} zPQz%O_)I~kNRA_v_|0Sxk+KSXHXq1&0Y5px2eMNM$Ezm@J{-UeuHvTmlG5@ncHMT& z@~TUY8i3k{{!<{&Wfj_|www3O$$-p4ewL1iw{2#P5j?h-jX=a3IMP1DO1@p-R- zmf&6u;k`q4(Te+X<&{-;YCJpB$NT&wSEJ<#t|f1A+O^~nk4x3*WrgCkYYR!uTW`a( zmE;}SSa$mP$d7Z-0$s6bzpoEB9iL^?EmtUb*AP^MR>r)4+f&;UlbN`db>IH+mY_;o zvyWcGCZj&xvUK5uWU{F0nQ|ug!0vDO^jiqdyTNW(#rYTXbpItduq=VUd35bZV{%C< z`#iOzB$NH4IMD<*GVpDq{kTxr+>$nMq2b13(?90^W`%fT!Q z%Or2Ec*PZ9&&BwL6M{{cCly{R*w1Q1HU7#Nb3=iwX^fjKRGrMM*5V@#nJpKgc&Iz7 z$_O~@ufis`NoYHRMa*Ffor6K~M&;McqWA7FwHnzU7}2knpD`gd&!sYI)M$%a^2Ud% z=452)QubKD^+&Cq{(!}$X$Tx3ftq5oRLabfZzFs-ll8 zQ35TJ^x>vS1eGTzGXAzn5ULLBiyf zBb_4Q1wBE3*&=}xMI$XhnAkqIdp~NEUKQDt1b}Rh3ahu`fuPhwO~fp0*qmHvEjenL z4=26eSvqoZZ9|`KgKRmPRD;NsY%`C-)|RC*sUn+dEEep%Exz@~ZHVs4>h@MNUe+XD zT@5Lky9jKy{BY!G<#|D8yXC{YP9u}elyD5o^G_Brb&>L^b{#wLsxcv1t{q@y7KTg|c7L5-I zBGuJLHpK*39#Dlp*6;SChYuSbdP~QdKuYy_b9g)`J-a>abCJ&fK6q4fOq@Ye^g@T9 zo!B$wa19cO!eWr`R~mM{($>q%&Suen8O=_^vQHmvyx9{h8i*^m9p}1RJt|0vnF`*A zs#QuOjp$0n!m{lw%HjML@yJa>$7c~BG5u@65N7I@3;mI+Oh6nOj34bEoE6lNo~q%n z>2ov8^0uGmkx`m4)U+$z>r$aP9|Ssvm1;UsvVd}c9Tb_q@+sGX&Jl6YZEg(9+16* zo7!XpdnYz<{6S23LMvYBo^cY*RL{@_NsU&6>*+KgY z;Q)>!OMN}ZILQ_-#WPlJHv5e6T=As5JJdH(5CjtWHM%36#K2-SMEEDBRQrg}-P3HL zm73B*ijtB-5zhB+)Lnj)nN3(%gEBNZH{f7q|J->g01ITy{>WD%nhM;|!%!FrDC8{w-tVn z(omfY>IcZ(7%E|?Jk1MzdQb~J&1WDd{erDItgn_rTbWJ3F|H3KgEvUxBKXkI;1pt! z7!<%FHR9J)16w&L;2!u&eDf2=3*-YUje{mYbxN0QJ2HaxXN&vHX<=!l73svt+p|c) z@oDcJWe*P7IV@|1I65DyX>YG`?CSGrJ}px%EQQz2S?`>og<_|U$<4gblp&`f`QWf} zZ8ffdE4)zXpQTSM8@0Q(XE*X3YN-th*`S0q{!T7)ZgDor6 zJ5@K^TSGrv>4=Osogd8Zd_bm`Lp@~MJGm~1ro(kjWniuvvlBNc=u@hPZ;#pc?)CRT ze%sBYWe-EK$t&!&_T@4{F4R-e-W9C>am8GGWpjZgu#y_^zIk6jz2q1*qDvSAzKxXo_0Me%K3{$^j8L*aiUT@@=z!_{_p5yN z0XfSn1x@h5COSSJ ziHQFK^`YFUxWQ0$V~*9w{MmizL6{jth`IS8WUfi(IQ5=(j~?nY$>S2Uw*2AGe8ow+ zz>yZgjJCU7uBmSu3fND-gFay0*9o1yg(|L}OH1a7)qr@lkZZ^AqlMCVqx!YQ+_D&% zfNW*3k$@y_;{5MEaVD`7MQ_cr0%#Zf3q8Z!d-KBpUi^(8%K!NU=4APIN&^3!DF3_j t{`2)e#6ciW#`+f_;{T5W4ROX^A(&MSRRitbC%s*lxQL8!g`i%*{{od)X+Hn} literal 0 HcmV?d00001 From 2bd433cd1799264de907de6ca4ec046bd39b3318 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Wed, 23 Oct 2024 16:37:39 -0700 Subject: [PATCH 02/16] Renaming cli page --- ...-ent-manage-cache-using-cli.md => mcc-ent-manage-using-cli.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename windows/deployment/do/{mcc-ent-manage-cache-using-cli.md => mcc-ent-manage-using-cli.md} (100%) diff --git a/windows/deployment/do/mcc-ent-manage-cache-using-cli.md b/windows/deployment/do/mcc-ent-manage-using-cli.md similarity index 100% rename from windows/deployment/do/mcc-ent-manage-cache-using-cli.md rename to windows/deployment/do/mcc-ent-manage-using-cli.md From b2a5749c44158060c220df83458ca9e6f3d42711 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Wed, 23 Oct 2024 16:39:38 -0700 Subject: [PATCH 03/16] Rename troubleshooting page --- ...port-and-troubleshooting.md => mcc-ent-troubleshooting.md} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename windows/deployment/do/{mcc-ent-support-and-troubleshooting.md => mcc-ent-troubleshooting.md} (95%) diff --git a/windows/deployment/do/mcc-ent-support-and-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md similarity index 95% rename from windows/deployment/do/mcc-ent-support-and-troubleshooting.md rename to windows/deployment/do/mcc-ent-troubleshooting.md index 4199588658..467471df0a 100644 --- a/windows/deployment/do/mcc-ent-support-and-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -1,6 +1,6 @@ --- -title: MCC support and troubleshooting -description: Details on how to troubleshoot and seek support for Microsoft Connected Cache for Enterprise (MCC). +title: MCC troubleshooting +description: Details on how to troubleshoot common issues for Microsoft Connected Cache for Enterprise (MCC). ms.service: windows-client ms.subservice: itpro-updates ms.topic: how-to From c35dbee783eeaa9c6a61dd5d715c6d2f4845e936 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Wed, 23 Oct 2024 16:42:39 -0700 Subject: [PATCH 04/16] Update TOC with new page names --- windows/deployment/do/TOC.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index 5fdeb51d86..4ebaba436e 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -50,7 +50,7 @@ - name: Deploy MCC to Windows href: mcc-ent-deploy-to-windows.md - name: Using CLI to create and manage cache nodes - href: mcc-ent-manage-cache-using-cli.md + href: mcc-ent-manage-using-cli.md - name: Verify cache node functionality href: mcc-ent-verify-cache-node.md - name: Monitor cache node @@ -64,7 +64,7 @@ - name: Frequent Asked Questions href: mcc-ent-faq.yml - name: Support and troubleshooting - href: mcc-ent-support-and-troubleshooting.md + href: mcc-ent-troubleshooting.md - name: MCC for Enterprise and Education (early preview) href: mcc-ent-private-preview.md - name: Release notes From e1546f1fd789e2753207bc30d3e4ad8130f8831c Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 24 Oct 2024 17:47:43 -0700 Subject: [PATCH 05/16] Replace MCC with Connected Cache --- .../do/mcc-ent-create-resource-and-cache.md | 46 +++++----- .../deployment/do/mcc-ent-deploy-to-linux.md | 14 +-- .../do/mcc-ent-deploy-to-windows.md | 26 +++--- windows/deployment/do/mcc-ent-edu-overview.md | 90 ++++++++++--------- windows/deployment/do/mcc-ent-faq.yml | 12 +-- .../deployment/do/mcc-ent-manage-using-cli.md | 20 ++--- windows/deployment/do/mcc-ent-monitoring.md | 38 ++++---- .../deployment/do/mcc-ent-prerequisites.md | 35 ++++---- .../deployment/do/mcc-ent-private-preview.md | 14 +-- .../deployment/do/mcc-ent-release-notes.md | 16 ++-- .../deployment/do/mcc-ent-troubleshooting.md | 18 ++-- .../do/mcc-ent-uninstall-cache-node.md | 18 ++-- .../do/mcc-ent-update-cache-node.md | 26 +++--- .../do/mcc-ent-verify-cache-node.md | 24 ++--- 14 files changed, 200 insertions(+), 197 deletions(-) diff --git a/windows/deployment/do/mcc-ent-create-resource-and-cache.md b/windows/deployment/do/mcc-ent-create-resource-and-cache.md index f1bb077c2b..3cfc44f9f2 100644 --- a/windows/deployment/do/mcc-ent-create-resource-and-cache.md +++ b/windows/deployment/do/mcc-ent-create-resource-and-cache.md @@ -1,6 +1,6 @@ --- -title: Create and configure MCC cache nodes -description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes. +title: Create and configure Microsoft Connected Cache nodes +description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education cache nodes. ms.service: windows-client ms.subservice: itpro-updates ms.topic: how-to @@ -16,17 +16,17 @@ ms.date: 06/03/2024 # Create Microsoft Connected Cache Azure resource and cache nodes -This article outlines how to create and configure your Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes. The creation and configuration of your cache node takes place in Azure. The deployment of your cache node requires downloading and running an OS-specific provisioning package on your host machine. +This article outlines how to create and configure your Microsoft Connected Cache for Enterprise and Education cache nodes. The creation and configuration of your cache node takes place in Azure. The deployment of your cache node requires downloading and running an OS-specific provisioning package on your host machine. ## Prerequisites 1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a free-of-charge service hosted in Azure. You'll need a pay-as-you-go Azure subscription in order to onboard to our service. To create a subscription, go to [pay-as-you-go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/). -2. **Hardware to host MCC**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps. +2. **Hardware to host Connected Cache**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps. -For more information on sizing and OS requirements, see [the prerequisites for using MCC](mcc-ent-prerequisites.md). +For more information on sizing and OS requirements, see [the prerequisites for using Connected Cache](mcc-ent-prerequisites.md). -## Create MCC Azure resource +## Create Connected Cache Azure resource # [Azure portal](#tab/portal) @@ -58,9 +58,9 @@ For more information on sizing and OS requirements, see [the prerequisites for u * Install Azure CLI extension **mcc** by following the instructions [here](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions). - * Resource group under which an MCC resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one. + * Resource group under which a Connected Cache resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one. -#### Create MCC Azure resource +#### Create Connected Cache Azure resource Replace the following placeholders with your own information: * *\*: Name of an existing resource group in your subscription. @@ -73,7 +73,7 @@ az mcc ent resource create --mcc-resource-name --resource-group --- -## Create MCC cache node +## Create Connected Cache cache node # [Azure portal](#tab/portal) @@ -117,7 +117,7 @@ az mcc ent node create --cache-node-name --mcc-resource-name *: The size of cache drive. Must be at least 50 Gb. * *\*: If proxy needs to be enabled or not.
Accepted values: enabled, disabled
- Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine. + Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache cache node to your host machine. * *\*: The proxy host name or ip address. Required if proxy is set to enabled. * *\*: Proxy port number. Required if proxy is set to enabled. * *\*: Update ring the cache node should have.
@@ -158,7 +158,7 @@ az mcc ent node update --cache-node-name --mcc-resource-name
-### Configure Windows MCC +### Configure Windows-hosted Connected Cache node Use the following command to configure cache node for deployment to a **Windows** host machine. Replace the following placeholders with your own information: @@ -171,7 +171,7 @@ Replace the following placeholders with your own information: * *\*: The size of cache drive. Must be at least 50 Gb. * *\*: If proxy needs to be enabled or not.
Accepted values: enabled, disabled
- Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine. + Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache cache node to your host machine. * *\*: The proxy host name or ip address. Required if proxy is set to enabled. * *\*: Proxy port number. Required if proxy is set to enabled. * *\*: Update ring the cache node should have.
@@ -240,7 +240,7 @@ To deploy cache nodes using Azure CLI, see #### Proxy settings
-You can choose to enable or disable proxy settings on your cache node. Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine. +You can choose to enable or disable proxy settings on your cache node. Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the Connected Cache node to your host machine.
@@ -258,14 +258,14 @@ You can choose to enable or disable proxy settings on your cache node. Proxy sho ## Other operations on resource and cache nodes
-### List all MCC resource +### List all Connected Cache resources # [Azure portal](#tab/portal) -Navigate to the resource group under which you would like to see the MCC resources. +Navigate to the resource group under which you would like to see the Connected Cache resources. # [Azure CLI](#tab/cli) -Use the following command to list all the MCC resources under the resource group. +Use the following command to list all the Connected Cache resources under the resource group. Replace the following placeholders with your own information: * *\*: An existing resource group in your subscription. @@ -279,7 +279,7 @@ az mcc ent resource list --resource-group ### List all cache nodes # [Azure portal](#tab/portal) -On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the MCC resource. +On the left pane, click on 'Cache Nodes' under 'Cache Node Management' to see all the cache nodes under the Connected Cache resource. # [Azure CLI](#tab/cli) @@ -296,14 +296,14 @@ az mcc ent node list --mcc-resource-name --resource-group ---
-### Delete MCC resource +### Delete Connected Cache resource # [Azure portal](#tab/portal) -Navigate to the MCC resource to delete and click on the delete button on top. +Navigate to the Connected Cache resource to delete and click on the delete button on top. # [Azure CLI](#tab/cli) -Use the following command to delete the MCC resource. +Use the following command to delete the Connected Cache resource. Replace the following placeholders with your own information: * *\*: Name of the resource group in your subscription. @@ -319,7 +319,7 @@ az mcc ent node delete --cache-node-name --mcc-resource-name [!IMPORTANT] > - Microsoft Connected Cache is currently a preview feature. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). -Microsoft Connected Cache (MCC) for Enterprise and Education (preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. MCC can be managed from an Azure portal or through Azure CLI and can be deployed to as many Windows devices, Linux devices, or VMs as needed. Managed Windows devices can be configured to download cloud content from a Connected Cache server by applying the client policy using management tools such as Intune.
+Microsoft Connected Cache for Enterprise and Education (preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. Connected Cache can be managed from an Azure portal or through Azure CLI and can be deployed to as many Windows devices, Linux devices, or VMs as needed. Managed Windows devices can be configured to download cloud content from a Connected Cache server by applying the client policy using management tools such as Intune. -Microsoft Connected Cache (MCC) for Enterprise and Education (preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For information about Microsoft Connected Cache in Configuration Manager (generally available, starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/configmgr/core/plan-design/hierarchy/microsoft-connected-cache). +Microsoft Connected Cache for Enterprise and Education (preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For information about Microsoft Connected Cache in Configuration Manager (generally available, starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/configmgr/core/plan-design/hierarchy/microsoft-connected-cache). -Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsystem for Linux](/windows/wsl/about) and either a [Group Managed Service Account](/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts), local user account, or domain user account are required to run WSL. WSL needs to run in a user context and any user, even if the currently logged-in user, could be used to run WSL and Microsoft Connected Cache.
+Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsystem for Linux](/windows/wsl/about) and either a [Group Managed Service Account](/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts), local user account, or domain user account are required to run WSL. WSL needs to run in a user context and any user, even if the currently logged-in user, could be used to run WSL and Microsoft Connected Cache. -### Supported scenarios and deployments +## Supported scenarios and configurations -Microsoft Connected Cache for Enterprise and Education (preview) is intended to support the following content delivery scenarios:
-* Pre-provisioning of devices using Windows Autopilot
-* Co-managed clients that get monthly update and Win32 apps from Microsoft Intune. For more information, see Support for Intune Win32 apps.
-* Cloud-only managed devices, such as Intune-enrolled devices without the Configuration Manager client, that get monthly update and Win32 apps from Microsoft Intune. For more information, see Support for cloud-managed devices.
+Microsoft Connected Cache for Enterprise and Education (preview) is intended to support the following content delivery scenarios: + +- Pre-provisioning of devices using Windows Autopilot +- Co-managed clients that get monthly updates and Win32 apps from Microsoft Intune +- Cloud-only managed devices, such as Intune-enrolled devices without the Configuration Manager client, that get monthly updates and Win32 apps from Microsoft Intune Microsoft Connected Cache is built for flexible deployments to support a number of enterprise configurations: -##### Branch office +### Branch office + Customers may have globally dispersed offices that meet the following parameters: -* 10 – 50 Windows Clients -* No dedicated server hardware -* Internet bandwidth is great to limited (satellite internet) -* Possibly intermittent connectivity -
-To support the branch the branch office scenario, customers can deploy to a Windows 11 client (see Host machine requirements) device. -##### Large Enterprise +- 10 – 50 Windows Clients +- No dedicated server hardware +- Internet bandwidth is great to limited (satellite internet) +- Possibly intermittent connectivity + +To support the branch office scenario, customers can deploy a Connected Cache node to a Windows 11 client device. + +### Large Enterprise + Customers may have office spaces, data centers, or Azure deployments that meet the following parameters: -* 100's or 1,000's of Windows devices (client or server). -* Existing hardware – Decommissioned DP, file server, cloud print server -* Azure VMs and Azure Virtual Desktop -* Internet bandwidth is great to limited (T1) +- 100's or 1,000's of Windows devices (client or server). +- Existing hardware – Decommissioned DP, file server, cloud print server +- Azure VMs and Azure Virtual Desktop +- Internet bandwidth is great to limited (T1) -### Supported content types +To support the large enterprise scenario, customers can deploy a Connected Cache node to a server running Windows Server 2022 or Ubuntu 22.04. + +See [Connected Cache node host machine requirements](mcc-ent-prerequisites.md) for recommended host machine specifications in each configuration. + +| Enterprise configuration | Download speed range | Download speeds and approximate content volume delivered in 8 Hours | +|---|---|---| +|Branch Office|< 1 Gbps Peak| 500 Mbps => 1,800 GB

250 Mbps => 900 GB

100 Mbps => 360 GB

50 Mbps => 180 GB| +|Small to Medium Enterprises/Autopilot Provisioning Center (50 - 500 devices in a single location) |1 - 5 Gbps| 5 Gbps => 18,000 GB

3 Gbps => 10,800 GB

1 Gbps => 3,600 GB| +|Medium to Large Enterprises/Autopilot Provisioning Center (500 - 5,000 devices in a single location) |5 - 101 Gbps Peak| 9 Gbps => 32,400 GB

5 Gbps => 18,000 GB

3 Gbps => 10,800 GB| + +## Supported content types When clients download cloud-managed content, they use Delivery Optimization from the cache server installed on a Windows server or VM. Cloud-managed content includes the following types: -* Windows updates: Windows feature and quality updates -* Office Click-to-Run apps: Microsoft 365 Apps and updates -* Client apps: Intune, store apps, and updates -* Endpoint protection: Windows Defender definition updates -For the full list of content endpoints that Microsoft Connected Cache for Enterprise and Education supports, see [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md).
+- Windows updates: Windows feature and quality updates +- Office Click-to-Run apps: Microsoft 365 Apps and updates +- Client apps: Intune, store apps, and updates +- Endpoint protection: Windows Defender definition updates -### Hardware or VM Requirements -See [Host machine requirements](mcc-ent-prerequisites.md) for complete details. - -|Deployment Scenarios| Download Speed Range | Download Speeds and Content Volume Delivered in 8 Hours | VM/Hardware Recommendation | -|---|---|---|---| -|Branch Office|< 1 Gbps Peak| 500 Mbps - 1,800 GB

250 Mbps - 900 GB

100 Mbps - 360 GB

50 Mbps - 180 GB| 4 Cores

Up to 8 GB Memory with 4 GB of Free

100 GB free disk space| -|Small to Medium Enterprises/Autopilot Provisioning Center - 50 - 500 devices in a single location|1 - 5 Gbps| 5 Gbps - 18,000 GB

3 Gbps - 10,800 GB

1 Gbps - 3,600 GB| 8 Cores

Up to 16 GB Memory with 4 GB of Free

500 GB free disk space| -|Medium to Large Enterprises/Autopilot Provisioning Center - 500 - 5,000 devices|5 - 101 Gbps Peak| 9 Gbps - 32,400 GB

5 Gbps - 18,000 GB

3 Gbps - 10,800 GB| 16 Cores

32 GB Memory with 4 GB of Free

2 200-500 GB SSDs| - -
+For the full list of content endpoints that Microsoft Connected Cache for Enterprise and Education supports, see [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md). ## How it works -The following diagram displays an overview of how MCC functions:
- -:::image type="content" source="./images/mcc_ent_publicpreview.png" alt-text="Diagram displaying the components of MCC." lightbox="./images/mcc_ent_publicpreview.png"::: +The following diagram displays an overview of how Connected Cache functions: +:::image type="content" source="./images/mcc_ent_publicpreview.png" alt-text="Diagram displaying the components of Connected Cache." lightbox="./images/mcc_ent_publicpreview.png"::: 1. The Azure management portal for Microsoft Connected Cache or CLI are used to create cache nodes, configure deployments, including unauthenticated proxy settings. 1. Prepare Windows or Linux devices. If deploying to Windows devices, prepare accounts - gMSA, local user account, domain account. Deploy to Windows or Linux devices using scripts. @@ -88,8 +91,7 @@ The following diagram displays an overview of how MCC functions:
1. Devices can fallback to CDN if cache server is unavailable for any reason or use Delivery Optimization delay fallback to http (CDN )settings to prefer the local cache server. Customers can view data regarding Microsoft Connected Cache downloads on management portal and Windows Update for Business reports - -## Next step +## Next steps >[!div class="nextstepaction"] ->[Create MCC Azure resources](mcc-ent-create-resource-and-cache.md) \ No newline at end of file +>[Create Connected Cache Azure resources](mcc-ent-create-resource-and-cache.md) \ No newline at end of file diff --git a/windows/deployment/do/mcc-ent-faq.yml b/windows/deployment/do/mcc-ent-faq.yml index 653c5676a0..e099a27f79 100644 --- a/windows/deployment/do/mcc-ent-faq.yml +++ b/windows/deployment/do/mcc-ent-faq.yml @@ -1,7 +1,7 @@ ### YamlMime:FAQ metadata: - title: MCC Frequently Asked Questions - description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise (MCC). + title: Microsoft Connected Cache for Enterprise and Education Frequently Asked Questions + description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise. ms.service: windows-client ms.subservice: itpro-updates ms.topic: faq @@ -25,8 +25,8 @@ sections: questions: - question: What are the licesning requirement? answer: Microsoft Connected Cache for Enterprise and Education is available to all Windows E3, E5 and F3 and Education A3 and A5 customers. - - question: Is there a charge to create MCC resources and cache node on Azure? - answer: No. You won't be charged to create MCC resource and cache nodes on Azure. However, you need an Azure pay-as-you-go subscription to create the resources but there is no charge for the resource itself. + - question: Is there a charge to create Connected Cache resources and cache node on Azure? + answer: No. You won't be charged to create Connected Cache resource and cache nodes on Azure. However, you need an Azure pay-as-you-go subscription to create the resources but there is no charge for the resource itself. - question: Is there a nondisclosure agreement to sign? answer: No, a nondisclosure agreement isn't required. - question: What will Microsoft Connected Cache for Enterprise and Education do for me? @@ -40,7 +40,7 @@ sections: - [Azure pay-as-you-go subscription](https://azure.microsoft.com/offers/ms-azr-0003p/). - [Hardware to host Microsoft Connected Cache](mcc-ent-edu-overview.md) - [Host machine requirements](mcc-ent-prerequisites.md) - - question: What host OS do I need to deploy MCC? + - question: What host OS do I need to deploy Connected Cache? answer: You can use Linux or Windows OS. Depending on the OS, the provisioning script and certain provisioning steps are different. - question: What content is cached by Microsoft Connected Cache? answer: For more information about content cached, see [Delivery Optimization and Microsoft Connected Cache content endpoints](delivery-optimization-endpoints.md). @@ -64,7 +64,7 @@ sections: answer: No. It's important to keep the Microsoft Connected Cache software up to date, especially when it comes to security issues. Microsoft validates updates prior to releasing Enterprises Connected Cache updates and only releases updates when it's necessary to keep customers secure or to ensure the continued successful operation of Connected Cache nodes for customers. - question: How do I set up CLI? answer: For more information, see [How to install the Azure CLI](/cli/azure/install-azure-cli). - - question: How do I install MCC extension? + - question: How do I install the Microsoft Connected Cache Azure CLI extension? answer: For more information, see [Install the Microsoft Connected Cache extension](mcc-ent-manage-cache-using-cli.md#prerequisites). - question: What do I do if I have to set up or change existing proxy? answer: You can enable proxy and provide proxy information on Azure portal or use the CLI. Don't forget to rerun the provisioning script after making any proxy changes. For more information, see [Set up or change existing proxy](mcc-ent-create-resource-and-cache.md#proxy-settings). diff --git a/windows/deployment/do/mcc-ent-manage-using-cli.md b/windows/deployment/do/mcc-ent-manage-using-cli.md index c48dd5e04b..6faca3726f 100644 --- a/windows/deployment/do/mcc-ent-manage-using-cli.md +++ b/windows/deployment/do/mcc-ent-manage-using-cli.md @@ -1,6 +1,6 @@ --- -title: Manage MCC cache nodes using CLI -description: Details on how to manage Microsoft Connected Cache for Enterprise (MCC) cache nodes via Azure CLI commands. +title: Manage Microsoft Connected Cache nodes using CLI +description: Details on how to manage Microsoft Connected Cache for Enterprise cache nodes via Azure CLI commands. ms.service: windows-client ms.subservice: itpro-updates ms.topic: how-to @@ -20,18 +20,18 @@ ms.date: 06/03/2024
-This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise (MCC) cache nodes using Azure CLI. +This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise cache nodes using Azure CLI. ## Prerequisites: 1. **Install Azure CLI**: [How to install the Azure CLI](/cli/azure/install-azure-cli) -1. **Install MCC extension**: Install MCC extension via the command below +1. **Install Connected Cache extension**: Install Connected Cache extension via the command below ```azurecli-interactive az extension add --name mcc ``` -To learn more about installting extensions, visit [Install the MCC extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions) +To learn more about installting extensions, visit [Install the Connected Cache extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)

@@ -50,11 +50,11 @@ az group create --name myrg --location westus Once the resource group is created, you'll need to create a Microsoft Connected Cache for Enterprise resource. -### 2. Create an MCC Azure resource +### 2. Create a Connected Cache Azure resource -An MCC Azure resource is a top-level Azure resource under which cache nodes can be created. +A Connected Cache Azure resource is a top-level Azure resource under which cache nodes can be created. -To create an MCC Azure resource, use `az mcc ent resource create` +To create an Connected Cache Azure resource, use `az mcc ent resource create` ```azurecli-interactive az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg @@ -63,7 +63,7 @@ az mcc ent resource create --mcc-resource-name mymccresource --resource-group my
>[!IMPORTANT] ->In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully started creating MCC resource. +>In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully started creating your Connected Cache resource.
@@ -142,7 +142,7 @@ az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-res ### Example script: -Below is a pseudocode example of how to script bulk creation and configuration of an MCC Azure resource and multiple MCC cache nodes. +Below is a pseudocode example of how to script bulk creation and configuration of a Connected Cache Azure resource and multiple Connected Cache cache nodes. ![Screenshot of cache node summary in the Azure portal interface.](../images/mcc-ent-cache-node-summary.png) | Metric | Description | | --- | --- | -| Healthy nodes | Your MCC node will frequently send heartbeat messages to our backend. If your node has responded in the last 24 hours, it will be labeled as healthy. | +| Healthy nodes | Your Connected Cache node will frequently send heartbeat messages to our backend. If your node has responded in the last 24 hours, it will be labeled as healthy. | | Unhealthy nodes | If your node has not sent a heartbeat message in the last 24 hours, it will be labeled as unhealthy. | | Max in | The maximum ingress in Mbps (Megabits per second) that your node has pulled from CDN in the last 24 hours. | | Max out | The minimum egress in Mbps that your node has pushed out to devices in your network over the last 24 hours. | | Average in | The average ingress in Mbps that your node has pulled from CDN in the last 24 hours. | | Average out | The average egress in Mbps that your node has pushed out to devices in your network over the last 24 hours. | -| Cache efficiency | The percentage of all content requests your MCC node receives that are ultimately delivered by your MCC node. An well-performing node should have an efficiency > 90%. | +| Cache efficiency | The percentage of all content requests your Connected Cache node receives that are ultimately delivered by your Connected Cache node. An well-performing node should have an efficiency > 90%. | ### Key Metrics -The two monitoring charts on the Overview page more visually represent the usage of your MCC node, as well as the types cached content delivered by your node over various time intervals. +The two monitoring charts on the Overview page more visually represent the usage of your Connected Cache node, as well as the types cached content delivered by your node over various time intervals. ![Screenshot of key metric charts in the Azure portal interface.](../images/mcc-ent-key-metric-charts.png) @@ -55,15 +55,15 @@ The two monitoring charts on the Overview page more visually represent the usage Both filters displayed will only impact the data shown in the 2 charts below. - By time: View data from the last 1 hour to 30 days - - By cache node: View data from individual cache nodes or the sum of all your active MCC nodes. + - By cache node: View data from individual cache nodes or the sum of all your active Connected Cache nodes. #### Outbound Traffic Chart -This chart displays the egress in Mbps that your MCC node was delivering at specific timestamps. The value in the chart's key represents the average egress over the specified time period. +This chart displays the egress in Mbps that your Connected Cache node was delivering at specific timestamps. The value in the chart's key represents the average egress over the specified time period. #### Volume by Content Type -This chart displays the amount (in GB) of each supported content type that your MCC node is delivering at specific timestamps. You can find the complete list of supported content types here: [Microsoft Connected Cache content and services endpoints | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/delivery-optimization-endpoints) +This chart displays the amount (in GB) of each supported content type that your Connected Cache node is delivering at specific timestamps. You can find the complete list of supported content types here: [Microsoft Connected Cache content and services endpoints | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/delivery-optimization-endpoints) The content types in the key are sorted from highest to lowest volume an each have a distinct color. The bar chart is stacked such that you can visually compare total volume being delivered at different timestamps @@ -75,18 +75,18 @@ Listed below are the additional metrics you can access in this section: | Metric | Description | | --- | --- | -| Inbound | The number of content requests your MCC node receives over a specified period of time. | -| Hits | The number of times your MCC node fulfills a content request by pulling from its cache. | -| Misses | The number of times your MCC node is not able to fulfill a content request by pulling from its cache | +| Inbound | The number of content requests your Connected Cache node receives over a specified period of time. | +| Hits | The number of times your Connected Cache node fulfills a content request by pulling from its cache. | +| Misses | The number of times your Connected Cache node is not able to fulfill a content request by pulling from its cache | ### Customizable Dashboards -Once you select the charts you would like to track, you can save them over to a personalized dashboard. This dashboard enables you to configure the chart title, filters, range, legend, and more. You can also use this personalized dashboard to set up alerts that will notify you if your MCC dips in performance. +Once you select the charts you would like to track, you can save them over to a personalized dashboard. This dashboard enables you to configure the chart title, filters, range, legend, and more. You can also use this personalized dashboard to set up alerts that will notify you if your Connected Cache node dips in performance. Some scenarios where you would want to set up these alerts: - • My MCC node is being shown as unhealthy and I want to know exactly when it stopped egressing last. -A new Xbox update just released last night and I want to know if my MCC node is helping deliver this content to my client machines. + • My Connected Cache node is being shown as unhealthy and I want to know exactly when it stopped egressing last. +A new Xbox update just released last night and I want to know if my Connected Cache node is helping deliver this content to my client machines. ## Additional Metrics -Once the content has left the MCC to be delivered, the node cannot track whether the content has successfully been delivered. To access client-side data, you can refer to this page: [Monitor Delivery Optimization | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/waas-delivery-optimization-monitor) \ No newline at end of file +Once the content has left the Connected Cache node, the node cannot track whether the content has successfully been delivered to the requesting Windows client. To access client-side data, you can refer to this page: [Monitor Delivery Optimization | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/waas-delivery-optimization-monitor) \ No newline at end of file diff --git a/windows/deployment/do/mcc-ent-prerequisites.md b/windows/deployment/do/mcc-ent-prerequisites.md index f95d8fb53d..95765edf54 100644 --- a/windows/deployment/do/mcc-ent-prerequisites.md +++ b/windows/deployment/do/mcc-ent-prerequisites.md @@ -1,6 +1,6 @@ --- -title: MCC prerequisites -description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCC). +title: Microsoft Connected Cache for Enterprise and Education prerequisites +description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education. ms.service: windows-client ms.subservice: itpro-updates ms.topic: conceptual @@ -15,17 +15,17 @@ ms.date: 09/27/2024 # Microsoft Connected Cache for Enterprise and Education Requirements -This article details the requirements and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCC). +This article details the requirements and recommended specifications for using Microsoft Connected Cache for Enterprise and Education. ## Licensing requirements -- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCC) service, you'll need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management). +- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education service, you'll need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management). If you don't have an Azure subscription already, you can create an Azure [pay-as-you-go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/). - The Azure resources used for MCC will be free to you during this public preview. + The Azure resources used for Connected Cache will be free to you during this public preview. -- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an MCC cache node. +- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an Connected Cache node. - [Windows Enterprise E3 or E5](/windows/whats-new/windows-licensing#windows-11-enterprise), included in [Microsoft 365 F3, E3, or E5](https://www.microsoft.com/microsoft-365/enterprise/microsoft365-plans-and-pricing?msockid=32c407b43d5968050f2b13443c746916) - Windows Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans) @@ -34,7 +34,7 @@ This article details the requirements and recommendations for using Microsoft Co ### General requirements -- Any previous installations of MCC must be [uninstalled](mcc-ent-uninstall-cache-node.md) before installing the latest version of MCC. +- Any previous installations of Connected Cache must be [uninstalled](mcc-ent-uninstall-cache-node.md) from the host machine before installing the latest version of Connected Cache. - [These listed endpoints](delivery-optimization-endpoints.md) must be reachable by the host machine. - The host machine must have no other services / applications utilizing port 80 (for example, ConfigManager or Distribution Point). - The host machine must have at least 4 GB of free memory. @@ -55,18 +55,19 @@ This article details the requirements and recommendations for using Microsoft Co - Red Hat Enterprise Linux (RHEL) 8.* or 9.* - If using RHEL, the default container engine (Podman) must be replaced with [Moby](https://github.com/moby/moby#readme) -### Networking recommendations for host machines +### Recommended host machine networking specifications -- Multiple network interface cards (NICs) on a single MCC instance aren't supported. +- Multiple network interface cards (NICs) on a single Connected Cache host machine isn't supported. - 1 Gbps NIC is the minimum speed recommended but any NIC is supported. - The NIC and BIOS should support SR-IOV for best performance. -### Host machine sizing recommendations +### Recommended host machine hardware specifications -| Component | Branch Office / Small Enterprise | Large Enterprise | -| --- | --- | --- | -| OS| Windows Server 2022
Windows 11 (Pro or Enterprise) | Same | -|NIC | 1 Gbps | 5 Gbps | -|Disk | SSD
1 drive
50 GB each |SSD
1 drive
200 GB each | -|Memory | 4 GB | 8 GB | -|Cores | 4 | 8 | +Based on your [enterprise configuration](mcc-ent-edu-overview.md), it is recommended to deploy your Connected Cache nodes to host machines that meet the following recommended hardware specifications. + +| | Branch Office | Small Enterprise | Large Enterprise | +| --- | --- | --- | --- | +| CPU cores | 4 | 8 | 16 | +| Memory | 8 GB, 4GB free | 16 GB, 4GB free | 32 GB, 4GB free | +| Disk storage | 100 GB free | 500 GB free | 2x 200-500 GB free | +| NIC | 1 Gbps | 5 Gbps | 10 Gbps | diff --git a/windows/deployment/do/mcc-ent-private-preview.md b/windows/deployment/do/mcc-ent-private-preview.md index 03c549f395..83b9aaa5aa 100644 --- a/windows/deployment/do/mcc-ent-private-preview.md +++ b/windows/deployment/do/mcc-ent-private-preview.md @@ -1,6 +1,6 @@ --- -title: MCC Private Preview -description: Details on Microsoft Connected Cache for Enterprise (MCC) Private Preview +title: Microsoft Connected Cache for Enterprise and Education Private Preview +description: Details on Microsoft Connected Cache for Enterprise Private Preview ms.service: windows-client ms.subservice: itpro-updates ms.topic: conceptual @@ -12,15 +12,15 @@ appliesto: ms.date: 06/03/2024 --- -# Microsoft Connected Cache for Enterprise and Education (MCC) Private Preview +# Microsoft Connected Cache for Enterprise and Education Private Preview -If you participated in the MCC early preview, thank you for your collaboration and feedback. +If you participated in the Connected Cache early preview, thank you for your collaboration and feedback. -To continue using MCC, we strongly recommend that you upgrade your existing cache nodes to the Public Preview release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the MCC Azure service. +To continue using Connected Cache, we strongly recommend that you upgrade your existing cache nodes to the Public Preview release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the Connected Cache Azure service. -As such, we strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the MCC caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. +As such, we strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the Connected Cache software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. ## Next step > [!div class="nextstepaction"] -> [View documentation for MCC Public Preview](mcc-ent-edu-overview.md) +> [View documentation for Connected Cache Public Preview](mcc-ent-edu-overview.md) diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index 45efd09f1b..9fd4a23d38 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -1,6 +1,6 @@ --- -title: MCC Release Notes -description: Release Notes for Microsoft Connected Cache for Enterprise and Education (MCC). +title: Microsoft Connected Cache Release Notes +description: Release Notes for Microsoft Connected Cache for Enterprise and Education. ms.service: windows-client ms.subservice: itpro-updates ms.topic: conceptual @@ -14,9 +14,9 @@ appliesto: ms.date: 09/27/2024 --- -# Release Notes for Microsoft Connected Cache for Enterprise and Education (MCC) +# Release Notes for Microsoft Connected Cache for Enterprise and Education -This article contains details about the latest releases of MCC. Since MCC is a Preview service, some releases may contain breaking changes that will be highlighted as such. +This article contains details about the latest releases of Connected Cache. Since Connected Cache is a Preview service, some releases may contain breaking changes that will be highlighted as such. ## Release v0.1.0 (Public Preview launch) @@ -30,11 +30,11 @@ This article contains details about the latest releases of MCC. Since MCC is a P - Added new "Outbound egress" and "Volume by Content type" monitoring charts to Azure portal user interface - Added ability to create custom monitoring charts under the Metrics tab in the Azure portal user interface -- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same MCC Azure resource -- Added Azure CLI support for programmatic creation and management of MCC Azure resources and cache nodes +- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same Connected Cache Azure resource +- Added Azure CLI support for programmatic creation and management of Connected Cache Azure resources and cache nodes - Added support for unauthenticated proxy and cloud proxy integration -- Added ability to set each cache node's Update Ring to govern cadence of MCC container updates +- Added ability to set each cache node's Update Ring to govern cadence of Connected Cache container updates ## Related content -- [Overview of MCC](mcc-ent-edu-overview.md) +- [Overview of Connected Cache](mcc-ent-edu-overview.md) diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md index 467471df0a..c7e47ea564 100644 --- a/windows/deployment/do/mcc-ent-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -1,6 +1,6 @@ --- -title: MCC troubleshooting -description: Details on how to troubleshoot common issues for Microsoft Connected Cache for Enterprise (MCC). +title: Microsoft Connected Cache for Enterprise and Education troubleshooting +description: Details on how to troubleshoot common issues for Microsoft Connected Cache for Enterprise. ms.service: windows-client ms.subservice: itpro-updates ms.topic: how-to @@ -15,9 +15,9 @@ ms.date: 09/27/2024 --- -# Troubleshoot Microsoft Connected Cache for Enterprise and Education (MCC) +# Troubleshoot Microsoft Connected Cache for Enterprise and Education -This article contains instructions on how to troubleshoot different issues you may encounter while using MCC. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [MCC Azure resource creation](mcc-ent-create-resource-and-cache.md). +This article contains instructions on how to troubleshoot different issues you may encounter while using Connected Cache. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [Connected Cache Azure resource creation](mcc-ent-create-resource-and-cache.md). ## Steps to obtain an Azure subscription ID @@ -26,11 +26,11 @@ This article contains instructions on how to troubleshoot different issues you m ## Troubleshooting Azure resource creation -MCC Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields. +Connected Cache Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields. ## Troubleshooting cache node issue -If you are facing issues with your cache node, it could be due to cache node being on the early preview version of MCC. Cache nodes belonging to early preview version will be under MCC resource that will have 'early preview' in its name. Please delete these cache nodes and associated MCC resource and create a new MCC resource on the new version. -For detailed instructions on creating MCC resource, see [Create MCC Azure resources](mcc-ent-create-resource-and-cache.md) +If you are facing issues with your cache node, it could be due to cache node being on the early preview version of Connected Cache. Cache nodes belonging to early preview version will be under Connected Cache resource that will have 'early preview' in its name. Please delete these cache nodes and associated Connected Cache resource and create a new Connected Cache resource on the new version. +For detailed instructions on creating Connected Cache resource, see [Create Connected Cache Azure resources](mcc-ent-create-resource-and-cache.md) ## Troubleshooting cache node deployment @@ -61,9 +61,9 @@ Optional: You have two options for manually curated links in this pattern: Next ## Diagnose and Solve -If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your MCC resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users might face as they onboard. +If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your Connected Cache resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users might face as they onboard. -You can find **Diagnose and solve problems** on the left pane within your MCC resource. +You can find **Diagnose and solve problems** on the left pane within your Connected Cache resource. Within **Diagnose and solve problems**, select **Troubleshoot** under the type of problem you're facing and follow the prompts that narrow down the solution to the issue. diff --git a/windows/deployment/do/mcc-ent-uninstall-cache-node.md b/windows/deployment/do/mcc-ent-uninstall-cache-node.md index 3d554c99a0..07c4678b1e 100644 --- a/windows/deployment/do/mcc-ent-uninstall-cache-node.md +++ b/windows/deployment/do/mcc-ent-uninstall-cache-node.md @@ -1,6 +1,6 @@ --- -title: Uninstall MCC cache nodes -description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCC) from a host machine. +title: Uninstall Microsoft Connected Cache for Enterprise and Education cache nodes +description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education from a host machine. ms.service: windows-client ms.subservice: itpro-updates ms.topic: how-to @@ -14,22 +14,22 @@ appliesto: ms.date: 09/27/2024 --- -# Uninstall MCC caching software from a host machine +# Uninstall Connected Cache caching software from a host machine -This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education (MCC) caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal. +This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal. -## Steps to uninstall MCC from a Windows host machine +## Steps to uninstall Connected Cache from a Windows host machine -1. Launch a PowerShell window *as administrator* and navigate to the MCC installation directory (C:\mcconwsl01 by default) +1. Launch a PowerShell window *as administrator* and navigate to the Connected Cache installation directory (C:\mcconwsl01 by default) 1. Run the `uninstallmcconwsl.ps1` script -## Steps to uninstall MCC from a Linux host machine +## Steps to uninstall Connected Cache from a Linux host machine -The `uninstallmcc.sh` script within the provisioning package uninstalls the MCC caching software and all related components, including: +The `uninstallmcc.sh` script within the provisioning package uninstalls the Connected Cache caching software and all related components, including: - IoT Edge - IoT Edge Agent - IoT Edge Hub -- MCC +- Connected Cache container - Moby CLI - Moby engine diff --git a/windows/deployment/do/mcc-ent-update-cache-node.md b/windows/deployment/do/mcc-ent-update-cache-node.md index 604ac96ddd..960f2a289d 100644 --- a/windows/deployment/do/mcc-ent-update-cache-node.md +++ b/windows/deployment/do/mcc-ent-update-cache-node.md @@ -1,6 +1,6 @@ --- -title: Update MCC cache nodes -description: Details on how Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes are updated by Microsoft. +title: Update Microsoft Connected Cache for Enterprise and Education cache nodes +description: Details on how Microsoft Connected Cache for Enterprise and Education cache nodes are updated by Microsoft. ms.service: windows-client ms.subservice: itpro-updates ms.topic: how-to @@ -13,28 +13,28 @@ appliesto: - ✅ Microsoft Connected Cache for Enterprise and Education ms.date: 09/27/2024 --- -# Configure container update frequency for Microsoft Connected Cache for Enterprise and Education (MCC) +# Configure container update frequency for Microsoft Connected Cache for Enterprise and Education -Microsoft Connected Cache for Enterprise and Education (MCC) caching software is deployed to host machines as a container. The container OS and any software component within the container need to be updated to address security vulnerabilities and improve quality and performance. These Microsoft-published container updates are referred to as "MCC updates" in this article. +Microsoft Connected Cache for Enterprise and Education caching software is deployed to host machines as a container. The container OS and any software component within the container need to be updated to address security vulnerabilities and improve quality and performance. These Microsoft-published container updates are referred to as "Connected Cache updates" in this article. -Microsoft silently deploys MCC updates to your cache nodes based on the Update Ring setting you configure for each cache node. +Microsoft silently deploys Connected Cache updates to your cache nodes based on the Update Ring setting you configure for each cache node. ## Update rings -MCC cache nodes can be configured to either the "Fast" or "Slow" update ring. If configured to update as part of the Fast ring, the cache node will be silently updated by Microsoft soon after the update is made available. If configured to update as part of the Slow ring, the cache node is silently updated by Microsoft within five weeks of the update becoming available. +Connected Cache nodes can be configured to either the "Fast" or "Slow" update ring. If configured to update as part of the Fast ring, the cache node will be silently updated by Microsoft soon after the update is made available. If configured to update as part of the Slow ring, the cache node is silently updated by Microsoft within five weeks of the update becoming available. -In other words, configuring cache nodes to update as part of the Slow ring provides users with the option to delay the update process until they have validated that the latest MCC update works within their environment. For example, a user could configure a test cache node to update as part of the Fast ring and validate that clients can successfully interact with the test cache node after the latest MCC update has been applied. This builds confidence that service won't be interrupted when the production cache nodes are updated as part of the Slow ring. +In other words, configuring cache nodes to update as part of the Slow ring provides users with the option to delay the update process until they have validated that the latest Connected Cache update works within their environment. For example, a user could configure a test cache node to update as part of the Fast ring and validate that clients can successfully interact with the test cache node after the latest Connected Cache update has been applied. This builds confidence that service won't be interrupted when the production cache nodes are updated as part of the Slow ring. ### Update ring options >[!IMPORTANT] ->In the event of a critical security patch, Microsoft may elect to initiate an MCC update to your cache node as soon as possible (even if the cache node has been set to the Slow Ring). Visit the [Release notes](mcc-ent-release-notes.md) page for a detailed changelog of each MCC update. +>In the event of a critical security patch, Microsoft may elect to initiate an Connected Cache update to your cache node as soon as possible (even if the cache node has been set to the Slow Ring). Visit the [Release notes](mcc-ent-release-notes.md) page for a detailed changelog of each Connected Cache update. #### Fast Ring -All MCC cache nodes are configured to update as part of the Fast ring by default. MCC cache nodes in the Fast ring will be updated soon after an update is made available. Microsoft will silently update cache nodes at a time of day when update traffic is likely to be minimal, such as 3:00 AM (local time) on Saturday. +All Connected Cache nodes are configured to update as part of the Fast ring by default. Connected Cache nodes in the Fast ring will be updated soon after an update is made available. Microsoft will silently update cache nodes at a time of day when update traffic is likely to be minimal, such as 3:00 AM (local time) on Saturday. #### Slow Ring -Configuring an MCC cache node to update as part of the Slow ring provides users with the option to delay MCC software updates until the update can be validated. There are three settings that control when MCC updates will be applied to MCC cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI. +Configuring an Connected Cache node to update as part of the Slow ring provides users with the option to delay Connected Cache software updates until the update can be validated. There are three settings that control when Connected Cache updates will be applied to Connected Cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI. | Setting | Description | | --- | --- | @@ -44,15 +44,15 @@ Configuring an MCC cache node to update as part of the Slow ring provides users ## Update process -When Microsoft publishes an MCC update, the MCC service attempts to update all MCC cache nodes based on their Update Ring membership. If a cache node can't complete the silent MCC update within 6 hours of starting, an error message is surfaced in the Azure portal. +When Microsoft publishes an Connected Cache update, the Connected Cache service attempts to update all Connected Cache nodes based on their Update Ring membership. If a cache node can't complete the silent Connected Cache update within 6 hours of starting, an error message is surfaced in the Azure portal. ## Update terminology, criteria, and SLA -MCC updates will be released based on need instead of on a set cadence. +Connected Cache updates will be released based on need instead of on a set cadence. | Update type | Criteria and SLA | | --- | --- | | Security | Security updates are the highest priority and will be released based on the severity rating of the vulnerability. [Critical and High](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 60 days of discovery. [Medium and Low](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 120 days | | Quality | Quality updates fix a specific problem and addresses a noncritical, non-security-related bug. Quality updates could include performance fixes for a specific problem or changes related to cache efficiency or maximum egress for example. Quality updates are released along with security updates or when necessary to ensure proper functioning of the Microsoft Connected Cache software. | -For information on all released Microsoft Connected Cache updates, see the [MCC release notes](mcc-ent-release-notes.md). +For information on all released Microsoft Connected Cache updates, see the [Connected Cache release notes](mcc-ent-release-notes.md). diff --git a/windows/deployment/do/mcc-ent-verify-cache-node.md b/windows/deployment/do/mcc-ent-verify-cache-node.md index bf7720bce4..c190dbf048 100644 --- a/windows/deployment/do/mcc-ent-verify-cache-node.md +++ b/windows/deployment/do/mcc-ent-verify-cache-node.md @@ -1,6 +1,6 @@ --- -title: Verify MCC cache node functionality -description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes. +title: Verify Microsoft Connected Cache for Enterprise and Education cache node functionality +description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education cache nodes. author: chrisjlin ms.author: lichris manager: naengler @@ -9,20 +9,20 @@ ms.subservice: itpro-updates ms.topic: how-to ms.date: 09/27/2024 appliesto: -- ✅ Windows-hosted MCC cache nodes -- ✅ Linux-hosted MCC cache nodes +- ✅ Windows-hosted Connected Cache cache nodes +- ✅ Linux-hosted Connected Cache cache nodes - ✅ Microsoft Connected Cache for Enterprise and Education --- -# Verify MCC cache node functionality +# Verify Connected Cache node functionality -This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCC) cache node is functioning correctly. +This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education cache node is functioning correctly. -These steps should be taken after deploying MCC caching software to a [Windows](mcc-ent-deploy-to-windows.md) or [Linux](mcc-ent-deploy-to-linux.md) host machine. +These steps should be taken after deploying Connected Cache software to a [Windows](mcc-ent-deploy-to-windows.md) or [Linux](mcc-ent-deploy-to-linux.md) host machine. -## Steps to verify functionality of MCC cache node +## Steps to verify functionality of Connected Cache node -1. To verify that the MCC container on the host machine is running and reachable, run the following command from the host machine: +1. To verify that the Connected Cache container on the host machine is running and reachable, run the following command from the host machine: ```powershell wget http://localhost/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com @@ -30,13 +30,13 @@ These steps should be taken after deploying MCC caching software to a [Windows]( If successful, there should be an HTTP response with StatusCode 200. -1. To verify that Windows clients in your network can reach the MCC cache node, visit the following address from a web browser on a Windows client device: +1. To verify that Windows clients in your network can reach the Connected Cache node, visit the following address from a web browser on a Windows client device: `http://[HostMachine-IP-address]/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com` - If successful, the Windows client device should begin to download a small image file from the MCC cache node. + If successful, the Windows client device should begin to download a small image file from the Connected Cache node. -1. To check how much content an individual Windows client has pulled from an MCC cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device. +1. To check how much content an individual Windows client has pulled from an Connected Cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device. You should see a donut chart titled Download Statistics. If the Windows client has pulled content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server". From 3a8faa199f352f3a86a0d829b8b4267cbdf2207b Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 24 Oct 2024 18:06:53 -0700 Subject: [PATCH 06/16] Added steps to point clients at nodes --- windows/deployment/do/mcc-ent-deploy-to-linux.md | 6 ++++++ windows/deployment/do/mcc-ent-deploy-to-windows.md | 6 ++++++ 2 files changed, 12 insertions(+) diff --git a/windows/deployment/do/mcc-ent-deploy-to-linux.md b/windows/deployment/do/mcc-ent-deploy-to-linux.md index 8385641122..d674b4e504 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-linux.md +++ b/windows/deployment/do/mcc-ent-deploy-to-linux.md @@ -49,6 +49,12 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the sudo ./provisionmcc.sh customerid="enter mccResourceId here" cachenodeid=" enter cacheNodeId here " customerkey=" enter customerKey here " registrationkey="enter registrationKey here" drivepathandsizeingb="enter physicalPath value,enter sizeInGb value here" shoulduseproxy="enter true if present, enter false if not" proxyurl=http://enter proxy hostname:enter port ``` +## Steps to point Windows client devices at Connnected Cache node + +Once you have successfully deployed Connected Cache to your Linux host machine, you will need to configure your Windows client device(s) to request Microsoft content from the Connected Cache node. + +You can do this by setting the [DOCacheHost or DOCacheHostSource policies via Intune](./waas-delivery-optimization-reference.md#cache-server-hostname). + ## Next step > [!div class="nextstepaction"] diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md index 68720ee8fa..68077a256f 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-windows.md +++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md @@ -59,6 +59,12 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the ./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid [enter mccResourceId here] -cachenodeid [enter cacheNodeId here] -customerkey [enter customerKey here] -registrationkey [enter registration key] -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy [enter true if present, enter false if not] -proxyurl "http://[enter proxy host name]:[enter port]" -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential ``` +## Steps to point Windows client devices at Connnected Cache node + +Once you have successfully deployed Connected Cache to your Windows host machine, you will need to configure your Windows client device(s) to request Microsoft content from the Connected Cache node. + +You can do this by setting the [DOCacheHost or DOCacheHostSource policies via Intune](./waas-delivery-optimization-reference.md#cache-server-hostname). + ## Next step > [!div class="nextstepaction"] From bc236e351bcb7356dd6e1664e33423f35865af82 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 24 Oct 2024 18:07:09 -0700 Subject: [PATCH 07/16] Fixed formatting on overview page --- windows/deployment/do/mcc-ent-edu-overview.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-edu-overview.md b/windows/deployment/do/mcc-ent-edu-overview.md index 11ce424a3d..59c0cd45ae 100644 --- a/windows/deployment/do/mcc-ent-edu-overview.md +++ b/windows/deployment/do/mcc-ent-edu-overview.md @@ -19,7 +19,7 @@ ms.date: 05/09/2023 # Microsoft Connected Cache for Enterprise and Education Overview > [!IMPORTANT] -> - Microsoft Connected Cache is currently a preview feature. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). +> Microsoft Connected Cache is currently a preview feature. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). Microsoft Connected Cache for Enterprise and Education (preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. Connected Cache can be managed from an Azure portal or through Azure CLI and can be deployed to as many Windows devices, Linux devices, or VMs as needed. Managed Windows devices can be configured to download cloud content from a Connected Cache server by applying the client policy using management tools such as Intune. @@ -68,6 +68,7 @@ See [Connected Cache node host machine requirements](mcc-ent-prerequisites.md) f |Medium to Large Enterprises/Autopilot Provisioning Center (500 - 5,000 devices in a single location) |5 - 101 Gbps Peak| 9 Gbps => 32,400 GB

5 Gbps => 18,000 GB

3 Gbps => 10,800 GB| ## Supported content types + When clients download cloud-managed content, they use Delivery Optimization from the cache server installed on a Windows server or VM. Cloud-managed content includes the following types: - Windows updates: Windows feature and quality updates From 53de6a1d482be5fb684db5fab5b8a08bcc16a5a5 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 24 Oct 2024 18:07:28 -0700 Subject: [PATCH 08/16] Fixed formatting on troubleshooting and update pages --- windows/deployment/do/mcc-ent-troubleshooting.md | 5 +++-- windows/deployment/do/mcc-ent-update-cache-node.md | 2 ++ 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md index c7e47ea564..ac83190e31 100644 --- a/windows/deployment/do/mcc-ent-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -29,11 +29,12 @@ This article contains instructions on how to troubleshoot different issues you m Connected Cache Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields. ## Troubleshooting cache node issue + If you are facing issues with your cache node, it could be due to cache node being on the early preview version of Connected Cache. Cache nodes belonging to early preview version will be under Connected Cache resource that will have 'early preview' in its name. Please delete these cache nodes and associated Connected Cache resource and create a new Connected Cache resource on the new version. For detailed instructions on creating Connected Cache resource, see [Create Connected Cache Azure resources](mcc-ent-create-resource-and-cache.md) - ## Troubleshooting cache node deployment + TODO: Add introduction sentence(s) [Include a sentence or two to explain only what is needed to complete the procedure.] TODO: Add ordered list of procedure steps @@ -43,6 +44,7 @@ TODO: Add ordered list of procedure steps 1. Step 3 ## Troubleshooting cache node monitoring + TODO: Add introduction sentence(s) [Include a sentence or two to explain only what is needed to complete the procedure.] TODO: Add ordered list of procedure steps @@ -67,7 +69,6 @@ You can find **Diagnose and solve problems** on the left pane within your Connec Within **Diagnose and solve problems**, select **Troubleshoot** under the type of problem you're facing and follow the prompts that narrow down the solution to the issue. - ## Filing a support request TODO: Add steps for filling out a CSS ticket. diff --git a/windows/deployment/do/mcc-ent-update-cache-node.md b/windows/deployment/do/mcc-ent-update-cache-node.md index 960f2a289d..da724f7627 100644 --- a/windows/deployment/do/mcc-ent-update-cache-node.md +++ b/windows/deployment/do/mcc-ent-update-cache-node.md @@ -31,9 +31,11 @@ In other words, configuring cache nodes to update as part of the Slow ring provi >In the event of a critical security patch, Microsoft may elect to initiate an Connected Cache update to your cache node as soon as possible (even if the cache node has been set to the Slow Ring). Visit the [Release notes](mcc-ent-release-notes.md) page for a detailed changelog of each Connected Cache update. #### Fast Ring + All Connected Cache nodes are configured to update as part of the Fast ring by default. Connected Cache nodes in the Fast ring will be updated soon after an update is made available. Microsoft will silently update cache nodes at a time of day when update traffic is likely to be minimal, such as 3:00 AM (local time) on Saturday. #### Slow Ring + Configuring an Connected Cache node to update as part of the Slow ring provides users with the option to delay Connected Cache software updates until the update can be validated. There are three settings that control when Connected Cache updates will be applied to Connected Cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI. | Setting | Description | From a3418e7c6ba2477f6443c9a0a1f492599af77357 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 24 Oct 2024 19:39:33 -0700 Subject: [PATCH 09/16] Acrolinx fixes --- .../deployment/do/mcc-ent-deploy-to-linux.md | 4 +- .../do/mcc-ent-deploy-to-windows.md | 6 +- windows/deployment/do/mcc-ent-edu-overview.md | 32 +++++----- .../deployment/do/mcc-ent-manage-using-cli.md | 4 +- windows/deployment/do/mcc-ent-monitoring.md | 59 +++++++++---------- .../deployment/do/mcc-ent-prerequisites.md | 6 +- .../deployment/do/mcc-ent-release-notes.md | 2 +- .../deployment/do/mcc-ent-troubleshooting.md | 2 +- .../do/mcc-ent-uninstall-cache-node.md | 2 +- .../do/mcc-ent-update-cache-node.md | 10 ++-- .../do/mcc-ent-verify-cache-node.md | 4 +- 11 files changed, 65 insertions(+), 66 deletions(-) diff --git a/windows/deployment/do/mcc-ent-deploy-to-linux.md b/windows/deployment/do/mcc-ent-deploy-to-linux.md index d674b4e504..4b3db901c2 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-linux.md +++ b/windows/deployment/do/mcc-ent-deploy-to-linux.md @@ -49,9 +49,9 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the sudo ./provisionmcc.sh customerid="enter mccResourceId here" cachenodeid=" enter cacheNodeId here " customerkey=" enter customerKey here " registrationkey="enter registrationKey here" drivepathandsizeingb="enter physicalPath value,enter sizeInGb value here" shoulduseproxy="enter true if present, enter false if not" proxyurl=http://enter proxy hostname:enter port ``` -## Steps to point Windows client devices at Connnected Cache node +## Steps to point Windows client devices at Connected Cache node -Once you have successfully deployed Connected Cache to your Linux host machine, you will need to configure your Windows client device(s) to request Microsoft content from the Connected Cache node. +Once you have successfully deployed Connected Cache to your Linux host machine, you'll need to configure your Windows client devices to request Microsoft content from the Connected Cache node. You can do this by setting the [DOCacheHost or DOCacheHostSource policies via Intune](./waas-delivery-optimization-reference.md#cache-server-hostname). diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md index 68077a256f..d219734b31 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-windows.md +++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md @@ -53,15 +53,15 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`. -1. Replace the values in the following provisioning command before running it on the host machine. Note that `-mccLocalAccountCredential $myLocalAccountCredential` is only needed if you are using a Local User account as the Connected Cache runtime account. +1. Replace the values in the following provisioning command before running it on the host machine. Note that `-mccLocalAccountCredential $myLocalAccountCredential` is only needed if you're using a Local User account as the Connected Cache runtime account. ```powershell-interactive ./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid [enter mccResourceId here] -cachenodeid [enter cacheNodeId here] -customerkey [enter customerKey here] -registrationkey [enter registration key] -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy [enter true if present, enter false if not] -proxyurl "http://[enter proxy host name]:[enter port]" -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential ``` -## Steps to point Windows client devices at Connnected Cache node +## Steps to point Windows client devices at Connected Cache node -Once you have successfully deployed Connected Cache to your Windows host machine, you will need to configure your Windows client device(s) to request Microsoft content from the Connected Cache node. +Once you have successfully deployed Connected Cache to your Windows host machine, you'll need to configure your Windows client devices to request Microsoft content from the Connected Cache node. You can do this by setting the [DOCacheHost or DOCacheHostSource policies via Intune](./waas-delivery-optimization-reference.md#cache-server-hostname). diff --git a/windows/deployment/do/mcc-ent-edu-overview.md b/windows/deployment/do/mcc-ent-edu-overview.md index 59c0cd45ae..64d059bc58 100644 --- a/windows/deployment/do/mcc-ent-edu-overview.md +++ b/windows/deployment/do/mcc-ent-edu-overview.md @@ -4,9 +4,9 @@ description: Overview, supported scenarios, and content types for Microsoft Conn ms.service: windows-client ms.subservice: itpro-updates ms.topic: conceptual -ms.author: carmenf -author: cmknox -manager: aaroncz +ms.author: andyriv +author: chrisjlin +manager: naengler ms.reviewer: mstewart ms.collection: tier3 appliesto: @@ -35,27 +35,27 @@ Microsoft Connected Cache for Enterprise and Education (preview) is intended to - Co-managed clients that get monthly updates and Win32 apps from Microsoft Intune - Cloud-only managed devices, such as Intune-enrolled devices without the Configuration Manager client, that get monthly updates and Win32 apps from Microsoft Intune -Microsoft Connected Cache is built for flexible deployments to support a number of enterprise configurations: +Microsoft Connected Cache is built for flexible deployments to support several different enterprise configurations: ### Branch office -Customers may have globally dispersed offices that meet the following parameters: +Customers may have globally dispersed offices that meet some or all of the following parameters: -- 10 – 50 Windows Clients -- No dedicated server hardware -- Internet bandwidth is great to limited (satellite internet) -- Possibly intermittent connectivity +- Have 10 – 50 Windows devices on-site +- Don't have dedicated server hardware +- Have Internet bandwidth that is limited (satellite internet) +- Have intermittent Internet connectivity To support the branch office scenario, customers can deploy a Connected Cache node to a Windows 11 client device. ### Large Enterprise -Customers may have office spaces, data centers, or Azure deployments that meet the following parameters: +Customers may have office spaces, data centers, or Azure deployments that meet some or all of the following parameters: -- 100's or 1,000's of Windows devices (client or server). -- Existing hardware – Decommissioned DP, file server, cloud print server -- Azure VMs and Azure Virtual Desktop -- Internet bandwidth is great to limited (T1) +- Have 100s or 1,000s of Windows devices (desktop or server) +- Have some existing server hardware (Decommissioned Distribution Point, file server, cloud print server) +- Have Azure VMs and/or Azure Virtual Desktop deployed +- Have Internet bandwidth that is mediocre (T1 or T3 lines) To support the large enterprise scenario, customers can deploy a Connected Cache node to a server running Windows Server 2022 or Ubuntu 22.04. @@ -88,8 +88,8 @@ The following diagram displays an overview of how Connected Cache functions: 1. Prepare Windows or Linux devices. If deploying to Windows devices, prepare accounts - gMSA, local user account, domain account. Deploy to Windows or Linux devices using scripts. 1. The Microsoft Connected Cache container is deployed to the device using Azure IoT Edge container management services and the cache server begins reporting status and metrics to Delivery Optimization services. 1. The DOCacheHost setting is configured using Intune or other MDM, DHCP custom option, or registry key. -1. Devices request content from the cache server, the cache server forwards the requests to the CDN and fills the cache, the cache server delivers the content requested to the devices, and uses Peer to Peer (depending on DO Download mode settings) for all DO content. -1. Devices can fallback to CDN if cache server is unavailable for any reason or use Delivery Optimization delay fallback to http (CDN )settings to prefer the local cache server. +1. Devices request content from the cache server, the cache server forwards the requests to the CDN and fills the cache, the cache server delivers the content requested to the devices, and uses Peer to Peer (depending on DO Download mode settings) for all DO content. +1. Devices can fall back to CDN if cache server is unavailable for any reason or use Delivery Optimization delay fallback to http (CDN) settings to prefer the local cache server. Customers can view data regarding Microsoft Connected Cache downloads on management portal and Windows Update for Business reports ## Next steps diff --git a/windows/deployment/do/mcc-ent-manage-using-cli.md b/windows/deployment/do/mcc-ent-manage-using-cli.md index 6faca3726f..de3cddce1f 100644 --- a/windows/deployment/do/mcc-ent-manage-using-cli.md +++ b/windows/deployment/do/mcc-ent-manage-using-cli.md @@ -31,7 +31,7 @@ This article outlines how to create, configure, and deploy Microsoft Connected C az extension add --name mcc ``` -To learn more about installting extensions, visit [Install the Connected Cache extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions) +To learn more about installing extensions, visit [Install the Connected Cache extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)

@@ -54,7 +54,7 @@ Once the resource group is created, you'll need to create a Microsoft Connected A Connected Cache Azure resource is a top-level Azure resource under which cache nodes can be created. -To create an Connected Cache Azure resource, use `az mcc ent resource create` +To create a Connected Cache Azure resource, use `az mcc ent resource create` ```azurecli-interactive az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg diff --git a/windows/deployment/do/mcc-ent-monitoring.md b/windows/deployment/do/mcc-ent-monitoring.md index 2fb8a62181..060afcf66f 100644 --- a/windows/deployment/do/mcc-ent-monitoring.md +++ b/windows/deployment/do/mcc-ent-monitoring.md @@ -16,77 +16,76 @@ ms.date: 09/04/2024 # Monitor cache node usage -Tracking the status of your Connected Cache node is essential to making sure you are getting the most out of the service. +Tracking the status and performance of your Connected Cache node is essential to making sure you're getting the most out of the service. -For basic monitoring, navigate to the "Overview" tab. Here you will be able to view a cache node summary dashboard and charts for key metrics. No additional work is necessary, all the monitoring in this section will function right after your Connected Cache node has been installed. +For basic monitoring, navigate to the "Overview" tab. Here you'll be able to view a collection of predefined metrics and charts. All the monitoring in this section will function right after your Connected Cache node has been deployed. -For advanced monitoring, navigate to the "Metrics" section under the "Monitoring" tab. Here you will be able to access more sampled metrics (hits, misses, inbound traffic) and specify different aggregations (count, avg, min, max, sum). You can then use this data to create customized dashboards and configure alerts. Overall, this section is designed to cater to your specific monitoring needs and preferences. +For advanced monitoring, navigate to the "Metrics" section under the "Monitoring" tab. Here you'll be able to access more sampled metrics (hits, misses, inbound traffic) and specify different aggregations (count, avg, min, max, sum). You can then use this data to create customized charts and configure alerts. -Between the two monitoring sections, you will be able to gather essential insights into the health, performance, and efficiency of your Connected Cache nodes. +Between the two monitoring sections, you'll be able to gather essential insights into the health, performance, and efficiency of your Connected Cache nodes. ## Basic Monitoring ### Cache node summary -The preset monitoring data for Connected Cache is displayed on the Overview page in the Azure portal. Below are the metrics you will find in the "Cache Node Summary" dashboard, along with their descriptions. Please take note that this dashboard only reflects data from all cache nodes the last 24 hours. The filters that are displayed below the dashboard only affect the data shown in the "Key Metrics" charts. +Below are the metrics you'll find in the "Cache Node Summary" dashboard, along with their descriptions. This dashboard only reflects data received from cache nodes in the last 24 hours. - ![Screenshot of cache node summary in the Azure portal interface.](../images/mcc-ent-cache-node-summary.png) | Metric | Description | | --- | --- | -| Healthy nodes | Your Connected Cache node will frequently send heartbeat messages to our backend. If your node has responded in the last 24 hours, it will be labeled as healthy. | -| Unhealthy nodes | If your node has not sent a heartbeat message in the last 24 hours, it will be labeled as unhealthy. | -| Max in | The maximum ingress in Mbps (Megabits per second) that your node has pulled from CDN in the last 24 hours. | -| Max out | The minimum egress in Mbps that your node has pushed out to devices in your network over the last 24 hours. | -| Average in | The average ingress in Mbps that your node has pulled from CDN in the last 24 hours. | -| Average out | The average egress in Mbps that your node has pushed out to devices in your network over the last 24 hours. | -| Cache efficiency | The percentage of all content requests your Connected Cache node receives that are ultimately delivered by your Connected Cache node. An well-performing node should have an efficiency > 90%. | +| Healthy nodes | Your Connected Cache node will periodically send heartbeat messages to the Connected Cache service. If the Connected Cache service has received a heartbeat message from your Connected Cache node in the last 24 hours, the node will be labeled as healthy. | +| Unhealthy nodes | If the Connected Cache service hasn't received a heartbeat message from your Connected Cache node in the last 24 hours, the node will be labeled as unhealthy. | +| Max in | The maximum ingress in Megabits per second (Mbps) that your node has pulled from CDN endpoints in the last 24 hours. | +| Max out | The minimum egress in Mbps that your node has sent to Windows devices in its network over the last 24 hours. | +| Average in | The average ingress in Mbps that your node has pulled from CDN endpoints in the last 24 hours. | +| Average out | The average egress in Mbps that your node has sent to Windows devices in its network over the last 24 hours. | +| Cache efficiency | The percentage of all content requests your Connected Cache node receives that can be fulfilled using your node's cached content. A well-performing node should have an efficiency > 90%. | -### Key Metrics +### Key metric charts -The two monitoring charts on the Overview page more visually represent the usage of your Connected Cache node, as well as the types cached content delivered by your node over various time intervals. +The two predefined charts on the Overview page visually represent the egress and types of content served by your Connected Cache node. The filters that are displayed below the cache node summary dashboard only affect the data shown in the key metric charts. - ![Screenshot of key metric charts in the Azure portal interface.](../images/mcc-ent-key-metric-charts.png) #### Filters -Both filters displayed will only impact the data shown in the 2 charts below. +There are two filter controls that can be used to configure the key metric charts. - - By time: View data from the last 1 hour to 30 days - - By cache node: View data from individual cache nodes or the sum of all your active Connected Cache nodes. +- Timespan: Select how far back the chart should display +- Cache nodes: Select which Connected Cache nodes the chart should display data for #### Outbound Traffic Chart -This chart displays the egress in Mbps that your Connected Cache node was delivering at specific timestamps. The value in the chart's key represents the average egress over the specified time period. +This chart displays the average egress in bits per second (b/s) that your selected Connected Cache nodes delivered over the specified timespan. #### Volume by Content Type -This chart displays the amount (in GB) of each supported content type that your Connected Cache node is delivering at specific timestamps. You can find the complete list of supported content types here: [Microsoft Connected Cache content and services endpoints | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/delivery-optimization-endpoints) +This chart displays the volume of each supported content type in bytes (B) that your selected Connected Cache nodes delivered over the specified timespan. See [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md) for a complete list of supported content types. -The content types in the key are sorted from highest to lowest volume an each have a distinct color. The bar chart is stacked such that you can visually compare total volume being delivered at different timestamps +The content types displayed in the chart each have a distinct color and are sorted in descending order of volume. The bar chart is stacked such that you can visually compare total volume being delivered at different points in time. ## Advanced Monitoring -To expand upon the metrics shown in the Overview tab, navigate to the "Metrics" tab in the left side toolbar of Azure Portal. +To expand upon the metrics shown in the Overview tab, navigate to the "Metrics" tab in the left side toolbar of Azure portal. -Listed below are the additional metrics you can access in this section: +Listed below are the metrics you can access in this section: | Metric | Description | | --- | --- | | Inbound | The number of content requests your Connected Cache node receives over a specified period of time. | | Hits | The number of times your Connected Cache node fulfills a content request by pulling from its cache. | -| Misses | The number of times your Connected Cache node is not able to fulfill a content request by pulling from its cache | +| Misses | The number of times your Connected Cache node isn't able to fulfill a content request by pulling from its cache | ### Customizable Dashboards -Once you select the charts you would like to track, you can save them over to a personalized dashboard. This dashboard enables you to configure the chart title, filters, range, legend, and more. You can also use this personalized dashboard to set up alerts that will notify you if your Connected Cache node dips in performance. +Once you select the charts you would like to track, you can save them to a personalized dashboard. You can configure the chart title, filters, range, legend, and more. You can also use this personalized dashboard to set up alerts that will notify you if your Connected Cache node dips in performance. -Some scenarios where you would want to set up these alerts: - • My Connected Cache node is being shown as unhealthy and I want to know exactly when it stopped egressing last. -A new Xbox update just released last night and I want to know if my Connected Cache node is helping deliver this content to my client machines. +Some example scenarios where you would want to set up a custom alert: + +- My Connected Cache node is being shown as unhealthy and I want to know exactly when it stopped egressing last +- A new Microsoft Word update was released last night and I want to know if my Connected Cache node is helping deliver this content to my Windows devices ## Additional Metrics -Once the content has left the Connected Cache node, the node cannot track whether the content has successfully been delivered to the requesting Windows client. To access client-side data, you can refer to this page: [Monitor Delivery Optimization | Microsoft Learn](https://learn.microsoft.com/en-us/windows/deployment/do/waas-delivery-optimization-monitor) \ No newline at end of file +Your Connected Cache node can keep track of how much content has been sent to requesting Windows devices, but the node can't track whether the content was successfully received by the device. For more information on accessing client-side data from your Windows devices, see [Monitor Delivery Optimization](waas-delivery-optimization-monitor.md). diff --git a/windows/deployment/do/mcc-ent-prerequisites.md b/windows/deployment/do/mcc-ent-prerequisites.md index 95765edf54..5a8de5dc85 100644 --- a/windows/deployment/do/mcc-ent-prerequisites.md +++ b/windows/deployment/do/mcc-ent-prerequisites.md @@ -25,7 +25,7 @@ This article details the requirements and recommended specifications for using M The Azure resources used for Connected Cache will be free to you during this public preview. -- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an Connected Cache node. +- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from a Connected Cache node. - [Windows Enterprise E3 or E5](/windows/whats-new/windows-licensing#windows-11-enterprise), included in [Microsoft 365 F3, E3, or E5](https://www.microsoft.com/microsoft-365/enterprise/microsoft365-plans-and-pricing?msockid=32c407b43d5968050f2b13443c746916) - Windows Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans) @@ -63,11 +63,11 @@ This article details the requirements and recommended specifications for using M ### Recommended host machine hardware specifications -Based on your [enterprise configuration](mcc-ent-edu-overview.md), it is recommended to deploy your Connected Cache nodes to host machines that meet the following recommended hardware specifications. +Based on your [enterprise configuration](mcc-ent-edu-overview.md), it's recommended to deploy your Connected Cache nodes to host machines that meet the following recommended hardware specifications. | | Branch Office | Small Enterprise | Large Enterprise | | --- | --- | --- | --- | | CPU cores | 4 | 8 | 16 | -| Memory | 8 GB, 4GB free | 16 GB, 4GB free | 32 GB, 4GB free | +| Memory | 8 GB, 4 GB free | 16 GB, 4 GB free | 32 GB, 4 GB free | | Disk storage | 100 GB free | 500 GB free | 2x 200-500 GB free | | NIC | 1 Gbps | 5 Gbps | 10 Gbps | diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index 9fd4a23d38..aa3cdec687 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -26,7 +26,7 @@ This article contains details about the latest releases of Connected Cache. Sinc - Contains client changes - Affects Linux, Windows host machines -### Changenotes +### Change notes - Added new "Outbound egress" and "Volume by Content type" monitoring charts to Azure portal user interface - Added ability to create custom monitoring charts under the Metrics tab in the Azure portal user interface diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md index ac83190e31..4ca009c4d8 100644 --- a/windows/deployment/do/mcc-ent-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -30,7 +30,7 @@ Connected Cache Azure resource creation can be initiated using either the Azure ## Troubleshooting cache node issue -If you are facing issues with your cache node, it could be due to cache node being on the early preview version of Connected Cache. Cache nodes belonging to early preview version will be under Connected Cache resource that will have 'early preview' in its name. Please delete these cache nodes and associated Connected Cache resource and create a new Connected Cache resource on the new version. +If you're facing issues with your cache node, it could be due to cache node being on the early preview version of Connected Cache. Cache nodes belonging to early preview version will be under Connected Cache resource that will have 'early preview' in its name. Please delete these cache nodes and associated Connected Cache resource and create a new Connected Cache resource on the new version. For detailed instructions on creating Connected Cache resource, see [Create Connected Cache Azure resources](mcc-ent-create-resource-and-cache.md) ## Troubleshooting cache node deployment diff --git a/windows/deployment/do/mcc-ent-uninstall-cache-node.md b/windows/deployment/do/mcc-ent-uninstall-cache-node.md index 07c4678b1e..3ca253488b 100644 --- a/windows/deployment/do/mcc-ent-uninstall-cache-node.md +++ b/windows/deployment/do/mcc-ent-uninstall-cache-node.md @@ -14,7 +14,7 @@ appliesto: ms.date: 09/27/2024 --- -# Uninstall Connected Cache caching software from a host machine +# Uninstall Connected Cache software from a host machine This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal. diff --git a/windows/deployment/do/mcc-ent-update-cache-node.md b/windows/deployment/do/mcc-ent-update-cache-node.md index da724f7627..2528e132b5 100644 --- a/windows/deployment/do/mcc-ent-update-cache-node.md +++ b/windows/deployment/do/mcc-ent-update-cache-node.md @@ -36,25 +36,25 @@ All Connected Cache nodes are configured to update as part of the Fast ring by d #### Slow Ring -Configuring an Connected Cache node to update as part of the Slow ring provides users with the option to delay Connected Cache software updates until the update can be validated. There are three settings that control when Connected Cache updates will be applied to Connected Cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI. +Configuring a Connected Cache node to update as part of the Slow ring provides users with the option to delay Connected Cache software updates until the update can be validated. There are three settings that control when Connected Cache updates will be applied to Connected Cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI. | Setting | Description | | --- | --- | -| Week of the month | 1st to 4th week can be selected. There are three to four months in a year that could have a 5th week. If there's a 5th week, the update could be applied during that 5th week if the day of the week falls near the last day of the month.| +| Week of the month | 1st to 4th week can be selected. There are three to four months in a year that could have a fifth week. If there's a fifth week, the update could be applied during that fifth week if the day of the week falls near the last day of the month.| | Day of the week | Monday through Sunday can be selected. | | Time of day | Time of day is based on UTC and a 24 hour clock. | ## Update process -When Microsoft publishes an Connected Cache update, the Connected Cache service attempts to update all Connected Cache nodes based on their Update Ring membership. If a cache node can't complete the silent Connected Cache update within 6 hours of starting, an error message is surfaced in the Azure portal. +When Microsoft publishes a Connected Cache update, the Connected Cache service attempts to update all Connected Cache nodes based on their Update Ring membership. If a cache node can't complete the silent Connected Cache update within 6 hours of starting, an error message is surfaced in the Azure portal. ## Update terminology, criteria, and SLA -Connected Cache updates will be released based on need instead of on a set cadence. +Connected Cache updates are released based on need instead of on a set cadence. | Update type | Criteria and SLA | | --- | --- | -| Security | Security updates are the highest priority and will be released based on the severity rating of the vulnerability. [Critical and High](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 60 days of discovery. [Medium and Low](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 120 days | +| Security | Security updates are the highest priority and are released based on the severity rating of the vulnerability. Patches for [Critical and High](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities are released by Microsoft within 60 days of discovery. Patches for [Medium and Low](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities are released by Microsoft within 120 days. | | Quality | Quality updates fix a specific problem and addresses a noncritical, non-security-related bug. Quality updates could include performance fixes for a specific problem or changes related to cache efficiency or maximum egress for example. Quality updates are released along with security updates or when necessary to ensure proper functioning of the Microsoft Connected Cache software. | For information on all released Microsoft Connected Cache updates, see the [Connected Cache release notes](mcc-ent-release-notes.md). diff --git a/windows/deployment/do/mcc-ent-verify-cache-node.md b/windows/deployment/do/mcc-ent-verify-cache-node.md index c190dbf048..cd55655189 100644 --- a/windows/deployment/do/mcc-ent-verify-cache-node.md +++ b/windows/deployment/do/mcc-ent-verify-cache-node.md @@ -36,9 +36,9 @@ These steps should be taken after deploying Connected Cache software to a [Windo If successful, the Windows client device should begin to download a small image file from the Connected Cache node. -1. To check how much content an individual Windows client has pulled from an Connected Cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device. +1. To check how much content an individual Windows client has downloaded from a Connected Cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device. - You should see a donut chart titled Download Statistics. If the Windows client has pulled content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server". + You should see a donut chart titled Download Statistics. If the Windows client has downloaded content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server". ## Related content From 6ac3041bf041d07fb9999f41c7e684461950fcab Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 24 Oct 2024 22:17:42 -0700 Subject: [PATCH 10/16] Additions to troubleshooting page --- .../deployment/do/mcc-ent-troubleshooting.md | 85 +++++++++++-------- 1 file changed, 51 insertions(+), 34 deletions(-) diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md index 4ca009c4d8..3abfe22572 100644 --- a/windows/deployment/do/mcc-ent-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -17,7 +17,7 @@ ms.date: 09/27/2024 # Troubleshoot Microsoft Connected Cache for Enterprise and Education -This article contains instructions on how to troubleshoot different issues you may encounter while using Connected Cache. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [Connected Cache Azure resource creation](mcc-ent-create-resource-and-cache.md). +This article contains instructions on how to troubleshoot different issues you may encounter while using Connected Cache. These issues are categorized by the task in which they may be encountered. ## Steps to obtain an Azure subscription ID @@ -26,49 +26,66 @@ This article contains instructions on how to troubleshoot different issues you m ## Troubleshooting Azure resource creation -Connected Cache Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields. +[Connected Cache Azure resource creation](mcc-ent-create-resource-and-cache.md) can be initiated using either the Azure portal user interface or the Azure CLI command set. -## Troubleshooting cache node issue +If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields during the resource creation process. -If you're facing issues with your cache node, it could be due to cache node being on the early preview version of Connected Cache. Cache nodes belonging to early preview version will be under Connected Cache resource that will have 'early preview' in its name. Please delete these cache nodes and associated Connected Cache resource and create a new Connected Cache resource on the new version. -For detailed instructions on creating Connected Cache resource, see [Create Connected Cache Azure resources](mcc-ent-create-resource-and-cache.md) +## Troubleshooting cache node configuration -## Troubleshooting cache node deployment +[Configuration of your Connected Cache node](mcc-ent-create-resource-and-cache.md) can be done using either the Azure portal user interface or the Azure CLI command set. -TODO: Add introduction sentence(s) -[Include a sentence or two to explain only what is needed to complete the procedure.] -TODO: Add ordered list of procedure steps +If you're encountering a validation error, check that you have filled out all required configuration fields. -1. Step 1 -1. Step 2 -1. Step 3 +If your configuration doesn't appear to be taking effect, check that you have clicked the "Save" button at the top of the configuration page in the Azure portal user interface. + +## Troubleshooting cache nodes created during early preview + +Cache nodes created and deployed during the [Microsoft Connected Cache for Enterprise and Education early preview](mcc-ent-private-preview.md) should continue to function but can no longer be managed or monitored remotely via the Connected Cache Azure service. + +As such, we strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the Connected Cache software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. + +## Troubleshooting cache node deployment to Windows host machine + +[Deploying a Connected Cache node to a Windows host machine](mcc-ent-deploy-to-windows.md) involves running a series of PowerShell scripts contained within the Windows provisioning package. These scripts will attempt to write log files to the installation directory specified in the provisioning command (`C:\mccwsl01\InstallLogs` by default). + +There are three types of installation log files: + +1. **WSL_Mcc_Install_Transcript**: This log file records the lines printed to the PowerShell window when running the installation script +1. **WSL_Mcc_Install_FromRegisteredTask_Status**: This log file records the high level status that is written during the registered tasks install +1. **WSL_Mcc_Install_FromRegisteredTask_Transcript**: This log file records the detailed status that is written during the registered tasks install + +The Registered Task Transcript is usually the most useful for diagnosing the installation issue. + +Once the Connected Cache software has been successfully deployed to the Windows host machine, you can check if the cache node is running properly by doing the following on the Windows host machine: + +1. Launch a PowerShell process as the account specified as the runtime account during the Connected Cache install +1. Run `wsl -d Ubuntu-22.04-Mcc-Base` to access the Linux distribution that hosts the Connected Cache container +1. Run `sudo iotedge list` to show which containers are running within the IoT Edge runtime + +If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs --f`. + +You can also reboot the IoT Edge runtime using `sudo iotedge restart`. + +## Troubleshooting cache node deployment to Linux host machine + +[Deploying a Connected Cache node to a Linux host machine](mcc-ent-deploy-to-linux.md) involves running a series of Bash scripts contained within the Linux provisioning package. + +Once the Connected Cache software has been successfully deployed to the Linux host machine, you can check if the cache node is running properly by doing the following on the Linux host machine: + +1. Run `sudo iotedge list` to show which containers are running within the IoT Edge runtime + +If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs --f`. + +You can also reboot the IoT Edge runtime using `sudo iotedge restart`. ## Troubleshooting cache node monitoring -TODO: Add introduction sentence(s) -[Include a sentence or two to explain only what is needed to complete the procedure.] -TODO: Add ordered list of procedure steps +Connected Cache node status and performance can be [monitored using the Azure portal user interface](mcc-ent-monitoring.md). -1. Step 1 -1. Step 2 -1. Step 3 +If the [basic monitoring](mcc-ent-monitoring.md#basic-monitoring) visuals on the Overview tab are showing unexpected or erroneous values, refresh the browser window. - +If the issue persists, check that you have configured the Timespan and Cache nodes as desired. ## Diagnose and Solve -If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your Connected Cache resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users might face as they onboard. - -You can find **Diagnose and solve problems** on the left pane within your Connected Cache resource. - -Within **Diagnose and solve problems**, select **Troubleshoot** under the type of problem you're facing and follow the prompts that narrow down the solution to the issue. - -## Filing a support request - -TODO: Add steps for filling out a CSS ticket. +You can also use the **Diagnose and solve problems** functionality provided by the Azure portal interface. This tab within the Microsoft Connected Cache Azure resource will walk you through a few prompts to help narrow down the solution to your issue. From 3c506c2708845994da6fe08e785e89b4c697919f Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 24 Oct 2024 22:26:03 -0700 Subject: [PATCH 11/16] Fix broken links --- windows/deployment/do/mcc-ent-create-resource-and-cache.md | 2 +- windows/deployment/do/mcc-ent-faq.yml | 4 ++-- windows/deployment/do/mcc-ent-prerequisites.md | 2 +- windows/deployment/do/mcc-ent-verify-cache-node.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/deployment/do/mcc-ent-create-resource-and-cache.md b/windows/deployment/do/mcc-ent-create-resource-and-cache.md index 3cfc44f9f2..1450c17321 100644 --- a/windows/deployment/do/mcc-ent-create-resource-and-cache.md +++ b/windows/deployment/do/mcc-ent-create-resource-and-cache.md @@ -204,7 +204,7 @@ To deploy the cache node to a **Linux** host machine, see ### [Azure CLI](#tab/cli) To deploy cache nodes using Azure CLI, see >[!div class="nextstepaction"] ->[Manage cache nodes using CLI](mcc-ent-manage-cache-using-CLI.md) +>[Manage cache nodes using CLI](mcc-ent-manage-using-CLI.md) ---
diff --git a/windows/deployment/do/mcc-ent-faq.yml b/windows/deployment/do/mcc-ent-faq.yml index e099a27f79..41fab60818 100644 --- a/windows/deployment/do/mcc-ent-faq.yml +++ b/windows/deployment/do/mcc-ent-faq.yml @@ -65,7 +65,7 @@ sections: - question: How do I set up CLI? answer: For more information, see [How to install the Azure CLI](/cli/azure/install-azure-cli). - question: How do I install the Microsoft Connected Cache Azure CLI extension? - answer: For more information, see [Install the Microsoft Connected Cache extension](mcc-ent-manage-cache-using-cli.md#prerequisites). + answer: For more information, see [Install the Microsoft Connected Cache extension](mcc-ent-manage-using-cli.md#prerequisites). - question: What do I do if I have to set up or change existing proxy? answer: You can enable proxy and provide proxy information on Azure portal or use the CLI. Don't forget to rerun the provisioning script after making any proxy changes. For more information, see [Set up or change existing proxy](mcc-ent-create-resource-and-cache.md#proxy-settings). - question: How do we set up Microsoft Connected Cache if we support multiple countries or regions? @@ -75,4 +75,4 @@ sections: - question: Does the user have to be logged using the account that installed Microsoft Connected Cache on Windows or Linux? answer: No. As part of the installation on Windows a scheduled task is created using the account used to install Connected Cache. Regardless of which user is logged in or not logged in, the scheduled task remains running. On Linux, Connected Cache is installed by the user and remains running regardless of which user is logged in to the OS. - question: What do I do if I need more support and have more questions even after reading this FAQ page? - answer: For further support for Microsoft Connected Cache, see [Troubleshooting issues for Microsoft Connected Cache for Enterprise and Education](mcc-ent-support-and-troubleshooting.md). If you still need more support, you can contact customer support. + answer: For further support for Microsoft Connected Cache, see [Troubleshooting issues for Microsoft Connected Cache for Enterprise and Education](mcc-ent-troubleshooting.md). If you still need more support, you can contact customer support. diff --git a/windows/deployment/do/mcc-ent-prerequisites.md b/windows/deployment/do/mcc-ent-prerequisites.md index 5a8de5dc85..938d52a217 100644 --- a/windows/deployment/do/mcc-ent-prerequisites.md +++ b/windows/deployment/do/mcc-ent-prerequisites.md @@ -65,7 +65,7 @@ This article details the requirements and recommended specifications for using M Based on your [enterprise configuration](mcc-ent-edu-overview.md), it's recommended to deploy your Connected Cache nodes to host machines that meet the following recommended hardware specifications. -| | Branch Office | Small Enterprise | Large Enterprise | +| Component | Branch Office | Small / Medium Enterprise | Large Enterprise | | --- | --- | --- | --- | | CPU cores | 4 | 8 | 16 | | Memory | 8 GB, 4 GB free | 16 GB, 4 GB free | 32 GB, 4 GB free | diff --git a/windows/deployment/do/mcc-ent-verify-cache-node.md b/windows/deployment/do/mcc-ent-verify-cache-node.md index cd55655189..2c63db2453 100644 --- a/windows/deployment/do/mcc-ent-verify-cache-node.md +++ b/windows/deployment/do/mcc-ent-verify-cache-node.md @@ -43,4 +43,4 @@ These steps should be taken after deploying Connected Cache software to a [Windo ## Related content - [Monitor cache node usage](mcc-ent-monitoring.md) -- [Troubleshoot cache node](mcc-ent-support-and-troubleshooting.md) +- [Troubleshoot cache node](mcc-ent-troubleshooting.md) From 649bf7c183fc97333e9645e202950586318c1f6c Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Fri, 25 Oct 2024 14:58:25 -0700 Subject: [PATCH 12/16] Clarified steps + added notes to Windows deployment page --- .../deployment/do/mcc-ent-deploy-to-windows.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md index d219734b31..0c1fee800d 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-windows.md +++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md @@ -26,12 +26,14 @@ Before deploying Connected Cache to a Windows host machine, ensure that the host # [Azure portal](#tab/portal) 1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command. -1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine. +1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine. **Note**: The installer should be in a folder that is not synced to OneDrive, as this will interfere with the installation process. 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run. -1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`. +1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account. - If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`. + For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`. + + If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`. **Note**: You will need to apply a local security policy to permit the Local User account to "Log on as a batch job". 1. Run the provisioning command on the host machine. @@ -49,11 +51,13 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the 1. Download and extract the [Connected Cache provisioning package for Windows](https://aka.ms/MCC-Ent-InstallScript-WSL) to your host machine. 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run. -1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`. +1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account. - If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`. + For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`. -1. Replace the values in the following provisioning command before running it on the host machine. Note that `-mccLocalAccountCredential $myLocalAccountCredential` is only needed if you're using a Local User account as the Connected Cache runtime account. + If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`. **Note**: You will need to apply a local security policy to permit the Local User account to "Log on as a batch job". + +1. Replace the values in the following provisioning command before running it on the host machine. **Note**: `-mccLocalAccountCredential $myLocalAccountCredential` is only needed if you're using a Local User account as the Connected Cache runtime account. ```powershell-interactive ./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid [enter mccResourceId here] -cachenodeid [enter cacheNodeId here] -customerkey [enter customerKey here] -registrationkey [enter registration key] -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy [enter true if present, enter false if not] -proxyurl "http://[enter proxy host name]:[enter port]" -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential From 1f7cae57d94937ec79e43f4c7d6927c81d922339 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Fri, 25 Oct 2024 14:58:46 -0700 Subject: [PATCH 13/16] Added wsl install command to prereqs page --- windows/deployment/do/mcc-ent-prerequisites.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-prerequisites.md b/windows/deployment/do/mcc-ent-prerequisites.md index 938d52a217..1878a73a01 100644 --- a/windows/deployment/do/mcc-ent-prerequisites.md +++ b/windows/deployment/do/mcc-ent-prerequisites.md @@ -45,7 +45,7 @@ This article details the requirements and recommended specifications for using M - Windows 11 must have [OS Build 22631.3296](https://support.microsoft.com/topic/march-12-2024-kb5035853-os-builds-22621-3296-and-22631-3296-a69ac07f-e893-4d16-bbe1-554b7d9dd39b) or later - Windows Server 2022 must have [OS Build 20348.2227](https://support.microsoft.com/topic/january-9-2024-kb5034129-os-build-20348-2227-6958a36f-efaf-4ef5-a576-c5931072a89a) or later - The Windows host machine must support nested virtualization. -- The Windows host machine must have [WSL2 installed](/windows/wsl/install#install-wsl-command). +- The Windows host machine must have [WSL2 installed](/windows/wsl/install#install-wsl-command). You can install this on Windows 11 and Windows Server 2022 by running the PowerShell command `wsl.exe --install --no-distribution`. ### Additional requirements for Linux host machines From 9cd06356e0e7d79745018d83682b6ec0f5ed4046 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Fri, 25 Oct 2024 15:10:02 -0700 Subject: [PATCH 14/16] Added proxy, WSL, scheduled task sections to troubleshooting page --- .../deployment/do/mcc-ent-troubleshooting.md | 33 +++++++++++++++---- 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md index 3abfe22572..b7566354ba 100644 --- a/windows/deployment/do/mcc-ent-troubleshooting.md +++ b/windows/deployment/do/mcc-ent-troubleshooting.md @@ -28,7 +28,7 @@ This article contains instructions on how to troubleshoot different issues you m [Connected Cache Azure resource creation](mcc-ent-create-resource-and-cache.md) can be initiated using either the Azure portal user interface or the Azure CLI command set. -If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields during the resource creation process. +If you're encountering an error during resource creation, check that you have the necessary permissions to create Azure resources under your subscription and have filled out all required fields during the resource creation process. ## Troubleshooting cache node configuration @@ -38,6 +38,8 @@ If you're encountering a validation error, check that you have filled out all re If your configuration doesn't appear to be taking effect, check that you have clicked the "Save" button at the top of the configuration page in the Azure portal user interface. +If you have changed the proxy configuration, you will need to re-provision the Connected Cache software on the host machine for the proxy configuration to take effect. + ## Troubleshooting cache nodes created during early preview Cache nodes created and deployed during the [Microsoft Connected Cache for Enterprise and Education early preview](mcc-ent-private-preview.md) should continue to function but can no longer be managed or monitored remotely via the Connected Cache Azure service. @@ -46,6 +48,8 @@ As such, we strongly recommend you [recreate your existing resources in Azure](m ## Troubleshooting cache node deployment to Windows host machine +### Collecting Windows-hosted installation logs + [Deploying a Connected Cache node to a Windows host machine](mcc-ent-deploy-to-windows.md) involves running a series of PowerShell scripts contained within the Windows provisioning package. These scripts will attempt to write log files to the installation directory specified in the provisioning command (`C:\mccwsl01\InstallLogs` by default). There are three types of installation log files: @@ -56,15 +60,32 @@ There are three types of installation log files: The Registered Task Transcript is usually the most useful for diagnosing the installation issue. +### Updating the WSL2 kernel + +If the Connected Cache installation is failing due to WSL-related issues, try running `wsl.exe --update` to get the latest version of the WSL kernel. + +### Checking if the Connected Cache container is running + Once the Connected Cache software has been successfully deployed to the Windows host machine, you can check if the cache node is running properly by doing the following on the Windows host machine: 1. Launch a PowerShell process as the account specified as the runtime account during the Connected Cache install 1. Run `wsl -d Ubuntu-22.04-Mcc-Base` to access the Linux distribution that hosts the Connected Cache container 1. Run `sudo iotedge list` to show which containers are running within the IoT Edge runtime -If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs --f`. +If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs -- -f`. -You can also reboot the IoT Edge runtime using `sudo iotedge restart`. +You can also reboot the IoT Edge runtime using `sudo systemctl restart iotedge`. + +### Checking Connected Cache scheduled tasks + +Once the Connected Cache container is running, a scheduled task is periodically run under the Connected Cache runtime account to keep WSL from cleaning up the Connected Cache container. + +You can use Task Scheduler on the host machine to check the status of this scheduled task. + +1. Open Task Scheduler on the host machine +1. Navigate to the Active Tasks section and double-click on "MCC_Monitor_Task" +1. Select the scheduled task "MCC_Monitor_Task" +1. Select the "Triggers" tab and confirm that the Status is "Enabled" ## Troubleshooting cache node deployment to Linux host machine @@ -74,9 +95,9 @@ Once the Connected Cache software has been successfully deployed to the Linux ho 1. Run `sudo iotedge list` to show which containers are running within the IoT Edge runtime -If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs --f`. +If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs -- -f`. -You can also reboot the IoT Edge runtime using `sudo iotedge restart`. +You can also reboot the IoT Edge runtime using `sudo systemctl restart iotedge`. ## Troubleshooting cache node monitoring @@ -84,7 +105,7 @@ Connected Cache node status and performance can be [monitored using the Azure po If the [basic monitoring](mcc-ent-monitoring.md#basic-monitoring) visuals on the Overview tab are showing unexpected or erroneous values, refresh the browser window. -If the issue persists, check that you have configured the Timespan and Cache nodes as desired. +If the issue persists, check that you have configured the Timespan and Cache node filters as desired. ## Diagnose and Solve From e0ed22f6c25ed640a4a3a7cee5b2948cfe0c2738 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Fri, 25 Oct 2024 15:11:37 -0700 Subject: [PATCH 15/16] Fix to windows deploy page --- windows/deployment/do/mcc-ent-deploy-to-windows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md index 0c1fee800d..d0b1d06cb5 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-windows.md +++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md @@ -48,7 +48,7 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the ``` 1. Save the resulting output. These values will be passed as parameters within the provisioning command. -1. Download and extract the [Connected Cache provisioning package for Windows](https://aka.ms/MCC-Ent-InstallScript-WSL) to your host machine. +1. Download and extract the [Connected Cache provisioning package for Windows](https://aka.ms/MCC-Ent-InstallScript-WSL) to your host machine. **Note**: The installer should be in a folder that is not synced to OneDrive, as this will interfere with the installation process. 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run. 1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account. From 1545d3a959349c8c7d8b587436c6c92f02ebce14 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Fri, 25 Oct 2024 15:19:17 -0700 Subject: [PATCH 16/16] Acrolinx fixes --- windows/deployment/do/mcc-ent-deploy-to-windows.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md index d0b1d06cb5..34bb04d55a 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-windows.md +++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md @@ -26,14 +26,14 @@ Before deploying Connected Cache to a Windows host machine, ensure that the host # [Azure portal](#tab/portal) 1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command. -1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine. **Note**: The installer should be in a folder that is not synced to OneDrive, as this will interfere with the installation process. +1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine. **Note**: The installer should be in a folder that isn't synced to OneDrive, as this will interfere with the installation process. 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run. 1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`. - If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`. **Note**: You will need to apply a local security policy to permit the Local User account to "Log on as a batch job". + If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`. **Note**: You'll need to apply a local security policy to permit the Local User account to `Log on as a batch job`. 1. Run the provisioning command on the host machine. @@ -48,14 +48,14 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the ``` 1. Save the resulting output. These values will be passed as parameters within the provisioning command. -1. Download and extract the [Connected Cache provisioning package for Windows](https://aka.ms/MCC-Ent-InstallScript-WSL) to your host machine. **Note**: The installer should be in a folder that is not synced to OneDrive, as this will interfere with the installation process. +1. Download and extract the [Connected Cache provisioning package for Windows](https://aka.ms/MCC-Ent-InstallScript-WSL) to your host machine. **Note**: The installer should be in a folder that isn't synced to OneDrive, as this will interfere with the installation process. 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run. 1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`. - If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`. **Note**: You will need to apply a local security policy to permit the Local User account to "Log on as a batch job". + If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`. **Note**: You'll need to apply a local security policy to permit the Local User account to `Log on as a batch job`. 1. Replace the values in the following provisioning command before running it on the host machine. **Note**: `-mccLocalAccountCredential $myLocalAccountCredential` is only needed if you're using a Local User account as the Connected Cache runtime account.