Quantcast
Channel: TechNet Blogs
Viewing all 36188 articles
Browse latest View live

Licensing Logic: What’s new in the Microsoft Products and Services Agreement?

$
0
0

Written by David Cattanach on September 20th, 2015

MPSA, the Microsoft Products and Services Agreement is the evolution of Microsoft’s Volume Licensing (VL) programs. It has been maturing and developing steadily since introduction in late 2013.

Where does MPSA fit in?

Figure 1 below gives a high-level representation of where MPSA sits within the current VL agreement family. You can read the MPSA at-a-glance document and visit the MPSA page for an overview of the program itself.

 

Figure 1: MPSA (purple area) within the VL program landscape. FY is based on Microsoft’s financial year, e.g. FY16 spans July 2015-June 2016

What’s new in MPSA?

The latest enhancements to MPSA include:

1. MSDN and Visual Studio available through MPSA.

2. Microsoft Azure available through MPSA on a pay-as-you-go basis. Customers can start using Azure immediately and will be billed at the end of each quarter for what they’ve used. This eliminates the need to determine and pay upfront monetary commitments; customers only pay for what they use.

3. Availability of the Enterprise Cloud Suite (ECS). Previously, ECS was only available through an Enterprise Agreement.

4. Multi-year durations so customers can opt for 1, 2 and 3 year subscriptions for certain Online Services.

5. Price Protection for the duration of a subscription when customers purchase a subscription to an Online Service.

6. Same Service Alignment for packages and online services so that after the first order is placed all subsequent orders for the same product will align to the same end date.

Let’s explain some of the newer concepts in detail.

 

Multi-year durations with Price Protection

Wouldn’t it be glorious to be able to budget for 3 years of online services in the warm knowledge that you can add seats at the same price, or even less? That’s the key with multi-year duration and price protection. It is possible to do a workaround at the moment by buying up to five years’ worth of seats and keeping them in the VL portal until needed. For example, if I want 500 seats of Office 365 E3, I could place 5 orders for 500 seats of E3 and I would receive 5 VL keys. I use the first key in year one, the second in year two, etc. Once purchased, a customer has up to five years to activate an online services key.

But what if I wanted to add another 100 seats? I’d need to buy the E3 licences again and pay the prevailing price. So the workaround is not ideal and price protection with a multi-year duration is superior.

If a customer buys a multi-year subscription for Office 365 they get a price ceiling for all subsequent orders within that 2 or 3-year duration. This price ceiling is equal to the current price taken from the price list at time of the initial order. When they place a future order for the same product, they can be confident they will never pay more than the price ceiling and may even pay a lower price if the price drops or there’s a promotion or concession at the time of order.

 

Figure 2: Example of price protection in a multi-year duration agreement

In figure 2, a customer has a Purchasing Account Anniversary (PAA) every January. In October, they purchase 2,300 ECS user subscription licences (USL). In a single-year agreement, this purchase would be pro-rated up to their PAA so they would pay for 3 months. The customer would like to lock prices in for 3 years so they are committing to 2,300 ECS USLs each year until the third PAA, January 2018, and in return they will gain price protection for all subsequent ECS USLs made by that Purchasing Account. With the first year pro-rated, this gives them 27 monthsof certainty.

When the customer makes the initial purchase in October, there happened to be a price list promotion (shown by the blue tick). That was the best price for the customer so that price is applied to the whole order of 27 months. They can choose to pay the full 27 months in advance or they can spread payments. The price ceiling is also set at the price list figure.

 

Figure 3: Example of price protection for additional purchases in a multi-year duration agreement

In May 2016, the customer wants to add another 700 ECS USLs (figure 3). Because they are adding to a service they already have and for which there is price protection, Same Service Alignmentcomes into play and these purchases will align to the same end date. This means that they place an order for 20 months of the service (click).

At the time of purchase, there is the price ceiling which was the price set at the original purchase back in October 2015. But the current price list is also checked along with any promotions or concessions that might apply to see if any of these prices are lower than the price ceiling. Whichever price is the best (shown here as the purple tick) is used and locked for this new 20-month order and again payments can be made upfront or spread.

As this is a commitment, subscriptions can’t be reduced within the multi-year duration agreement. Protected prices also apply to a single Purchasing Account (PA); this is an important factor because many organisations buying through MPSA do so through several PAs.

 

Expect More Enhancements to MPSA in the Future

Since launch, the MPSA has been hugely successful. Whilst the Enterprise Agreement remains the most appropriate VL program for customers who are able to make an enterprise-wide commitment, the MPSA is perfect for transactional purchasing of on-premises and online licences. Select Plus has now been retired and since July 1st no new commercial Select Plus agreements can be signed, and from July 1st 2016, no new orders will be taken on existing commercial Select Plus agreements.

MPSA will continue to mature and evolve and will eventually become the Volume Licensing platform for all future offers. We’ll continue to keep you up to date with blog posts and readiness events.


Microsoft Dynamics AX: планы разработки 10/2015

Tip o’ the Week #296 – Win10 Xbox App: snap snap, grin grin

$
0
0

