Into Windows 10 https://docs.microsoft.com/archive/blogs/okemokoloebube/feed.xml Designed to help enterprises with an emphasis on Windows 10 and Mobile Device Management Tue, 16 Apr 2019 05:22:06 GMT en-US hourly 1 Enroll a Windows 10 Machine into Windows AutoPilot https://docs.microsoft.com/archive/blogs/okemokoloebube/enroll-a-windows-10-machine-into-windows-auto-pilot Mon, 11 Sep 2017 10:44:35 GMT https://blogs.msdn.microsoft.com/okemokoloebube/?p=765 https://docs.microsoft.com/en-us/windows/deployment/windows-10-auto-pilot What I’ll like to do is provide a walkthrough on how to go through this whole process. Something to keep in mind is that to do it's magic behind the scenes Auto Pilot uses Azure AD and a device ID pre-populated in the Microsoft Cloud to make it happen.
  1. You need to have Azure Active Directory P1 or P2
  2. Windows 10 1703 [July Update] and above is needed on the Client Machine going through this process
  3. Internet access is required when going through the OOBE. It’s how we connect to the cloud service
  4. The Device must be registered to your Organization.
Let's Walk through these one at a time.   Azure AD P1 or P2: If you don’t know the difference between the Azure AD offerings, you can see the table here which explains it better than I can https://www.microsoft.com/en-us/cloud-platform/azure-active-directory-features Azure AD has different offerings and the higher you go the more features you get. For the Windows Auto Pilot service you need to be at level P1 or P2. If you are running on the free level then this will not work.   Windows 10 1703 [July Update] and above is needed on the Client Machine going through this process: This one is pretty straight forward but you need to be on Windows 1703 with the July update. On my machine the Windows version is Microsoft Windows Version 1703 (OS Build 15063.601). From my tests things go a lot better when you are on the latest cumulative update for Windows 1703   Internet Access: If you don't have internet access your machines will not be able to connect to the Windows Auto Pilot service. You'll basically get the normal Windows Out Of Box Experience every other consumer machine gets.   Registering a device to your organization: Every device [Including Virtual Machines] have a hardware ID and this is what needs to be registered in the Microsoft Cloud. It lets our cloud service know a device is registered to an organization think of it like an asset tag connected to the cloud. When the Auto Pilot service detects a registered hardware ID it connects it to the right Azure AD tenant and all the  pre-configured settings start flowing down to the client machine. Microsoft is working with hardware vendors so that in the future companies purchasing devices can have the vendors Pre-register the devices before they even get delivered to the company purchasing them. For this exercise we'll be using a PowerShell script to extract the hardware ID and uploading it into the Cloud. The PowerShell Command I'm running can be found here https://www.powershellgallery.com/packages/Get-WindowsAutoPilotInfo/1.1/DisplayScript Now I'm going to walk you through the setup of a Windows 10 machine which is registered in my organization and is configured to be enrolled through Windows Auto Pilot. There are two stages I'll show you.  
  1. The first is getting the hardware ID extracted using the PowerShell command.
  2. The second is getting the hardware ID into the cloud service through Windows Store For Business [WSFB]
  3. The final stage is turning on the machine and seeing if it works.
    EXTRACT HARDWARE ID Since we are doing this manually we'll have to extract the hardware ID using a PowerShell script. You want to install the Script on your Windows 10 machine from an elevated Powershell Prompt using this command PS> Install-Script -Name Get-WindowsAutoPilotInfo You might get a bunch of prompts depending on if you have done this before talking about running unsigned scripts and having the right permissions. I said yes to everything but this is a demo machine so there are no consequences to doing so. Make sure you are not breaking any organizational policies.     If you run the command and all goes well the script will be in this location C:\Program Files\WindowsPowerShell\Scripts\       Our next step is to then use the script to pull the device information from WMI. The information will be created and out into a spreadsheet which can then be read by the Cloud Service. Something to add is that you need to set your restriction policy to allow you run scripts from the location of the PowerShell script.  I am on a demo machine so I set mine to unrestricted, but you probably don’t want to do that in a real world environment.  The command I ran to set my restriction policy is Set-ExecutionPolicy unrestricted The command format is .\Get-WindowsAutoPilotInfo.ps1 -ComputerName <ComputerName> -OutputFile .\NameOfOutputfile.csv   If everything goes well you should now see a .CSV file with the name you chose in the location from which you ran the command. This means that the command was executed correctly and we can uploaded the device ID into the Windows Store For Business. Something you might be thinking is how to get these device ID’s of brand new machines without booting into Windows for the first time. The first thing to note is that Microsoft is working to make sure this manual process is almost never used. We are providing Hardware vendors the means to do this, so you never have to worry about this. However, if you do want to do this today you can do this at the very first step of the OOBE experience. You can bring up a console at the first step OOBE by pressing [Shift + F10] and then you would can grab the script from a network share or storage device and run it. You’ll generate a .CSV file which you can then copy to another location from where you can access it. It definitely requires getting your hands dirty but with Hardware Vendors being onboarded for this process we expect our customers to not have to go through this for much longer.     UPLOAD HARDWARE ID INTO THE CLOUD [WSFB] Navigate to the Windows Store for Business and Sign in https://businessstore.microsoft.com/en-us/store   You need to be a Windows Store For Business Admin to do this by the way so if you’re not this is not going to work After you login to the store Click on Manage   Click on Devices on the left-hand side of the browser Click on Add Devices.   If this is your first time doing this then you might have to create an AutoPilot Deployment Profile but more on that later. After you click on “Add Device” Windows Explorer will pop up and you need to point it to the location of the CSV file you created.     After you select the file it will ask you if you want to add it to a group. you have the choice of creating a new group or adding it to an existing group. I simply chose to add it to an existing group previously created. If all goes well and we read the device ID then you should see a message at the top letting you know that it your request is being processed. I kept refreshing the browser and about 4 minutes later I see a new machine show up.       You have the option of creating a an AutoPilot Deployment Profile and assigning it a different set of settings compared to another profile. An example that comes to mind is giving your IT Admin an AutoPilot profile that gives them Local Admin rights while you have another profile for other users that doesn't give them Admin rights. I decided to create a new Auto Pilot Deployment Profile, so I can assign it the options I want. To create a new profile I clicked on the arrow next to “Auto Pilot Deployment” and clicked on “Create new Profile”       I can now select the OOBE options I want my users to skip using the buttons on the right hand side     I click create and my profile should now be available. I then check the box on the device I just added and click on the arrow below “AutoPilot Deployment” and I can now Apply the profile I just created.       This means that the Auto Pilot settings I’ve activated for that profile will be applied to that device. Now that we’ve done all that I’m going to reset my machine and see what happens, fingers crossed!   TURN ON THE MACHINE TO SEE IF IT WORKS At this point in the real world all a user has to do is turn on the machine given to them by IT and during the first boot up the machine will contact the Auto Pilot service. Since this is a demo I'm using a Virtual Machine which I just reset. The first screen I see when I turn on the machine is the Keyboard Layout and I then choose my language.     I choose the layout Skip over some basic Windows Setup Questions. I accept the License Agreement and Install some updates in the background and then I get to the login screen. What I want to see is the name of my Azure AD tenant when I go to login.     This means we've successfully connected with the Windows AutoPilot service and we are getting settings from our tenant. Once It picks up the organization the device is registered to then we should be fine. Something that you can do is use an MDM service like Intune to push compliance policies to your devices. In my case we have multi-factor authentication turned on so I get prompted to set that up and I also have Windows Hello turned on. If I had applications being pushed to the machine then they'll be getting installed at this point.     And we are on the desktop!   I can go into settings and verify that it is joined to Azure AD, I like when stuff works the first time.   I have the Power BI application assigned to all users in my tenant through the Windows Store For Business and I see it's installed   So we are in the program. What I’ve shown you is me pulling the device ID from a Windows 10 1703 machine and then enrolling the Device into the Microsoft Store through the Windows Store For Business and applying a Windows AutoPilot profile to it. We then deployed the device and during OOBE the device got configured to be a corporate ready device using Intune policies in this case. I hope it helps you! Until next time may your path to deployment of Windows 10 get even shorter thanks to AutoPilot!]]> Update Compliance https://docs.microsoft.com/archive/blogs/okemokoloebube/updatecompliance Sun, 23 Apr 2017 21:59:38 GMT https://blogs.msdn.microsoft.com/okemokoloebube/?p=665 What if I told you there was a tool that would allow you to see in one glance what version of Windows 10 you are running [1507, 1511, 1607, 1703]? What if I told you the same tool will even show you if your Windows 10 machines had on the latest cumulative updates? What if I told you the tool was currently being offered at no charge while it’s in Preview? Allow me to introduce you to “Update Compliance” Update Compliance leverages data collected by the Windows telemetry service to give build a report on where you were with your Windows 10 machines regarding Windows updates. Sure, tools like System Center have this reporting ability built into them but Update Compliance does this without needing the same kind of infrastructure tools like System Center require. Something to note is that it’s currently in preview and the service is offered for free. I have no idea if this will end after it becomes generally available or not. updatecomplianceimage24   Let’s look at what you can expect to see when you have Windows Update Compliance Set up: -          An overview of how many Windows 10 machines you have enrolled into the service -          You also see how many machines are reported as “needing Attention”. Machines needing attention are machines that require some action from you and the action on your part. An example of a machine needing attention would be a machine running a build of Windows 10 that is out of support. updatecomplianceimage1  -          It lets you know if you have the latest quality update for the Windows 10 version you are on.  updatecomplianceimage2  -          It lets you know if you have the latest Security Updates on your Windows 10 Machine  updatecomplianceimage3  -          It lets you see if you have the latest feature updates   updatecomplianceimage4  -          It also shows you what branch of Windows 10 you are on which could be Current Branch [CB], Current Branch for Business [CBB], Long-term Servicing Branch[LTSB]  updatecomplianceimage5  Update Compliance uses Windows Telemetry to understand what version of Windows 10 you are running and it also checks to see if you have the latest updates installed.   2 very important things to understand: This is a preview feature which is currently being offered as a free service. Since it’s in preview that means that major changes can be made before it is made available for the general public. This is a Windows 10 only feature. If you enroll a Windows 7 machine it will automatically get moved into the Upgrade Readiness portal. Only Windows 10 machines show up in the Update Compliance portal.   How do you get started? Well the enrollment process is the exact same as Upgrade Readiness which I’ve written about in a different blog post. I’ll give you a general overview but the steps are the exact same as they are in this post https://blogs.msdn.microsoft.com/okemokoloebube/2016/09/28/windows-upgrade-analytics/  
  1. You need an Azure Account. There is currently no working around this requirement, but you can set up an Azure Trial tenant which means you don’t get charged. The trial lasts for 30 days and then after that you have to put in a credit card to keep using it. If Update Compliance is the only service on your Azure Account you will not get charged as it is currently offered as a free service. I know people get antsy about putting in credit card information but in my testing and in working with other customers, no one has been charged for using this particular service.Trial Azure Account + Update Compliance Service = No charge You can set up a free Azure Account Here https://azure.microsoft.com/en-us/free/
  2. After you get your Azure Account running you need to add OMS to Azure as Update Compliance runs on Azure. Note that it is called “Log Analytics” in the Azure Portal. Let’s walk through setting that up.
