Yesterday I got a chance to work with one of the customer who was facing issue with Profile Synchronization service in hung state as 'Starting' status in his SharePoint 2013 environment.

In the ULS viewer OWSTIMER.EXE process were throwing below error.

"UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS post database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: ERR_CONFIG_DB     at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ValidateConfigurationResult(UInt32 result)     at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ConfigureMiisStage2()     at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance)"

Based on above error I made action plan which directed to resolution.

1) Ran 'Get-SPServiceInstance' in Sharepoint Powershell to get the status of Profile Synchronization and found its in 'Provisioning' status.

2) Stopped Profile Synchronization service by running the command 'Stop-SPServiceInstance'.

3) Database was running on SQL2012 and  checked SQL Native client in C:\Windows\System32 and found it was version11 (sqlncli11.dll).

4) Next step was to check the SharePoint box and found there are no SQL Native client deployed which is one of prerequisite for SharePoint 2013 deployment.

5) After deploying SQL Server 2008 R2 SP1 Native Client in all SharePoint boxes, clicked on Start 'User Profile Synchronisation Service' and it Started successfully.

The Microsoft Virtual Machine Converter 2.0 is available! The Microsoft Virtual Machine Converter provides a supported, freely available, stand-alone solution for converting VMware-based virtual machines and virtual disks to Hyper-V-based virtual machines and virtual hard disks (VHDs). 

There is also a release of an update to the Migration Automation Toolkit (MAT). This is a collection of PowerShell scripts that will automate conversions using MVMC.  You can use it to convert several machines at once, on a single server – or scale it out and execute conversions on many servers at the same time.

With the release, you will be able to access many new features including:

• On-premises VM to Azure VM conversion
• PowerShell interface for scripting and automation support
• Added support for vCenter & ESX(i) 4.1, 5.0 and now 5.5
• VMware virtual hardware version 4 – 10 support
• Linux Guest OS support including CentOS, Debian, Oracle, Red Hat Enterprise, SuSE enterprise and Ubuntu.
• Migration Automation Toolkit support for MVMC 2.0

Migration Automation Toolkit (MAT)
http://gallery.technet.microsoft.com/Automation-Toolkit-for-d0822a53

More Information
http://blogs.technet.com/b/server-cloud/archive/2014/04/08/available-now-the-microsoft-virtual-machine-converter-2-0.aspx

MVMC Converter Download
http://www.microsoft.com/en-us/download/details.aspx?id=42497

Microsoft has been listening to customer feedback. Much of this feedback has been received and some of the results are being given back to our users of Windows 8.1 in the form of updates. Recently, a very big update for Windows 8.1 was released. Read all about it here:

http://windows.microsoft.com/en-us/windows-8/whats-new

Since Microsoft wants to ensure that customers benefit from the best support and servicing experience and to coordinate and simplify servicing across both Windows Server 2012 R2, Windows 8.1 RT and Windows 8.1, this update will be considered a new servicing/support baseline. What this means is those users who have elected to install updates manually will have 30 days to install Windows 8.1 Update  on Windows 8.1 devices; after this 30-day window - and beginning with the May Patch Tuesday, Windows 8.1 user's devices without the update installed will no longer receive security updates.

This means that Windows 8.1 users - starting patch Tuesday in May 2014 and beyond - will require this update to be installed.  If the Windows 8.1 Update is not installed, those newer updates will be considered “not applicable.”

More detailed information can be found in the following links:

KB2919355 (Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014)
http://support.microsoft.com/kb/2919355

A servicing stack update is available for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2: March 2014
http://support.microsoft.com/kb/2919442

What's New in the Windows 8.1 Update
http://technet.microsoft.com/en-us/windows/dn646749

Windows 8.1 Update: The IT Pro Perspective
http://blogs.windows.com/windows/b/springboard/archive/2014/04/02/windows-8-1-update-the-it-pro-perspective.aspx
 
Windows Server 2012 R2 Update is now available to subscribers
http://blogs.technet.com/b/windowsserver/archive/2014/04/02/windows-server-2012-r2-update-is-now-available-to-subscribers.aspx.
 
For those users who are still using Windows 8 and Windows 2012 (and not Windows 8.1 and Windows 2012 R2) you are unaffected and will continue to receive updates as normal.

The new baseline only exists for Windows 8.1 and Windows Server 2012 R2.

Another important item for our enterprise users and IT pros out there: There is also an issue regarding Windows 8.1 Update preventing interaction with WSUS 3.2 over SSL connections. This has been outlined in the following blog post:

Windows 8.1 Update (KB 2919355) prevents interaction with WSUS 3.2 over SSL
http://blogs.technet.com/b/wsus/archive/2014/04/08/windows-8-1-update-prevents-interaction-with-wsus-3-2-over-ssl.aspx

Microsoft plans to issue an update as soon as possible that will correct the issue and restore the proper behavior for Windows 8.1 Update KB 2919355 scanning against all supported WSUS configurations. Until that time, we are delaying the distribution of the Windows 8.1 Update KB 2919355 to WSUS servers.

You may still obtain the Windows 8.1 Update (KB 2919355) from the Windows Update Catalog or MSDN. However, we recommend that you suspend deployment of this update in your organization until we release the update that resolves this issue.

You may also find the workarounds discussed in this article to be useful for testing this Windows 8.1 Update for your organization. Thank you for your patience during this time.

In addition, some training and readiness docs have been recently published along with updated toolkits:

Windows 8.1 Update User Readiness Toolkit
http://www.microsoft.com/en-us/download/details.aspx?id=42255

Windows 8.1 Update Power User Guide for Business
http://www.microsoft.com/en-us/download/details.aspx?id=41667

Windows 8.1 Update how-to videos for business users
http://www.microsoft.com/en-us/download/details.aspx?id=42314

Windows Driver Kit 8.1 Update 1
http://www.microsoft.com/en-us/download/details.aspx?id=42273

Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1 Update
http://www.microsoft.com/en-us/download/details.aspx?id=39982

Additional Blogs:

http://blogs.windows.com/windows/b/springboard/archive/2014/04/02/windows-8-1-update-the-it-pro-perspective.aspx
http://blogs.windows.com/windows/b/windowsexperience/archive/2014/04/02/windows-8-1-update-important-refinements-to-the-windows-experience.aspx
http://blogs.windows.com/windows/b/business/archive/2014/04/02/building-the-mobile-workplace-with-windows-and-windows-phone.aspx
http://blogs.windows.com/windows/b/springboard/archive/2014/04/02/windows-8-1-update-the-it-pro-perspective.aspx
http://blogs.msdn.com/b/ie/archive/2014/04/02/stay-up-to-date-with-enterprise-mode-for-internet-explorer-11.aspx
http://blogs.technet.com/b/windowsserver/archive/2014/04/02/windows-server-2012-r2-update-is-now-available-to-subscribers.aspx
http://blogs.windows.com/windows/b/springboard/archive/2014/04/03/windows-8-1-sideloading-enhancements.aspx
http://blogs.technet.com/b/askpfeplat/archive/2014/04/07/exploring-windows-8-1-update-start-screen-desktop-and-other-enhancements.aspx

Summary: Manage DHCP server settings in Windows Server 2012 R2 with Windows PowerShell.

Honorary Scripting Guy, Sean Kearney, is here. This weekend, I’m getting a little geeky. I’m going to continue with more of Windows PowerShell and the network cmdlets. This is the sixth part in a series called Windows PowerShell Network Week. You also might enjoy reading:

• Windows Server 2012 R2 Network Cmdlets: Part 1
• Windows Server 2012 R2 Network Cmdlets: Part 2
• Windows Server 2012 R2 Network Cmdlets: Part 3
• Windows Server 2012 R2 Network Cmdlets: Part 4
• Windows Server 2012 R2 Network Cmdlets: Part 5

Today I’m going to investigate the cool new cmdlets for managing the DHCP server!

Oh I wish I had these at my last job! We were deploying new workstations and imaging systems. For this to work, I needed to send a Wake on Lan to the workstations. The problem was that I didn’t have SCCM on the remote sites and the WAN wasn’t passing the packets.

So I figured I could use Windows PowerShell and a cool Wake on Lan script from Marcus Van Orsow (/\/\0\/\/) running on the remote servers and my local one to do the trick. I combined this with a DHCP parsing trick from The Admin Guy. For the original post of this solution, see Powershell–Wake on LAN from /\/\o\/\/ and DHCP Parse from “The Admin Guy”–WHAT A COMBO!

I was happy with the solution, but at the time, I really wished that there was an easier way to work with DHCP. Now there is!

One of the challenges was to get a list of the available scopes in my original solution. In Windows Server 2012 R2, you can run the following cmdlet to get a list of available scopes in your DHCP server:

Get-DHCPServerv4Scope

As you can see, all of the details about this scope can be easily identified—even exported for documentation!

Get-DHCPServerv4Scope | Export-CSV C:\Foo\ContosoScopes.CSV

But here’s where Windows PowerShell rocks even more. What I can do now for modern day servers is use the cmdlets to build out a DHCP server.

First create a new scope. We’ll pick a pretty simple configuration:

Name ‘Sample’

Description ‘My Sample Scope Description’

Network 192.168.1.0

Subnet Mask 255.255.255.0 (24 bits)

Starting 192.168.1.100

Ending 192.168.1.200

We can do this in one line with Windows PowerShell:

Add-DhcpServerv4Scope -Name ‘Sample’ -StartRange 192.168.1.100 -EndRange 192.168.1.200
–Description ‘Sample for 192.168.1.0’ -SubnetMask 255.255.255.0

You can also edit the options for your scope with the same cmdlets. To make things easier, you can get a list of the available options defined in your DHCP server by using the Get-DHCPServerv4OptionDefinition cmdlet:

Get-DHCPServerv4OptionDefinition

So I can find the names I can use for options pretty easily:

Get-DHCPServerv4OptionDefinition | where { $_.Name –like ‘*DNS*’ }

We can obtain the name we can use for the router option in the same manner:

Get-DHCPServerv4OptionDefinition | where { $_.Name –like ‘*Router*’ }

Now we can add options to our new scope by leveraging the Set-DHCPServerv4OptionValue cmdlet. But instead of using the name, we need to use the OptionID provided for the name. To add a router IP of 192.168.1.1 to our current scope called ‘Sample’, we’d do it like this in Windows PowerShell:

$id=(Get-DHCPServerv4Scope | Where { $_.Name –eq ‘Sample’ }).ScopeID

Set-DHCPServerv4ScopeOptionValue –Scope $Id –optionid 3 –value 192.168.1.1

Now that we have the ID, we can set up the DNS servers for this scope. We’ll use two internal servers 192.168.1.5 and 192.168.1.25:

Set-DHCPServerv4ScopeOptionValue –Scope $Id –optionid 6 –value 192.168.1.5,192.168.1.25

What’s interesting with this cmdlet is you can’t put in a false DHCP server. It will validate that it’s a live server first!

Now thinking back to my original problem with DHCP servers, I could have easily pulled out the current list of leased IP addresses from all of my scopes by doing something as simple as this and storing them into a CSV file:

Get-DHCPServerv4Scope | Get-DHCPServerv4Lease | Export-CSV CurrentIP.csv

Pretty cool, eh?

Pop back over tomorrow for our final day of Windows PowerShell Network Week, and we’ll play with going where no cmdlet has boldly gone before: Easily managing a DNS server!

I invite you to follow the Scripting Guys on Twitter and Facebook. If you have any questions, send an email to the Scripting Guys at scripter@microsoft.com, or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then just remember, the Power of Shell is in You.

Sean Kearney, Windows PowerShell MVP, Honorary Scripting Guy

Er Heartbleed farlig for min Microsoft infrastruktur ? 

Heartbleed truslen i OpenSSL (katalogiseret som CVE-2014-0160) rammer alene OpenSSL. De mest anvendte applikationer, der anvender OpenSSL, er Apache og nginx.

Heartbleed har modtaget meget opmærksomhed de par dage i forskellige medier til trods for, at den er meget gammel. Så vidt jeg husker blev bristen afsløret allerede i 2011, men de sidste par dage har den fået et navn og er kommet på vores alles læber - og der er i øvrigt også kommet et sikkerhedspatch.

Truslen er også reel - en ondsindet hacker vil gennem sikkerhedshullet kunne få adgang til data, der ellers er krypteret, og dette giver en alvorlig sikkerhedsfejl. Sender du eksempelvis dit password gennem en OpenSSL-krypteret forbindelse, der ikke er blevet opdateret med sikkerhedspatch'et, risikerer du at vise dit password for en hacker.

