1. Agreement Scenario Discussion Lauren Lo Licensing Operations Specialist

2. Agreement Scenario Discussion Enterprise Program

3. EA Scenario I - Case study An Enterprise 6 customer has an existing enrollment which had expired on 30 th June 2006. What should the customer do in order to renew their contract?

4. EA Scenario I - Solution Based on Enterprise Agreement general T&C, customer can opt to extend for another 12 or 36 months by submitting a RENEWAL FORM with the Channel Price Sheet to APOC within 30 days upon expiration. The CPS will constitute the renewal order.

5. EA Scenario I - Solution Channel Partner can download the Renewal Form from Explore.MS: Explore.MS\Enterprise\Forms\Enterprise Enrollment Renewal Form APAC Complete the renewal form together with the Channel Price Sheet & amendment (if exceed 30 days) and send to APOC. Ensure all the documents are properly signed and PO number is available.

6. EA Scenario I - Solution Ensure to follow up with 3rd year True Up order for additional copies of license usage or Enterprise Update Statement for zero increase at previous enrollment before submitting renewal. Renewal price levels will be reset for each renewal term based upon the total number of qualified desktops as of the date of renewal. The new price level will not change throughout the renewal term.

7. EA Scenario II - Case study Due to expansion, an existing EA customer needs to add additional copies of licenses* to their enrollment and also at the same time, requires to purchase new additional products. How does the customer obtain these additional licenses? * Could be due to increase of desktop count or increase in copies for existing additional products

8. EA Scenario II - Solution Submit the EA True Up order and Additional Order electronically (via MOET). “New Order (NE)” To be used for any additional products not ordered before “True Up (TUP)” To be used for products that have been listed in the True Up table reflected on the CPS, OR For additional copies of products previously purchased via a “New Order”.

9. EA Scenario II - Solution For True Up, customer must determine the increase in copies for each product and place the order promptly. ALWAYS reference to the CPS for part number and program offering when placing order.

10. EA Scenario II - Solution All True Up orders via MOET will be placed on-hold in our internal system for pricing validation. Prices to be applied manually based on CPS. For New Order submission, the price will be applied automatically based on the current month price list (per Explore.MS)

11. EA Scenario II - Solution Checklist when submitting orders via MOET: Order / PO Type True Up Order = TUP New Order = NE Usage Date (Date of software deployment) TUP - impact on the year coverage and pricing NE - respective month pricing from Explore.MS

12. EA Scenario II - Solution Billing Option ONLY Prepayment = PE Agreement Offering Enterprise Product = CUS Additional Product = ACP **Note: It is important that the correct Order / PO type is selected as this will affect the prices

13. Questions?

14. Select Program Agreement Scenario Discussion

15. Select Scenario I - Case study Company X signed an enrollment for 36 months. Start effective date = 1 March 2005 End effective date = 29 February 2008 1st Year term (1-Mar-05 to 28-Feb-06) 2nd Year term (1-Mar-06 to 28-Feb-07) 3rd Year term (1-Mar-07 to 29-Feb-08)

16. Select Scenario I - Case study Input the appropriate usage dates when submitting MOET orders: Submitted Date Product Type Pricelist Month Required PricingUsage Date 15-Apr-05L/SAApr-053 Years Remaining 2-Feb-06L/SAFeb-063 Years Remaining 15-Jun-06L/SAMay-062 Years Remaining 15-Feb-07L/SAFeb-072 Years Remaining 1-Mar-07L/SAMar-071 Year Remaining 29-Feb-08L/SAFeb-081 Year Remaining 15-Mar-08L/SAFeb-081 Year Remaining 16-Mar-08L/SAMar-081 Year Remaining Note: For usage date, you may input a date range (Maximum 1 month) or a single date.

17. Select Scenario I - Solution Submitted Date Product Type Pricelist Month Required PricingUsage Date 15-Apr-05L/SAApr-053 Years RemainingBtw 1-Apr-05 to 30-Apr-05 2-Feb-06 (*)L/SAFeb-063 Years Remaining1-Feb-06 15-Jun-06L/SAMay-062 Years RemainingBtw 1-May-06 to 31-May-06 15-Feb-07 (*)L/SAFeb-072 Years Remaining1-Feb-07 1-Mar-07L/SAMar-071 Year RemainingBtw 1-Mar-07 to 31-Mar-07 29-Feb-08L/SAFeb-081 Year RemainingBtw 1-Feb-08 to 29-Feb-08 15-Mar-08 (**)L/SAFeb-081 Year RemainingBtw 1-Feb-08 to 29-Feb-08 16-Mar-08 (***)L/SAMar-081 Year RemainingRequires Manual Order

18. Select Scenario I - Solution Special Note - Orders with 1 asterisk (*) Though order submitted (e.g. 2-Feb-06) is within the 1st year term, usage date use should be 1-Feb-06 for 3 Yrs Remaining Pricing. Submitted Date = 2-Feb-06 Usage Date = 1-Feb-06 Pricing = 3 Years Remaining Coverage period = Feb-06 to Feb-08 Orders submitted with usage date after the 1st of every month (e.g. 2-Feb-06) will return a coverage period effective the following month (Mar-06 to Feb-08) with 2 Yrs Remaining Pricing.