Log in to Azure and you should see your dashboard. On the will be your selection/navigation pane and you want to click on “More Services” and then click on “Log Analytics”. updatecomplianceimage6   updatecomplianceimage7   You click on Log Analytics You then click on Add to add it to your Azure Workspace  updatecomplianceimage8  You have different options when creating the workspace depending on what you’ve set up in Azure before. To set up your workspace you need to Choose your name [This is the name of your workspace] Choose an Azure Subscription you want the workspace linked to Choose a Resource Group you want the workspace to be hosted in Choose your Location Choose Pricing [Free Tier is enough]  Something I normally do is “Pin to dashboard” for something I’m creating so I can find It on the dashboard once it gets deployed  updatecomplianceimage9    Once you fill out the information click “OK” You’ll get a prompt saying “Validating”  updatecomplianceimage10  You can also check in your notifications in Azure to see if it was successful  updatecomplianceimage11  If you pinned it to your dashboard you can go to your Azure dashboard and click on the name of the item you created. updatecomplianceimage12  You can also just click on “more services” and navigate to the Log Analytics screen and you should see your workspace. Click on the name of your workspace and it will take you to the OMS workspace page in Azure from where you can click on “OMS Portal” which will redirect you to the actual OMS service. updatecomplianceimage13   You should see something like this  updatecomplianceimage14  At this point we have no data and as we haven’t done anything. We need to do a couple of things   We need to add the “Update Compliance offering to our workspace We need to get the subscription ID We need to download the Upgrade Compliance deployment script We need to configure Windows 10 machines to upload telemetry to our workspace     ADD UPDATE COMPLIACE TO OUR WORKSPACE First thing we want to do is add the “Update Compliance” offering to our OMS Service. We can add this from the “Solutions Gallery which is on the left.   1.       Click on the Solutions Gallery Icon  updatecomplianceimage15  2.       You’ll see a lot of OMS Offerings, the one where looking for is on the right and is called “Update Compliance”. When you find it click on it  updatecomplianceimage16  3.       It’ll take you to the Update Compliance details page. Click on Add [It took a while to complete] updatecomplianceimage17   4.       You’ll be taken back to the home page, and you’ll see the “Update Compliance” pane show up on the dashboard  updatecomplianceimage18  You’ve now successfully added the Update Compliance solution to your workspace. To enroll devices you need a subscription ID which is a unique number that data from the machines you enroll need to upload data to your tenant.   We’ll do that next.   Generating Subscription ID 1.       From the Dashboard click on settings  updatecomplianceimage19   It will take you to the Setting Page   2.       Click on “Connected Sources” and in the next pane click on “Windows Telemetry”  updatecomplianceimage20   You should see a “Commercial ID Key” and you want to take note of where it is. This is the commercial ID we will point the data we upload to.   We now have our workspace setup but still no data. We need to download the Upgrade Compliance deployment script We need to configure Windows 10 machines to upload telemetry to our workspace There are two ways to get data into the Workspace:
  1. Use Group Policy to input the commercial ID’s on Windows 10 machines
  2. Use Windows upgrade Deployment Script located here to input the commercial ID. I’ve written a blog about “Upgrade Readiness” which uses the same script and does something similar. The section on “DOWNLOAD AND CUSTOMIZE UPGRADE COMPLIANCE DEPLOYMENT SCRIPT” explains how to use the script if that’s something you want to do. You can find the blog here https://blogs.msdn.microsoft.com/okemokoloebube/2016/09/28/windows-upgrade-analytics/
  USE GROUP POLICY This is the “easier” option as it requires inserting your commercial ID in a group policy and then pushing it out. The Group Policy is located here Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds updatecomplianceimage29   You type in the Commercial ID and you hit OK and then hit apply and you have enrolled that machine to upload data into your workspace.   It takes approximately 48 hours but if your script runs successfully your data should eventually show up in the OMS portal At some point you should see something similar to this [depending on how many machines you enrolled] show up on the Update Compliance tile in OMS. Click on it and get access to all the information brought to you by Update Compliance.    updatecomplianceimage27   Further Reading:  Get Started with Update Compliance https://docs.microsoft.com/en-us/windows/deployment/update/update-compliance-get-started   Use Update Compliance to monitor Windows Updates https://docs.microsoft.com/en-us/windows/deployment/update/update-compliance-using    updatecomplianceimage28  ]]> Are you ready for "Readyforwindows"? https://docs.microsoft.com/archive/blogs/okemokoloebube/readyforwindows Tue, 28 Mar 2017 14:29:12 GMT https://blogs.msdn.microsoft.com/okemokoloebube/?p=366 Hello There! My name is Okem and I'm a Windows Technical Resource at Microsoft. In this post I intend to show you a cool new website that can help you with your Windows 10 deployments.