Opmærksomheden giver en både sund og naturlig anledning til at overveje, om truslen kan påvirke den generelle Microsoft infrastruktur, herunder især Windows og IIS.

Heldigvis er truslen ikke noget, vi ser meget til i Danmark, og det skyldes, at en default konfiguration af ethvert Microsoft produkt ikke omfatter OpenSSL. Windows kommer med sin egen krypteringskomponent, Secure Channel (i daglig tale SChannel), som ikke er omfattet af truslen. Dette omfatter alle Windows operativsystemer og IIS versioner op til og inklusive IIS 8.5 (som er den aktuelle version) på følgende server operativsystemer:

• Windows Server 2003

• Windows Server 2003R2

• Windows Server 2008

• Windows Server 2008R2

• Windows Server 2012

• Windows Server 2012R2

Microsoft konti (det tidligere Windows Live ID), Microsoft Azure, Office 365 og alle andre Microsoft skyservices er heller ikke omfattet af truslen.

Eneste mulighed for, at være omfattet af truslen, er derfor, hvis der anvendes OpenSSL fremfor SChannel (f.eks. hvis der køres en Windows-version af Apache eller tilsvarende). For de brugere, der afvikler disse, anbefales det altid at følge de guidelines, der kommer fra den aktuelle udbyder af den berørte software. Dette kan du læse mere om på US Cert her.  

Du kan læse Wikipedias uddybende artikel her og det finske sikkerhedsfirma's Codenomicon beskrivelse her.

Virou rotina. Mais uma vez, a primeira colocação geral desta semana vai para Fernando Lugão Veltem. Ele não se limitou apenas a colaboração na comunidade Microsoft Technet Brasil mais também surpreendeu a comunidade Internacional.

Prêmio Maiores Revisores  Quem fez mais revisões individuais

#1 Fernando Lugão Veltem com 144 revisões.

#2 Marcelo Strippoli com 6 revisões.

#3 Durval Ramos com 5 revisões.

Prêmio Artigos mais atualizados  Quem atualizou mais artigos

#1 Fernando Lugão Veltem com 134 artigos.

#2 Durval Ramos com 5 artigos.

#3 Benoit Jester - MTFC com 2 artigos.

Prêmio maioria dos artigos atualizados  A maior quantidade de conteúdo atualizado em um único artigo

O artigo a ter a maioria das mudanças esta semana foi ASP.NET MVC - Início, Meio e Fim - Parte 1, escrito por Fabrício Sanchez

O revisor desta semana foi Renato Person,

O artigo a ter a maioria das mudanças esta semana foi Windows Server 2012 - Recuperação de Desastres com o Hyper-V Replica, escrito por Leandro E. Carvalho

Os revisores desta semana foram Fernando Lugão Veltem& Leandro E. Carvalho

O artigo a ter a maioria das mudanças esta semana foi Conhecendo as novas opções de mobilidade do Windows Server 2012 Hyper-V, escrito por Leandro E. Carvalho

Os revisores desta semana foram Fernando Lugão Veltem& Leandro E. Carvalho

O artigo a ter a maioria das mudanças esta semana foi The Following Error Occurred Attempting to Join the Domain (Sid Duplicados) , escrito por Jefferson Castilho

O revisor desta semana foi Fernando Lugão Veltem,

O artigo a ter a maioria das mudanças esta semana foi Como Funciona – System Center Advisor 2012, escrito por Thiago Guirotto

O revisor desta semana foi Fernando Lugão Veltem,

O artigo a ter a maioria das mudanças esta semana foi Solucionando Problemas: Impressão em Remote Desktop Service (Terminal Service) Parte 9 Final, escrito por Prof Andre Luiz

O revisor desta semana foi Fernando Lugão Veltem,

O artigo a ter a maioria das mudanças esta semana foi Server Core - Command Prompt - IF EXIST, escrito por Jordano Mazzoni - MVP

O revisor desta semana foi Fernando Lugão Veltem,

O artigo a ter a maioria das mudanças esta semana foi Habilitando a conta de Administrador no Windows 7, escrito por Luiz Henrique Lima Campos [MVP]

O revisor desta semana foi Fernando Lugão Veltem,

O artigo a ter a maioria das mudanças esta semana foi Windows Server 2012 - Recuperação de Desastres com o Hyper-V Replica, escrito por Leandro E. Carvalho

O revisor desta semana foi Leandro E. Carvalho,

O artigo a ter a maioria das mudanças esta semana foi Windows Server 2012 - Recuperação de Desastres com o Hyper-V Replica, escrito por Leandro E. Carvalho

O revisor desta semana foi Leandro E. Carvalho,

Prêmio Artigo com mais longa atualização  O artigo com mais longa atualização desta semana

O artigo que obteve maior atenção esta semana foi Como Funciona – System Center Advisor 2012, escrito por Thiago Guirotto

O revisor desta semana foi Fernando Lugão Veltem,

O artigo que obteve maior atenção esta semana foi ASP.NET MVC - Início, Meio e Fim - Parte 1, escrito por Fabrício Sanchez

O revisor desta semana foi Renato Person,

O artigo que obteve maior atenção esta semana foi Solucionando Problemas: Impressão em Remote Desktop Service (Terminal Service) Parte 9 Final, escrito por Prof Andre Luiz

O revisor desta semana foi Fernando Lugão Veltem,

O artigo que obteve maior atenção esta semana foi Conhecendo as novas opções de mobilidade do Windows Server 2012 Hyper-V, escrito por Leandro E. Carvalho

Os revisores desta semana foram Fernando Lugão Veltem& Leandro E. Carvalho

O artigo que obteve maior atenção esta semana foi Windows Server 2012 - Recuperação de Desastres com o Hyper-V Replica, escrito por Leandro E. Carvalho

Os revisores desta semana foram Fernando Lugão Veltem& Leandro E. Carvalho

O artigo que obteve maior atenção esta semana foi Server Core - Command Prompt - IF EXIST, escrito por Jordano Mazzoni - MVP

O revisor desta semana foi Fernando Lugão Veltem,

O artigo que obteve maior atenção esta semana foi The Following Error Occurred Attempting to Join the Domain (Sid Duplicados), escrito por Jefferson Castilho

O revisor desta semana foi Fernando Lugão Veltem,

O artigo que obteve maior atenção esta semana foi Habilitando a conta de Administrador no Windows 7, escrito por Luiz Henrique Lima Campos [MVP]

O revisor desta semana foi Fernando Lugão Veltem,

O artigo que obteve maior atenção esta semana foi Windows Server 2012 - Recuperação de Desastres com o Hyper-V Replica, escrito por

O revisor desta semana foi Leandro E. Carvalho,

O artigo que obteve maior atenção esta semana foi Windows Server 2012 - Recuperação de Desastres com o Hyper-V Replica, escrito por Leandro E. Carvalho

O revisor desta semana foi Leandro E. Carvalho,

Prêmio maioria dos artigos revisados   Artigo com mais revisões em uma semana

Esta semana, a maioria que brincava com artigo é Guia de Sobrevivência: Windows 8 e Windows 8.1, escrito por Jorge Barata [JB]. Ele foi revisto 4 vezes na semana passada.

Os revisores desta semana foram Marcelo Strippoli, WeberCarmo& Fernando Lugão Veltem

Esta semana, a maioria que brincava com artigo é Plataformas, escrito por Jorge Barata [JB]. Ele foi revisto 3 vezes na semana passada.

Os revisores desta semana foram Marcelo Strippoli& WeberCarmo

Esta semana, a maioria que brincava com artigo é Exchange Server 2013 Database Availability Groups, escrito por Fernando Lugão Veltem. Ele foi revisto 3 vezes na semana passada.

O revisor desta semana foi Fernando Lugão Veltem,

Esta semana, a maioria que brincava com artigo é Preparar ambiente para o System Center 2012 Configuration Manager SP1, escrito por Jeovan M. Barbosa. Ele foi revisto 2 vezes na semana passada.

O revisor desta semana foi Jeovan M. Barbosa,

Esta semana, a maioria que brincava com artigo é Portal de Grupos de Usuários Microsoft, escrito por Durval Ramos. Ele foi revisto 1 vez na semana passada.

O revisor desta semana foi Fernando Lugão Veltem,

Esta semana, a maioria que brincava com artigo é BizTalk Server 2013: Visualizando suas Dependências, escrito por Durval Ramos. Ele foi revisto 1 vez na semana passada.

O revisor desta semana foi Fernando Lugão Veltem,

Esta semana, a maioria que brincava com artigo é Grupos de Usuários de Desenvolvimento .Net, escrito por Durval Ramos. Ele foi revisto 1 vez na semana passada.

O revisor desta semana foi Fernando Lugão Veltem,

Esta semana, a maioria que brincava com artigo é Grupo de Usuários Microsoft Dynamics, escrito por Durval Ramos. Ele foi revisto 1 vez na semana passada.

O revisor desta semana foi Fernando Lugão Veltem,

Esta semana, a maioria que brincava com artigo é ALM – Como Editar Work items e Process Template do TFS – Process Template, escrito por Alan Nascimento Carlos. Ele foi revisto 1 vez na semana passada.

O revisor desta semana foi Fernando Lugão Veltem,

Esta semana, a maioria que brincava com artigo é Preparação para o Exame 70-341, escrito por Rafael Mantovani. Ele foi revisto 1 vez na semana passada.

O revisor desta semana foi Fernando Lugão Veltem,

Prêmio do artigo mais popular  Colaboração é o nome do jogo!

O artigo a ser atualizado pela maioria das pessoas desta semana é Guia de Sobrevivência: Windows 8 e Windows 8.1, escrito por Jorge Barata [JB]

Os revisores desta semana foram Marcelo Strippoli, WeberCarmo& Fernando Lugão Veltem

O artigo a ser atualizado pela maioria das pessoas desta semana é Plataformas, escrito por Jorge Barata [JB]

Os revisores desta semana foram Marcelo Strippoli& WeberCarmo

O artigo a ser atualizado pela maioria das pessoas desta semana é Autenticação via Powershell utilizando Get-Credential e PSCredential, escrito por Matheus Kamphorst

O revisor desta semana foi Fernando Lugão Veltem,

Agradecemos à todos os membros da nossa comunidade Microsoft pelas grandes contribuições realizadas ao longo desta semana. Vale lembrar, que toda e qualquer ajuda/contribuição para a comunidade é importante e muito bem vinda.

Hi all,

I’ve been meaning to write this for a long time now and finally I’ve had some time to actually sit down and write it.

The question that I always get asked onsite with customers is “how do we troubleshoot App-V 5.0?”

Some of the common errors we see look like this:

Application Failed to launch

Sync Failure

The starting point is the App-V event log which sits under Applications and Services Log – Microsoft – AppV – Client. The main log that you will use is the Admin Log.

Next step is to look at the “hidden” and “magic” debug logs which are available by selecting:

View – “Show Analytic and Debug Logs”

If you have ever looked at the extra logs there are certainly a lot available but which ones should you enable? Steve Thomas has given some great guidance into which logs you should enable in certain situations.

http://blogs.technet.com/b/gladiatormsft/archive/2013/11/13/app-v-on-operational-troubleshooting-of-the-v5-client.aspx

If anyone that has ever used these logs you have to enable them individually and manually which is a time consuming experience.

So let’s automate it, but where do you start?

Well Logman is your friend for ETW automation.

http://technet.microsoft.com/en-us/library/cc753820.aspx

Logman creates and manages Event Trace Session and Performance logs and supports many functions of Performance Monitor from the command line.

e.g. logman [create | query | start | stop | delete| update | import | export | /?] [options]

You can create a logman trace using the following script:

If we break the main part of this script we need to get all the provider for App-V registered on the machine so we’re using Get-WinEvent to find all the App-V providers.

Once we have this then the AppVClientProviders.txt file is created which will look something like this.

The final section is running the logman command.

The command switches are explained below:

-o Path of the output log file

-f Specifies the log format for the data collector

-pf File listing multiple Event Trace providers to enable

-ct <perf|system|cycle> Specifies the clock resolution to use when logging the time stamp for each event.

Once this has been ran the following “Data Collector Sets” under User Defined will be created in Performance Monitor.

You can view the properties of this data by right clicking and selecting “Properties”.

Once the settings you have configured are correct then you can start the trace with either the GUI:

Or through the logman command line:

Logman start APPV5Debug

Once the problem has been reproduced then stop the trace:

Logman stop APPV5Debug

Once the trace has been stopped the “appv5Debug.etl” will be available to be manipulated.

So that’s great we have an ETL trace of the problem but how do we view the trace??????

How many people have heard or have used Tracerpt.exe???