There are a variety of apps out there for grabbing your PC screen in video format, using for making tutorials, saving gaming footage or other activities. There are many free screen capture apps clip_image002(like Microsoft’s Expression encoder, which is still available though no longer being developed) that seem to be either pretty complex (if feature rich), or else they add all kinds of undesirable gunk to your PC at time of installation (does anyone really want the Ask Toolbar?), they force a length limit or watermark on your resulting video, etc. There are other, commercial, products (eg Camtasia) which are really good, though again can be feature-rich and complex.

What if you want to do a simple screen recording to help make a point, and you don’t want to spend ages learning how to use a Swiss Army Knife of a tool, or installing garbage/spyware on your PC, and can’t justify spending a bunch of cash for a software package you’ll use once or twice?

Well, if you’ve got Windows 10, you may be pleased to know there’s an app that comes with the OS that can be used to do exactly this – the Xbox App. You can use it to take screen snaps(though with desktop OneNote installed, you can quickly grab an area of the screen to the clipboard by pressing SHIFT+WindowsKey +S), or youcan save video footage of a target application window.

Since the functionality comes with the Xbox app, it’s safe to assume that it’s really intended to save game footage to your machine, but since it works with any windowed app too, then consider it a bonus regardless of whether you’re into gaming or not. Note that it only records one window, so if you’re looking to grab the whole desktop then you’re better off looking at the top of this tip, for Expression, Camtasia or others.

 

Capturing a window

clip_image004

Launch the Xbox app by clicking on the icon on your Start menu, or press Start and just type Xbox…

clip_image006Next, start the app you wish to record,   then press WindowsKey+G, which will open the Game Bar.

The Xbox app will ask to confirm that the target app you’re trying to record is a game – it doesn’t matter whether the app is or isn’t a game, so clip_image008just pretend that your target app is a game and launch the Game Bar.

clip_image010With the Game Bar open, you can either take a screenshot with the Camera icon, or begin recording video with the red circle Record icon. During recording, a small red indicator appears at the top of the currently selected window to confirm that recording is taking place, and showing the duration of the current recording. Clicking it will stop the recording, and pressing WindowsKey+G again will show the Game Bar again.

clip_image012Even easier, If you have the Xbox app running and the game bar is open, you can flick around to your target app just start recording the current application by pressing ALT+WindowsKey+R or grab a screenshot by pressing ALT+WindowsKey+PrtScrn.

Once your recording is complete, you can find it along with any screenshots with File Explorer under ThisPC\Videos\Captures. You can also find any of your recording in the Xbox app under Game DVR. That’s all there is to it.

PowerShell DSC FAQ: Sorting Out Certificates

$
0
0

 Hello, everyone. This week I posted over on the PowerShell Team Blog. One of the most common questions I get regarding PowerShell Desired State Configuration is about certificates. What kind do I need? How many? Where do they go? In this blog post we will sort out certificate requirements for PowerShell DSC.

You can read the post here: PowerShell DSC FAQ: Sorting Out Certificates.

Exchange 2016 Installation Screenshots

$
0
0

Now that that Exchange 2016 has been released, let’s take a look at the Exchange 2016 installation process.  We will see that there are some similarities compared to Exchange 2013 along with some differences.

Exchange 2016 can be downloaded from here

 

Planning And Preparation

As with every project proper planning and preparation is required.  Deploying Exchange is no different.  TechNet has an overview of the steps that are required:

 

Lab Configuration

The lab is based on Windows Server 2012 R2 servers for both Exchange and Domain Controllers.  No prior versions of Exchange have been installed into the lab, and Exchange 2016 will be deployed from scratch.   The domain name is contoso.com and we will deploy Exchange 2016 using the graphical installer and also the command line.  The Exchange organization will be called “Contoso”. 

 

Preparing AD

As with many customer environments, the Exchange team will not be the ones who will update the AD schema and prepare AD for the installation of Exchange.  To that end the AD preparation steps will be performed directly on the schema master, not an Exchange server. 

To prep AD for Exchange 2016, .NET framework 4.5.2 must be installed onto the machine that will be used to prepare AD.   Follow these steps to verify the installed version of the .NET Framework.  If required, install .NET 4.5.2 and restart the machine.

Install .Net Framework 4.5.2

Since we are using the schema master, the AD RSAT tools are already installed.  If the AD DS RSAL tools are not installed, install then using Server Manager or via Windows PowerShell using Install-WindowsFeature RSAT-ADDS

As with prior releases, we need to first extend the AD DS Schema, PrepareAD and finally PrepareDomains. 

  1. Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
  2. Setup.exe /PrepareAD /OrganizationName:"<organization name>" /IAcceptExchangeServerLicenseTerms
  3. Setup.exe /PrepareDomain:<FQDN of the domain you want to prepare> /IAcceptExchangeServerLicenseTerms

Note that the setup file is setup.exe, setup.com was last used with Exchange 2010 unattended setup.  It is also noteworthy that the full syntax has been specified, note that the shortcut syntax such as setup.exe /PS is not used.  This was covered in the 6 Mistakes To Avoid With Exchange 2013 CU Command Line Installations.  There are now 7 mistakes listed in the article, but if the title was changed links would break. 

First up, let’s prepare the AD schema:

Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Preparing AD Schema For Exchange 2016

Then we will run PrepareAD: 

Setup.exe /PrepareAD /OrganizationName:"Contoso" /IAcceptExchangeServerLicenseTerms

Preparing AD For Exchange 2016

