With Exchange 2007 and onwards, debug code tracing is logged to the ETW provider GUID 79BB49E6-2A2C-46E4-9167-FA122525D540. When you install Exchange, this ETW provider is registered formally and the GUI ExTRA application works. However, we can still manually do capture an ExTRA trace even if Exchange is not installed; the most common use would be setup issues.
Hola, en este blog voy a hacer una serie de notas sobre el fichero de paginación, una pregunta muy típica entre los administradores de sistemas es ¿en qué tamaño tengo que fijar el fichero de paginación?, ¿realmente necesito fichero de paginación? Cuando se habla del fichero de paginación surgen mil dudas y mil normas que siempre hemos creído como ciertas, pero que cuando investigas un poco más, te das cuentas que no son exactamente como se cuentan o como creímos que eran.
Para poder entender mejor el funcionamiento del fichero de paginación tenemos que entender el concepto de paginación. Este concepto aparece conjuntamente con el de memoria virtual, la paginación es uno de los esquemas de manejo de la memoria donde un proceso puede almacenar la información en memoria principal o en memoria secundaria según sea necesario. En esta técnica la memoria se divide en pequeñas partes llamadas marcos de página, a su vez, los procesos dividen la información que manejan en partes del mismo tamaño llamadas páginas.
De lo que se trata es que estén en memoria principal solo aquellas páginas que el proceso esté utilizando y las que no, estén almacenadas en memoria secundaria, en disco para ser exactos. Si el proceso necesita utilizar una página concreta que no está en memoria principal, genera una excepción al sistema operativo llamada fallo de página para que esta página sea copiada a memoria principal. Existen diferentes algoritmos en los cuales se determina que paginas son pasadas a memoria secundaria y cuáles no, de esta manera conseguimos que, en un espacio de memoria limitado puedan convivir más procesos de forma simultánea y estos solamente tendrán cargado en memoria principal aquellas páginas que realmente sean necesarias.
Sabiendo todo esto ya nos podemos hacer una idea de para que se utiliza el fichero de paginación, durante años he escuchado muchos comentarios sobre la paginación de Windows, muchos de ellos no muy buenos y la verdad es que nunca escuché un motivo técnico claro acerca del porque va mal, simplemente, va mal y ya. La cuestión es que Windows es capaz de manejar de forma automática el fichero de paginación, y es que si tú no sabes calcular cuánto necesitas de fichero de paginación, puedes hacer que Windows lo haga por ti mediante un algoritmo muy sencillo ya establecido. ¿Ese algoritmo es mejorable?, seguramente sí, pero entiendo que este algoritmo siempre será mucho mejor que si tú no sabes calcular cuánto necesitas de fichero de paginación y lo haces mal. Si estableces que sea el sistema quien gestione automáticamente este fichero, el sistema hará lo siguiente:
En XP y Windows Server 2003 (ambos ya están fuera de soporte), el sistema establecerá un tamaño inicial de 1,5 veces la RAM de la máquina y como máximo 3 veces la RAM de tu máquina.
En Windows Vista o 2008 Server y posteriores el algoritmo varía un poco y es más dinámico:
En Windows Vista y posteriores, cuando establecemos que el fichero de paginación sea gestionado por el sistema, si se tiene 1GB de memoria RAM instalada, el tamaño máximo del archivo de paginación es la RAM + 300 MB. Si tuvieras 4 GB de memoria RAM instalada, sin embargo, el tamaño máximo del archivo de paginación es 3 x RAM. Sobre la base de los recursos que el sistema tiene (RAM/espacio en disco), el sistema puede ajustar el tamaño de archivo de la paginación después de un reinicio si se añade más memoria o espacio de disco adicional.
Esto tiene ventajas e inconvenientes, como ventaja tenemos que, si no sabes gestionar el tamaño del fichero, tendrás un tamaño lo suficientemente grande como para que no tengas problemas ni en la paginación, ni en un crash de la máquina ya que como veremos más adelante el fichero de paginación es importante a la hora de crear un volcado. El inconveniente es que imagina que tenemos una máquina de 32GB de RAM, ¿realmente necesitarías un fichero de cómo mínimo 48GB o como máximo 96GB? La pregunta real es, una máquina con 32GB de RAM o 64GB, ¿realmente necesita paginar?
Lo iremos desvelando en las siguientes entregas del fichero de paginación.
Cada vez más los sistemas de impartición de justicia recurren al video como herramienta para resolver conflictos legales, ya sea como pruebas o como medio para permitir a los testigos hacer sus declaraciones y tener más información.
Con esta tendencia, se requiere de sistemas que ofrezcan video de alta calidad, almacenamiento del mismo, transmisión en alta definición y una eficaz administración para que abogados y jueces accedan al contenido.
...(read more)
Tratar la administración de una institución de gobierno que ofrece servicios a los ciudadanos como si fuera una empresa puede ofrecer muchos beneficios en torno a la rentabilidad de los recursos y, por supuesto, a la obtención de mayores ganancias, que en el caso de las entidades públicas se traducirían como mejores servicios a la población.
Una estrategia que algunas municipalidades han utilizado para mejorar sus procesos es manejar sus ciudades como...(read more)
In September 2014, Microsoft enabled Shared Computer Activation (SCA) mode in Microsoft Office 365 so that multiple Office 365 ProPlus users could share the same hardware in the following three scenarios:
Customer dedicated self-hosted (on-premises)
Dedicated third-party hosted
Windows Azure environment
In response to growing requests from service providers to deploy Office 365 ProPlus in third-party environments, Microsoft is excited to announce that multi-tenant third-party hosted scenarios are now permitted for SCA through partners who meet certain criteria.
Under the updated deployment scenario, hosting partners that are 1-Tier Microsoft Cloud Solution Provider (CSP) are now able to deploy multi-tenant remote desktop workloads with Office 365 ProPlus and/or E3, E4, E5 SKUs on-premises, in addition to being able to deploy multi-tenant remote desktop hosted workloads with those same Office 365 SKUs in Azure. Previously, the terms of Office 365 Shared Computer Activation required that these workloads could only be run on-premises with dedicated hardware.
Partner Spotlight
One of the first Microsoft hosting and service provider partners in the U.S. to take advantage of this Office 365 SCA update is ExternalIT, based in New York City. ExternalIT is vertically focused, specifically addressing virtual desktops with their hosted solution for financial analysts, which includes Office 365 components in addition to vertical industry applications.
Prior to the introduction of the updated SCA scenario, it was difficult for ExternalIT to transact under CSP, and it would have been equally difficult for their solution to scale using dedicated hardware.
Now other partners who are offering or looking to offer vertical hosted desktop solutions will be able to take advantage of this deployment scenario.
Requirements
We’d like all of our partners to be able to take advantage of the new, multi-tenant Office 365 ProPlus SCA deployment scenario like ExternalIT, but we do have some requirements:
To be eligible to participate in the SCA Program, a service provider must be a managed hosting partner, a valid and existing Direct (1-Tier) Cloud Solution Provider (CSP) and SPLA provider.
Partners can use Office 365 ProPlus and Office 365 E3, E4 and E5 SKUs only in multi-tenant deployment scenarios. These licenses can be obtained via CSP, or brought over from an existing customer.
There is a requirement to display a SCA landing page using supplied verbiage on your company’s website (see the example used by ExternalIT).
An amendment to your SPLA agreement is required in order to transact.
Click here for more information about Office365 ProPlus Shared Computer Activation.
Capturing more than 90% of the caucus results within three hours in a secure, accurate and trusted manner is an amazing accomplishment. In today’s special TechNet Radio episode, join Tommy Patterson as he welcomes the team that brought to life the 2016 Iowa Caucus app . Built on Microsoft technology, the new platform featured a secure system, enabling precincts to report their results directly by party, ensuring that only authorized Iowans were reporting results. Tune in and learn how this...(read more)
One of the topics that gets raised regularly with the OEM Server team is around when you should discuss selling the Datacenter vs. Standard editions of Windows Server 2012 R2 to customers, and usually it's easy to extract a few details about the customer scenario that will help shape those conversations. The main thing that needs to be taken into account is the number of virtualised Windows Server instances the customer needs to run on each server, but you also need to take into the account the potential number of Windows Server virtual machines you may need to run when you hit particular types scenarios. This is a high level overview, it's not going to present
Even though this initial piece is mostly focused on licensing, when in doubt with licensing issues make sure you contact your distributor or Microsoft licensing specialist to verify that what you want to supply to your customers will cover them from a licensing perspective. The different Microsoft licensing agreements are the source of truth for these things, and nothing in this post overrides or hopefully contradicts those.
Let's move on now and discuss those particular types of scenarios where the basic recommendation about the number of Windows Server VMs per server may not be as simple as you think. For the purpose of this post, let's focus on server recovery or even host server patching scenarios which have a great deal in common, with the major exception being the planned versus unplanned. Let's start with a simple scenario - a customer needs two servers to support Hyper-V's shared nothing Live Migration capability or Hyper-V Replica.
With a license for Windows Server 2012 R2 Standard per server, Server1 and Server2 would each be licensed to run two Windows Server virtual machines. If only two VMs are running per server, the customer is in compliance with their licensing. A critical update becomes available that needs to be installed on the Hyper-V host, and this update requires a hardware reboot. If the customer doesn't need the two virtual machines running on that server to be available during the server hardware restart, then the conversation is effectively done.
However, if the customer decides that they would like to perform Live Migrations and have all four virtual machines running at once on the second server, this means that server needs to be licensed for four concurrent virtual machines. The VM rights for one server aren't temporarily transferable to the other server, instead you need to think about two different licensing alternatives. The first of these is stacking two Windows Server 2012 R2 Standard licenses on each server, which would give you four virtual machine usage rights.
You can see from this scenario that it doesn't take too many VMs to get to the point where Datacenter becomes more cost efficient than stacking additional copies of Windows Server 2012 R2 Standard, which you would need to be doing on a per server basis to cover your customer. While your customers may be shifting some workloads to the cloud, there are some customers you still need to support their current on-premises software, and looking at deploying more on-premises solutions in the future, some of these in order to integrate with or accelerate certain cloud workloads.
As we go through more posts in this series, you will see some of benefits that Windows Server 2012 R2 Datacenter brings to customers who may be teetering on the edge of going down the multiple copies of Standard per server versus a single copy of Datacenter per server, but the big one is licensing simplicity and helping your customers remain compliant.
Following on from the last post where I discussed some of the reasons that Windows Server 2012 R2 Datacenter should be considered for customer deployments, today's post addresses some common questions around buying OEM Windows Server licenses versus purchasing via a Volume License program. The most important takeaway from the following information is that you can reap the benefits of both with your new server purchases, which will be explained below.
Here are the top line differences between OEM and Volume Licensing. This is not an in depth comparison of every difference, instead just calling out some of the differences for those who may not have purchased via a volume licensing program for their customers previously.
Windows Server 2012 R2 with different OEM license types
MNA preinstall or ROK is tied to hardware and can be pre-installed onto hardware, and OEMs can modify the OEM image to include additional software or customized images.
System Builder (COEM) license can be sold individually when sold with component hardware
System Builder and ROK include media
OEM product keys are provided on a COA that is attached to a server.
OEM licenses included support by the Server Manufacturer
Windows Server Volume Licensing
Licenses can be reassigned to different hardware every 90 days.
Licenses do not include Media, these need to be downloaded from the VLSC
Product keys are provided online through the VLSC.
There are many different possible licensing contracts that provide discounts for large purchases.
Common To Both
Windows Server 2012 R2 through OEM and Volume Licensing offers the same downgrade and virtualisation rights, which I introduced in the last post.
Adding Software Assurance To OEM Server Purchases
Microsoft Software Assurance can be purchased within 90 days of the OEM Software purchase. Software Assurance on Server Products offers business benefits which you can read about at the Software Assurance overview landing page. Some Software Assurance resources you may find useful also include Software Assurance at a glance (PDF) and Learn more about the specific benefits available for the products you license. One of the benefits that's probably worth thinking about now is the inclusion of new version rights during the term of your coverage, and with the launch of Windows Server 2016 planned for this year, it might help the conversation with those customers that might want to delay their purchase until Windows Server 2016 is shipping.
Why buy OEM server licenses and then add Software Assurance rather than just buying through VL? A couple of reasons - first of all you will usually find that OEM software is the lowest priced option, and then adding Software Assurance still keeps the overall cost lower than a VL+SA purchase. If you are buying ROK or preinstalled, it also saves time during server setup and configuration.
When using Microsoft Database Compare, you may receive the following error:
Could not load file or assembly 'Microsoft.ReportViewer.WinForms.Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. They system cannot find the file specified."
The error may occur if Microsoft Report Viewer Redistributable 2008 is not installed. It is a prerequisite for Database Compare.
To fix the error, install Microsoft Report Viewer Redistributable 2008, available here:
Born from Azure, Azure Stack helps organizations deliver Azure services from their own datacenter.
With Azure Stack, Microsoft is bringing proven innovation – including IaaS and higher level PaaS services – from hyper-scale datacenters to on-premises, enterprise-scale environments to meet customers’ business requirements.
Wondering what Azure Stack will offer when it eventually goes GA?
Check out the list below: (Note: The list of services is subject to change without notice)
Visual Studio Code PowerShell özelliğini sizler ile paylaşmak istiyorum . Aslında hepimiz böyle bir özellik bekliyorduk, çünkü Visual Studio Code bir çoğumuz için kod editöründen daha çok bir metin düzneleyicisi, bir ISE Editor , bir JS editör olmaya başladı.
Visual Studio Code başlangıç olarak temel kod bloklarında PowerShell için intelli sense özelliği vermekte idi şimdilerde ise extention ve pluginler ile daha da geliştirilmeye devam eviliyor.
Biraz özelliklere bakacak olursa bunlardan ilki parametreler için IntelliSense özelliği.
Yazdığımız fonksiyonlara fokus olma diğer bildiğimiz adı ile “Go to Defination F12”.
Tüm referanslar arasında arama “Find all References”
Komut dosyaları üzerinde veya proje içerisinde sembollerin listesini görüntülemek
Bu Özellik PowerShell MVP’si Keith Hill tarafından katkıda bulunarak geliştirilmiştir.
PowerShell Komut Analyzer kullanarak gerçek zamanlı komut analizi
Komutlarda Hata Ayıklama
Interaktif Komut Konsolu
Evet başlangıç özellikleri olarak hepize yetecek kadat özelliği barındırmakta üzerinde J Bunların yanı sıra geliştirmesi devam eden özellikler ve planlanan özellikler aşağıdaki gibidir.
Remote Debugging
Gelişmiş İnteraktif Konsol
Ortak sözdizimi için hızlı düzeltmeler
PowerShell Modülleri için ( arama ve yükleme) galeri entegrasyonu
Microsoft je 15.1.2016. godine objavio blog članak pod nazivom "Windows 10 Embracing Silicon Innovation", gdje su navedeni određeni podaci koji se tiču adaptacije Windows 10 operativnog sistema među poslovnim korisnicima, poput činjenice da je Windows 10 već instaliran na preko 22 miliona poslovnih uređaja te da je u aktivnom pilotu kod čak 76% naših poslovnih korisnika, odnosno novostima koje Windows 10 pruža za takvo okruženje, ali i o planu Microsofta kada je u pitanju podrška za uređaje sa novim procesorima.
Naime, Windows 7 je sada u fazi produžene podrške te će nastaviti biti podržan sa nadogradnjama koje se tiče sigurnosti i pouzdanosti do 14.1.2020. godine na procesorima iz prethodnih generacija, dok će Windows 8.1 imati istu podršku do 10.1.2023. godine.
U budućnosti, novi procesori koji se pojave na tržištu će zahtijevati korištenje aktuelne verzije Windows platforme. Na primjer, Windows 10 će biti jedina podržana Windows platforma za nadolazeće procesore i platforme kao što su Intel "Kaby Lake", Qualcomm "8996", AMD "Bristol Ridge", itd.
U isto vrijeme, aktuelna Intel platforma, poznata pod nazivom "Skylake", odnosno šesta generacija Intel Core procesora, će na Windows 7 i Windows 8.1 operativnim sistemima biti podržana do 17.7.2017. godine, nakon čega će uređaji bazirani na spomenutoj platformi koji se zadrže na Windows 7 i Windows 8.1 operativnim sistemima dobivati samo najkritičnije sigurnosne nadogradnje koje će biti izdane samo u slučaju da ne narušavaju pouzdanost ili kompatibilnost Windows 7 / 8.1 platforme na drugim uređajima. U tom smislu, preporuka Microsofta je da se svi uređaji na ovoj platformi nadograde na Windows 10 prije spomenutog datuma.
Na ovoj stranici možete pronaći listu Skylake-baziranih modela koji su podržani uz Windows 7 i Windows 8.1 operativne sisteme.
Microsoft Press offre la version électronique du livre Introducing Microsoft SQL Server 2016: Mission-Critical Applications, Deeper Insights, Hyperscale Cloud, Preview 2. Il est disponible sur ce lien.
Sejam muito bem-vindos a mais um Domingo Surpresa.
O monitoramento de aspectos como desempenho, disponibilidade e falhas é uma questão vital em qualquer tipo de aplicação. Apesar da sua inegável importância, este tipo de atividade costuma demandar um grande empenho do ponto de vista de desenvolvimento.
Em situações comuns este trabalho de monitoração implica em esforços de codificação ao longo de todo um projeto, com vistas a coletar dados que servirão de base para a geração das mais diversas análises. Cada análise, por sua vez, também poderá adicionar mais horas à fase de implementação (por estar normalmente atrelada à construção de alguma espécie de relatório).
Procurando simplificar este processo de monitoramento a Microsoft disponibilizou um serviço conhecido como Application Insights, o qual é parte do Microsoft Azure:
Contando com SDKs para inúmeras plataformas, o Application Insights tem por objetivo evitar ao máximo a codificação de instruções para a coleta de dados visando a monitoração posterior (muito embora customizações via código também sejam possíveis). Logo, esta alternativa não está restrita ao mundo .NET/Microsoft; Java, Node.js, Python, Ruby e JavaScript são outros exemplos de tecnologias suportadas. É importante destacar ainda que este serviço conta com inúmeros dashboards sofisticados, fornecendo visões em diferentes níveis analíticos.
Para saber mais sobre o Application Insights acesse o link:
証明書を開き、証明のパスのタブを開きます。一番上に表示されているのが、ルート証明機関です。(ダブルクリックでルート証明機関の証明書を開くことができます) そのルート証明機関が、マイクロソフトのルート証明機関に所属しているかを Microsoft Trusted Root Certificate Program Updates (http://aka.ms/rootupdates)にある最新のリスト (" most-current list of Program participants and enrolled roots" と書いてある最新のリスト) のリストから確認します。
リストに含まれていない場合は、今回の廃止措置の対象外の証明書です。(SSL/TLS 証明書は、マイクロソフト ルート証明書プログラムに参加している証明機関から発行されている SSL/TLS 証明書のみが廃止対象です。それ以外の証明機関から発行されている証明書は廃止対象ではありません。たとえば、企業内・組織内システムなどで、Windows Server の証明書サービスを利用して発行している証明書や、自己署名証明書は廃止の対象外です。)
Microsoft Azure Backup Server – část 1 Microsoft Azure Backup Server – část 2
Obnova dat ze zálohy Ve chvíli kdy nám zálohování běží a podařilo se nám data odzálohovat na lokální disk určený k zálohám a případně do Windows Azure, může v případě potřeby přistoupit k obnově dat ze záloh. Tedy v tomto případě přejdeme na záložku „Recovery“...(read more)
