Microsoft Security Technologies

Microsoft Security Technologies

 

Advertisements

Microsoft Cloud Solutions Provider

Microsoft Cloud Solutions Provider

 

The 1-Tier partner is approved by Microsoft and orders seats on behalf of customers directly from Microsoft, rather than through another partner type. To get that relationship, a partner must have a series of capabilities. To qualify for 1-Tier, a partner must be able to bill, provide 24×7 support, do technical integration and handle customer lifecycle management. Microsoft is also looking for partners with a business model around managed services IP and with broad market reach.

There’s also what Microsoft calls a 2-Tier model. In that one, the distributor or companies that were formerly part of the Microsoft Syndication Partner program handle the capabilities with Microsoft. Those partners are called 2-Tier distributors or cloud distributors. They in turn work with the bulk of Microsoft partners, who are the 2-Tier resellers. Depending on a given cloud distributor’s offering, those resellers may still have control over customer billing and may also be able to outsource white-labeled support services to the distributor. For much more detail on the emerging 2-Tier ecosystem, see the related feature in this section.

New investments will vary based on your current practice. Areas to consider:

  • Local tax implications of selling a subscription product versus a service
  • Adjustments to your sales incentive programs to reflect monthly revenue recognition
  • Management of credit risk and collections
  • Ability to transact billing on a monthly and/or annual basis
  • 24/7 end Customer Billing and Technical Support in local language
  • Pass through Microsoft service credits to customer service.  Approved service credits are provided to Partners, and it’s the Partners’ responsibility to pass through these service credits to their affected Customers since they own the Customer billing relationship.

A critical component of the CSP program is that the partner is the first point of contact for a customer support incident. Some types of support that partners are responsible for providing include:

  • Frontline billing and subscription
  • Provisioning
  • Answers to questions
  • Service and software updates
  • Software configuration
  • Performance issues within a partner’s span of control
  • Client connectivity and client desktop
  • Service availability issues within a partner’s span of control

Some types of incidents can be escalated to Microsoft, such as:

  • Supported tasks that are outside the functionality provided with available tools
  • Break/fix — undocumented problems with the service
  • Availability — service not accessible
  • Not operating according to service descriptions
  • Bugs and other irregularities that affect service appearance or operation
  • Large-scale network disruptions
  • Regional, multi-tenant impact

 

 

SPLA for On-Premises Servers – Microsoft’s best kept secret?

SPLA for On-Premises Servers – Microsoft’s best kept secret?

There is much talk about moving your IT into the cloud so you can enjoy the benefits of OPEX.  But what if keeping your servers on-premises still makes sense.  For example:

  • The server has not yet been financially written off
  • The server is still in great shape, but you need updated software
  • Your network bandwidth is not enough for the services you require access to
  • You have contractual or legislative agreements that dictate deployment options
  • You need for quick physical access to the server
  • Etc etc

In these circumstances the most likely response from a software distributor/reseller will be that you need to purchase software through a traditional volume license agreement.  This may be the right answer, however it does lock you into an upfront software purchase cycle.

But what happens if you need the flexibility to adapt to changing circumstances and enjoy a monthly subscription model that allows you to pay-as-you-go and pay-as-you-grow?

Cloud service providers have, for many years, been able to deliver this within their cloud infrastructure, using the Service Provider License Agreement (SPLA). However it was not possible with customer owned hardware deployed in customer premises.

HOWEVER in October 2013 this changed when Microsoft updated the terms of the SPLA.  This now allows your service provider (System integrator, reseller, managed service partner etc) to offer you a Cloud-like consumption model on your existing hardware, deployed in your premises.  This allows you to maximize existing hardware and network investments, within an OPEX model and provides flexibility to adapt to your changing IT needs.  Also by not having to buy licenses upfront you can repurpose you budget into other high value business areas.

What benefits are there with Microsoft SPLA vs Microsoft Open/Select Licensing?

  • Access all the most recent versions of Microsoft software for a standard monthly price. All are available to download, so there is no need to wait to receive physical copies.
  • Pay at the end of the month only for what you have consumed. This allows for minimal startup costs and better cash-flow management.
  • Licensing kept simple: No need for Server and CAL licensing calculation.
    • The per processor and per core model provides an unlimited number of users, access to the server software.  No separate SAL is required.
    • The Subscriber Access License (SAL) model, allocates a license for each unique user or device that is authorised to access the software.  No separate server license is required

So the next time you want to buy any Microsoft license, ask about SPLA and how you can enjoy the benefits of the OPEX way of subscribing and deploying these licenses on your own hardware on your premises