http://technet.microsoft.com/en-us/library/cc732700.aspx

The tracerpt command can be used to parse Event Trace Logs, log files generated by Performance Monitor, and real-time Event Trace providers. It generates dump files, report files, and report schemas.

Tracerpt.exe Usage

-l Event Trace log file to process

-lr Less restrictive; use best effort for events not matching event schema

-of <CSV|EVTX|XML> Dump format, the default is XML

-o [filename] Text output file. Default is dumpfile.xml.

Once tracerpt.exe has been ran you can then open the EVTX with the “Event Viewer” for extra debug information.

e.g.

Below is the full script that I use, it offers prompts to start and stop traces and some error checking.

To run this make sure you run the script as administrator otherwise when the script try to remove the previously created trace with fail with the following error.

Error:
Access is denied.
You're running with a restricted token, try running elevated.

Disclaimer

The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.

Conclusion

I hope this helps with your collection of debug traces and with your troubleshooting of App-V 5.0.

David Falkus | Premier Field Engineer | Application Virtualization

Summary: Use the DHCP server cmdlets in Windows Server 2012 R2 to show current clients.

 How can I use Windows PowerShell to show my current DHCP server clients?

 Use the Get-DHCPServerv4scope and Get-DHCPServerv4Lease cmdlets piped together:

Get-DHCPServerv4scope | Get-DHCPServerv4Lease 

Merhaba TechNet Wiki ailesi

         Bugün Pazar sürpriz olarak Bilişim Sektörüne gönül veren hatta bilişim sektörüne yön veren isimlerden olan çok değerli bir hocamızdan sizlere bahsetmek istiyorum. Tabii ki başlıktan da anlaşılacağı üzere Mustafa KARA’dan sizlere bahsedeceğim. Kendisi bilişim yürekten gönül vermiş ve bilgi ve tecrübelerini sürekli olarak bizlerle paylaşmaktadır. Şunu hepimiz iyi biliyoruz ki teknik anlamda Türkiye’de Türkçe kaynak sıkıntısı yaşanmaktadır. Kendisi Türkçe kaynaklar üreterek bu eksiklikleri başarılı bir şekilde tamamlamaktadır. Bunun yanında Türkiye’nin önde gelen IT Topluluğu olan MSHOWTO’da ve bir çok sitede makale webcastleri yayınlanmaktadır. Bunun yanında System Center Cloud and Datacenter Management konusunda 3 yıldır üst üste MVP’lik ünvanına layık görülmüştür. Peki Mustafa KARA bu zamana kadar neler yaptı. Yüzeysel olarak bir inceleyelim.

-          150’nin Üzerinde Teknik Makale

-          50’ye yakın Webcast

-          30’a yakın Seminer

-          20’ye yakın Workshop ve Microsoft Seminerleri

      Aslında yukarıda ki tabloya bakıldığında pekte söylenecek bir söz olmadığını düşünüyorum. Forumlarda verdiği cevapları işin içerisine katmıyorum bile gerisini siz düşünün J  Şuna her zaman inanmışımdır. Elinizde bir ekmek olduğunu düşünün ve bu ekmeği çevrenizde kaç kişi varsa bölüp paylaştığınızı işte değerli Mustafa KARA’da insanlarla bilgi ve tecrübelerini paylaşarak kısacası bizlerle ekmeğini paylaşıyor. Sektörde bulunan bir çok insanın kendisini geliştirmesinde ve mesleğini severek icra etmesini sağlıyor. Buraya kadar Mustafa KARA’nın yaptığı paylaşımlar hakkında dilimin döndüğü kadar bilgi vermeye çalıştım. Peki Mustafa KARA nasıl bir kişiliğe sahip öncelikle güler yüzlü kendisiyle konuşmaya kalktığınızda sizlerle emin olun ki kırk yıllık bir dost gibi konuşacağı kesin sizlerin de tahmin edeceği üzere ayrıntıya girmek abest olur diye düşünüyorum.  

Kendisi sadece MSHOWTOüzerinde makaleler yazmıyor. Bir çok platformda yazıyor. Bunların başında tabii ki TechNet üzerinde’de makaleler paylaşıyor.  

TechNet üzerinde paylaştığı makale sayısına baktığımızda toplamda 101 adet makale paylaşılmış ayrıntılı bilgiye buradan ulaşabilirsiniz.

Peki Mustafa Kara’ya Nasıl ulaşabilirsiniz. Sorunun cevabı oldukça basit Google Mustafa Kara yazın sonuçlara bakın. :D

MVP Profil : http://mvp.microsoft.com/en-us/mvp/Mustafa%20Kara-4033574

TechNet Profil : http://social.technet.microsoft.com/profile/mustafa%20kara%20-%20mvp/

Web Site : http://www.mustafakara.net.tr/

      Bugün kü Pazar sürprizi olarak dilimin döndüğü kadar sizlere kısaca değerli hocamız Mustafa KARA’yı anlatmaya çalıştım.  Bir hatamız olduysa af fola kendisini buradan tekrar tekrar tebrik ederek başarılarının devamını diliyorum. Başka blog postlarda görüşmek üzere…

Welcome back for another analysis of contributions to TechNet Wiki over the last week.

First up, the weekly leader board snapshot...

Fernando still waaaay out in front! Great work Fernando!

As always, here are the results of another weekly crawl over the updated articles feed.

Most Revisions Award   Who has made the most individual revisions

#1 Fernando Lugão Veltem with 270 revisions.

#2 Benoit Jester - MTFC with 111 revisions.

#3 .paul. _ with 34 revisions.

Just behind the winners but also worth a mention are:

#4 StarrAndersen with 23 revisions.

#5 Damir Dobric with 21 revisions.

#6 Shreeharsh Ambli with 21 revisions.

#7 Baris Aydogmusoglu with 20 revisions.

#8 Just Karl with 17 revisions.

#9 Shanky_621 with 15 revisions.

#10 pituach with 15 revisions.

Most Articles Updated Award   Who has updated the most articles

#1 Fernando Lugão Veltem with 245 articles.

#2 Benoit Jester - MTFC with 71 articles.

#3 StarrAndersen with 15 articles.

Just behind the winners but also worth a mention are:

#4 Durval Ramos with 10 articles.

#5 Shanky_621 with 8 articles.

#6 Just Karl with 7 articles.

#7 Damir Dobric with 5 articles.

#8 Denis Dyagilev with 5 articles.

#9 Ersin CAN - TAT with 5 articles.

#10 Tomasso Groenendijk with 4 articles.

Most Updated Article Award   Largest amount of updated content in a single article

The article to have the most change this week was Office365 Cloud Group Membership Management with Windows PowerShell Connector for FIM 2010 R2 , by Adam Weigert

This week's reviser was Adam Weigert

This is a very fine document.

A great addition to the wiki, methinks...

Very nice layout work. 

Very detailed article.

Thanks for this Adam!

Longest Article Award   Biggest article updated this week

This week's largest document to get some attention is Windows Azure Pack (#WAPack) and Related Blogs, Videos and TechNet Articles, by Hans Vredevoort - Hyper-V MVP

This week's reviser was Hans Vredevoort - Hyper-V MVP

This is an article that has come and gone. It looks like a complete rewrite to bring it up to date may be in the offering...

Most Revised Article Award   Article with the most revisions in a week

This week's most fiddled with article is masterMind Game, by .paul. _. It was revised 34 times last week.

This week's revisers were .paul. _& Shanky_621

This is a new entry into this month's Guru competition,and... wow... what a great entry! 

This is an example of how the Guru competitions have spurred some great minds into great publications!

We have had some truly amazing contributions from the TechNet community in the last year and a bit.

We are learning some great names, who will be remembered for generations to come.

Most Popular Article Award   Collaboration is the name of the game!

The article to be updated by the most people this week is Installing SQL Server 2014 Step by Step Tutorial, by pituach

This week's revisers were pituach, Just Karl, Benoit Jester - MTFC, Ed Price - MSFT, Naomi N & Shanky_621

This is a great example of how the community comes together to help buff a great contribution into perfection.

An amazing article by pituach, again for April's Guru competition, showing how the community are matching MS contributions like for like across all technologies!

Go go Gurus!!

Ninja Edit Award   A ninja needs lightning fast reactions!

Below is a list of this week's fastest ninja edits. That's an edit to an article after another person

• Revision 13 of Windows Server 2012 R2 Work Folders Kurulumu Için Yapilmasi Gereken Sertifika Islemleri, IIS Yapilandirmasi ve Kurulumu Part-1 (tr-TR) was saved by Fernando Lugão Veltem just 1 minute after Baris Aydogmusoglu

  Yey for Fernando! A deserved THIRD medal this week, for a TNWiki legend!
  Also in the charts this week are:

• Revision 1 of Building Custom Forms Using SharePoint Designer 2013 was saved by Fernando Lugão Veltem just 4 minutes after Dan Christian
• Revision 3 of Streaming Videos using Windows Azure Media Services & ASP.NET was saved by Benoit Jester - MTFC just 6 minutes after Shreeharsh Ambli
• Revision 4 of Parallel / Concurrent / Async Programming in C# using Tasks was saved by Benoit Jester - MTFC just 7 minutes after Shreeharsh Ambli
• Revision 3 of VBSCRIPT - Allow Users to choose which network drives to map, alert if process is running, find if current drive is mapped was saved by Benoit Jester - MTFC just 18 minutes after Dominic Ace
• Version 4 of VBSCRIPT - Allow Users to choose which network drives to map, alert if process is running, find if current drive is mapped was saved by Dominic Ace just 25 minutes after Benoit Jester - MTFC
• Revision 1 of Windows Azure Service Bus: Sending the message to queue and topic with JavaScript was saved by Chen V just 26 minutes after Damir Dobric
• Revision 14 of Windows Server 2012 R2 Work Folders Kurulumu Için Yapilmasi Gereken Sertifika Islemleri, IIS Yapilandirmasi ve Kurulumu Part-1 (tr-TR) was saved by Baris Aydogmusoglu just 27 minutes after Fernando Lugão Veltem
• Revision 2 of BizTalk: Resource Dispenser – Send Port Edition was saved by Ravindar Thati just 34 minutes after Benoit Jester - MTFC
• Revision 577 of Turkish Avengers Team Council Center was saved by Hasan Dimdik - TAT just 39 minutes after Ersin CAN - TAT

Hooray for TechNet Wiki!!!

It is definitely in good health for Spring!

We really are lucky to have such dedicated professionals helping grow this community.

Thank you all for enriching my week yet again!

Hopefully see you next week!

Best regards,
Pete Laker

With the release of the Windows 8.1 Update, there is a new mechanism available for running Windows called Windows Image Boot, or WIMBoot for short.  For details about what this is and how it works, see the Springboard blog.

Although MDT 2013 doesn’t include any specific support for WIMBoot (maybe something that could be considered for a future release), there’s nothing preventing anyone from following the instructions available in the ADK to create a task sequence that does it.  So I decided to try it.  Let’s walk through the process at a high level.

Step #1:  Create an image with Windows 8.1 Update

Because WIMBoot is a new feature with the Windows 8.1 Update, it makes sense that you first need to have a Windows 8.1 image that contains the Windows 8.1 Update.  The easiest way to do this is to download a pre-patched ISO from the Volume License Service Center on April 14th, but you can also inject the Windows 8.1 Update fixes into an existing Windows image.

Step #2: Get MDT 2013 to create a Windows PE 5.1 boot image

In order to deploy WIMBoot, you need to use a version of Windows PE that supports it.  That would be Windows PE 5.1.  But that’s not a version that you just download and use.  Instead, it’s a version that you (or ideally MDT) need to create.  The first step in that is to update the ADK to the latest version.  Download the new ADKSETUP.EXE and run it to install all the patches. 

After you’ve done that, the process for creating a Windows PE 5.1 image involves injecting the Windows 8.1 Update into Windows PE.  That’s not something MDT knows anything about, but since MDT includes the ability to run a script during the boot image generation process, it can be “taught.”  That means dropping in an updated UpdateExit.vbs script that injects the six Windows 8.1 Update fixes to the boot image.  And of course it needs to have those updates available to it, so you need to download those from the Download Center and place them where the script can find them.

After that’s done, update the deployment share, completely regenerating the boot image.  This will take quite a while, as the Windows PE generation process itself isn’t very fast to start with, but when you add in the patch installation process the time will easily double.  Maybe you want to try this in a lab :-)

Step #3: Teach MDT how to deploy using WIMBoot

