Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

Resources for IT Professionals

older | 1 | .... | 876 | 877 | (Page 878) | 879 | 880 | .... | 889 | newer

    0 0

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

    First up, the weekly leader board snapshot...

     

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

     

    Ninja Award Most Revisions Award  
    Who has made the most individual revisions
     

     

    #1 [Kamlesh Kumar] with 236 revisions.

      

    #2 Edward van Biljon with 50 revisions.

      

    #3 Ken Cenerelli with 47 revisions.

      

    Just behind the winners but also worth a mention are:

     

    #4 Richard Mueller with 33 revisions.

      

    #5 Ana Gauna with 20 revisions.

      

    #6 Patrik L with 17 revisions.

      

    #7 Waqas Sarwar(MCSE 2013) with 17 revisions.

      

    #8 Ken Brumfield with 14 revisions.

      

    #9 SYEDSHANU with 14 revisions.

      

    #10 Stoyan Chalakov with 12 revisions.

      

     

    Ninja Award Most Articles Updated Award  
    Who has updated the most articles
     

     

    #1 [Kamlesh Kumar] with 181 articles.

      

    #2 Edward van Biljon with 49 articles.

      

    #3 Ken Cenerelli with 39 articles.

      

    Just behind the winners but also worth a mention are:

     

    #4 Richard Mueller with 26 articles.

      

    #5 Patrik L with 10 articles.

      

    #6 Waqas Sarwar(MCSE 2013) with 6 articles.

      

    #7 Nonki Takahashi with 5 articles.

      

    #8 SYEDSHANU with 5 articles.

      

    #9 Ryen Kia Zhi Tang with 4 articles.

      

    #10 Abdul Rasheed Feroz Khan with 3 articles.

      

     

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

     

    The article to have the most change this week was MIM with SharePoint Server 2016 User profile: Add more Active Directory Domain for Synchronization., by Waqas Sarwar(MCSE 2013)

    This week's revisers were Edward van Biljon& Waqas Sarwar(MCSE 2013)

    New and shiny! Thanks Waqas, very useful!

     

     

    Ninja Award Longest Article Award  
    Biggest article updated this week
     

     

    This week's largest document to get some attention is Small Basic Blog: Authoring Schedule, by Ed Price - MSFT

    This week's reviser was Nonki Takahashi

    Always worth a mention, is this separate blog for Small Basic, an entry language for any budding programmer.

     

    As Small Basic Sched has won several times before, this week's SEDCOND largest document to get some attention is EASY KIDS LEARN using MVC and AngularJS, by SYEDSHANU

    This week's reviser was Richard Mueller

    Coincidentally another great resource for beginner coders. Go code!

     

     

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

     

    This week's most fiddled with article is Computação e Segurança do Trabalho, by Ana Gauna. It was revised 19 times last week.

    This week's reviser was Ana Gauna

    Busy bee Ana has been buffing this one to perfection, thanks Ana!

     

     

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

     

    The article to be updated by the most people this week is TechNet Guru Contributions - April 2016, by XAML guy

    Yey for the community, as more heroes step up and show us their talent! Love abound! Kudos to all.

    This week's revisers were SYEDSHANU, Janshair Khan, Stoyan Chalakov, Eldert Grootenboer& Nonki Takahashi

     

    As guru often wins, the article to be updated by the SECOND most people this week is Setup Raspberry Pi 2/3 with Windows 10 IoT Core OS for first usage:, by Abdul Rasheed Feroz Khan

    A great intro article to help anyone get started. Thanks Abdul keep 'em coming.

    This week's revisers were Abdul Rasheed Feroz Khan& mumtaj.j

     

     

    Ninja Award 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

     

    Ninja Award Winner Summary  
    Let's celebrate our winners!
     

     

    Below are a few statistics on this week's award winners.

    Most Revisions Award Winner
    The reviser is the winner of this category.

    [Kamlesh Kumar]

    [Kamlesh Kumar] has won 3 previous Top Contributor Awards:

    [Kamlesh Kumar] has not yet had any interviews, featured articles or TechNet Guru medals (see below)

    [Kamlesh Kumar]'s profile page



    Most Articles Award Winner
    The reviser is the winner of this category.

    [Kamlesh Kumar]

    [Kamlesh Kumar] is mentioned above.



    Most Updated Article Award Winner
    The author is the winner, as it is their article that has had the changes.

    Waqas Sarwar(MCSE 2013)

    This is the first Top Contributors award for Waqas Sarwar(MCSE 2013) on TechNet Wiki! Congratulations Waqas Sarwar(MCSE 2013)!

    Waqas Sarwar(MCSE 2013) has not yet had any interviews, featured articles or TechNet Guru medals (see below)

    Waqas Sarwar(MCSE 2013)'s profile page



    Longest Article Award Winner
    The author is the winner, as it is their article that is so long!

    Ed Price - MSFT

    Ed Price - MSFT has been interviewed on TechNet Wiki!

    Ed Price - MSFT has featured articles on TechNet Wiki!

    Ed Price - MSFT has won 138 previous Top Contributor Awards. Most recent five shown below:

    Ed Price - MSFT has TechNet Guru medals, for the following articles:

    Ed Price - MSFT's profile page

    SYEDSHANU

    SYEDSHANU has been interviewed on TechNet Wiki!

    SYEDSHANU has won 7 previous Top Contributor Awards. Most recent five shown below:

    SYEDSHANU has TechNet Guru medals, for the following articles:

    SYEDSHANU has not yet had any featured articles (see below)

    SYEDSHANU's profile page



    Most Revised Article Winner
    The author is the winner, as it is their article that has ben changed the most

    Ana Gauna

    Ana Gauna has won 2 previous Top Contributor Awards:

    Ana Gauna has not yet had any interviews, featured articles or TechNet Guru medals (see below)

    Ana Gauna's profile page



    Most Popular Article Winner
    The author is the winner, as it is their article that has had the most attention.

    XAML guy

    XAML guy has been interviewed on TechNet Wiki!

    XAML guy has featured articles on TechNet Wiki!

    XAML guy has won 106 previous Top Contributor Awards. Most recent five shown below:

    XAML guy has TechNet Guru medals, for the following articles:

    XAML guy's profile page

    Abdul Rasheed Feroz Khan

    This is the first Top Contributors award for Abdul Rasheed Feroz Khan on TechNet Wiki! Congratulations Abdul Rasheed Feroz Khan!

    Abdul Rasheed Feroz Khan has not yet had any interviews, featured articles or TechNet Guru medals (see below)

    Abdul Rasheed Feroz Khan's profile page



    Ninja Edit Award Winner
    The author is the reviser, for it is their hand that is quickest!

    SYEDSHANU

    SYEDSHANU is mentioned above.



    Another strong week of great work.

     Thanks to everyone for so much great content to read!

     

    Best regards,
    Pete Laker (XAML guy)

     


    0 0

     
    You've probably told more than once that FIM/MIM Service is a WCF Service which exposures several endpoints . Then how can we connect to the WCF service programmatically? In this blog, i will take the Resource Endpoint as a starting point and demo how to invoke Get method.

    Firstly, we create a Visual C# console Application and add a service reference to the create a proxy for the running FIMService. After clicking "OK", there are five default endpoints added to the configuration file App.config.

    Note: you shall modify the URI according to your fim service host name.

     

     

    Next, we need compose a request message by specifying the parameter. As described in the Developer reference page , a Get Request is to retrieve the object by supplying the objectID . Below is the copy of the code snippet.

    using System;
    using System.Collections.Generic;
    using System.Linq;
    using System.Text;
    using System.Threading.Tasks;
    using System.ServiceModel;
    using System.ServiceModel.Channels;
    using GetResourceDemo.FIMServiceReference;
    using Microsoft.ResourceManagement;
    using Microsoft.ResourceManagement.WebServices;
    using System.Xml;

    namespace GetResourceDemo
    {
       
    class Program
       
    {
           
    static void Main(string[] args)
           
    {

              
    //GetAction
                const string GetRCAction ="http://schemas.xmlsoap.org/ws/2004/09/transfer/Get";
               
    const string RMNameSpace ="http://schemas.microsoft.com/2006/11/ResourceManagement";
              
    //create a WCF resourceClient by referring the config file
               ResourceClient rc = new ResourceClient("ServiceMultipleTokenBinding_Resource"); 

              
    //compose the request message
               Message request;
              
    request = Message.CreateMessage(MessageVersion.Default,GetRCAction );
               
    // the built-in FIM administrator's account, shared across all the systems
               UniqueIdentifier id = new UniqueIdentifier("7fb2b853-24f0-4498-9534-4e10589723c4");
              
    request.Headers.Add(MessageHeader.CreateHeader("ResourceReferenceProperty",RMNameSpace, id.ToString(), false)); 

              
    //invoke the get method
               using (Message responseMessage = rc.Get(request))
              
    {
                  
    //Parse the reponse messgae
                   XmlDictionaryReader fullObject = responseMessage.GetReaderAtBodyContents();
                  
    XmlDocument Xdoc = new XmlDocument();
                  
    Xdoc.Load(fullObject);

                  
    XmlNamespaceManager xmlNamespace = new XmlNamespaceManager(Xdoc.NameTable);
                  
    xmlNamespace.AddNamespace("rm", RMNameSpace);
                  
    XmlNodeList nodes = Xdoc.SelectSingleNode("//rm:Person", xmlNamespace).ChildNodes;
                  
    foreach (XmlNode node in nodes)
                  
    {
                      
    Console.WriteLine("{0} : {1}", node.Name.ToString().Replace("rm:",""), node.InnerText.ToString());
                  
    }
              
    }

              
    Console.ReadKey();
           
    }
       
    }
    }

    Finally, build the project and run it, you’ll have all the information for the default FIM administrator. :)

    Further if you don't want to build the FIM client library from scratch, I would recommend the lithnet FIM client which simplifies the interactive with FIM Service.

    Capture


    0 0

    微軟聚焦台灣打造亞洲規模最大開放技術盛會

    亞太開發人員技術年會 DevDays Asia 419日首度登台

      繼去年10月微軟為結合全球與在地生態系統的重要夥伴以及加速開發多項產業物聯網解決方案,與經濟部簽署在台灣成立「物聯網產業發展中心」備忘錄後,微軟秉持著協助台灣產業夥伴取得與微軟開發工具與系統相關的最新技術,以及致力促進跨平台互通、開放規格與開放計畫的精神,由經濟工業局指導、經濟部數位內容產業推動辦公室與微軟首度推出亞太地區規模的「亞太開發人員技術年會」(DevDays Asia 2016@Taipei)

      此年會將於 4月19日 (二) 到 4月21日 (四) 在 TAF 空總創新基地舉行,高達 16 位來自微軟總部的技術首席與專家團隊將與本地的產業夥伴和開發人員,一起展開為期三天的精彩互動與交流,共同激盪出翻轉世界的驚人技術能量,並同時為社會公益主題注入創新火花。

     

    首屆「亞太開發人員技術年會」盛大登台  聚焦生產力及資料平台雙主軸

      微軟以推動擁抱開放與協助使用者成就更多的信念,陸續推出 Azure on Linux、SQL Server on Linux,更將在今年為期三天的「亞太開發人員技術年會」帶來微軟最新技術,主要分成生產力及資料平台兩大主軸,其中生產力強調的是協同作業;資料平台則聚焦在大數據及機器學習的應用,同時將 IoT 解決方案分為裝置開發、連結雲端、資料分析及加值服務來探討,而本次的技術年會將著重在資料分析、BI以及機器學習。會中並將延續去年微軟與經濟部簽署「物聯網產業發展中心」備忘錄,揭示截至目前為止的物聯網發展成果。此次開放技術年會更邀請到微軟總部雲端應用與資料平台與協同生產力專家來台,傳授第一手大數據應用、機器學習與資料分析、資料管理、資料視覺化、應用實戰或是 Office Add-Ins 開發介紹、Office 365 APIs 實戰、dev.office.com 資源介紹與開發平台等開發、Office Web Apps 整合應用、Office Add-in 與 Office 365 App 開發,協助開發者透過講解與實作,將創新想法透過最先進雲端開發工具與經驗交流具象,也將開放思維擴及更多的使用者。

     

    實踐公益好輕鬆 邀集開發者一起「好客松」

      此外,「亞太開發人員技術年會」令人矚目的焦點之一,是舉辦為期一天半的好客松 (Hackathon + A for Analytical + O for Open, HAOkathon) 活動,讓參賽者與微軟總部專家一起利用最新的科技為社會公益貢獻心力。在促進社會公益的年會主軸下,參賽者能夠以提高生產力、環境保護以及海洋生態系統保育、社會公益、政府公開資料或是改善大學教育為主題,透過科技的輔助,實踐以開放、分析技術成就社會公益的良善目標。

      「亞太開發人員技術年會」(DevDays Asia 2016 @Taipei) 將於 4月19日(二)~4月21日(四) 展開,不容錯過的亞洲規模最大開放技術盛會,詳見議程與線上報名請至以下網址:http://bit.ly/1oPK2bO


    0 0

    46.     Jak změnit motiv systému Windows 10?

    Motivy systému Windows se objevily poprvé ve Windows 98. Jedná se o soubor, který obsahuje několik typů pozadí, barevné nastavení pracovního prostředí, někdy i zvuky, kurzory myši apod. Změnou motivu si tak můžete během několika vteřin zcela změnit pracovní prostředí dle vašeho přání. Pro změnu motivu klikněte na pracovní ploše pravým tlačítkem myši a z nabídky vyberte příkaz Přizpůsobit a v levé části příkaz Motivy. V zobrazeném okně máte kromě výchozího motivu nazvaného Windows k dispozici i další motivy. Změnu a aktivaci nového motivu provedete tak, že jednoduše kliknete na motiv, který chcete použít.
     

    47.     Jak si stáhnout nové motivy pro Windows 10?

    Ve standardní instalaci systému Windows 10 je kromě základního motivu k dispozici i několik dalších. Největším zdrojem motivů je ale samozřejmě Internet, kde naleznete desítky a stovky motivů rozdělených do různých kategorií.
    Pro stažení nového motivu je nutné kliknout pravým tlačítkem myši na pracovní ploše počítače a z nabídky vybrat příkaz Přizpůsobit a Motivy. Windows zobrazí okno pro změnu vizuálních prvků a zobrazí dostupné motivy. Pouhým kliknutím na jeden z nabízených si můžete změnit grafické prostředí systému. Nicméně důležitý v tomto okně je odkaz Získat další motivy online. Po kliknutí na tento odkaz se otevře internetová stránka společnosti Microsoft, na které se nachází desítky motivů, které si můžete stáhnout a okamžitě začít používat.
     

    48.     Jak odinstalovat motiv systému?

    Pokud si do systému stáhnete nové motivy, je možné je v případě potřeby i odinstalovat. Například pokud se vám již nelíbí nebo je nepotřebujete a nechcete, aby vám zabíraly místo na disku. Stačí, když na nainstalovaný motiv kliknete pravým tlačítkem a vyberete příkaz Odstranit motiv. Odstranit motiv lze pouze u doinstalovaných motivů a ten, který chcete odstranit, nesmí být aktivní.

    49.     Jak nastavit pozadí pracovní plochy?

    Na pozadí pracovní plochy je možné mít libovolný obrázek. Změna obrázku na pozadí pracovní plochy je jednoduchá a lze ji provést těmito dvěma způsoby:
    1. Klikněte v Průzkumníkovi na požadovaný obrázek pravým tlačítkem myši a v zobrazené nabídce klikněte na položku Nastavit jako pozadí plochy.
    2. Klikněte na pracovní ploše pravým tlačítkem myši a v zobrazené nabídce klikněte na položku Přizpůsobit.  Zde si můžete zvolit jeden z předpřipravených obrázků nebo přes tlačítko Procházet zvolit svůj vlastní.

    50.     Jak si rychle zobrazit kalendář?

    V případě, že rychle potřebujete vědět, jaký den v týdnu byl nebo bude určité datum nebo prostě jen se chcete podívat na elektronický kalendář, stačí, když na hlavním panelu kliknete na zobrazené hodiny. Windows zobrazí kalendář nastavený na aktuální datum, nicméně je možné se kliknutím na název měsíce přepnout o úroveň výše. Dalším kliknutím se dostanete na výběr roku a dalším na výběr
    desetiletí. Přehledný kalendář je vám tedy vždy velice rychle k dispozici.

    0 0

    image
    Apr.
    11
    image
    image

    Script Download:  
    The script is available for download from https://gallery.technet.microsoft.com/scriptcenter/How-to-display-the-active-a0ea69db.

    You can also use  Microsoft Script Browser for Windows PowerShell ISE to download the sample with one button click from within your scripting environment. 

    The sample code displays the informations like Process-Id, Application Pool Name and the Request StartTime of the IIS Worker Process (w3wp.exe) in IIS 7.X and higher through Powershell.

    You can find more All-In-One Script Framework script samples at http://aka.ms/onescriptingallery


    0 0

    Das intelligente, vernetzte Heim wird für immer mehr Menschen zur alltäglichen Realität. Was früher nur in Form teurer, von Elektrikern verbauter Komplettsysteme verfügbar war, ist zur von jedermann nachrüstbaren Massenware aus dem Elektrofachmarkt geworden. Mit cleveren, kleinen Geräten lassen sich heute Heizung und Licht automatisch oder aus der Ferne steuern, Markisen und Jalousien je nach Lichteinfall und Wetterbedingungen aus- und einfahren oder Türschließanlagen per Smartphone betätigen.

    Je weiter die Vernetzung jedoch voranschreitet, desto größer werden auch die Sicherheitsprobleme. Denn je mehr Smart-Home-Geräte in den Wohnungen Einzug halten, desto interessantere Ziele geben sie auch für Kriminelle ab. Hinzu kommt, dass für viele Hersteller etwa von App-gesteuerten Jalousien oder Heizungssystemen das Thema Datenschutz und Datensicherheit noch Neuland ist und sie bislang nur wenig Know-how dazu aufbauen konnten. Bei manchen Systemen fehlt beispielsweise eine standardmäßige Absicherung mit Benutzernamen und Passwort oder auch eine Möglichkeit, um erkannte Sicherheitslücken per automatischem Update zu stopfen. Zudem existieren momentan keine verbindlichen Standards, die zumindest einen Minimalschutz fest vorgeben würden.

    Umso interessanter sind daher die Empfehlungen, die das Land Rheinland-Pfalz in einem Verbraucherdialog zusammen mit Experten auf dem Gebiet des Verbraucher- und Datenschutzes sowie mit Vertretern der Wirtschaft und Wissenschaft erarbeitet hat. Zusammen präsentierten sie vor einigen Wochen ein Ergebnispapier mit Empfehlungen zum Verbraucher- und Datenschutz bei Smart-Home-Angeboten, das sich gleichermaßen an Verbraucher und Anbieter richtet.

    Die Empfehlungen decken den gesamten Einsatz von Smart-Home-Technik ab, beginnend mit der Installation und Inbetriebnahme über die Bedienung sowie den Personenbezug und die Zweckbindung der mit Smart-Home-Lösungen erfassten Daten bis hin zur Datensparsamkeit und -sicherheit. Unter anderem wird gefordert, dass die Nutzer die Möglichkeit haben müssen, Datenflüsse aus ihrem häuslichen Bereich zu unterbinden, dass personenbezogene Daten gelöscht werden können und personenbezogene Geräte-, Verbrauchs- und Nutzungsdaten nur in verschlüsselter Form gespeichert und über verschlüsselte Verbindungen übertragen werden sollen. Ein wichtiger Punkt ist auch, dass Sicherheitsaktualisierungen der Software-Komponenten möglich sein müssen.

    Leider handelt es sich bei diesem Ergebnispapier lediglich um eine Empfehlung ohne verbindliche Wirkung. Dennoch ist die Initiative, die dahintersteht, zu loben, und es bleibt zu hoffen, dass sie dazu beiträgt, die Diskussion über die Sicherheitsproblematik von Smart-Home-Technik weiter ins Bewusstsein der Öffentlichkeit zu rücken – und natürlich Anbieter zu motivieren, von Beginn an auf die Widerstandsfähigkeit ihrer Produkte zu achten.

    Bis dahin gelten zwei der sonst üblichen Tipps uneingeschränkt auch fürs Smart Home:

    • Sichere Passwörter sind unabdingbar: Viele vernetzte Geräte fürs Heim lassen sich über einen Webdienst oder eine App auch von außen steuern. Alles, was einen Angreifer demnach von der Übernahme der Technik im Haushalt abhält, ist ein sicheres Passwort. Von daher gilt auch hier: Passwort-Manager bereiten nicht nur öfter verwendeten Passwörtern (Passwort-Recycling) ein Ende. Sie erzeugen auch lange, zufällig zusammengewürfelte Zeichenketten, die im Falle eines Falles schwer zu erraten sind für einen Angreifer.
    • Software-Updates sind ein Muss: Firmware spielt im vernetzten Zuhause eine entscheidende Rolle - wie auch sonst im digitalen Leben. Entsprechend regelmäßig muss daher geprüft werden, ob es für die diversen Gerätschaften Firmware-Upgrades gibt. Diese bringen in aller Regel wichtige Sicherheitsupdates mit und nicht nur ein paar neue Funktionen.

    Gastbeitrag von Michael Kranawetter, National Security Officer (NSO) bei Microsoft in Deutschland. In seinem eigenen Blog veröffentlicht Michael alles Wissenswerte rund um Schwachstellen in Microsoft-Produkten und die veröffentlichten Softwareupdates.


    0 0

    Beschreibung

    Monitoring und Automatisierung sind Schlüsselelemente für kosteneffizienten Rechenzentrumbetriebs und eine schnellere Erbringung von Dienstleistungen für Ihr Business. Optimieren Sie Ihre Rechenzentrums-Infrastruktur durch Unterstützung der Innovationen und Erfahrungen für Unternehmen, die die Microsoft Cloud Plattform bietet.
    Mit den Funktionen des Microsoft Azure Stack und Windows Server 2016 können Sie Ihre On-Premise-Infrastruktur „Cloud-Ready“ machen, um schneller auf wechselnde Geschäftsanforderungen reagieren zu können.

    Nutzen Sie daher die Chance, sich mit unseren Experten und anderen Teilnehmern über das Thema „Transform the Datacenter“ auf unserem Services Forum auszutauschen.
     
    Agenda


    • 12.00-13.00 Begrüßung bei einem gemeinsamen Mittagsbuffet
    • 13.00-14.30 Microsoft Azure Stack & Windows Server 2016

    Hybride Infrastrukturen einfach und sicher aufgebaut und dabei echte Azure Technologien ins eigene RZ gebracht

    Wir zeigen Ihnen, wie Windows Server 2016 Ihnen helfen kann, Kosten für die eigene Infrastruktur zu reduzieren und gleichzeitig von den Innovationen der Azure Rechenzentren zu partizipieren. Besonders deutlich wird dies mit Azure Stack, welcher Ihnen die „Azure Cloud in your Datacenter“ bereitstellen kann. Beide Themen werden aufzeigen, wie sich die Technologien im Rechenzentrum in naher Zukunft weiter entwickeln werden.

    Referent: Stefan Böhler

    • 14.30-15.00 Pause 
    • 15.00-16.30 Monitoring und Automatisierung von public und hybrid Clouds

    Monitoring und Automatisierung von (hybriden) Cloudszenarien bedeutet neue Herausforderungen und Möglichkeiten für die IT. Die Überwachung von einzelnen IT-Komponenten verliert an Bedeutung. Im Gegenzug gewinnt das Monitoring und Management von komplexen (hybriden) Services massiv an Bedeutung. Wir zeigen Ihnen anhand diverser Demos, wie Sie mit Microsoft Technologien Ihre hybriden Cloudszenarien effektiv automatisieren und überwachen können.

    Referent: Dirk Brinkmann

    • 16.30-17.00 Verabschiedung 

    Datum, Ort, Zeit

    30.05.2016, Hamburg, Microsoft
    31.05.2016, Berlin, Microsoft
    13.06.2016, Stuttgart, Microsoft
    20.06.2016, München, Microsoft
    14.07.2016, Köln, Microsoft

    Die Veranstaltung beginnt um 12:00 Uhr und endet gegen 17:00 Uhr.

    Zielgruppe
    CIOs, Teamleiter, Architekten, Projektleiter, Rechenzentrumsleiter

    Level 200
    (Level Skala: 100= Strategisch/ 200= technischer Überblick/ 300=tiefe Fachkenntnisse/  400= technisches Expertenwissen)

    Anmeldung
    Zur Anmeldung wenden Sie sich bitte direkt an Ihren Microsoft Technical Account Manager oder Engagement Manager. Gerne können Sie Ihre Anmeldung auch an peger@microsoft.com senden.


    0 0

    Today’s Tip…

    I ran across this frequently asked questions blog post: http://blogs.technet.com/b/ad/archive/2015/12/11/azuread-mailbag-self-service-password-reset.aspx and I wanted to point out this great question…

    Question: I love the SSPR functionality but my users authenticate with AD FS. Is there a way I can leverage SSPR with ADFS?

    Answer: Absolutely! It only takes three steps using AD FS 2012 R2 web theme customization to add a nice "Can't access your account?" link in the sign-in page like below:

    clip_image001

    Step 1: Create and export the AD FS Web Theme

    Use Windows PowerShell to create a new AD FS web theme from the current one and to export its different resources to your local disk. We will use this new theme to add the link directing users to the password reset page. Just type in the highlighted commands: "New-ADFSWebTheme -Name ADFSAndSSPRFun -SourceName default". "Export-ADFSWebTheme -Name ADFSAndSSPRFun -DirectoryPath C:\customization"

    image

    After this step, all the images, CSS, scripts, and other resources will be available in the local directory you specified (in this example c:\Customization). The folder structure should look like this:

    Step 2: Tweak onload.js to add the link

    Edit the onload.js file, (located under the "script" folder in the root directory you exported to in step 1) and add this little script snippet at the end. This will add the link at the end of the page:

    image

    Step 3: Upload the new content and switch to the new theme

    Finally, use Windows PowerShell to upload our modified onload.js file from step 2, in the theme we created in step 1.

    Once the theme is updated, we'll switch AD FS to use the new theme.

    Set-AdfsWebTheme -TargetName ADFSAndSSPRFun -AdditionalFileResource @{Uri='/adfs/portal/script/onload.js';path="c:\customization\script\onload.js"}

    Set-AdfsWebConfig -ActiveThemeName ADFSAndSSPRFun

    image

    And that's it. Now your users easily access the Self Service Password Reset capabilities.

    For other great frequently asked questions about our Azure AD Self-Service Password reset capabilities, check out the following Microsoft article…

    http://blogs.technet.com/b/ad/archive/2015/12/11/azuread-mailbag-self-service-password-reset.aspx


    0 0

    Today marks the start of the one-year countdown before Exchange Server 2007 reaches the end of extended support. If Exchange Server 2007 is still part of your messaging infrastructure, it’s not too early to start planning an update.

    It’s hard to believe that it’s been 9+ years since we released CCR, LCR and SCR. These technologies of course laid the ground work for the Database Availability groups we’ve relied upon since Exchange Server 2010. Exchange Server 2007 also marked the start of the transition to building Exchange Server on .Net Frameworks as well. We have continued that investment and the .Net Frameworks is now the foundation of all critical Exchange processes in Exchange Server 2013, 2016 and Office 365. PowerShell, also new to Exchange Server 2007, is even more prevalent in current versions of Exchange and is the de facto management tool for modern Exchange Servers.

    As revolutionary as Exchange Server 2007 was at the time, our latest versions of Exchange Server and Office 365 have even more to offer. Customers running Exchange Server 2007 have the option to upgrade via mailbox move to Exchange Server 2010, 2013 or migrate directly to Office 365. Customers wanting to migrate to our latest version of Exchange Server, Exchange Server 2016, will need to first decrement Exchange Server 2007. Customers wanting to maximize their on-premises server investment should strongly consider migrating to Exchange Server 2016 as Exchange Server 2013 is already three years into its own 10-year lifecycle.

    Below are links which you may find helpful to start planning your migration off of Exchange Server 2007 and be on your way to experiencing the latest capabilities of Exchange Server.

    The Exchange Team


    0 0

    皆さまこんにちは。

    Windows Client 担当の野明です。Windows 10 に関してさまざまな情報が公開されてきたので、今回は少しまとめてみたいと思います。

    まずはじめに、Windows 10 はご存知の通り WaaS モデルの採用により定期的に機能追加されていきます。コンシューマー向けの CB(Current Branch)、企業向けの CBB(Current Branch for Business)、特定用途向け LTSB(Long Term Servicing Branch)といったモデルが御座います。

    これらサービスモデルの説明は https://technet.microsoft.com/ja-jp/library/mt598226(v=vs.85).aspxをご参照下さい。

     

    Windows 10 20157 29 日にCBCBBLTSB がリリースされ、201511 月にCB 向けのVer 1511(コードネーム TH2)がリリースされました、そして先日 CBB 向けの Ver 1511 リリースされました。

    CBB リリース情報: http://blogs.technet.com/b/windowsitpro/archive/2016/04/08/windows-10-1511-is-now-a-current-branch-for-business-cbb-release.aspx

     

    今まで提供されてきた Windows 10 のビルド番号とサービシングモデル: https://technet.microsoft.com/ja-jp/windows/release-info

     

    また、今までの Windows 10 の更新履歴は https://technet.microsoft.com/ja-jp/windows/release-infoに記載しています。

     

    今後どういった機能が追加されていくかを記載したロードマップ: https://www.microsoft.com/en-us/WindowsForBusiness/windows-roadmap


    サービシングモデルとロードマップを参考にして頂き、Windows 10 の展開にお役立て下さい。


    0 0
    0 0

    Registre-se no webinar do dia 12 de Abril de 2016 – “Microsoft IoT e estratégias de segurança”-  como reforçar a sua estratégia para fixar dispositivos, conexões seguras e uma nuvem confiável. 

    https://info.microsoft.com/Tips-for-a-Secure-IoT-Strategy_Registration.html?wt.mc_id=US_CE_TC_OO_BLOG_NONE&ls=BLG&lsd=IOT%20Webinar


    0 0

    Registrense en el webinar de 12 de  abril de 2016 -"Microsoft IoT y estrategias de seguridad "- cómo fortalecer su estrategia para asegurar dispositivos, conexiones seguras y una nube de confianza.

    https://info.microsoft.com/Tips-for-a-Secure-IoT-Strategy_Registration.html?wt.mc_id=US_CE_TC_OO_BLOG_NONE&ls=BLG&lsd=IOT%20Webinar


    0 0

    Con el lanzamiento del thriller de acción Quantum Break comienza una nueva era donde la unión de los ecosistemas de Xbox One y Windows 10 permitirá tener más juegos de Xbox en desarrollo que nunca. Quantum Break ofrece una experiencia inmersiva única que combina emocionantes escenas live action y un elenco estelar que incluye a Shawn Ashmore (“X-Men: Days of Future Past”) como el héroe Jack Joyce, Aidan Gillen (“Game of Thrones”...(read more)

    0 0

    В прошлый раз мы с вами разобрались с тем, каким образом устроены внутренние механизмы SQL Server Service Broker-а (http://blogs.technet.com/b/sqlruteam/archive/2016/04/07/sqlserver_2d00_service_2d00_broker_2d00_troubleshooting_2d00_overview.aspx). С этого блога начинаем знакомство с проблемами, которые могут возникнуть с брокером и методами их решения.

    Далее мы обратим свое внимание на сетевые проблемы, как наиболее часто встречающиеся при первоначальном развертывании и при эксплуатации системы.

    Какие виды ошибок сетевого доступа, чаше всего возникают при эксплуатации сервис-брокера

    1. Общие сетевые проблемы характерные для любой установки SQL Server. 

    2. Отсутствие точек подключения (Endpoint).

    3. Точки подключения переведены в режим останова (STOPPED) или неправильно настроены.

    4. Доступ к точкам подключения закрыт межсетевым экраном.

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

    1. Убедиться в доступности удаленного хоста командой ping host_name, а если ping host_name не проходит, то выполнить ping по IP-адресу, и далее разбираться с системой разрешения имен.  

    2. Убедиться в доступности удаленного SQL Server с помощью команды SQLCMD -E -Sserver. Если это подключение невозможно, то необходимо разбираться с сетевыми соединениями на SQL Server, доступностью портов и работой SQL Browser.


    После решения общих сетевых проблем (если это не привело к положительному результату и сервис-брокер по прежнему не работает) можно переключиться на решение специфических проблем сервис-брокера.

    Отсутствие точек подключения (Endpoint)

     Необходимо убедиться, что точки подключения для Service Broker-а созданы, для этого необходимо выполнить команды.

    use InstInitiatorDB;
    GO
    select* fromsys.service_broker_endpoints;
    GO
    select* fromsys.endpoints where name ='InstInitiatorEndpoint';

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

    Точки подключения переведены в режим останова (STOPPED) или неправильно настроены 

    Если одна из точек остановлена (или некорректно настроена), то при попытке соединения с ней возникнет ошибка как показано ниже.


    Такая же ошибка отображается и в трассах SQL Profiler. Как видно из трасс, SQL Server (не смотря на наличие ошибки) продолжает свои попытки установить соединение на точку подключения удаленного сервера.


    При наличии подобной ошибки рекомендуется убедиться в доступности порта удаленной точки подключения. Как видно в данном случае соединение к порту не возможно.

    После этого можно проверить"слушает" ли удаленный сервер порт номер 4022 (в данном случае это номер порта для Service Broker-а). Здесь  показано как мы выгружаем в файл ports.txtданные о том, какой из процессов "слушает" какой порт.


    После решения данной сетевой проблемы и восстановления соединения, сообщения будут переданы автоматически  (См. последние 5 строк трассы).

      

    Справедливости ради необходимо сказать, что с помощью утилиты ssbdiagnose.exe мы бы добились того же результата значительно быстрее.

      

     Доступ к точкам подключения закрыт межсетевым экраном.

    Еще одной наиболее вероятной проблемой может быть закрытие портов межсетевыми экранами. Это более чем возможно, и потому еще, что для сервис-брокера могут использоваться нестандартные номера портов. 

    Последовательность решения здесь принципиально не отличается от вышеописанной, и, более того, как и в предыдущем случае, утилита ssbdiagnose.exe оказывается на высоте, давая нужный результат сразу.


    В следующих статьях мы продолжим рассмотрение возможных причин некорректной работы SQL Server Service Broker.

     

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

     

     

     

     

     

     


    0 0

    As I've already mentioned in my previous post, that Azure Backup and Azure Site Recovery functionality become available in Azure CSP. Previous post was related to Azure Backup, and today I'll talk about Azure Site Recovery.

    Azure Site Recovery (ASR) is a cloud service that provides management and orchestration for disaster recovery scenarios.

    Here are details regarding ASR pricing:

    1. You are charged for every protected instance (VM) - ~$16 for VM, replicated to non-Azure site (customer's backup DC or service provider DC) and ~$54 for VM, replicated to Azure.
    2. If you use replication or VMs to Azure, then you also will be charged for consumed storage and storage transactions. ASR uses Page blobs on Geo-redundant Storage Accounts (GRS).I recommend to use storage pricing calculator.
    3. If a failover occurred and protected VMs in Azure become active, then you also will be charged for consumed Compute resources. In this scenario replication traffic direction will be opposite - from Azure DC to customer's DC. It means that you also will be charged for outbound network traffic.

    Available Azure Site Recovery scenarios in CSP

    ASR in Azure CSP is a little bit different from ASR in traditional subscriptions. First of all, there is no Backup Vault and Site Recovery Vault anymore. Now there is only one vault called "Recovery Services Vault", which combines Backup and Replication functions.

    Here are ASR Scenarios, currently available in Azure CSP:

    1. From my site to Azure #1: VMM
      Replicates Hyper-V VMs managed my VMM to Azure using Hyper-V Replica
    2. From my site to Azure #2: Standalone Hyper-V Hosts
      Replicates Hyper-V VMs to Azure using Hyper-V Replica, without VMM.
    3. From my site to Azure #3: vCenter
      Replicates vSphere VMs to Azure on vCenter-managed hosts using Configuration server (former InMage Scout).
    4. From my site to Azure #4: Physical Machines
      Also former InMage based scenario. Simillar to scenario #3, but doesn't use vCenter. In fact - this scenario allows you to replicate any supported Windows Server or Linux server to Azure - no matter is it a VM on KVM or non-virtualized server. Universal scenario.
    5. From my site to another site: VMM
      Replicates Hyper-V VMs from primary VMM-managed site to secondary VMM-managed site using Hyper-V Replica.

     There are scenarios, that are available in traditional Azure subscriptions, that are not available via Azure CSP (yet?):
    1. Between two on-premises VMM sites with SAN Array Replication
    Although this scenario is very similar to scenario #5, I assume that you won't be able to configure source and target storage array mapping in the current UI on newAzure portal. I mean this button from the old portal:

    Anyway - I don't have any supported storage arrays in the lab, so I can't check it by myself. If you'll be to check it - please, leave information in the comment.

    2. Between two on-premises VMWare sites
    This scenario allows you to install InMage Scout solution in 2 different VMWare sites and configure replication of VMs and disaster recovery. InMage was acquired by Microsoft in 2014, so currently this solution is licensed via Azure Site Recovery subscription, using the pricing model provided above. But the overall installation and management experience of InMage Scout is very different from other ASR scenarios. Because of that, I suppose, this scenario wasn't migrated to the new Azure Portal.

    Also this scenario covers physical servers in one site to VMWare VMs in a backup site disaster recovery. More details about this scenario is available here.

    Disaster Recovery to Azure

    For all Disaster Recovery scenarios to Azure location, you must use a Storage Account to store replicated VMs data. On the Azure Portal click +New -> Data & Storage -> Storage Account. Specify a Storage Account name and choose:

    • Deployment mode = Resource Manager (classic non-ARM storage account won't fly)
    • Performance = Standard (we don't need SSD storage here)
    • Replication = Geo-redundant Storage (GRS) - because ASR doesn't support LRS storage
    • Choose Subscription and Resource Group where your Recovery Services vault is stored
    • Choose the preferred location. When a disaster will occur, VMs will be launched in this geo.

    Also you need to create at least one Virtual Network in Azure region that you will use for DR.

    There are some requirements for this scenario that you must remember:

    1. Hyper-V hosts must run Windows Server 2012 R2.
    2. Guest OS in the VM must be supported in Azure, it must be 64-bit.
    3. VMs must be highly available (= run on top of Hyper-V cluster).
    4. Max virtual disk size is limited by 1023Gb, this is the current limitation for Azure VMs.
    5. iSCSI, SharedVHDX and FC-attached disks are not supported.
    6. VHDX is supported. Although VHDX isn't currently supported in Azure, Site Recovery automatically converts VHDX to VHD when you fail over to Azure.
    7. VMs with multiple network adapters are now supported.
    8. Generation 2 VMs are supported only if they run Windows Server 2012 R2. Linux on Gen2 VMs is not supported. Also generation 2 virtual machine with OS disk type of Basic Disk which includes 1 or 2 Data volumes with disk format as VHDX which is less than 300GB is supported.

    From Hyper-V to Azure without VMM

    This scenario allows you to replicate tenant VMs that run on clustered Hyper-V hosts in customer or service provider datacenter (main DC). If a main DC will fail, then ASR will manage the disaster recovery process and launch all protected in a specified Azure datacenter. This is the simplest scenario in terms of deployment. Read the full documentation about this scenario here.

    Go to "Site Recovery" menu in Recovery Vault Settings and select "From my site to Azure" and "Standalone Hyper-V hosts" scenario.

    Create a new Hyper-V Site:

    Then download Vault Credentials for this site:

     

    Download and install Azure Site Recovery Provider (not Agent!) on all Hyper-V hosts that you wish to protect. Use the vault credentials that you've downloaded from Azure portal during the installation process. After that, these Hyper-V hosts will appear on Azure Portal.

    Create a Replication Policy:

    Associate the Replication Policy with this Hyper-V Site:

    OK, configuration step is done. Now we need to add replication for specific Hyper-V VMs. Click +Replicate button and select a Hyper-V Site that we've just created. Choose Resource Manager deployment model (because Classic is not available in CSP).

    On the next step you'll see all VMs on all Hyper-V hosts that were found in this site. Choose the VMs that you wish to replicate to Azure.

    Specify OS type (Windows or Linux) and select a storage account:

     

    And choose the replication policy:

     

    That's all. Now we can go to "Replicated Items" menu, where we'll see all the replicated VMs. You can check the status of initial replication, which can take some time.

    As you see, Azure automatically detects the most appropriate size for this VM. Don't forget to select a desired vNet in Azure, which will be used after the failover:

      

    When everything is done, try to launch a test failover:

    From Hyper-V to Azure with VMM

    This scenario allows you replicate tenant VMs that run on Hyper-V hosts, managed by VMM 2012 R2, to any Azure location. Also it has integration with Azure Pack. If a main DC (customer's DC or service provider's DC) will fail, then ASR will manage the disaster recovery process and launch all VMs, that were assigned to a protected VMM cloud, in a specified Azure datacenter. Read the documentation regarding this scenario here. It covers classic non-ARM ASR functionality, but the overall approach is the same. Also read this article.

    Download the Vault Credentials:

    Download and install Azure Site Recovery Provider on the VMM server. If you have a clustered VMM installation, then install ASR Provider on the active cluster node, and install it on all passive nodes after that.

    Important note - ASR Provider configuration is applied to a whole VMM environment. It means that you can't use different recovery vaults for different clouds/VMs. So if a service provider wants to use Azure as a backup datacenter, he'll need to use the same Azure subscription to enable ASR for different tenants.

    Download and install Azure Site Recovery Agent (not Provider!) on all Hyper-V hosts that a part of a protected Cloud in VMM. All VMs are being replicated to Azure using Hyper-V Replica functionality, so no agents need to be installed inside a VM.

    OK, after that your VMM server (or cluster) will appear on the Azure Portal. Create a replication policy, choose VMM clouds that you wish to protect and configure Network Mapping.

    Then you need to enable replication for all existing VMs in the protected cloud that you wish to replicate to Azure by clicking "Enable Hyper-V recovery manager protection":

     

    Also you can enable replication for all new VMs by modifying the template or enabling the replication manually during the VM creation:

    If you use Azure Pack on the main site, that you can enable replication for VMs by clicking "Enable protection" option in the Plan settings. After that all the VMs in this plan will be replicated to Azure using ASR.

    Also you can enable VM replication on Azure Portal:

    After all these steps, try to make a test failover VMM cloud to Azure using the procedure, described in the previous scenario.

    From any server to Azure

    This scenario is called "From my site to Azure: Physical Machines (not virtualized)" in the UI. But in fact you can use it to replicate any Windows Server or supported Linux to Azure, no matter is it a physical server or Hyper-V/VMWare virtual machine. Read the documentation for this scenario here.

    This scenario is agent-based, so an agent need to be installed on every VM that you want to replicate (but it can be installed automatically). This is different from Hyper-V/VMM scenarios described above, where the replication is provided on a host level using Hyper-V Replica functionality.

    Go to "Site Recovery" menu in settings and choose "From my site to Azure" and "Physical machines (not virtualized)" scenario.

    You need to add new Configuration server in your On-Premise environment. This is a re-designed InMage Scout server, which combines former Process Server and Master Target Server roles of Scout (btw, you still can install them manually and add via Azure Portal).

    Download Vault Credentials from this page:

    Deploy a new VM with Windows Server 2012 R2 in the site, where you want to use replication to Azure. In my case it is a service provider environment, managed by Azure Pack. Logon to this VM as an administrator. Download and launch Azure Site Recovery Unified Setup:

    Choose "No", because we don't plan to protect VMWare VMs in this case:

    Use your Vault Credentials file:

     

    And wait until the installation will complete:

    After that Microsoft Azure Site Recovery Configuration Server wizard will launch. Click "Add Account" and specify a domain user, who have admin credentials on servers, that you with to replicate to Azure. You can change this later by launching this wizard using C:\Program Files (x86)\Microsoft Azure Site Recovery\Home\svsystems\bin\cspsconfigtool.exe.

    If you plan to replicate Linux servers, that you'll need to add a separate account with root access on your Linux machines.

    Then download and install the latest version of Azure Site Recovery Provider (current ASR Provider version, included in Configuration server distributive, was outdated). 

    Configuration Server will appear on Azure Portal just after the installation:

     

    Create new Replication Policy. Enable "Multi-VM consistency", to be able to replicate servers in groups. Replication across the group members will be consistent (e.g. several domain controllers).

     

    OK, configuration is completed. Now we need to add protected servers and configure their replication to Azure. Prepare Windows Server and Linux machined like is described in the documentation.

    After that, go to "Replicated Items" and click "+Replicate".

    Add servers that you wish to replicate. That must be accessible via LAN from the Configuration Server.

      

    Wait until the specified servers will be discovered by Configuration Server. Enable "Replicate physical machines together in a replication group" to use replication policies with "Multi-VM consistency" enabled.

    Choose a replication policy:

     

    After that Configuration Server will push a replication agent installation on the specified servers. Agent will check if all the requirements are met and start the initial replication.

    When the initial replication will be completed, try to launch test failover to check if everything is OK.

    From VMWare to Azure

    This scenario allows you to replicate VMWare vSphere VMs, hosted in On-Premise environment (customer or service provider datacenter) to Azure. Very similar to previous scenario. Documentation is the same, it is available here.

    Go to "Site Recovery" menu in settings and choose "From my site to Azure" and "vCenter" scenario.

     

    Now you'll need to add new Configuration server in your On-Premise environment (if you didn't install it in previous scenario). This is a re-designed InMage Scout server, which combines former Process Server and Master Target Server roles of Scout (btw, you still can install them manually and add via Azure Portal).

    Download Vault Credentials from this page:

     

    Deploy a new vSphere VM with Windows Server 2012 R2 in the site, where you want to use replication to Azure. Logon to this VM as an administrator. Install VMWare PowerCLI 6.0. Then install Download and launch Azure Site Recovery Unified Setup:

     

    Use your Vault Credentials file:

     

    And wait until the installation will complete:

     

    Then Microsoft Azure Site Recovery Configuration Server wizard will launch. Click "Add Account" and specify a domain user, who have admin credentials on servers, that you with to replicate to Azure. Also add another account that has access to vCenter server. You can change this later by launching this wizard using C:\Program Files (x86)\Microsoft Azure Site Recovery\Home\svsystems\bin\cspsconfigtool.exe. If you plan to replicate Linux servers, that you'll need to add a separate account with root access on your Linux machines.

    After that download and install the latest version of Azure Site Recovery Provider (current ASR Provider version, included in Configuration server distributive, was outdated).

    Configuration Server will appear on Azure Portal just after the installation:

     

    On the next step you need to add vCenter to the Configuration Server. I think that there is a bug on this step, because in my case UI can't load the available Configuration Server, it can show this message forever:

     

    As a workaround, go back to step 2, choose the available Configuration Server and click "+vCenter" button.

     

    Create new Replication Policy. Enable "Multi-VM consistency", to be able to replicate servers in groups. Replication across the group members will be consistent (e.g. several domain controllers).

     

    OK, configuration is completed. Now we need to add protected servers and configure their replication to Azure. The procedure is similar to the previous scenario. When the initial replication will be completed, try to launch test failover to check if everything is OK.

    Disaster Recovery across two sites

    As I already mentioned before, currently ASR supports only one site to site scenario - VMM to VMM. Documentation regarding this scenario is available here. In this scenario there are 2 On-Premise sites - main datacenter and backup datacenter. Any of them can be a customer datacenter or a service provider datacenter. ASR manages the disaster recovery processes, but a replication traffic goes directly between Hyper-V hosts using Hyper-V Replica functionality. You can use this scenario to offer DisasterRecovery-as-a-Service in Azure Pack.

    To configure this scenario, go to "Site Recovery" menu in Recovery Services vault Settings and choose scenario "From my site to another site":

    On the next step you need to add VMM server (or several VMM servers in a cluster) to ASR. Download the vault registration key:

    Download and install Azure Site Recovery Provider on VMM servers in both sites. If you have a clustered VMM installation, then install ASR Provider on the active cluster node, and install it on all passive nodes after that.

    Important note - ASR Provider configuration is applied to a whole VMM environment. It means that you can't use different recovery vaults for different clouds/VMs. So if a service provider wants to provide "Backup Datacenter" service to a customer and replicates all the VMs from customer DC to his DC, he needs to use the same Azure subscription with the same Recovery Services vault for different tenants.

    Download and install Azure Site Recovery Agent (not Provider!) on all Hyper-V hosts that a part of a protected Cloud in VMM (in main on in backup DC). All VMs are being replicated to a backup DC using Hyper-V Replica functionality, so no agents need to be installed inside a VM.

    OK, after that your VMM servers will appear on the Azure Portal. Create a replication policy:

    Then choose VMM clouds in main and backup datacenter:

    Last step in the configuration wizard - map virtual networks in Main DC and Backup DC. This step is optional, but very recommended.

    Then you need to enable replication for all existing VMs in the protected cloud that you wish to replicate to the backup site by clicking "Enable Hyper-V recovery manager protection":

    Also you can enable replication for all new VMs by modifying the template or enabling the replication manually during the VM creation:

    If you use Azure Pack on the main site, that you can enable replication for VMs by clicking "Enable protection" option in the Plan settings. After that all the VMs in this plan will be replicated to Azure using ASR.

    Also you can enable VM replication on Azure Portal:

    After all these steps, try to make a test failover VMM cloud to the backup site and check if everything is working right.

    ASR Recovery Plans

    OK, now when you've deployed, configured and tested ASR functionality for disaster recovery of Hyper-V VMs, vSphere VMs and physical servers from your site to Azure, or from your main datacenter to your secondary datacenter, it's time to feel the true power that ASR gives you with a functionality called "Recovery Plans".

    Recovery Plans allow you to configure all the steps that can be needed during disaster recovery failover situations. For example, re-configure network load balancer or change Traffic Manager configuration when a disaster occurs. To create a new recovery plan, go to Recovery Services vault settings and click "+Recovery Plan":

    Then you can configure steps for a failover process. You can add your own actions to the process. There are 2 types of actions: Azure Automation Scripts and Manual actions. Azure Automation Scripts are powerful, you can read about some ASR examples here.

    But unfortunately, Azure Automation is not yet available in Azure CSP. I hope it will be changes soon.

    Manual actions are instructions that you or your colleague should do during the failover. This is a simple text, that guide you through the whole process when a disaster will occur. No so exciting as Azure Automation Scripts though.

    OK, that's all for today. Check Azure Site Recovery by yourselves. It is a great cloud service with a great value, and it's great that it became available via Azure CSP. Let's see how Microsoft CSP Partner will use it to provide Disaster Recovery services to their customers.


    0 0

    SYMPTON:

    Users receive message "There was a problem signing you in.  Please try again in a few minutes.", when trying to sign in to the Next Generation Sync client.

    CAUSE:

    Credential Manager was disabled.

    SOLUTION:

    Enable Credential Manager.

    -Go to Start

    -Type in Regedit

    -Navigate to the path - HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa

    -Right click on LSA key and select New, DWord, type DisableDomainCred

    -Set value to 1


    0 0

    image
    Apr.
    12
    image
    image

    Script Download:  
    The script is available for download from https://gallery.technet.microsoft.com/scriptcenter/How-to-Enable-IIS-Remote-fdb21036.

    You can also use  Microsoft Script Browser for Windows PowerShell ISE to download the sample with one button click from within your scripting environment. 

    The sample script provides the below functionality: 1. Remotely enable the RemoteManagement in WMSVC on all the specified server 2. Enable the IIS Manager Credentials and Windows Credentials only. 3. Create a Test IIS user (non-admin) and add this test use to the concerned site.

    You can find more All-In-One Script Framework script samples at http://aka.ms/onescriptingallery


    0 0

    ISSUE:

    When trying to sync with Next Generation Sync client (NGSC), the user can sign in, choose a location to store files, however, after receiving the “Loading your list of folders”, users receive the following message:

    CAUSE:


    Document library schema contains required columns or a column with validation formula.

    SOLUTION:

    -On the OneDrive site, click link to switch to classic mode


    -Select the Library tab

    -Choose Library Settings button

    -Inspect each column and remove required restrictions and validation formulas if applicable.


    0 0

    Evernote 對生產力以及 Get things done 懷有極大的熱忱。當已經很好用的服務彼此之間可以串連協作時,您的一天又可以運作的更流暢一些。因此,今天我們很榮幸向您介紹一個 Outlook 的增益集:Evernote for Outlook。有了它,Outlook 的使用者可以輕鬆地保存重要電子郵件到 Evernote,要在 Outlook 裡分享記事也更容易。

    新的 Outlook.com 使用者,以及使用 Outlook 2013、Outlook 2016 和 Outlook 網頁版的 Office 365 使用者都可以利用 Evernote for Outlook。如果您使用 Evernote for Outlook,可以直接從 Outlook 擷取電子郵件訊息和附加檔案到 Evernote 裡存入;也可以將 Evernote 記事附加到您正在撰寫的 Outlook 電子郵件中。

    儲存 Outlook 電子郵件到 Evernote

    使用 Evernote for Outlook 增益集,好處是避免讓重要電子郵件遺失在擁擠的收件匣裡,還能將一個專案的所有相關資料都整合在一起。

    您可以選擇將單封電子郵件或完整對話串,包括其中附件,直接存到指定的記事本中;還可以直接加上標籤及更多說明。按下儲存後,您的 Evernote 帳戶裡就會出現這一篇電子郵件的記事,接著繼續在 Evernote 編輯。

    小提示:如果您會收到週報表或團隊報告等電子郵件,可將它們都存到 Evernote 記事本中。如此一來,隨時都有這些報告的可編輯記事版,免除當需要時還得從收件匣東翻西找的困擾。

    附加記事到 Outlook 電子郵件

    使用 Evernote for Outlook 增益集也方便您附加記事到電子郵件中。怎麼做呢?您可以從 Outlook 增益集的側邊選單選擇一本 Evernote 記事本,或搜尋指定的記事。

    選擇好要附加的記事後,該記事會以預覽模式顯示在電子郵件中。所有收件人都可以點擊縮圖以查看完整記事。

    no shadow

    馬上嘗試

    Outlook.com 使用者,請確認你的帳戶已升級到最新版。如果還不是 Outlook.com 使用者,現在註冊即可取得最新版並開始使用 Evernote 的 Outlook 增益集囉!

    依照下列步驟,即刻開始使用 Evernote for Outlook 吧:

    • 如果你使用的是 Outlook 2013 或 Outlook 2016,請點「檔案」再點「管理增益集」。Outlook 網頁版或 Outlook.com 使用者,請點右上角的齒輪圖示,再點「管理增益集」。
    • 在「管理增益集」頁面,點擊 + 符號再選「從 Office 市集新增」。
    • 點選 Evernote for Outlook 增益集再按新增按鈕,就會開始安裝。

    請注意:Evernote for Outlook 在 Mac 版 Outlook 2016 僅供唯讀。

    更多 Evernote for Outlook 相關資訊,請查看我們的快速入門指南或造訪 App Center。從此再也不用擔心遺失任何重要資訊囉!

     

    作者: Evernote Taiwan 發佈日期: 08 四月 2016


older | 1 | .... | 876 | 877 | (Page 878) | 879 | 880 | .... | 889 | newer