At this point we cannot add any Exchange 2010 or Exchange 2013 servers since Exchange 2016 PrepareAD was executed, and there were no prior Exchange servers.  This is covered in the post Exchange Upgrades–The Point Of No Return

If you have an Exchange 2010 deployment, and wish to move to Exchange 2016 there is no Exchange requirement to install Exchange 2013.  You may wish to install Exchange 2013 for other reasons.  For example applications and services that may only be supported with that version of Exchange. 

Finally we need to prepare the domain.  There is a single domain in this forest – contoso.com. 

Setup.exe /PrepareDomain:contoso.com /IAcceptExchangeServerLicenseTerms

Preparing AD Domain For Exchange 2016

Now that AD has been successfully prepared, we can move to preparing the Exchange 2016 servers themselves.  Allow time for AD to replicate before attempting to install the first Exchange server.

 

Install Prerequisites On Exchange 2016 Mailbox Server

Prior to installing Exchange 2016, prerequisites need to be installed onto the underlying OS.  While it is possible to use the /InstallWindowsComponents that does not install the other components that are not in-box. 

To install the required Windows Server 2012 R2 OS components run the below from PowerShell:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation –Restart

Note that –Restart has been added to automatically restart the server. 

Installing Exchange 2016 OS Prerequisites

Once the server restarts, then we need to install:

Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

NET Framework 4.5.2

Installing Exchange 2016 Server .NET FramewworkInstalling Exchange 2016 Server UC Managed API

Installing the UC Managed API will install:

Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.50727
Microsoft Server Speech Platform Runtime (x64)
Microsoft Speech Platform VXML Runtime (x64)
Microsoft Server Speech Recognition Language - TELE (en-US)
Microsoft Server Speech Text to Speech Voice (en-US, Helen)
Microsoft Lync Server 2013, Bootstrapper Prerequisites Installer Package
Microsoft Unified Communications Managed API 4.0, Runtime

 

Installing Exchange 2016 Using Setup Wizard

Start the Exchange 2016 setup.exe using an elevated prompt if UAC is enabled, though it is a good habit to always elevate so it is not missed.

Starting Exchange 2016 Setup - Checking For Updates

Starting Exchange 2016 Setup - Intializing

Starting Exchange 2016 Setup - Introduction

Starting Exchange 2016 Setup - License Agreement

Starting Exchange 2016 Setup - Recommended Settings

The prior screens have been similar to Exchange 2013, and now we see a major difference.  There is now a single Exchange 2016 role that combines both the CAS and Mailbox roles from Exchange 2013.  Multirole installation was the recommendation for the last two Exchange releases and is the basis of the Exchange Preferred Architecture

Starting Exchange 2016 Setup - Server Role Selection

In Exchange 2016 the default installation path remains the same as Exchange 2013, this is C:\Program Files\Microsoft\Exchange Server\V15

Note that Exchange 2013 and 2016 will consume considerable more space in the install folder compared to Exchange 2010.  Plan accordingly.  Creating a 50GB C: drive and installing Exchange 2016 to the default location will not end well.

Starting Exchange 2016 Setup - Install Location

Exchange 2016 has malware scanning enabled by default.  This can be disabled at installation time if you plan to use a 3rd party product instead. 

Starting Exchange 2016 Setup - Malware Protection

Once the readiness checks have completed, click install. 

Starting Exchange 2016 Setup - Readiness Checks Complete

Exchange 2016 will then be installed.

Exchange 2016 Setup - Setup In Progress

Note that setup requests the server be restarted to complete the installation process. 

Exchange 2016 Setup - Setup Completed

To complete the install, restart the server. 

 

Installing Exchange 2016 Using Command Line

As noted in the installing Exchange 2016 prerequisites section, the prerequisites must be installed.  Refer to the above section for installing:

  1. Required Windows OS components
  2. UC Managed API
  3. .NET Framework 4.5.2

The sever below has all of the above already installed, so we can focus upon the command line installation aspects in this section. 

Since AD was already prepared with the Exchange organization name it is not specified below in the command below.  For all of the Exchange 2016 setup switches, please review TechNet

As noted above, an elevated command prompt is used to initiate the install:

Setup.exe /mode:Install /role:Mailbox /IAcceptExchangeServerLicenseTerms

Exchange 2016 Command Line Installation

Again once setup completes the server must be restarted. 

In the below screenshot, we can see the two lab servers:

Exchange 2016 Servers Sucessfully Installed

  

Post Installation Tasks

Exchange 2016 may be installed, but there are many tasks remaining.  The various URLs for the web services on the server must be configured.  This must match the CAS namespace design for your Exchange deployment. 

The below shows the default Exchange 2016 configuration for the OWA virtual directories.  Typically they will require modification.

Exchange 2016 Default URLs For OWA

Do not leave the default self signed certificates bound to the various services.  Proper PKI issued certificates should be immediately installed and configured. It is recommended that Exchange be installed into a dedicated AD site so that users in the production AD sites do not try to leverage the services of the new server prior to the correct CAS namespaces and certificates being configured.  In this case, remember to change the Autodiscover Site Scope coverage to reflect the correct AD site.  This must be done manually.

 

Please refer to TechNet for additional post installation tasks

Cheers,

Rhoderick

Office 365 Things You Need To Know: Internal Use Rights