The steps necessary to apply a WIM using WIMBoot are not surprisingly different than what MDT typically does, so the existing LTIApply.wsf script won’t do it.  So we need a new script.  Fortunately, because we can focus exclusively on this one scenario, the scripting needed to this, which follows the ADK steps documented at http://technet.microsoft.com/en-us/library/dn605112.aspx, isn’t too hard.  To add more flexibility and to solve some challenges, I added a few features:

• The script will dynamically determine the size of the “Images” volume needed to hold the WIM file, then shrink the OS partition by that size.  That way, you don’t need to modify the “Format and Partition Disk” step to specify an explicit size, which is nearly impossible to do anyway because you want a fixed-size partition after the OS partition, where the OS partition says “100% of the remaining free space”, an impossible combination in the UI.
• The script will export an existing WIM to make it ready for WIMBoot.  This export process, done using DISM.EXE /Export-Image /WIMBoot, ends up adding a lot of time to the deployment process though, because it ends up decompressing and recompressing the contents of the WIM in the process of exporting it.  As an alternative, you can do this once ahead of time (manually) and tell the script that you’ve done this.
• If for some reason you want to explicitly specify the size of the images partition, you can through a command line parameter.
• Ideally the machine would be set up properly so that the system recovery options (Reset My PC/Refresh My PC) work.  To do this, you need a Windows RE boot image that has been updated with the Windows 8.1 Update fixes, using the same basic steps documented at http://technet.microsoft.com/en-us/library/dn613859.aspx.  That part must be done manually, but the script will look for the WinRE.wim file in the same folder as the OS WIM and copy it to the same “Images” volume and register it as a recovery image.

The next piece is a task sequence.  Since WIMBoot is really only useful for bare metal deployments, I took the standard client task sequence template and chopped it down to the bare minimum needed to perform a bare metal WIMBoot deployment, while still supporting things like driver injection, app installation, Windows Update installation, etc.  The original “Install Operating System” is left in but disabled, since that’s the step that provides a simple way to associate an OS with the task sequence.  Instead of running this step, a new step was added to run “LTIApplyWIMBoot.wsf”, the new script discussed above.  The net result is something that looks like this:

Step #4:  Deploy

Find a machine that meets the requirements and you’re ready to do a bare metal deployment:

• 16GB or 32GB SSD or eMMC solid-state storage.
• UEFI 2.3.1 system (Windows 8 logo-certified).

Ideally these would be machines that come already configured for WIMBoot (since you know it meets the requirements and has been tested by the OEM to ensure good performance).  But if you just want to test it out, you can try it on Windows Server 2012 R2 Hyper-V or Windows 8.1 Hyper-V, since both support “type 2” virtual machines that use UEFI. 

What do you have to do?

Just complete the previous four steps.  OK, but those steps leave out the details, so let’s use a checklist instead.

1. Create a Windows 8.1 Update operating system image by injecting the Windows 8.1 Updates into an existing Windows 8.1 image, or download a new Windows 8.1 Update ISO already containing the updates from VLSC (available on April 14th).  Import the operating system into your MDT deployment share.
2. Download the updated ADKSETUP.EXE for the ADK for Windows 8.1 and use it to install the updated ADK components released with Windows 8.1 Update.
3. Download the Windows 8.1 Update prerequisite (a servicing stack update) for both x86 and x64 from http://support.microsoft.com/kb/2919442, and place them into the “C:\Program Files\Microsoft Deployment Toolkit\Samples” folder.  (Note that both x86 and x64 versions are needed because they will be used to update x86 and x64 boot images.)
4. Download the individual x86 and x64 Windows 8.1 Updates from the download center and place them into the “C:\Program Files\Microsoft Deployment Toolkit\Samples” folder.  (Note that both x86 and x64 versions are needed because they will be used to update x86 and x64 boot images.)  With the downloads from step #3 and these, you should have a total of 12 different MSU files in the folder.
5. Place the updated “UpdateExit.vbs” file in the attached zip file into the same “C:\Program Files\Microsoft Deployment Toolkit\Samples” folder, replacing the version that is already there.  (If you’ve made any other changes to this, you’ll need to merge your changes into the attached version.)  This script will be called during the deployment share update process to inject the Windows 8.1 Update into the boot images, which is what is needed to make Windows PE 5.1 boot images.
6. Update your deployment share by right-clicking on it and choosing the “Update deployment share” option.  Make sure you check the “Completely regenerate the boot images” option, as this is needed the first time to get Windows PE updated.
7. Check the results of the “update” process to make sure all the MSU files were injected successfully by making sure all the steps have good return codes.  Here’s an example:
   
   About to run: DISM.EXE /Image:"C:\Users\mniehaus\AppData\Local\Temp\MDTUpdate.11324\Mount" /Add-Package /PackagePath:"C:\Program Files\Microsoft Deployment Toolkit\Samples\Windows8.1-KB2919442-x86.msu"
   Return code from command = 0
   About to run: DISM.EXE /Image:"C:\Users\mniehaus\AppData\Local\Temp\MDTUpdate.11324\Mount" /Add-Package /PackagePath:"C:\Program Files\Microsoft Deployment Toolkit\Samples\Windows8.1-KB2919355-x86.msu"
   Return code from command = 0
   About to run: DISM.EXE /Image:"C:\Users\mniehaus\AppData\Local\Temp\MDTUpdate.11324\Mount" /Add-Package /PackagePath:"C:\Program Files\Microsoft Deployment Toolkit\Samples\Windows8.1-KB2932046-x86.msu"
   Return code from command = 0
   About to run: DISM.EXE /Image:"C:\Users\mniehaus\AppData\Local\Temp\MDTUpdate.11324\Mount" /Add-Package /PackagePath:"C:\Program Files\Microsoft Deployment Toolkit\Samples\Windows8.1-KB2937592-x86.msu"
   Return code from command = 0
   About to run: DISM.EXE /Image:"C:\Users\mniehaus\AppData\Local\Temp\MDTUpdate.11324\Mount" /Add-Package /PackagePath:"C:\Program Files\Microsoft Deployment Toolkit\Samples\Windows8.1-KB2938439-x86.msu"
   Return code from command = 0
   About to run: DISM.EXE /Image:"C:\Users\mniehaus\AppData\Local\Temp\MDTUpdate.11324\Mount" /Add-Package /PackagePath:"C:\Program Files\Microsoft Deployment Toolkit\Samples\Windows8.1-KB2934018-x86.msu"
   Return code from command = 0
   About to run: DISM.EXE /Image:"C:\Users\mniehaus\AppData\Local\Temp\MDTUpdate.11324\Mount" /Cleanup-Image /StartComponentCleanup /ResetBase
   Return code from command = 0
   
   
8. Place the new “WIMBoot.xml” task sequence template from the attached zip file into the “C:\Program Files\Microsoft Deployment Toolkit\Templates” folder.
9. Place the new “LTIApplyWIMBoot.wsf” script into the deployment share’s “Scripts” folder.
10. Create a new task sequence, selecting the “WIMBoot Task Sequence” template and the operating system image that you imported.
11. Perform a bare metal deployment using the updated boot images (update WDS if using PXE, generate new boot CDs, etc.), selecting your new task sequence.

In this scenario, you’ll notice during the task sequence execution that the operating image is exported to make it ready for WIMBoot.  This export process takes a long time, because it changes the compression method used for the WIM.  It's the easiest option since it requires no additional steps on your part, but it’s not the quickest.  If you want to make the process faster, you can follow these steps:

1. Export the existing WIM image using this DISM command:
   DISM.EXE /Export-Image /WIMBoot /SourceImageFile:<original WIM> /SourceIndex:1 /DestinationImageFile:<new WIM to create>
2. Import the new WIM into your deployment share.
3. Update your existing WIMBoot task sequence to use the new image.
4. Modify the task sequence step “Apply WIM Boot Image“ to add a “/Optimized:TRUE” switch to the LTIApplyWIMBoot step to indicate that no export is required.

Note that this WIM image can still be used for non-WIMBoot deployments – it’s ready for WIMBoot, but not optimized for WIMBoot.  If you want to take it a step further, you can optimize that exported image (following the above three steps first) using these steps:

1. Mount the WIMBoot-ready image using DISM:
   DISM.EXE /Mount-Image /ImageFile:<WIM file> /Index:1 /MountDir:C:\Mount
2. Optimize the image for WIMBoot using DISM:
   DISM.EXE /Image:C:\Mount /Optimize-Image /WIMBoot
3. Commit the changes to the WIM file:
   DISM.EXE /Unmount-Image /MountDir:C:\Mount /Commit
4. Import the modified image into your deployment share.
5. Update your existing WIMBoot task sequence to use the new image.
6. Modify the task sequence step “Apply WIM Boot Image“ to add a “/Optimized:TRUE” switch to the LTIApplyWIMBoot step to indicate that no export is required.

And one more thing:  You need to perform some additional steps if you want Windows RE to work for recovering a WIMBoot system.  This is needed to ensure the refresh/reset my PC options work from PC Settings, that the machine can self-repair if something happens during the boot process, that BitLocker recovery can work properly, etc.  So it’s highly recommend that you do this.  To do this, follow these steps:

1. Mount your Windows image using DISM:
   DISM.EXE /Mount-Image /ImageFile:<WIM file> /Index:1 /MountDir:C:\Mount
2. Move the WinRE.WIM out of the image (since recovery can’t boot a WIM within a WIM):
   move C:\mount\Windows\Windows\System32\Recovery\winre.wim C:\winre.wim
3. Commit the changes to the WIM file:
   DISM.EXE /Unmount-Image /MountDir:C:\Mount /Commit
4. Mount the WinRE.WIM file:
   DISM.EXE /Mount-Image /ImageFile:C:\winre.wim /Index:1 /MountDir:C:\Mount
5. Inject the downloaded Windows 8.1 updates into the WIM image:
   DISM.EXE /Image:C:\Mount /Add-Package /PackagePath:Windows8.1-KB2919442-x86.msu
   DISM.EXE /Image:C:\Mount /Add-Package /PackagePath:Windows8.1-KB2919355-x86.msu
   DISM.EXE /Image:C:\Mount /Add-Package /PackagePath:Windows8.1-KB2932046-x86.msu
   DISM.EXE /Image:C:\Mount /Add-Package /PackagePath:Windows8.1-KB2937592-x86.msu
   DISM.EXE /Image:C:\Mount /Add-Package /PackagePath:Windows8.1-KB2934018-x86.msu
6. Cleanup the image as described in the ADK documentation:
   DISM.EXE /Image:C:\Mount /Cleanup-Image /StartComponentCleanup /ResetBase
7. Commit the changes to the WIM file:
   DISM.EXE /Unmount-Image /MountDir:C:\Mount /Commit
8. Export the contents of the WIM into a new WIM to reduce the size of the image:
   DISM.EXE /Export-Image /SourceImageFile:C:\winre.wim /SourceIndex:1 /DestinationImageFile:C:\winre-new.wim
9. Copy the resulting file into the same folder as the operating system WIM on the deployment share, e.g. “C:\DeploymentShare\Operating Systems\WIMBoot”.  Make sure the file is named “winre.wim” so that the LTIApplyWIMBoot.wsf script can find it; the script will take care of the remaining steps.

And that’s all there is to it. 

Well, almost.  I need to point out a few more things:

• I am providing these scripts and the task sequence template as-is.  It’s not supported by Microsoft, so don’t call support about it.  Feel free to e-mail me at mniehaus@microsoft.com, but I can’t guarantee a quick response – might take weeks or months before I get to the e-mail :-)
• When you use a non-WIMBoot image (one not exported using the steps above), the recompression process that happens when the image is exported causes the new image to be larger than the original one.  The LTIApplyWIMBoot script attempts to guess at how big, assuming it will be about one-third bigger, but that might not be accurate.  If you run into issues where the OS image and winre.wim won’t fit, you can either go through the export steps above (so no guessing needs to be done), or you can explicitly specify how big you want to make the images partition by adding an “ImagesSize” switch to the LTIApplyWIMBoot command line.  See the script comments for more information.
• If you choose to optimize the operating system image using the steps above, you might also want to export the image into a new WIM file to make it as small as possible.  It won’t be a huge difference, but on a 16GB system, every little bit helps.
• Remember, WIMBoot is intended for new hardware that has smaller (16GB or 32GB) SSD or eMMC disks, and requires Windows 8 certified UEFI systems.  I would only recommend using it on systems that originally shipped from the manufacturer configured for WIMBoot.  For example, let’s say you purchased a new 16GB tablet that was configured with WIMBoot and the Windows 8.1 “core” SKU, and you wanted to deploy Windows 8.1 Enterprise to it.  You could use the provided task sequence to completely wipe the device (no data migration) and reload it.
• If you want to try this in a VM, feel free – but remember it needs to be a UEFI virtual machine (e.g. Hyper-V on Windows 8.1 or Windows Server 2012 R2).  But this isn’t intended for virtual machines, VDI, or other scenarios.
• If you’ve set everything up correctly, you should be able to see in the Disk Management tool that the C: drive is using WIMBoot.  And more importantly, the refresh and reset recovery options should work.  Try them out at least once to make sure.
• I included steps in the task sequence template to restore user state (useful for a “replace” scenario), to inject drivers, to inject updates, and to install apps.  But there is nothing to capture state.  That’s because this is a bare metal-only scenario.
• Make sure you have a lot of free disk space, as the Windows PE generation process will likely require at least 3GB of available space to inject the Windows 8.1 Update files (before the cleanup process shrinks it back down again).
• You won’t see any progress reported while the updates are being injected into Windows PE, as the UpdateExit.vbs script doesn’t have the ability to provide any real-time status information back to Workbench.  Just be patient – you can see via Task Manager that the DISM commands are still running.