System Center Config Manager 2012 R2 – Windows 2012 R2 OSD Task Sequence

System Center Config Manager 2012 R2 – Windows 2012 R2 OSD Task Sequence

 

 

Desktop Support Escalation Tests

Desktop Support Escalation Tests

Level 1 HelpDesk

  • Document the exact error message and process to replicate the issues with the end user or process

Level 2 Desktop Support

  • Can you replicate the problem
  • Can you replicate the problem with another User Account
  • Can you replicate the problem with another Computer
  • Can you replicate the problem with Elevated privileges
  • Can you reset the Profile
  • Is the problem affecting single user or multiply user

Level 3 Server Support

  • Check all existing Settings
  • Check Eventlogs
  • Google the User error message
  • What has changed

 

Exploiting Unicode Character RTL ‘RIGHT-TO-LEFT OVERRIDE’ (U+202E)

Exploiting Unicode Character ‘RIGHT-TO-LEFT OVERRIDE’ (U+202E)

 

This is one of the easiest exploits to implement in a Microsoft Windows systems. Yet, its impossible to meditate against. This exploit can be used for domain names as well. :- http://unicode.org/reports/tr36/#Bidirectional_Text_Spoofing

 

 

Obfuscating Executables

 

Examples

  • CORP_INVOICE_08.14.2011_Pr.phyldoc.exe, was made to display as CORP_INVOICE_08.14.2011_Pr.phylexe.doc by placing the unicode command for right to left override just before the “d” in “doc”.
  • SexyAlexe.ppt – > SexyAl\xe2\x80\xaetpp.exe
  • SexyAl\xe2\x80\xaetpp.exe
  • SexyAl\u202Etpp.exe
  • \xe2\x80\xaecod.yrammus_evituc\xe2\x80\xad2011.exe
  • \u202Ecod.yrammus_evituc\u202D2011.exe
  • \xe2\x80\xaetpp.stohsnee\xe2\x80\xadfunny.scr
  • \u202Etpp.stohsnee\u202Dfunny.scr

Microsoft Partner Information

Microsoft Partner Information

OSD – Injecting the Windows 7 Kernel Mode Driver Framework (KMDF)

OSD – Injecting the Windows 7 Kernel Mode Driver Framework (KMDF)

  1. Download the Kernel-Mode Driver from http://www.microsoft.com/en-au/download/details.aspx?id=38423
  2. Open the MSU file with 7Zip software kmdf-1.11-Win-6.1-x64.msu and extract to a foldercalled Windows 7 KMDF 1.11
  3. Copy the contents to the OSD Folder location
  4. Identify location of the OSD WIM file
    1. Open ConfigMgr \ Software Library \ Operating Systems \ Operating System Images \ Select the Imaged and Open Properties \ Select Data Source and take note of image path
    2. \OSD\Operating System\Windows 7 Enterprise with Sp1 x64 – WIM only\install.wim
  5. Run Deployment and Imaging Tools Environment with Elevated Administrator Privileges – C:\Windows\system32\cmd.exe /k “C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\DandISetEnv.bat “
  6. DISM.exe /Get-WimInfo /WimFile:C:\test\images\myimage.wim /Index:1
  7. MD E:\Scratch Folder
  8. DISM.exe /Mount-Wim /WimFile:C:\test\images\myimage.wim /index:1
    /MountDir:C:\test\offline
  9. DISM.exe /Image:C:\test\offline /Get-Packages
  10. Dism /image:C:\test\offline /Add-Package /PackagePath:C:\packages\package.cab
  11. dism /get-packages /image e:\scratch
  12. dism /unmount-Image /mountdir E:\Scratch /commit
  13. dism /unmount-wim /mountdir E:\Scratch \wimMount /discard
DISM.exe /Mount-Wim /WimFile:"E:\OSD\Operating System\Windows 7 Enterprise with Sp1 x64 - WIM only\install.wim" /index:1 /MountDir:E:\Scratch
DISM.exe /Image:E:\Scratch /Get-Packages
Dism /Image:E:\Scratch /Add-Package /PackagePath:"E:\OSD\Operating System\Windows 7 KMDF 1.11\Windows6.1-KB2685811-x64.cab"
DISM.exe /Image:E:\Scratch /Get-Packages

Package Identity : Package_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11
State : Install Pending
Release Type : Update
Install Time : 28-Nov-2014 5:10

dism /unmount-Image /mountdir:E:\Scratch /commit

Reference