$
0
0

TimTetrickPhoto

Tim Tetrick

As we kick off the blog series this month on Office 365 Things You Need To Know, I first want to make sure that as Microsoft Partners you are taking full advantage of your Internal Use Rights benefits.

Microsoft Partners receive Internal Use Rights (IUR) licenses for Microsoft software and online services as a membership benefit of Microsoft Action Pack and Microsoft Partner Network (MPN) competencies. These licenses can be used for internal productivity and collaboration, demonstration, development and testing, as well as for internal training purposes. The IUR benefit also comes with the added flexibility of being able to choose on-premises, online services, or any combination in between, plus the ability to change this at any time.

Here are the license grants you get for Office 365 across Action Pack and Silver and Gold competencies.

image

You may have heard it said there is no better way to sell Microsoft products and services than to use Microsoft products and services on a daily basis to run your business.  And it is absolutely true!  Here are just some of the benefits of utilizing your Internal Use Rights.

image

To get more information on your IUR benefits, go to http://aka.ms/IUR.

To activate your IUR benefits, go to http://aka.ms/ActivateIUR (a Microsoft Account associated with admin rights is required to access).

Thanks for reading and remember to check out the rest of the Office 365 Things You Need To Knowblog series happening this month!

(SQL) Tip of the Day: Cancelling a V12 Migration via PowerShell

$
0
0

Today’s (SQL) Tip…

If you are moving from V11 to V12 with a large database and are on a lower tier such as S0 or Basic you will notice it can take a very long time. This is because you are limited to the DTUs available to you during the move from V11 to V12 also. To work around this you can move to a higher tier database during the move and move back down after it has finished.

If you are already in the middle of the migration and it has taken a long time you can cancel the migration via Azure powershell and the cmdlet Stop-AzureSqlServerUpgrade.

To do this, install the latest version of Azure Powershell.

Run:

Switch-AzureMode AzureResourceManager

Get-AzureSqlServerUpgrade -ServerName ExampleServer -ResourceGroupName ExampleResourceGroup

If the status is listed as InProgress you can run

Stop-AzureSqlServerUpgrade -ServerName ExampleServer –ResourceGroupName ExampleResourceGroup

Once Get-AzureSqlServerUpgrade shows “Stopped” as the status you can change your edition and restart the migration.

EMET Reporting

$
0
0

 

So I frequently get customers that ask how do I know what EMET is actually doing out there.  Unfortunately like a number of our products EMET is basically the client.  We do have GPO’s to manage it but there is no included System Center reporting console or the like.

If your organization is fortunate enough to have some type of SIEM / SCOM etc that has agents on all clients then you can use that to gather the appropriate source EMET Event ID 1,2 (Maybe 42 for SSL Pinning) events from the Application Event Log to determine when mitigations are being triggered in your environment.  More commonly I see customers that either don’t have a SIEM or if they do have one they rarely put the agent across all of their desktops.

In the scenario with no agents on the clients then typically what we see and recommend is the use of Windows Event Forwarding to centralize the events of interest.  In some cases forwarding is used to drop them all in a centralized location then you utilize the SIEM agent on that central location and just consume the specific events from that central location and this tends to work out well in many environments.

For the customers that don’t have a SIEM or would just like to have some tools to help with piloting/deployment etc I present the following set of scripts/solution:

The basic premise of the solution looks like this (sorry my visio skills= bad Smile )

image

  • GPO tells client to talk to WEF Subscription Server WEFSERVER1
  • Client contacts WEFSERVER1 for subscription which says to send EMET 1,2
  • Client subsequently forwards EMET Event ID 1,2 any time they occur
  • Script EMETReporting.ps1 on the WEF server triggers anytime new event comes in and parses out interesting data fields to a c:\emet\emet.csv file
  • PowerBI Desktop dashboard file consumes emet.csv and shows visualizations of the data
  • Optional you put that PowerBI file up in the PowerBI service and use the PowerBI Personal Data Gateway client to sync it to the cloud and get a web based dashboard that also has IOS/Android/Windows apps available to it.

I’ve placed all the files at https://github.com/kurtfalde/EMET-Reporting except for an event log watcher module from http://pseventlogwatcher.codeplex.com/ which you will also need. Start off by downloading the entire contents of both locations and place them in a c:\EMET folder on the server which you are planning to utilize for a WEF (Windows Event Forwarding) Subscription Server.

Once copied there you should have a folder that pretty much has the following content

image

The first thing to run is the EMETWEFServerSetup.ps1 script as this will configure the following:

  • Set WinRM service to start automatically
  • Run WinRM quickconfig to ensure that WinRM is listening and the correct firewall inbound rules are enabled
  • Increases the size of the Forwarded Events log to 500Mb
  • Runs wecutl qc –quiet to configure the Windows Event Collection service to be able to create/manage WEF Subscriptions
  • Imports a preconfigured EMETSubscription.xml that collects EMET Event ID 1,2 for “Domain Computers”
  • Imports and creates a Task Scheduler item that runs the EMETReporting.ps1 script in the background anytime the computer restarts

(FYI you may need to right click and “unblock” the .ps1 and .psm1 files as PS execution policies don’t like running things from the Internet)

Once you run the EMETWEFServerSetup.ps1 script spot check and verify that the task scheduler item is in place and that the Event Subscription is in place.