Please try this out when you have some spare time, and post some comments indicating if it worked or not.  Most of the validation of the steps in this blog was done in hotel rooms, airports, and airplanes…

Summary: Manage DNS server settings with Windows PowerShell in Windows Server 2012 R2.

Honorary Scripting Guy, Sean Kearney, is here. Our final part of the Windows PowerShell Network Week series has arrived. You also might enjoy reading:

• Windows Server 2012 R2 Network Cmdlets: Part 1
• Windows Server 2012 R2 Network Cmdlets: Part 2
• Windows Server 2012 R2 Network Cmdlets: Part 3
• Windows Server 2012 R2 Network Cmdlets: Part 4
• Windows Server 2012 R2 Network Cmdlets: Part 5
• Windows Server 2012 R2 Network Cmdlets: Part 6

Today I’m going to show you a couple of really cool and easy ways to work with your DNS server. These are things I never had working in the field that would have made my life easier.

I remember going to sites and wishing I had an easy way to pull the configuration of a DNS server and store it away for later use. Well, now I can!

Built into Windows Server 2012 R2, is a simple report called Get-DnsServer, which will produce the output of my current configuration. Here’s a quick output from my test server at Energized.local:

Get-DNSServer

There’s a lot more to this report, but I could take this away for later viewing with a simple Export-CLIXML cmdlet:

Get-DNSServer | Export-CLIXML DnsConfig.xml

I found that to be pretty cool! On any workstation that has Windows PowerShell, I can review this report by running this cmdlet against the same file —even without the cmdlets or the DNS Server service:

Import-CLIXML Dnsconfig.xml

Do you need to get a list of DNS zones on your server?

Get-DNSServerZone

How about a list of all DNS records for a particular zone? That’s something I could do before—but never as a straight object. Now I can say show me all records of type “A” for a particular zone like this:

Get-DNSServerZone ‘Contoso.local’ | Get-DNSServerResourceRecord –Rrtype A

You can also do more than reporting on a DNS server’s configuration. You can create information within the DNS server. Here, we create a brand new zone called Contoso.local, which replicates to all forests:

Add-DNSServerPrimaryZone –name ‘Contoso.local’ –replicationscope Forest

We now do some pretty cool naming, like creating records in said zone, directly from the Windows PowerShell console:

Add-DnsServerResourceRecord -ZoneName 'contoso.local' -IPv4Address '192.168.1.35' -Name ‘ContosoWeb1' -A

This line would have created an “A” record called “ContosWeb1” in the Contoso.local domain with an IP address of 192.168.1.35. This means creating DNS records en masse is now far easier.

Or better yet, what if you need to edit a lot of records? We can now change the value of DNS records in Windows PowerShell quite easily. Let’s say the value of the record for our web server needed to change to 10.0.0.35 because we moved the server to our DMZ zone. We can execute this from Windows PowerShell like this:

$OldRecord=Get-DNSServerResourceRecord –name ‘ContosoWeb1’ –Zonename ‘Contoso.local’

$NewRecord=$OldRecord

$NewRecord.RecordData.IPV4Address=”10.0.0.35”

Set-DNSServerResourceRecord –oldinputobject $OldRecord –newinputobject $NewRecord –zonename ‘Contoso.local’

Are you new to managing Windows Server? Or do you have an infrastructure running without the GUI? Never fear. With just a little bit of Windows PowerShell magic, you can manage all of your network needs! And that concludes Windows PowerShell Network Week.

I invite you to follow the Scripting Guys on Twitter and Facebook. If you have any questions, send an email to the Scripting Guys at scripter@microsoft.com, or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then just remember, the Power of Shell is in You.

Sean Kearney, Windows PowerShell MVP, Honorary Scripting Guy 

1.1 Γενικά

Σε αυτό το άρθρο θα κάνουμε έλεγχο της ανθεκτικότητας των Storage Spaces έναντι βλάβης ενός, δύο ή και περισσοτέρων σκληρών δίσκων πάνω στους οποίους έχουν υλοποιηθεί. Θα εξετάσουμε και τα τρία επίπεδα ασφάλειας που προσφέρονται, δηλαδή τα :

• Two Way Mirroring
• Three Way Mirroring και
• Parity

Υπάρχει μια αντιστοιχία των παραπάνω επιπέδων ασφαλείας με τα γνωστά μας RAID levels, αλλά όχι απόλυτη μια που, όπως θα δούμε, μπορούμε να δημιουργήσουμε ένα Two-Way Mirrorμε χρήση τριών (3) δίσκων.

Ένα πλήθος με τις συνηθέστερες ερωτήσεις και τις απαντήσεις τους σχετικά με τα Storage Spaces θα βρείτε στο παρακάτω σύνδεσμο :

Storage Spaces Frequently Asked Questions (FAQ)

Ενώ, πολύ χρήσιμος είναι και ο παρακάτω πίνακας στον οποίο παρουσιάζεται ο συσχετισμός των επιπέδων ασφαλείας των Storage Spaces με τον ελάχιστο απαιτούμενο αριθμό δίσκων.

Για την δημιουργία των Storage Spaces και τους ελέγχους της αντοχής τους, την προσομοίωση δηλαδή της βλάβης, θα χρησιμοποιήσουμε το αγαπημένο μας εργαλείο, το PowerShell, ενώ όλες οι δοκιμές θα διεξαχθούν σε εργαστηριακό περιβάλλονπου περιλαμβάνει έναν Windows Server 2012R2 Hyper-V host και ένα Guest VM με Windows Server 2012R2

1.2 Έλεγχος αντοχής Two Way Mirroring

1.2.1 Δημιουργία δίσκων

Για να δημιουργήσουμε τους σκληρούς δίσκους και τους συνδέουμε στο Guest VM, εκτελώντας τις παρακάτω εντολές στον Hyper-V host

# Create three VHDX

1..3| %{New-VHD -Path "C:\Virtual Machines\W2012R2\Virtual Hard Disks\Disk-$_.vhdx" -LogicalSectorSizeBytes 4096 -PhysicalSectorSizeBytes 4KB -SizeBytes 20GB -Dynamic}

 # Attach VHDX disks to a VM

1..3|%{Add-VMHardDiskDrive -VMName W2012R2 -Path "C:\Virtual Machines\W2012R2\Virtual Hard Disks\Disk-$_.vhdx" -ControllerType SCSI}

1.3 Δημιουργία Storage Pool

Το Storage Space υλοποιείται επάνω σε ένα Storage Pool, που το δημιουργούμε με τις παρακάτω εντολές

# Create Storage Pool

$disks=Get-PhysicalDisk -CanPool $true

$StorSubSys=Get-StorageSubSystem -FriendlyName *Spaces*

New-StoragePool -FriendlyName StorPool-01 -PhysicalDisks $disks -StorageSubSystemFriendlyName $StorSubSys.FriendlyName

1.4 Υλοποίηση Storage Space

Έχοντας λοιπόν δημιουργήσει το απαιτούμενο Storage Pool, υλοποιούμε το Two-Way Μirror Storage Space, με το απαιτούμενο partition και το drive letter της επιλογής μας, με τις παρακάτω εντολές

# Create Storage Space

New-VirtualDisk -FriendlyName StorSpace-01 -ResiliencySettingName Mirror -StoragePoolFriendlyName StorPool-01 -UseMaximumSize

$DiskNo = (Get-VirtualDisk -FriendlyName StorSpace-01 | Get-Disk).Number

Set-Disk -Number $DiskNo -IsReadOnly 0

Set-Disk -Number $DiskNo -IsOffline 0

Initialize-Disk -Number $DiskNo -PartitionStyle MBR

New-Partition -DiskNumber $DiskNo -DriveLetter S -UseMaximumSize

Initialize-Volume -DriveLetter S -FileSystem NTFS -Confirm:$false

Εάν θέλουμε να δούμε την κατάσταση του Storage Space, του partition και των φυσικών δίσκων πάνω στους οποίους έχουν δημιουργηθεί, τότε χρησιμοποιούμε την παρακάτω εντολή

# Display Physical Disks that construct a volume

Get-Volume S | Get-Partition | Get-Disk | Get-VirtualDisk | Get-PhysicalDisk | ft -AutoSize

FriendlyName CanPool OperationalStatus HealthStatus Usage           Size

------------ ------- ----------------- ------------ -----           ----

PhysicalDisk3 False   OK               Healthy     Auto-Select 19.25 GB

PhysicalDisk1 False   OK               Healthy     Auto-Select 19.25 GB

PhysicalDisk2 False   OK               Healthy     Auto-Select 19.25 GB

1.5 Βλάβη ενός δίσκου

Θα προσομοιώσουμε τις εξής βλάβες ενός από τους δίσκους που απαρτίζουν την συστοιχία και θα παρατηρήσουμε τα αποτελέσματα στο Storage Pool και στο Storage Space.

1. Αφαίρεση
2. Επαναφορά
3. Αφαίρεση και αντικατάσταση με νέο
4. Προσθήκη του χαλασμένου δίσκου μετά την αντικατάσταση του

1.5.1 Αφαίρεση

Η αφαίρεση του δίσκου και συγκεκριμένα του τρίτου, γίνεται με την παρακάτω εντολή στον Hyper-V Host

# Remove Disk

Remove-VMHardDiskDrive -VMName W2012R2 -ControllerNumber 0 -ControllerLocation 3 -ControllerType SCSI

Στο guest VM, διαπιστώνουμε την βλάβη του δίσκου, ως εξής

PS C:\Windows\system32> Get-PhysicalDisk | ft -AutoSize

FriendlyName   CanPool OperationalStatus HealthStatus Usage   Size

------------   ------- ----------------- ------------ -----           ----

PhysicalDisk-1 False   Lost Communication Warning    Auto-Select 19.25 GB

PhysicalDisk1 False   OK                 Healthy     Auto-Select 19.25 GB

PhysicalDisk2 False   OK                 Healthy     Auto-Select 19.25 GB

Ενώ έχουμε και εγγραφές στο System Event Log

PS C:\Windows\system32> Get-EventLog -LogName System -Source Disk | fl

Index             : 456

EntryType         : Warning

InstanceId         : 2147745949

Message           : Disk 3 has been surprise removed.

Category           : (0)

CategoryNumber     : 0

ReplacementStrings : {\DR3, 3}

Source             : disk

TimeGenerated     : 12/4/2014 9:22:20 πμ

TimeWritten      : 12/4/2014 9:22:20 πμ

Η κατάσταση του Storage Pool είναι η εξής

PS C:\Windows\system32> Get-StoragePool | ft -AutoSize

 FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly

------------ ----------------- ------------ ------------ ----------

Primordial   OK               Healthy     True         False    

StorPool-01 Degraded         Warning     False       False    

Η κατάσταση του Storage Space είναι η εξής

PS C:\Windows\system32> Get-Volume S | Get-Partition | Get-Disk | Get-VirtualDisk | ft -AutoSize

FriendlyName ResiliencySettingName OperationalStatus HealthStatus IsManualAttach Size

------------ --------------------- ----------------- ------------ -------------- ----

StorSpace-01 Mirror               Incomplete       Warning     False         27 GB

Μετά την αφαίρεση του δίσκου λοιπόν, το Storage Pool είναι Degraded (υποβαθμισμένο)και το Storage Spaceείναι σε κατάσταση προειδοποίησης (Warning).

Η λειτουργική κατάσταση όμως του Storage Space είναι καλή και τα δεδομένα μας διαθέσιμα και ασφαλή.

1.5.2 Επαναφορά