Here are some deployment questions I'm hoping we can answer indirectly as I talk about this relatively new offering:
    1. How do I know what applications are ready for Windows 10?
    2. Is there an easy way to get a picture of what applications are certified for Windows 10 without going to each vendor?
    3. How do I know what version of this application is being used on Windows 10?
    4. What kind of applications are others installing?
    Allow me introduce you to readyforwindows.com This is a site set up to allow any user check and see the adoption and possibly support status for a given application. If you are an ISV then you can also declare your support for Windows 10 on this site. All you need to do is search for the name of the software vendor or the software and the site will provide you what it based on the information you enter
      readyforwindowshomepage
      readyforwindowssearch You can then click on the results and get more information. Microsoft is all about options so we give you the option of searching by the application name or the ISV or Software Providers name. Before we dive into the results let's back up and understand the data we are looking at. We'll try to answer the following questions
      1. Where does Microsoft get all this data?
      2. What is the adoption status?
      3. What does supported on Windows 10 mean?
         
      Where does Microsoft get all this data? As millions of people to Windows 10 both in the consumer space and the enterprise space we collected telemetry [if it's turned on] and are able to get insight into what applications are running. As the data gets uploaded we use machine learning in Azure to pull out insights and Information which we then present to you in a readable format.
           
        What is the adoption status? The Adoption Status is based on information from commercial devices that share data with Microsoft and does not include data from consumer devices or devices that do not share data so the status may not be representative of the adoption rate across all Windows 10 devices. This allows us give you information when you look at that app to let you know the app is being used widely or not. We also tell you the build of Windows 10 we see the software running on. The different entries you can see for the Adoption Status are as follows:
        Insufficient Data means too few commercial Windows 10 devices are sharing information for this solution for Microsoft to categorize its adoption. Adopted means the solution has been installed on at least 10,000 commercial Windows 10 devices. Highly Adopted means the solution has been installed on at least 100,000 commercial Windows 10 devices. Contact Developer means there may be compatibility issues with this solution, and thus Microsoft recommends contacting the software provider to learn more.
           
        What does "Supported on Windows 10" Mean? This means that the software vendor [ISV] has certified that it's software is Windows 10 ready. In my example I'll use Microsoft owned software so as to not get into any legal issues. Microsoft is not an ISV so it doesn't need to provide a support statement to itself however for illustration purposes we'll treat it like one. If that's the case then not only will we give you the adoption status but we'll also give it a nice green checkmark stating that it's certified for Windows 10. For this to happen the ISV has to create a listing in the Ready for Windows directory, and provide a link to a public support statement on their website declaring
        (a) support for at least one of the following servicing branches of Windows 10: Current Branch, Current Branch for Business and/or a Long-Term Servicing branch, (b) that your product works with 32-bit and/or 64-bit Windows 10, Internet Explorer 11, or Microsoft Edge.
              Here's a cheap plug:
              If everyone turns off Windows Telemetry we don't have this information. The information we have is only as good as the information we get from the field. More telemetry = more data! If you have further questions you can see the readyforwindows FAQ page
                  Now let's look at one entry and I'll put on my Deployment Admin hat and walk through what I can extract from the information provided. This is based on my understanding of the data and should be used as a guideline. I've chosen System Center as the software to evaluate and since it's owned by Microsoft there is no ISV support statement. For the purposes of our example I have added the "Supported on Windows 10" sticker which you'll see on third party software that's been certified for Win 10 by the vendor.systemcenterimage2
                Here's how I would look at this if I was an Admin reviewing this information:
                1. System is supported on Windows 10 which means it has vendor support which is highly important in case we run into any issues.
                2. It has some versions that are highly adopted which means it's been put through a lot of use cases and hopefully a lot of issues have been worked out by the vendor
                3. The latest version is not highly adopted which could be because it's new to the market and still being deployed but it's adopted and that’s fine with me
                4. Vendor Support trumps the "Highly Adopted" status in my book.
                  Here's another example of another product which is adopted. Since it's a Microsoft Product I know it's vendor supported but we'll treat it like it's not for our example microsoftwordmui With my Admin hat this is what this will mean to me:
                1. The ISV hasn't provided official documentation to say this is supported. It doesn't mean it is not supported, it just means they haven't provided that information to the ready for windows site. Follow Up - Reach out to ISV to see if they officially support this on Windows 10
                2. The latest version is highly adopted on Windows 10 which means there are enough users out there. This could mean that the software works and it might even work great since it's being used by a lot of users. For me as an Admin I'll flag this one as needing further investigation. Follow Up - Need to look online for known issues. Follow Up - Reach out to ISV to see if they officially support this on Windows 10
                3. Lack of an official statement saying software is supported is concerning and needs to be investigated Follow Up - Reach out to ISV to see if they officially support this on Windows 10
                I hope you see how Ready For Windows can serve as a resource to plan moving from Windows 7 to Windows 10. The "Adoption Status" should be seen as a good place to start gathering information about an application as it relates to Windows 10. It doesn't eliminate the need for testing or even a proof of concept but it gets you off the blocks and in some cases provides information to help you know what to look into. Remember that the Adoption Status is based on information from commercial devices that share data with Microsoft and does not include data from consumer devices or devices that do not share data so the status may not be representative of the adoption rate across all Windows 10 devices. Keep in mind that just because an application is not adopted does not mean it is not supported. The Application Vendor makes the final call on what is supported and what is not. The same applies for the reverse – just because an application is highly adopted doesn’t mean it is officially supported. Some of the Win32 API’s from Windows 7 are also present on Windows 10 so applications might work without being officially supported. For a more centralized tool that allows you get even deeper into planning for your Windows 10 deployment look into Upgrade Analytics. Upgrade Analytics analyzes system, application, and driver data to help organizations determine when computers are upgrade-ready.   Upgrade Analytics Information Official Site https://www.microsoft.com/en-us/WindowsForBusiness/windows-analytics Setup Upgrade Analytics https://blogs.msdn.microsoft.com/okemokoloebube/2016/09/28/windows-upgrade-analytics/
                  Hope that helps and happy deployment!
                ]]>                                 Windows Upgrade Analytics https://docs.microsoft.com/archive/blogs/okemokoloebube/windows-upgrade-analytics Wed, 28 Sep 2016 22:33:44 GMT https://blogs.msdn.microsoft.com/okemokoloebube/?p=105     The analysis of the data is done in the Microsoft cloud which is called Azure as most of you know so you’ll need an Azure Tenant to do this. The service offering in Azure that does the actual analysis is called OMS which stands for operations management suite. Before you get concerned about costs this is a free offering which you don’t have to pay for right now.   Here’s what you need for this process:  
                1. A Microsoft account to access the Microsoft cloud [Azure] - Free
                2. An Azure subscription tied to the Microsoft account – You can sign up for a Free Trial here. Keep in mind they require a credit card during the free trial sign up process to verify your identity but you don’t get charged unless you switch to a paid subscription.
                3. Operations Management Suite or OMS – You get the choice of adding one to your azure tenant for free
                    I walk you through creating number 1 and number 3 which can be done for free. Number 2 is also free but requires that you sign up for Azure which requires a credit card which won’t be charged and a phone number.       To sign up for Windows Upgrade Analytics navigate to this site https://www.microsoft.com/en-us/WindowsForBusiness/upgrade-analytics There’s a banner at the top that should say, “Sign up Now” and then there is the “Sign in” option in the top far right hand corner   The next step depends on what kind of relationship you currently have with Microsoft/Azure. The instructions I give assume scenario 1. If you don’t fall into that scenario skip to the part which is relevant to you in the instructions.  
                1. I have no Microsoft or Azure AD Account and I’m not sure what that is:
                Click Sign in and then click “Create an account” below to create a new Microsoft account. Log in with the newly created Microsoft account and click on “Sign up Now” and then fill out the “Create a new Workspace” form.  
                1. I have a Microsoft Account or Azure AD account but I have no Azure Tenant:
                Log in with the Microsoft account and click on “Sign up Now” and then fill out the “Create a new Workspace” form.  
                1. I have an Azure AD Tenant I’m willing to use with no OMS Service running:
                Click Sign up and log in with your Azure AD credentials you want to use. Use your current Tenant and create a new OMS workspace  
                1. I have an Azure AD Tenant with OMS running:
                Click sign up and Log in with your Azure AD credentials. Choose your OMS service and follow the instructions below to activate Windows Upgrade Analytics.     SCENARIO ONE:   Click on “Sign In” and then click on “create One” to start the account creation process. SignInIcon SignIn   CreateAnAccount   After I create the account I am now taken back to the page and I’m logged in as the Microsoft user I created. If that doesn’t happen for you simply go back to the page and click on “Sign In” and sign in with your newly created Microsoft Account. ContactMe   Now I click on “Sign Up Now” and it brings me to this page where I sign in with the new account I just created OMSWorkorSchoolSignIn The first sign in was to sign in with a Microsoft or Azure AD account which means were a user in the online world of Microsoft. This last sign in is to sign OMS in Azure and create a workspace. OMSSignUpPage Fill out the information and then Click Create If your Microsoft Account doesn't have an Azure Subscription associated with it [if you just created a new one, it doesn't] then you'll have to create an Azure Subscription to link to your Microsoft Account.   This is the screen you’ll see LinkAzureSubcription   You need to click on “Create New” to create an Azure subscription which like I explained earlier has free trials. Make sure the Microsoft account you are using for OMS is the account you use when creating your azure tenant. I won’t go into creating an Azure tenant as the instructions are straight forward.   After you do that you can come back to this screen and continue.   SCENARIO 3 and 4:   Here you either create a new Azure Tenant/Subscription or you use one you already have. You can choose an Azure directory and then choose a subscription if you have multiple subscriptions. SelectAzureDirectory In my case I didn't have an azure OMS account so I had to create one. If you already have an Azure Tenant, then you don't need to create another one but You'll need to create an OMS workspace. If you have OMS, then your OMS workspace will be listed there and you can simply use that one or you can choose or create a new one. After accepting agreements, you then get into the Microsoft Operations Management Suite OMSSuite At this point you have an OMS Portal but you don't have it set up to collect any kind of data. We need to go tell it what kind of data to collect Click on Settings in the left bottom OverviewSettingsInstalledSolutions You should see Upgrade Analytics on the right side of your screen which tells you that you have an upgrade Analytics Preview license.   Click on "Connected Sources" OMSWorkspaceSettingsPage Then click on "Windows Telemetry" and click on subscribe in the bottom right corner Subscribe You should now be set up with a Commercial ID which is unique to your OMS workspace. This unique ID can be added to a Windows 7 or Windows 8.1 client machine and it allows them to direct the data they are uploading to the appropriate workspace. You should copy this key and keep it in a safe place.   I walk through details of setting up a Windows 8.1 machine to upload data below but if you want the full breakdown you can find it in this TechNet article   Setting up a Windows 8.1 Client Machine to upload data to the Workspace: I did mine on a Windows 8.1 machine and I'm working to do one on a Windows 7 machine but the general principles are the same which you can see below. For Windows 8.1 you must install KB 2976978 to get it to work correctly. After I installed it I downloaded the Update Script from here https://www.microsoft.com/en-us/download/details.aspx?id=53327   The update script allows you to configure a machine to upload data and set the unique commercial ID of the OMS workspace you want to upload the data to. Below are instructions for how to use the script:   DOWNLOAD AND CUSTOMIZE UPGRADE COMPLIANCE DEPLOYMENT SCRIPT You can get the script from here https://www.microsoft.com/en-us/download/details.aspx?id=53327 You need to customize the scripts to work with your environment. You have to input your Commercial ID in the script to make it upload data to your environment. If you want insight into what the script does I’ve put the explanation below The Upgrade Analytics deployment script does the following:
                1. Sets commercial ID key + CommercialDataOptIn + RequestAllAppraiserVersions keys.
                2. Verifies that user computers can send data to Microsoft.
                3. Checks whether the computer has a pending restart.
                4. Verifies that the latest version of KB package 10.0.x is installed (requires 10.0.14348 or subsequent releases).
                5. If enabled, turns on verbose mode for troubleshooting.
                6. Initiates the collection of the telemetry data that Microsoft needs to assess your organization’s upgrade readiness.
                7. If enabled, displays the script’s progress in a cmd window, providing you immediate visibility into issues (success or fail for each step) and/or writes to log file.
                To get the run the Upgrade Analytics deployment script ready to run in your environment:
                • Download the Upgrade Analytics deployment script and extract UpgradeAnalytics.zip. The files in the Diagnostics folder are necessary only if you plan to run the script in troubleshooting mode.
                • Edit the following parameters in RunConfig.bat:
                1. Provide a storage location for log information. Example: %SystemDrive%\UADiagnostics
                2. You can store log information on a remote file share or a local directory. If the script is blocked from creating the log file for the given path, it creates the log files in the drive with the Windows directory. Input your commercial ID key.
                3. By default, the script sends log information to both the console and the log file. To change the default behavior, use one of the following options: logMode = 0 log to console only logMode = 1 log to file and console logMode = 2 log to file only
                • For troubleshooting, set isVerboseLogging to $true to generate log information that can help with diagnosing issues. By default, isVerboseLogging is set to $false. Ensure the Diagnostics folder is installed in the same directory as the script to use this mode.
                • Notify users if they need to restart their computers. By default, this is set to off.
                • After you finish editing the parameters in RunConfig.bat, you are ready to run the script. Take note for production environments it needs to run in the SYSTEM context.
                See below for changes I made to my own script: upgradereadinessscriptshot   I basically set up my script to collect data and create a log just in case there are any failures. I also allow it log sites my users visit since so I can start to build a list of internal sites my users visit and make sure they are compatible with Windows 10. I set up my script to log all sites visited including external sites but you can set yours up to log only internal sites. You need to run the production script under the SYSTEM Account. There are many ways to do this but I personally chose to use Task Scheduler. Use what works for you but with task scheduler I can export a task and push it to multiple users. Here’s a general summary of what I did Created a task in task scheduler Configured it to run under the System Account Configured it to “Run with the Highest Privileges” Configured it to be a Windows 7 task Configured it to run every day at 2pm Pointed it to the script location Everyone does thing differently but below are screenshots of the changes I made to my task. The most important thing you need to do is make sure you set the task to run in the SYSTEM account and make sure it runs with the highest privileges. Breakdown: Create a task by going to “Task Scheduler” and click on Create a task which is on the right. Call it what you want and make sure, you change the “When running the task, use the following account” to “SYSTEM” You need to change the Account that the task will run under to the System Account Select “Run with the Highest Privileges” Click on “Change User or Group” Click on Advanced Click on Find Now Configure For: Windows 10 updatecomplianceimage30   Set a Trigger: I set mine to run daily at 2pm, it’s up to you to choose what cadence you want. The product group says that is no longer necessary to run the script every day to upload data as the telemetry service is now smart enough to send regular telemetry on any changes. upgradereadinesstask2   Under Actions leave it on “Start a Program” and navigate to the script using browse. Keep in mind it should be in a location every machine can reach so you might want to put it on a network share updatecomplianceimage25   upgradereadinesstask3       If you want to run this on laptops, then pay attention to the conditions tab. You might not want it to run on AC power. upgradereadinesstask4   Settings Tab: The big thing I did here was to allow the task to be run on demand, so I can test it to make sure it works upgradereadinesstask5 Since I chose to log data I can check the logs to see if the task runs when it should. What you want to see is “Script Finished Successfully”. If you see anything else, then your script failed to complete updatecomplianceimage26 It takes approximately 48 hours but if your script runs successfully your data should eventually show up in the OMS portal It takes about 24 - 48 hours for the data to show up in the portal but eventually I see this OMSSuite I can now go in and look at the data collected on that machine and review it by simply clicking on the "Upgrade Analytics preview" tile PrepareYourEnvironment I can click on the different options and I clicked on "Not Reviewed" and then I can export it using the export option LogSearch By default it exports it into an excel spreadsheet SaveExport Exported Excel Sheet ExcelSpreadsheet There’s a lot you can do with the tool which I haven’t covered but I hope you get an idea of how it works. If you are into OMS you can use the data collected just like you can use data from other sources and build reports.   I didn’t cover windows 10 in this talk but it can also collect data from windows 10. The big thing to note is that you must have Telemetry turned on to at least collect basic information from your machine using the policy under Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds. You can read more about that here   Further Reading: Upgrade Analytics Architecture https://technet.microsoft.com/itpro/windows/deploy/upgrade-analytics-architecture TelemetryArchitechure   Upgrade Analytics requirements https://technet.microsoft.com/itpro/windows/deploy/upgrade-analytics-requirements#important-information-about-this-release  ]]>                                 Windows 10 Retail Demo Mode https://docs.microsoft.com/archive/blogs/okemokoloebube/windows10retaildemo Tue, 26 Jul 2016 01:00:52 GMT https://blogs.msdn.microsoft.com/okemokoloebube/?p=1   It has a warning you should read by the way as someone really smart took their time to write it.   If you click the change option be aware of 2 things  
                1. All your personal data on the machine is about to be deleted forever. Yes, including your post it notes and your wallpaper.
                2. You need to be connected to the internet for this to work.
                  Free tip: This doesn't work if your machine is domain joined or joined to Intune. If you click on the word Windows 5 times and you don't get the prompt, then you need to leave the domain you are connected to or disconnect from the mobile device management service your machine is joined to Issues you can run into: CantChangeToRetailDemo This means you don't have internet connection. We need an internet connection to make this happen because some of the demo content is downloaded from the internet. After you fix that it go back to Start\Settings\Update & Security\Activation and click on Windows 5 times. When you get the "Change to Retail Demo Mode" Prompt click on change and it should now take you to this screen. When you see this screen leave the boxes blank and click on "Finish" Getthelatestdemocontent   Your machine should then reboot and when it comes back on it will have a demo account. I went into Start\Settings\Accounts and my demo user is called "Darrin DeYoung" SomeSettings And that is how you go into Retail Demo Mode. Don't get any ideas and do it on a friend’s computer when they beat you in Call of Duty by the way   Okem Okolo-Ebube  ]]>