EMET Parsing Task (In Task Scheduler)

image

EMET Audit Events (In Event Viewer)

image

Go ahead and start the task scheduler item so the script registers that it’s watching for events incoming and parsing them.  It should restart automatically if you reboot the system at any point.

At this point we need to ensure clients are talking to this server which we will do via a GPO.  Create or modify an existing GPO that is assigned to your EMET clients and configure the Policy>Computer Configuration>Administrative Templates>Windows Components>Event Forwarding>Target Subscription Manager setting to point to the WEF server you just configured.

image

Once this has been completed test some clients to ensure they picked up the setting and are talking to the WEF server and pulling the subscription properly. After running a GPupdate on the clients the best place to look is in Event Viewer>Applications and Services Logs>Microsoft>Windows>Eventlog-ForwardingPlugin>Operational Event log.  A good event is 100  which says that the Subscription EMET Audit Events was created successfully (if you have others you are probably going to have to do some troubleshooting if you have nothing make sure you have the WinRM service set to automatic on your clients).  Event should look like this.

image

You can also check the subscription on the WEF server and look at how many clients it has in the Event Viewer as well.

image

At this point if everything is working properly you should hopefully see that the script begins parsing events as they come in.  The subscription is set to gather an existing EMET Event ID 1,2 on the clients event logs so if you have had any triggering that hasn’t rolled off your application event logs you may well start getting data immediately.  If not you could always test by loading Java in IE and testing the ASR mitigation by browsing to a site that attempts to load Java.

Provided all of the other items worked properly and a EMET.csv is now being created in the c:\emet\emet.csv you can now open that with the included PowerBI Desktop Dashboard file.  You will need to download and install the PowerBI Desktop Client from https://powerbi.microsoft.com/en-us/desktop (it’s free), once installed open the “EMET Dashboard.pbix” file in the c:\emet folder.  It will initially have junk test lab data in it and not your environment yet, you wan to click the ‘Refresh’ button at the top which will cause it to import the c:\emet\emet.csv file and display actual data from your environment.

image

You can either just use this as a local dashboard or if you want to put it in the cloud/sync it then consider using the PowerBI service (can either be purchased individually or part of o365 subscriptions) to host this.  I’m not going to go through the steps for this here but you can basically import the .pbix file to PowerBI, download the PowerBI Personal Gateway Client and configure it on the server and then set your data model that you uploaded to sync automatically through the client.  This in turn will give you a web based dashboard which also has IOS/Android/Windows apps available to it. 

image

Hopefully some of you take the time and try this out I would really appreciate feedback.  Thanks


Privacidade e o Windows 10

$
0
0

No mundo conectado de hoje, manter a nossa privacidade é um tema extremamente importante para cada um de nós, portanto, as perguntas são bem-vindas e também o feedback que recebemos desde que o Windows 10 foi lançado.

Confiança é o pilar central da nossa visão de computação mais pessoal, e sabemos que temos a ganhar. Temos tido tempo para expandir a documentação sobre a nossa abordagem hoje com este blog, e novos conteúdos, estamos postando hoje para consumidores e Profissionais de TI, projetado para complementar o nosso One Microsoft Privacy Policy. Estamos ansiosos para a próxima rodada de perguntas e comentários sobre estes novos postings. Posso garantir que nenhuma outra empresa está mais comprometida, mais transparente e escutando nossos clientes sobre esse importante tema que estamos discutindo hoje.