Επαναφέρουμε τον δίσκο που αφαιρέσαμε, με την παρακάτω εντολή στον Hyper-V host

Add-VMHardDiskDrive -VMName W2012R2 -Path 'C:\Virtual Machines\W2012R2\Virtual Hard Disks\Disk-3.vhdx' -ControllerType SCSI -ControllerLocation 3

Στο Guest VM παρατηρούμε ότι ο δίσκος έχει επανέλθει

PS C:\Windows\system32> Get-PhysicalDisk | ft -AutoSize

FriendlyName CanPool OperationalStatus HealthStatus Usage           Size

------------ ------- ----------------- ------------ -----           ----

PhysicalDisk3 False   OK               Healthy     Auto-Select 19.25 GB

PhysicalDisk1 False   OK               Healthy     Auto-Select 19.25 GB

PhysicalDisk2 False   OK               Healthy     Auto-Select 19.25 GB

PhysicalDisk0 False   OK               Healthy     Auto-Select   50 GB

Η κατάσταση του Storage Pool είναι

PS C:\Windows\system32> Get-StoragePool | ft -AutoSize

FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly

------------ ----------------- ------------ ------------ ----------

Primordial   OK               Healthy     True         False    

StorPool-01 OK               Healthy     False       False  

Και του Storage Space

PS C:\Windows\system32> Get-Volume S | Get-Partition | Get-Disk | Get-VirtualDisk | ft -AutoSize

 FriendlyName ResiliencySettingName OperationalStatus HealthStatus IsManualAttach Size

------------ --------------------- ----------------- ------------ -------------- ----

StorSpace-01 Mirror               OK               Healthy     False         27 GB

Επομένως το Storage Subsystem και συγκεκριμένα τα Storage Spaces, κατάλαβαν την επαναφορά του δίσκου, έκαναν όλες τις απαραίτητες ενέργειες αποκατάστασης και η κατάσταση της συστοιχίας είναι και πάλι Healthy.

Όλες αυτές οι ενέργειες έγιναν στο παρασκήνιο και τα δεδομένα μας ήταν συνεχώς διαθέσιμα.

1.5.3 Αφαίρεση και αντικατάσταση με νέο

Στην περίπτωση αυτήν θα αντικαταστήσουμε τον δίσκο που θα αφαιρέσουμε με καινούριο. Όπως προηγουμένως, αφαιρούμε τον δεύτερο δίσκο με την παρακάτω εντολή στο Hyper-V Host

Remove-VMHardDiskDrive -VMName W2012R2 -ControllerNumber 0 -ControllerLocation 2 -ControllerType SCSI

Στο Guest VM διαπιστώνουμε την βλάβη με τους τρόπους που παρουσιάστηκαν στην παράγραφο 1.5.1 Αφαίρεση.

Η κατάσταση λοιπόν της συστοιχίας είναι η εξής

PS C:\Windows\system32> Get-Volume S | Get-Partition | Get-Disk | Get-VirtualDisk | ft -AutoSize

 FriendlyName ResiliencySettingName OperationalStatus HealthStatus IsManualAttach Size

------------ --------------------- ----------------- ------------ -------------- ----

StorSpace-01 Mirror               Incomplete       Warning     False         27 GB

Προσθέτουμε τον νέο δίσκο στην ίδια θέση που είχε και ο χαλασμένος που αφαιρέθηκε, με τις εξής εντολές στον Hyper-V Host

New-vhd -Path 'C:\Virtual Machines\W2012R2\Virtual Hard Disks\Disk-2-Repair.vhdx' -LogicalSectorSizeBytes 4096 -PhysicalSectorSizeBytes 4KB -SizeBytes 20GB -Dynamic

Add-VMHardDiskDrive -VMName W2012R2 -Path 'C:\Virtual Machines\W2012R2\Virtual Hard Disks\Disk-2-Repair.vhdx' -ControllerType SCSI -ControllerLocation 2

Βλέπουμε τον νέο δίσκο στο guest VM

PS C:\Windows\system32> Get-PhysicalDisk | ft -AutoSize

FriendlyName   CanPool OperationalStatus HealthStatus Usage           Size

------------   ------- ----------------- ------------ -----           ----

PhysicalDisk3 False   OK                 Healthy     Auto-Select 19.25 GB

PhysicalDisk1 False   OK                 Healthy     Auto-Select 19.25 GB

PhysicalDisk-1 False   Lost Communication Warning     Auto-Select 19.25 GB

PhysicalDisk0 False   OK                 Healthy     Auto-Select   50 GB

PhysicalDisk2 True   OK                 Healthy     Auto-Select   20 GB

Για να ξεκινήσει η επιδιόρθωση της συστοιχίας θα πρέπει να αφαιρεθεί ο χαλασμένος δίσκος από το Storage Pool και να προστεθεί ο καινούριος. Αυτό γίνεται με τι εξής εντολές στο Guest VM

Get-PhysicalDisk | where OperationalStatus -like Lost* | Set-PhysicalDisk -Usage Retired

PS C:\Windows\system32> Get-PhysicalDisk | ft -AutoSize

FriendlyName   CanPool OperationalStatus HealthStatus Usage           Size

------------   ------- ----------------- ------------ -----           ----

PhysicalDisk3 False   OK                 Healthy     Auto-Select 19.25 GB

PhysicalDisk1 False   OK                 Healthy     Auto-Select 19.25 GB

PhysicalDisk-1 False   Lost Communication Warning     Retired     19.25 GB

PhysicalDisk0 False   OK                 Healthy     Auto-Select   50 GB

PhysicalDisk2 True   OK                Healthy     Auto-Select   20 GB

Προσθέτουμε τον νέο δίσκο στο Storage Pool με την εντολή

Add-PhysicalDisk -StoragePoolFriendlyName StorPool-01 -PhysicalDisks (Get-PhysicalDisk -CanPool $true)

Για να ξεκινήσει η διαδικασία της αποκατάστασης εκτελούμε την εντολή

Repair-VirtualDisk -FriendlyName StorSpace-01

Μετά την ολοκλήρωση της αποκατάστασης ελέγχουμε την λειτουργική κατάσταση του Storage Space (συστοιχία) ως εξής

PS C:\Windows\system32>

Get-Volume S | Get-Partition | Get-Disk | Get-VirtualDisk | ft -AutoSize

 FriendlyName ResiliencySettingName OperationalStatus HealthStatus IsManualAttach Size

------------ --------------------- ----------------- ------------ -------------- ----

StorSpace-01 Mirror                OK               Healthy     False         27 GB

Και του Storage Pool

PS C:\Windows\system32> Get-Volume S | Get-Partition | Get-Disk | Get-VirtualDisk | Get-StoragePool | ft -AutoSize

FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly

------------ ----------------- ------------ ------------ ----------

StorPool-01 Degraded         Warning     False       False    

To storage Pool είναι σε κατάσταση Degraded γιατί περιλαμβάνει τον δίσκο που έχει χαλάσει

PS C:\Windows\system32> Get-StoragePool -FriendlyName StorPool-01 | Get-PhysicalDisk | ft -AutoSize

FriendlyName   CanPool OperationalStatus HealthStatus Usage           Size

------------   ------- ----------------- ------------ -----           ----

PhysicalDisk3 False   OK                 Healthy     Auto-Select 19.25 GB

PhysicalDisk1 False   OK                 Healthy     Auto-Select 19.25 GB

PhysicalDisk-1 False   Lost Communication Warning     Retired     19.25 GB

PhysicalDisk2 False   OK                 Healthy     Auto-Select 19.25 GB

Αφαιρώντας λοιπόν αυτόν τον δίσκο

Remove-PhysicalDisk -StoragePoolFriendlyName StorPool-01 -PhysicalDisks (Get-PhysicalDisk | where OperationalStatus -like Lost*)

Η κατάσταση της συστοιχίας γίνεται Healthy

PS C:\Windows\system32> Get-StoragePool | ft -AutoSize

FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly

------------ ----------------- ------------ ------------ ----------

Primordial   OK               Healthy     True         False    

StorPool-01 OK               Healthy     False       False

Όλες αυτές οι ενέργειες έγιναν στο παρασκήνιο ενώ τα δεδομένα μας ήταν διαρκώς διαθέσιμα.

1.5.4 Προσθήκη του χαλασμένου δίσκου μετά την αντικατάσταση του

Στην παράγραφο αυτή θα εξετάσουμε την συμπεριφορά των Storage Spaces, εάν προστεθεί ο δίσκος που είχε πριν αφαιρεθεί και αντικατασταθεί με νέο.

Προσθέτουμε λοιπόν πάλι τον δίσκο, εκτελώντας στον Hyper-V host

Add-VMHardDiskDrive -VMName W2012R2 -Path 'C:\Virtual Machines\W2012R2\Virtual Hard Disks\Disk-2.vhdx' -ControllerType SCSI

Με την προσθήκη του δίσκου στο VM έχουμε την εξής εικόνα

PS C:\Windows\system32> Get-PhysicalDisk | ft -AutoSize

 FriendlyName CanPool OperationalStatus     HealthStatus Usage           Size

------------ ------- -----------------     ------------ -----           ----

PhysicalDisk3 False   OK                   Healthy     Auto-Select 19.25 GB

PhysicalDisk1 False   OK                   Healthy     Auto-Select 19.25 GB

PhysicalDisk5 False   Unrecognized Metadata Unhealthy   Unknown       20 GB

PhysicalDisk0 False   OK                   Healthy     Auto-Select   50 GB

PhysicalDisk2 False   OK                   Healthy     Auto-Select 19.25 GB

Ο δίσκος αναγνωρίζεται ως Unhealthy και φαίνεται να περιλαμβάνει Unrecognized Metadata, δεδομένα δηλαδή των οποίων την περιγραφή δεν φαίνεται να την γνωρίζει το VM.

Για το storage Pool και την συστοιχία δεν έχει αλλάξει τίποτα και είναι σε κατάσταση Healthy

Get-Volume S | Get-Partition | Get-Disk | Get-VirtualDisk | Get-StoragePool | ft -AutoSize

 FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly

------------ ----------------- ------------ ------------ ----------

StorPool-01 OK               Healthy     False       False    

Get-Volume S | Get-Partition | Get-Disk | Get-VirtualDisk | ft -AutoSize

 FriendlyName ResiliencySettingName OperationalStatus HealthStatus IsManualAttach Size

------------ --------------------- ----------------- ------------ -------------- ----

StorSpace-01 Mirror               OK               Healthy     False         27 GB

Εάν θέλουμε να χρησιμοποιήσουμε αυτόν τον δίσκο, θα πρέπει να γίνει επαναφορά (reset) της κατάστασης του.

Get-PhysicalDisk | where OperationalStatus -like Unrecognized* | Reset-PhysicalDisk

Παρατηρούμε λοιπόν ότι η προσθήκη του παλιού δίσκου που ενώ υπήρχε στο Storage Pool και στο Storage Space αφαιρέθηκε και αντικαταστάθηκε με νέο δεν έχει κάποια επίπτωση στην λειτουργία του Storage Space (συστοιχία).

1.6 Αφαίρεση δύο (2) δίσκων

To Storage Space που εξετάζουμε είναι τύπου Two-Way Mirror. Αυτός ο τύπος συστοιχίας επιτρέπει την ομαλή λειτουργία σε περίπτωση βλάβης ενός (1) από τους δίσκους που την απαρτίζουν. Εάν υποστούν βλάβη δύο από τους δίσκους της τότε αναμένεται η συστοιχία να μην λειτουργεί και τα δεδομένα που είναι αποθηκευμένα επάνω της να μην είναι διαθέσιμα.

Ετσι εάν αφαιρέσουμε δύο δίσκους, μέσω των παρακάτω εντολών στον Hyper-V host

Remove-VMHardDiskDrive -VMName W2012R2 -ControllerNumber 0 -ControllerLocation 1 -ControllerType SCSI

Remove-VMHardDiskDrive -VMName W2012R2 -ControllerNumber 0 -ControllerLocation 2 -ControllerType SCSI

Παρατηρούμε ότι το Storage Pool είναι σε κατάσταση εκτεταμένης βλάβης

PS C:\Windows\system32> Get-StoragePool | ft -AutoSize

FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly

------------ ----------------- ------------ ------------ ----------

Primordial   OK               Healthy     True         False    

StorPool-01 Read-only         Unhealthy   False       False    

Ενώ το Storage Space δεν υπάρχει

PS C:\Windows\system32> Get-Volume S | Get-Partition | Get-Disk | Get-VirtualDisk | ft -AutoSize

Get-Volume : No MSFT_Volume objects found with property 'DriveLetter' equal to 'S'. Verify the