19. Select Scenario I - Solution Special Note - Orders with 2 asterisk (**) Partners have 15 days grace period to place orders with previous month pricelist or upon anniversary date. Please note that usage date should fall between 1- Feb-08 to 29-Feb-08. Do not use a usage date (e.g. 1-Mar-08 or after) for non-renewal enrollment.

20. Select Scenario I - Solution Special Note - Order with 3 asterisks (***) On the 16th day upon enrollment expiration, all subsequent MOET orders will not be accepted. Partners require to seek assistance from Microsoft Licensing Specialist (LS). LS will review the case and submit for higher approval. Upon receiving approval, send manual order with approval to APLQUEST. Please note that Microsoft may reject the late order if there is insufficient evident to support the case.

21. Select Scenario II - Case study Company Y received a Price Level Review letter due to compliance check. There is at least one pool (e.g. Systems pool) which is at the risk of being re-level (e.g. From level A to Terminated). How do you assist your customer to meet the forecasted level and avoid being re-leveled?

22. Select Scenario II - Case study Some Agreement information: Select Master Start Effective Date = 1 Oct 2005 1st Compliance Anniversary Check Date = 1 Oct 2006 Summary of table in Price Level Review letter:

23. Select Scenario II - Solution Identify the Anniversary check date and which year was being check. 33% = 1 st Yr Check Anniversary Check Date

24. Select Scenario II - Solution Identify which pool have not meet the forecasted level (e.g. Systems pool at level A). Forecast not met

25. Select Scenario II - Solution Identify how many unit points are require to maintain at present level (e.g. Systems pool at level A) Unit Points required

26. Select Scenario II - Solution Advise your customer to submit order before 30 Sept 06 (this is stated in the letter) so that you have at least 15 days grace period to submit order via MOET. Customer to submit order

27. Select Scenario II - Solution End customer will have 45 days to place orders to you upon receipt of the Price Level Review Letter in order to meet compliance for their SELECT forecast (Day range before the compliance check date may varies depending on Master Start Effective Date). Once Microsoft issues the Final Price Adjustment letter (60 days after compliance check date), end user will have another 30 days to place their orders. Note that this 30 days grace period is for end user to place their final backlog of orders before the pool level adjustment is effective. These orders WILL NOT be taken into account for the compliance check.

28. Questions ?

29. CASA Program Agreement Scenario Discussion

30. CASA Scenario I - Case study A Campus 3.4 customer has an existing 12- month coverage which is expiring 31st December 2006. What should the customer do in order to renew their subscription?

31. CASA Scenario I - Solution Based on CASA Agreement 3.4 general T&C, clause 3d & 6, 12-mth (1-year) customer can opt to extend for another 12 months by submitting an order on or before the expiration (i.e. 31st Dec 2006) to the LAR. Extension order should include an updated FTE/Eligible PC count and any changes to the product selections.

32. CASA Scenario I - Solution LAR can download the extension form from Explore.MS.: Explore.MS\Campus\Forms\Campus and School Extension Request Form (APOC) Explore.MS\School\Forms\Campus and School Extension Request Form (APOC) Complete the form and submit to APLQUEST (no signature is required from end customer and partners)

33. CASA Scenario I - Solution Once extension form has been processed, extension order must be submitted through MOET within 30 days from the extension effective start date (i.e. by 31st Jan 2007 for this case study). Expiring 3-year customers CANNOT use the extension form. They need to sign a new Subscription Enrollment*. * Check out for the latest version then

34. CASA Scenario II – Case study An existing school, ABC, has just signed a 36- month School Subscription enrollment effective June 1st, 2006 and purchased Office Pro Qty 300. However, in Nov’ 2006, school XYZ (with 150 eligible PCs) merged under the same school foundation with ABC. How should the ABC School report the additional licenses?

35. CASA Scenario II - Solution Adding into ABC enrollment mid-term to deploy immediately, you need to:- Contact MS Subsidiary for an amendment Submit the amendment to APOC for processing Once the amendment is processed, you will receive email confirmation Submit order via MOET Adding into ABC enrollment at upcoming anniversary i.e. June 1st, 2007 End customer to submit letter or contact MS Subsidiary for an amendment Thereafter, submit anniversary order (including the additional desktops quantity) via MOET.

36. CASA Scenario II - Solution Note: Based on CASA Agreement 3.4 general T&Cs, clause 3c, all software (Applications, Systems and CAL products) is licensed on an Institution-wide basis. What does this mean? E.g. Original Office Pro qty = 300 Office Pro qty from affiliate = 150 Total qty = 450

37. Questions ?

38. Microsoft provides this material solely for informational and marketing purposes. Customers should refer to their agreements for a full understanding of their rights and obligations under Microsoft’s Volume Licensing programs. Microsoft software is licensed, not sold. The value and benefit gained through use of Microsoft software and services may vary by customer. Customers with questions about differences between this material and the agreements should contact their reseller or Microsoft account manager. © 2006 Microsoft Corporation. All rights reserved. Microsoft is a registered trademark of Microsoft Corporation in the United States and/or other countries.