Desde o início, nós projetamos o Windows 10 com dois simples princípios de privacidade em mente:

    • O Windows 10 recolhe informações para que o produto funcione melhor para você.
      • Você está no controle com a capacidade de determinar quais informações são coletadas.

      Com o Windows 10, as informações que coletamos são criptografadas em trânsito para os nossos servidores e, em seguida, armazenados em instalações seguras. Consideramos os dados que coletamos e os que não coletamos e os classificamos em 3 níveis:

      1. Segurança e confiabilidade dos dados


      Recolhemos uma quantidade limitada de informação para nos ajudar a oferecer uma experiência segura e confiável. Isso inclui dados como um ID anônimo do dispositivo, tipo de dispositivo, e a quando um aplicativo tem seu crash, coletamos os dados para que a Microsoft e seus parceiros desenvolvedores usem estes dados (o porquê do crash) continuamente a fim de aumentar a confiabilidade dos aplicativos. Isso não inclui qualquer de seu conteúdo ou arquivos pessoais, e nós tomamos várias medidas para evitar cobrança de qualquer informação que diretamente possa identifica-lo, como seu nome, endereço de e-mail ou ID de conta.

      Um ótimo exemplo de como esses dados foram utilizados de forma eficaz foi apenas no último mês, quando os dados agregados nos mostraram que uma determinada versão de um driver de gráficos estava falhando em alguns PCs Windows 10, então causava uma reinicialização. Este driver não era amplamente utilizado, mas ainda assim o problema impactou os clientes. Nós imediatamente entramos em contato com o parceiro que constrói o driver, trabalhamos juntos para que  a correção no Windows fosse iniciada no prazo de 24 horas. Nós usamos os dados dos dispositivos dos participantes do programa Insiders' para confirmar que o problema foi resolvido, e, em seguida, distribuímos a corretivo (Fix) para o grande público através de uma atualização do dia seguinte – all in all -  esses dados nos ajudaram a encontrar, corrigir e resolver um problema significativo no prazo de 48 horas.

      Em nossas atualizações corporativas, a Microsoft, um pouco mais tarde este ano permitirá aos clientes corporativos a opção para desativar esta telemetria, mas nós recomendamos fortemente contra isso.

       

      2. Dados de personalização


      Devemos aspirar e oferecer uma experiência do Windows personalizado para você, quais as vantagens de saber algumas coisas sobre você a personalizar a sua experiência, como, por exemplo, saber se você é um fã e torcedor do Seattle Seahawks ou do Real Madrid, de modo a lhe proporcionar as atualizações do jogo e pontuações ou recomendar aplicativos para que você possa desfrutar e lembrar as palavras comuns que você digite em conversas por mensagens de texto para lhe fornecer convenientes sugestões de texto. Você está no controle das informações que recolhemos para estes fins e pode atualizar suas configurações a qualquer momento. Observe que, com novas funcionalidades, tais como Cortana que necessitam de mais informações pessoais para fornecer a experiência completa, você será perguntado se você deseja ativá-los e lhe serão dadas mais opções  de privacidade e de personalização.

       

      3. Os dados que coletamos não são usados para publicidade


      Ao contrário de algumas outras plataformas, que não importa quais são as suas opções de privacidade que você escolher, nem o Windows 10 nem qualquer outro software Microsoft digitaliza o conteúdo do seu e-mail ou outras comunicações, ou mesmo os seus arquivos, a fim de fornecer publicidade direcionada para você.

       

      O seu Feedback é realmente que faz a diferença

      Ouvir o seu feedback tem sido a fundação do Windows 10, e o feedback sobre a privacidade não é uma exceção. Do nosso programa de Insiders, temos uma secção de privacidade em nosso Feedback do Windows app, para que possamos ter um diálogo aprofundado sobre nossa política de privacidade. Como um exemplo de resposta direta ao feedback que recebemos, em todos os recursos do Windows 10, os clientes irão receber a próxima atualização de recursos da família, com as configurações padrão projetadas para ser mais adequada para os adolescentes, em comparação com as crianças menores. Além disso, estamos trabalhando em maneiras de melhorar ainda mais as notificações aos pais sobre relatórios de atividades no Windows. Além disso, vamos lançar atualizações para clientes corporativos com base no seu feedback mais tarde ainda este ano. Esta colaboração com os Insidersé inestimável para a nossa equipe, e nós continuamos a acolher quem deseja trabalhar conosco  sobre o futuro do Windows 10 e pode se inscrever aqui neste link.

      Se você alguma vez encontrar uma situação em que nosso software não está se comportando da maneira que deve com as suas configurações de privacidade, por favor nos informe neste link. Como segurança, estamos empenhados em acompanhar todos os problemas relatados, sondar continuamente nosso software com principais técnicas de ponta e atualizar proativamente os dispositivos compatíveis com as atualizações necessárias.

      Nós realmente apreciamos um diálogo rico em comentários a fim de tornar o Windows 10 melhor para todos nós. Vamos continuar a ouvir e responder, para ganhar sua confiança.

      Obrigado.

      - Terry Myerson 


      Fonte: http://blogs.windows.com/windowsexperience/2015/09/28/privacy-and-windows-10/

      Privacidad y Windows 10

      $
      0
      0

      En el mundo conectado de hoy, un tema de increíble importancia para todos es cómo mantener nuestra privacidad, por ello, agradecemos las preguntas y la retroalimentación que hemos recibido desde el lanzamiento de Windows 10.

      Uno de los pilares centrales de nuestra visión de Computación Más Personal es la confianza, y sabemos que es algo que debemos ganar. Nos hemos tomado el tiempo de aumentar la documentación de nuestra perspectiva actual a través de este blog, y hoy estamos publicando contenido nuevo para nuestros consumidores y Profesionales de IT , que está diseñado para complementar nuestra Política de Privacidad de One Microsoft. Estamos a la espera de la siguiente ronda de preguntas y retroalimentación sobre estas nuevas publicaciones. Les aseguro que no hay otra compañía más comprometida, que escuche con más atención a los clientes sobre todo lo relacionado con este tema tan importante.

      Desde el principio diseñamos Windows 10 con dos principios muy claros en mente:

        1. Windows 10 recolecta información para que el producto funcione mejor para usted.
        1. Usted tiene el control gracias a la capacidad de determinar qué información se va a recolectar.

      Con Windows 10, la información que recolectamos queda encriptada durante el tránsito a nuestros servidores, y luego se almacena en un lugar seguro. Consideramos los datos que recolectamos y los que no recolectamos en 3 niveles:

       

      1. Datos de seguridad y confiabilidad

       La información que recolectamos es limitada, y nos ayuda a ofrecer una experiencia segura y confiable. Esto incluye datos como ID de dispositivo anónimo, tipo de dispositivo, datos de caída de aplicaciones, que tanto Microsoft, como nuestros socios desarrolladores, usamos para la mejora continua de la confiabilidad de aplicaciones. Esto no incluye su contenido ni sus archivos, y tomamos pasos extra para evitar recolectar información que lo identifique directamente, como su nombre, su dirección de correo electrónico, o la ID de su cuenta.

      El mes pasado pudimos ver lo efectivo que es el uso que damos a los datos, cuando los datos agregados nos mostraron que una versión en particular de un controlador de gráficos se empezó a colapsar en algunas PCs con Windows, lo que hacía que se reiniciara. El uso de este controlador no muy amplio, pero estaba afectando a los clientes. Contactamos de inmediato a nuestro socio encargado del controlador y trabajamos juntos para hacer la corrección en Windows Insiders en cuestión de 24 horas. Usamos los datos de algunos dispositivos que corrían Insiders para confirmar que el problema estaba resuelto, y luego implementamos el arreglo para el público en general a través de una actualización el día siguiente. Con todo, los datos nos ayudaron a encontrar, corregir y resolver un problema importante en cuestión de 48 horas.

      Las actualizaciones para nuestra funcionalidad empresarial, que se lanzarán este mismo año, darán a nuestros clientes empresariales la opción de desactivar la telemetría, pero recomendamos ampliamente no hacerlo.

       

      2. Datos de personalización

      Aspiramos a brindarle una experiencia agradable y personalizada con Windows, que se puede beneficiar conociendo ciertos datos para ofrecerle una experiencia personalizada, por ejemplo, saber si usted sigue a los Halcones Marinos de Seattle, o al Real Madrid, para mostrarle las puntuaciones de los partidos, o para recomendarle aplicaciones que le pueden gustar, incluso para recordar las palabras que más usa para sus mensajes de texto y darle convenientes sugerencias con el texto predictivo. Usted controla la información que recolectamos con este objetivo y puede actualizar la configuración en cualquier momento. Es importante observar que las nuevas funcionalidades, como Cortana, que requieren información más personal para ofrecerle la experiencia completa, piden activar estas funciones y le ofrecen opciones adicionales para personalizar su privacidad.

      3. No recolectamos datos para publicidad

       A diferencia de otras plataformas, no importa qué opciones de privacidad elija, ni Windows 10 ni ningún otro software Microsoft escanea el contenido de su correo electrónico ni otras comunicaciones, ni sus archivos, para enviarle publicidad específica.

       

      Su retroalimentación marca una diferencia

      Uno de los cimientos de Windows 10 fue escuchar su retroalimentación, y la retroalimentación sobre la privacidad no es la excepción. Para Windows Insiders, tenemos una sección de Privacidad en la aplicación Windows Feedback, para poder mantener un diálogo detallado sobre la privacidad. Por ejemplo, sobre la respuesta directa a la retroalimentación recibida, todos los clientes de Windows 10 recibirán una actualización de las funcionalidades de familia, con ajustes predeterminados para hacerlas más adecuadas para adolescentes, comparado con los ajustes para niños pequeños. Además, estamos trabajando en nuevas maneras de mejorar todavía más las notificaciones que reciben los niños y sus padres sobre los informes de actividad en Windows. En el otoño también lanzaremos actualizaciones para clientes empresariales basadas en su retroalimentación. Esta colaboración con Insiders es invaluable para nuestro equipo, y todos los que deseen trabajar con nosotros en el futuro de Windows 10 son bienvenidos aquí.

      Si alguna vez se encuentra en una situación en la que nuestro software no se esté comportando como debería con los ajustes de privacidad que haya elegido, puede informarnos aquí. Al igual que con la seguridad, estamos comprometidos a dar seguimiento a todos los problemas reportados, a revisar continuamente nuestro software con técnicas de vanguardia, y a actualizar de manera proactiva los dispositivos soportados con las actualizaciones que sea necesario.

      Agradecemos ampliamente el enriquecedor diálogo que hemos tenido para mejorar Windows 10 para todos. Seguiremos escuchando y respondiendo a sus preguntas, para ganar su confianza.

      Gracias,

      -Terry

      Fonte:http://blogs.windows.com/windowsexperience/2015/09/28/privacy-and-windows-10/

      Revisiones de los Boletines de Seguridad MS15-097 y MS15-099 el 30 de septiembre de 2015.

      $
      0
      0

      Queremos darles a conocer dos revisiones de boletines de seguridad que se publicaron  el 30 de septiembre de 2015.

       

      Se revisaron los boletines de seguridad para ofrecer actualizaciones del producto Office 2016 que se acaba de lanzar.  A continuación presentamos una descripción general: 

      MS15-097

      Vulnerabilidades en el componente de gráficos de Microsoft que pueden permitir la ejecución remota de códigos

      V2.0 (30/9/2015)

      Se hizo una revisión del boletín, para anunciar la disponibilidad del paquete de actualización de Skype para Business 2016. Los clientes que usan Skype para Business 2016 deben aplicar la actualización 2910994 para quedar protegidos contra las vulnerabilidades aquí indicadas. La mayoría de los clientes tienen habilitada la actualización automática y no necesitan realizar ninguna acción, dado que la actualización se descargará e instalará automáticamente.

      Detalles

      https://technet.microsoft.com/en-us/library/security/ms15-097

       

      MS15-099

      Vulnerabilidades en Microsoft Office que pueden permitir la ejecución remota de códigos

      V3.0 (30/9/2015)

      Se revisó el boletín para anunciar la disponibilidad de un paquete de actualización de Microsoft Office 2016. Los clientes que usan Microsoft Office 2016 deben aplicar la actualización 2910993 para quedar protegidos contra las vulnerabilidades aquí indicadas. La mayoría de los clientes tienen habilitada la actualización automática y no necesitan realizar ninguna acción, dado que la actualización se descargará e instalará automáticamente.

      Detalles:

      https://technet.microsoft.com/en-us/library/security/ms15-099

       

      Enlaces directos a Advanced Threat Analytics (ATA) de Microsoft y Operations Management Suite (OMS) de Microsoft

      $
      0
      0

      Aquí estoy, para compartirles de nuevo los que estoy haciendo…y otra vez me voy por la tangente! Les presento dos temas que a lo mejor son nuevos para ustedes, o no.  Tan solo estoy tratando de asignar recursos a ATA y a OMS.  Espero que les sean útiles.  Creo que en el siguiente  ya  los escucharan más sobre estas soluciones en Microsoft Ignite...:)

       

      Principales recursos de Advanced Threat Analytics (ATA) de Microsoft

      ATA es una plataforma instalada en el sitio que le ayuda a proteger a su empresa contra ataques dirigidos mediante el análisis, aprendizaje e identificación automáticos de comportamientos normales y anormales de entidades (dispositivos de usuario y recursos).

        • ¡Foro de ATA donde puede publicar preguntas y ver las respuestas!

      Principales recursos de Operations Management Suite (OMS) de Microsoft

      Operations Management Suite de Microsoft es la solución de administración de IT para la era de la nube; una sola solución, construida para administrar su ambiente completo sin importar su ubicación, su sistema operativo, los hipervisores o las opciones del proveedor de la nube.

       

       

      Original http://blogs.technet.com/b/tangent_thoughts/archive/2015/09/30/microsoft-advanced-threat-analytics-ata-amp-microsoft-operations-management-suite-oms-quick-links.aspx

      OpenStack and Vagrant with Nano Server

      ¿A quién elegirán al Imperio o a los Rebeldes?

      $
      0
      0
      Sabemos que ya no pueden esperar más por el lanzamiento del nuevo Star Wars: Battlefront el 17 de noviembre. Sin embargo, nos complace anunciarles que este 8 de octubre, estará disponible la beta abierta para que puedan experimentar un poco las grandes batallas que tendrán muy pronto en sus consolas. En esta versión podrán disfrutar de tres misiones y enfrentarse al Imperio, o si es de su elección, a la Alianza Rebelde con las naves y vehículos que ya conocen de sus películas favoritas de esta saga...(read more)

      PowerTip: Use Non-Approved Cmdlet or App within PowerShell Workflow

      $
      0
      0

      Summary: Learn how to use a basic inline script in Windows PowerShell workflows.

      Hey, Scripting Guy! Question I’m trying to convert a Windows PowerShell script to a workflow, but I keep running into an error that suggests
                 the cmdlet cannot be used in a workflow. How can I get around this?

      Hey, Scripting Guy! Answer Wrap that section of the workflow as an inline script, and recapture your variables with the Using keyword,
                 for example:

      Inlinescript

                  {

                  $Somevariable=Using:SomeVariable

                  Start-ProblematicFunction $Somevariable

                  }

       


      Top Support Solutions for System Center 2012 Configuration Manager

      $
      0
      0

      Top Microsoft Support solutions for the most common issues experienced when you use System Center 2012 Configuration Manager (updated quarterly).

      Note: Some content is for earlier versions of Configuration Manager but is listed here because the solution provided remains applicable to the current version.

      1. Solutions related to application management and software distribution:

      2. Solutions related to software update deployment:

      3. Solutions related to the client is not installed, not active, not assigned, or missing actions:

      4. Solutions related to installation, supersedence, or detection issues with specific updates:

      5. Solutions related to operating system deployment – Preboot Execution Environment (PXE):

      Top Support Solutions for System Center 2012 Service Manager

      $
      0
      0

      Top Microsoft Support solutions for the most common issues experienced when you use System Center 2012 Service Manager.

      1. Solutions related to reporting:

      2. Solutions related to service requests:

      3. Solutions related to Exchange Connector:

      4. Solutions related to incident management:

      5. Solutions related to workflow performance:

      Top Support Solutions for System Center 2012 Operations Manager

      $
      0
      0

      Top Microsoft Support solutions for the most common issues experienced when you use System Center 2012 Operations Manager.

      1. Solutions related to operations or infrastructure:

      2. Solutions related to setup or deployment:

      3. Solutions related to agent connectivity:

      4. Solutions related to management packs:

      5. Solutions related to other Microsoft management packs:

      Top Support Solutions for System Center 2012 Endpoint Protection

      $
      0
      0

      Top Support Solutions for System Center 2012 Data Protection Manager

      $
      0
      0

      Top Microsoft Support solutions for the most common issues experienced when you use System Center 2012 Data Protection Manager.

      1. Solutions related to console crashes:

      2. Solutions related to file server backup and restore:

      3. Solutions related to Hyper-V and Virtual Server protection:

      4. Solutions related to SQL Server protection:

      5. Solutions related to Storage Pool: Disk, Replica, or Recovery Point Volume issues:

      Viewing all 36188 articles
      Browse latest View live


      <script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>