value of the property and retry.

At line:1 char:1

+ Get-Volume S | Get-Partition | Get-Disk | Get-VirtualDisk | ft -AutoSize

+ ~~~~~~~~~~~~

   + CategoryInfo         : ObjectNotFound: (S:Char) [Get-Volume], CimJobException

   + FullyQualifiedErrorId : CmdletizationQuery_NotFound_DriveLetter,Get-Volume

Εάν επανασυνδέσουμε τους δίσκους στο VM τότε το Storage Pool και το Storage Space θα έρθουν και πάλι σε καλή λειτουργική κατάσταση.

Outlook 2013では、電子メール アドレスとパスワードを入力するだけで自動的にアカウントを設定することが可能です。
また、従来のバージョンの Outlook と同様に手動で電子メール アカウント設定を行うこともできます。

----------------------------------
自動で電子メールアカウントを設定する場合
「方法 1. 自動アカウント設定機能を使って電子メール アカウントを設定する」に記載した手順を実行してください。

自動設定に失敗する場合、または自分でアカウント設定を行いたい場合
「方法 2. 手動で電子メールアカウントを設定する」に記載した手順を実行してください。
----------------------------------

方法 1. Outlook 2013 の自動アカウント設定機能を使って電子メールアカウントを設定する
 

1. Outlook を起動します。この時点で [Outlook 2013 へようこそ] 画面が現れるかどうかで、次に行う手順が異なります。

方法 2. Outlook 2013 で、手動で電子メールアカウントを設定する

Outlook 2013 で、手動で電子メールアカウントを設定する場合や自動アカウント設定が失敗した場合は、次の手順で操作します。

注 : 手動でアカウント設定する場合、インターネット サービス プロバイダー (プロバイダー) から提供されている情報を確認します。

　　　設定情報がご不明な場合は、プロバイダー契約時に発行された書類をご確認いただくか、ご利用のプロバイダーに直接お問い合わせください。

・[電子メール アカウントの追加] 画面で [はい] が選択されていることを確認して [次へ] をクリックします。

6. [新しいメッセージの配信先]で、送受信するメッセージの配信先 (保存先) を設定します。
※ 特に指定がなければ、そのまま 7. に進みます。

・[新しい Outlook データファイル]

・[既存の Outlook データファイル]

以上で電子メール アカウントが設定されました。

Sou André Ricardo Novello, tenho 26 anos e moro em Piracicaba-SP. Trabalho em uma pequena empresa de Contabilidade, no qual sou responsável por toda área de TI (Telefonia, Sistema, Infraestrutura, Servers e clients). Sou pós graduado em Redes de Computadores e como preferência de área sou certificado em virtualização, sendo MCTS Server e Desktop Virtualization. Também tenho uma empresa que está começando, que irá oferecer serviços de guarda de notas fiscais eletrônicas (NFE PROTECT).

Minha especialidade onde trabalho é manter o sistema de contabilidade sempre disponível e também em virtualização. Tenho um Hyper-V com algumas máquinas virtuais para a utilização do SPED Fiscal e Contábil, um PFSENSE para filtro de conteúdo e possuo também um Server 2012 R2 WSUS para testes.

Durante o ano de 2013 contribui bastante no fórum technet respondendo as perguntas de Hyper-V e também ganhando conhecimento baseado nos incidentes e problemas que os outros tiveram. Ao solucionar alguns problemas tive o prazer de conhecer algumas pessoas e fazer amigos. Também escrevi artigos para o Technet sobre Hyper-V 2008 e 2012 e R2 baseado nas novas características e funções. Outros artigos também de instalação da família System Center, Certificação e RDS. Neste ano de 2014 pretendo continuar a postar artigos relacionados ao Hyper-V, como o Veeam Backup, System Center integrado com Hyper-V.

Primeiramente tem que gostar de contribuir a experiência que obteve com todo o esforço de livros e laboratórios por horas estudando. Depois decidir qual área seguir e começar a frequentar o fórum Technet, que foi o lugar em que me abriu as portas para começar esse compartilhamento de informação. Depois que decidi responder nos fóruns de Hyper-V, Windows Server e Windows Client, minhas experiências com soluções de problemas se ampliaram e com isso resolvi fazer artigos para o technet, para contribuir ainda mais. Então o importante é persistir no que gosta e para atingir o MVP você irá ganhar visibilidade e não passará despercebido pelos olhos da Microsoft e de outros profissionais que lhe darão feedback sobre o belo trabalho realizado. E o MVP é um caminho para todos, pois para quem prefere palestrar, falar via webcast, escrever artigo, livros entre outros, tudo isso será analisado pelos brilhantes profissionais da Microsoft no Brasil.

A partir do fórum technet, depois de ganhar experiência e também utilizar dos artigos dos outros profissionais resolvi começar a postar também e não somente ficar respondendo ao fórum. Os artigos são todos fantásticos, muita informação valiosa pra quem está precisando entender a tecnologia sobre qualquer plataforma, seja ela virtualização ou programação.

Contribuo sempre na área de virtualização do Fórum Technet e também pelo Linkedin quando há algumas dúvidas de conhecidos que são postadas por lá. Também pelo meu blog http://andrenovello.wordpress.com/. Estou querendo reformular meu blog e fazer um site para os artigos não se perderem em posts antigos.

Quero fazer vídeos para adicionar junto aos conteúdos postados, melhorar sempre a qualidade dos meus artigos, gostaria de começar algumas palestras e se possível webcasts. Pretendo ainda em 2014 tirar meu MCSE em Private Cloud, estou um pouco longe, mas como projeto de carreira quero atingir esses passos.

Extraio toda informação de virtualização e private cloud que envolve o System Center para poder aplicar no dia a dia e para o aprendizado. Infelizmente onde trabalho não necessita de grande infraestrutura para poder aplicar toda tecnologia. Tanto Wiki brasil como dos EUA tem artigos e resoluções de problemas fundamentais.

Sempre acompanhei muito blog de outros profissionais que estão mais aparente, como Marcelo Sincic, Rafael Bernardes, Fabio Hara, Vinícius Apolinário, Leandro Carvalho entre outros que poderia citar, mas o trabalho de todos eles sendo reconhecido pelo pessoal me motiva a ajudar e também a manter o blog e criar uma comunidade de amigos que pode nos ajudar no dia a dia e contar as experiências e problemas que passam.

Idag har alla företag och organisationer en ständigt växande mängd data. Data som rätt använd kan leda till insikter och kunskap som möjliggör framgång för både små och stora verksamheter. Idag kan vi med hjälp av Big Data analyser göra allt från att förutsäga valresultat till att förhindra spridning av epidemier. Med nya SQL Server 2014, Analytics Platform System och Power BI är det möjligt för alla typer av verksamheter att använda all tillgänglig data för ökade insikter. Den 15 april klockan 19:00 visar vi hur.

"Med den här lanseringen tar vi ett några riktigt stora steg framåt i kompletteringen av vår lösning för Business Intelligence. Vi lanserar nästa generation av vår databasplattform och gör Big Data lättillgängligt för alla. Vi visar också upp en fantastisk lösning för visualisering som redan har fått stor uppskattning bland våra kunder" säger Tommy Flink, produktchef för Business Intelligence.

Datum: 15 april, 2014
Starttid: 19:00
Vem: Microsofts CEO Satya Nadella, COO Kevin Turner, och CVP Quentin Clark
Var: San Francisco, USA - se sändningen live här

För mer information, vänligen kontakta

Tommy Flink
Produktchef för Business Intelligence på Microsoft i Sverige
Tel: 073-408 32 17
E-post: tommy.flink@microsoft.com

Sign up to MVA Hero today and get your free hero costume (t-shirt) and earn some great prizes!

I am still surprised at how many IT Professionals and developers haven’t made use of the Microsoft Virtual Academy to learn about Microsoft technologies and stay up do date as new versions are released. Each module has a basic test and decks to accompany the videos focused around a particular subject and they are graded to indicate how advanced they are.

One of the great things about MVA is how wide and deep the content is, but there isn’t really any sort of path through the courses as they might apply to your role e.g. which are the right Microsoft Azure courses to do, how do I get up to speed on Hyper-V with all the improvements in Windows Server 2012R2? 

So the TechNet UK team have a plan called MVA Hero to fix that and have some fun at the same time!  We wondered what sort of super heroes worked in a datacentre, what skills they would need, and mapped this onto the latest MVA courses.

Cloud Ninja is all about Azure and even if you aren’t planning to use Azure just yet it’s actually a great way to spin up VM’s and learn some of the Microsoft core technologies if you haven’t got a free server to use for evaluations.

Captain Code is getting to grips with PowerShell which will should give you time back in your day to do more MVA courses rather than clicking on endless dialog boxes to do repetitive tasks.

Dr Desktop will be all over Configuration Manager and In Tune as it’s no fun to fiddle with profiles applications on all the devices accessing corporate resources one by one.

RackMan understands how to turn Just a Bunch of |VMs (JBOV) into services that can scale, be costed and provisioned using self service just like a public cloud.

Hypervisor needs to efficiently allocate compute network and storage and provide quality of service to all of those to prevent noisy neighbours hogging resources.

Solid Server understand that while we have all seen Windows Server we haven’t seen all of Windows Server , and things like IP Address Management, storage spaces and VDI are all hidden away waiting to be turned on.

Taking the courses these heroes have done is a good starter and will help you get on the road to expertise and ultimately certification. Even if your are familiar with older versions it they’ll show you what’s new and may uncover some useful tips that you didn’t know was already in the product. For example, I did a talk in Leeds last week where no one knew about the Active Directory recycle bin in Windows Server 2008 R2, and at another event no one had seen IP address Management although everyone was running Windows Server 2012!

We are having a bit of fun with the MVA - when you sign up to MVA Hero you will receive a free t-shirt and then once you complete a badge, you will be rewarded with a stress ball hero figurine (collect all six!) to show you have earned the skills of the MVA SuperSix!

So to quote one of my colleagues on why she loves working at Microsoft “it’s all about learning and laughing”

Microsoft Technology User Group (MTUG) og Microsoft inviterer til gratis heldagsseminar ‘Microsoft System Center 2012 R2, Powershell og Windows Sikkerhet i praksis’

Dato: Torsdag 8. mai
Tid: 09:00 -16:00
Sted: Universitetet i Oslo, Simula Auditoriet, Gaustadalléen 23B. http://www.uio.no/om/finnfram/omrader/gaustad/ga06/

Arrangementet er kostnadsfritt.

Noe av tingene dere får høre om: Fredrik Knalstad skal fortelle oss om hvordan effektivisere driften ved bruk av Service Manager og IT Process Automation. Tommy Finsen skal holde Pass the Hash fordraget sitt som han har holdt for Forsvaret, NTNU, Avinor m.fl. Om Windows sikkerhet er noe for deg, så vil du ikke gå glipp av dette foredraget. Thomas Gudmundsen kommer også å viser oss med en demo basert presentasjon hvordan du enkelt kan håndtere Bring Your Own Device (BYOD) for enheter som bruker Windows, Windows RT, Mac, Windows Phone, Apple iOS og Android fra ett konsoll ved hjelp av SCCM og InTune. Full oversikt med påmelding finner dere her.

Agenda:

09:00 – 09:50 The Power of Self Service in System Center

10:00 - 11:30 Pass the Hash

11:30 - 12:00 Lunch

12:00 – 12:50 Håndter ditt datasenter med bruk av Windows PowerShell

13:00 – 13:50 Public Cloud og Private Cloud  - Hvordan Azure knytter de sammen

14:00 – 14:50 Windows Intune med System Center 2012 R2 Configuration Manager

15:00 – 15:50 Automatiser System Center Deployment med PowerShell Deployment Toolkit

Info om sessionene:

09:00 – 09:50 The Power of Self Service in System Center (Fredrik Kristian Knalstad)

Hvordan spare kostnader og effektivtisere Drifts tjenester ved bruk av Service Manager og IT Process Automation. I denne sesjonen vil vi se på hvordan integrasjoner til System Center kan gi din bedrift ROI for dine investeringer i System Center.

10:00 - 11:30 Pass the Hash (Tommy Finsen)

Identitetstyveriet som knekker et hvert Windows-miljø ved angrep på singel-sign-on mekanismene i alle windows-systemer. De beste hjernene hos Microsofts Cyber Security Team, og eksterne sikkerhetskonsulenter, jobbet i et år for å finne mottiltak. Det fant ingen pillekur, kun risikoreduserende arkitektur/tiltak.

-          Introduksjon til trusler, angrepsmetoder, verktøy og hvordan de omgår deteksjon

-          Gjennomgang av et vellykket angrep fra ide til «foten på innsiden»

-          Hva er en hash og hvordan brukes den?

-          Live demo av «pass the hash» angrep

-          Gjennomgang av risikoreduserende tiltak

-          Gjennomgang av Microsofts referansearkitektur for vern mot «pass the hash»

-          Hva er gjort i av endringer  i Windows 8.1/2012R2 som direkte følge av «pass the hash»

11:30 – 12:00 LUNCH

12:00 – 12:50 Håndter ditt datasenter med bruk av Windows PowerShell (Erik Holgernes)

I dette foredraget vil du få innblikk i hvordan man kan utnytte nye funksjoner i Windows PowerShell for å sentralt håndtere et Microsoft datasenter. Store deler av foredraget vil være

demobasert, og vi beveger oss inn på PowerShell-nyheter som; "Desired State Configuration" og "Workflows". Vi skal se hvordan disse teknologiene kan utnyttes for å effektivisere drift, oppsett og automatisering av et datasenter.

13:00 – 13:50 Public Cloud og Private Cloud  - Hvordan Azure knytter de sammen (Børge Hansen)

Cloud OS er Microsoft sin visjonen for hvordan Public Cloud og Private Cloud skal fungere i samspill. Vi tar en gjennomgang av de siste nyhetene i Microsoft Azure som gjør dette mulig.

14:00 – 14:50 Windows Intune med System Center 2012 R2 Configuration Manager (Thomas Gudmundsen)

Demo-basert presentasjon de vi ser på integrasjonsprosessen og hvordan en administrator enkelt håndterer Bring Your Own Device (BYOD). 

Administrer PCer og enheter som bruker Windows, Windows RT, Mac, Windows Phone, Apple iOS og Android fra ett konsoll.

15:00 – 15:50  Automatiser System Center Deployment med PowerShell Deployment Toolkit (Christian  Føsund)

PowerShell Deployment Toolkit er et verktøy som lar deg automatisere utrullingen av alle System Center komponentene ved bruk av PowerShell.

Christian vil forklare hvordan verktøyet fungerer og hvordan det kan bli brukt til å rulle ut hele System Center 2012 R2 i en lab samt som produksjon på under 2 timer!

Vi har begrenset antall plasser på dette arrangementet og anbefaler rask registrering.

Meld deg på HER!

For spørsmål ta kontakt med Irena Okoren på a-irokor@microsoft.com eller 4835-0834.

Kom i gang! Sjekk Microsoft SC webinar serie på youtube http://bit.ly/OOxGif

 
Vel Møtt!

В предыдущих блогах мы рассмотрели основы построения In-Memory баз данных. См. http://blogs.technet.com/b/sqlruteam/archive/2014/03/28/sql2014_5f00_memory_5f00_optimized_5f00_rdbms_5f00_overview_5f00_physical_5f00_structure.aspx, http://blogs.technet.com/b/sqlruteam/archive/2014/04/03/sql2014_5f00_memory_5f00_optimized_5f00_rdbms_5f00_overview_5f00_hash_5f00_indexes.aspx.

Из предыдущего блога стало понятно, что в  In-Memory базах данных используется другой класс индексов. Это hash-индексы. Hash-индексы играют важную роль в работе этого типа баз. В отличии от стандартных баз (On-Disk), где возможно существование таблицы в формате "куча" (heap), при этом страницы, принадлежащие одной таблице, связаны вместе с использованием специальных структур (IAM), таблицы, оптимизированные для выполнения в памяти (Memory optimized table), не могут быть созданы без наличия хотя бы одного hash-индекса.  

Однако у hash-индексов есть серьезный недостаток. Они не могут использоваться для поиска по диапазону значений. Для устранения этого недостатка в таблицах используются Bw-tree индексы.

BW-tree индексы. Это еще зачем?

Как вы знаете в классических (On-Disk) OLTP базах используются B-tree индексы. Их структура представляют собой сбалансированное N-дерево (отсюда "B", что значит balanced). О достоинствах такого подхода написано много и нет смысла это повторять, однако...

Однако такие индексы имеют и серьёзные недостатки, которые стали особенно заметны при росте нагрузки на систему и увеличении количества процессоров.

Основные недостатки B-tree индексов:

• Наложение блокировок (Lock) и защелок (Latch).
• Необходимость балансировки дерева, а отсюда наложение Latch-ей
• Деление страниц связанной с фиксированным размером страниц и опять же, связанное с этим наложение Latch-ей.

Как понятно из вышеприведенных рассуждений - основная проблема, существующей индексной системы это наличие "защелок" (Latches) без которых невозможно обойтись в много задачных и многопроцессорных системах. Для устранения этого в новой системе реализован метод неблокирующих модификаций, основанный на добавлении дельта-записей к существующим записям при выполнении их модификаций. Т.е. система никогда не производит in-place обновления, а все операции обновлений реализуются путем добавления новой дельта-записи. При таком подходе производится только краткосрочная блокировка ячейки памяти, где храниться ссылка на обновленную запись, чтобы перенаправить эту ссылку в новое местоположение.

Давайте посмотрим на структуру Bw-tree дерева.

Внешне оно не отличается от стандартного B-tree дерева, но это только внешне.

Первое отличиесостоит в том, что адреса индексных страниц это не номера страниц, как в стандартной (On-Disk) базе данных, а адрес ячеек памяти, где реально размещена эта страница. Т.о. страница не должна быть размещена в фиксированном месте определяемом ее номером (file:page). При таком подходе отсутствует необходимость перемещения страницы при ее делении и нет фрагментации, поскольку страницы в памяти никак не связаны с дисковыми страницами. Связь между номером страницы и ее адресом производится через Page Mapping Table (Таблица привязки страниц).

Второе отличиесостоит в том, что в данной структуре размеры страниц индексов не фиксированы (elastic pages) и система сама принимает решение о необходимости деления или слияния страниц.  В случае деления страницы происходит ее добавление к существующей цепочке страниц и модификация адресных ссылок. Такая операция может быть выполнена очень быстро и практически без блокировки данных.

Третье отличие - страницы литьевого уровня всегда ссылаются на строки (как в некластерном индексе).

Четвертое отличие - модификация данных. Она всегда выполняется без блокировки модифицируемой строки путем добавления дельта записи к существующей строке.

Давайте рассмотрим принцип модификации данных в дереве Bw-tree индекса.

Предположим мы хотим вставить новую строку в дерево индекса. По своему содержимому эта строка должна быть вставлена в страницу P. Адрес страницы P хранится в Page Mapping Table (PMT). При вставке строки к странице P добавляется новая дельта-строка (Insert record 50) и в Page Mapping Table переписывается ссылка на эту строку, а из нее на страницу. При удалении строки происходит тоже самое. Со временем таких строк станет достаточно много и СУБД примет решение о слиянии строк со страницей.

 Добавление новых строк производится методом Compare and swap (См. http://en.wikipedia.org/wiki/Compare-and-swap). Суть метода состоит в том, что атомарно производится модификация ячейки памяти, где содержится указатель на модифицируемую страницу, и в эту ячейку записывается адрес дельта строки. Поскольку такая операция выполняется очень быстро, то вероятность конфликта очень мала, но если конфликт за ячейку памяти возникает, то он обрабатывается СУБД.

Как указывалось выше новая СУБД использует страницы индексов переменных размеров. Для уменьшения количества переключений между дельта записями СУБД периодически выполняет консолидацию страниц. Суть консолидации состоит в слиянии всех строк, которые были вставлены (модифицированы) и удалении строк, которые были удалены. Данная операция выполняется путем создания новой страницы, копирования в нее всех данных и переключения указателя в PMT на новый адрес.

Такое архитектура индексов (latch-free) предполагает наличие некоего механизма удаления неиспользуемых страниц. Такой механизм создан и называется Garbage Collection. Задача этого механизма - производить сканирование страниц и очистка неиспользуемых участков памяти.    

 Поскольку данный тип индекса преимущественно ориентирован на выборку по диапазону значений, то для выполнения этой операции разработаны алгоритмы обеспечивающие непротиворечивость операций выборки при модификации данных.

Предположим мы выполняем запрос по диапазону значений, по которому построен индекс.

SELECT * FROM t1 WHERE NAME BETWEEN 'Alex' and 'Bob'

• Запоминается момент времени начала транзакции выборки данных.
  
• Выполняется проход по дереву индексов с целью формирования вектора ссылок для выборки данных.
• После сканирования и формирования вектора определяется не произошло ли каких-либо изменений, которые могут изменить вектор.
  
• Если произошли, то выполняется обновление вектора.
  
• Если нет, то производится считывание данных соответствующих критерию выборки и временной метке начала транзакции. (См. )http://blogs.technet.com/b/sqlruteam/archive/2014/03/28/sql2014_5f00_memory_5f00_optimized_5f00_rdbms_5f00_overview_5f00_physical_5f00_structure.aspx.
  

В цикле блогов мы рассмотрели основные принципы построения новой СУБД (In-Memory Database). Далее мы начнем рассмотрение работы с этой частью SQL Server.

Александр Каленик, Senior Premier Field Engineer (PFE), MSFT (Russia) 

こんにちは、Exchange サポート チームの竹本です。

Exchange 2013 も SP1 のリリースが行われ、更にお問い合わせの数も増えてまいりました。ご利用いただきありがとうございます。

今回はその Exchange 2013 を監視するための Exchange 管理パックについてです。

 既に半年以上前になってしまいましたが、Exchange 2013 用の管理パックが昨年の 7 月にリリースされています。

 　Title : Microsoft Exchange Server 2013 Management Pack

　URL : http://www.microsoft.com/en-us/download/details.aspx?id=39039

 Exchange 2013 用の管理パックはこれまでの管理パックと大きく異なり、基本的に 75 個のイベント ベースのモニターしか存在しません。

つまり、これまでのように、管理パックの処理でスクリプトを定期実行してその健全性を確認したり、テスト用メールボックスを使用して Test 系の診断コマンドを実行したり、パフォーマンス カウンタを定期的に取得して一定期間閾値を超えたらアラートを上げたり、、、といった処理は行われず、またモニターのヘルス状況に応じて生成されるアラートが調整されるなどの動作 (相関エンジンの動作) もありません。

 ではどのようにして正常性の監視を行うかというと、これは全て Exchange サーバー自身にゆだねられた形となっています。

 ご存知の方も多いかと思いますが、Exchange 2013 では Managed Availability (管理可用性) と呼ばれる可用性監視機能を Exchange サーバー自身が保持しており、これにより各プロトコル (ActiveSync/AutoDisocver/ECP/IMAP/EWS/OWA/POP/PowerShell/SMTP など) や各コンポーネント (Transport/Store/UM など) の正常監視、異常検知時の自動修復などが行われるようになっています。

そのため、サーバーの監視自体はこの Managed Availability の機能を利用しており、Exchange 2013 管理パックでは対象サーバーのイベント ログのみを監視し、こちらの内容に応じてヘルス状態の異常を検知すること、そしてその後アラートにつなげる事が、メインの役割となっています。

 具体的なイベントの監視イメージについては、以下のようになっております。

このイベントは、対象のサーバー上でデータベース (MDB112) がオフラインであるために発生したものです。

この状況を検知し、SCOM (System Center Operations Manager) 側で表示可能なヘルス エクスプローラーでは以下のように、Store コンポーネントにおいて障害が発生した事を確認できます。 

この管理パックの内容については、以下 System Center チームのブログ (英語) でもご紹介させていただいておりますので、併せてご参照ください。 

　Title : MP Blog: Exchange 2013 Management Pack released

　URL : http://blogs.technet.com/b/momteam/archive/2013/05/14/exchange-2013-management-pack-released.aspx

 また、以下 TechNet サイトも英語となりますが、管理パック ガイドとしてご案内させていただいており、この管理パックがどのように動作するのか、またそこで監視対象となっている Exchange サーバーの Health Sets についても紹介がありますので、少しでもご参考になればと思います。

　Title : Exchange Server 2013 Management Pack Guide

　URL : http://technet.microsoft.com/en-us/library/ee758046(v=exchg.150).aspx

 なお監視対象のサーバーで Microsoft Exchange Health Manager サービスが停止しているような場合は、これらイベントを拾う事ができず、SCOM で監視することもできません。

このサービスは既定で "自動" 起動するようになっていますが、先日ブログでの紹介の通り起動しないケースも確認されておりますため、もし "SCOM で監視できない!" という場合には、一度ご確認ください。

今後も当ブログおよびサポート チームをよろしくお願いいたします。