Now you have your PPKG in an ISO, attach it to your virtual machine. Your PPKG needs to be at the root of the file system and not in a subfolder. Then in the console pane I ran:ĭir 'C:\Users\Administrator\Documents\Windows Imaging and Configuration Designer (WICD)\Contoso_Tablets' *.ppkg | New-IsoFile -Path C:\ISOs\Contoso_Tablets_v1.ISOĭir being an alias for Get-ChildItem just lists all the files with the PPKG extension, we then pipe this list into the New-IsoFile function and specify the path of the output ISO (make sure the folder exists first!) To create the ISO with New-IsoFile, I pasted the New-IsoFile code into a PowerShell ISE Script Window and clicked Run (the play icon).
MS OFFICE TESTEN SOFTWARE
There's also various paid for and free third party software that you can use to create an ISO. In order to get my PPKG file into an ISO I have used a PowerShell Function from the TechNet Gallery called New-IsoFile. Here we can use our provisioning package!Īt this point, virtual machine extensions aren't running so we can't start an enhanced session in order to connect a USB device, so how can we get our provisioning package into our VM? Start the VM again and it will boot into OOBE only it will be different this time, the first screen will be the language selection screen. Once sysprep has completed and the VM has shut down, it's a good idea to take a checkpoint so you can re-use this VM as many times as you like for testing your provisioning packages. If you were going to duplicate this image to other machines then you would tick the generalize box, otherwise just change the Shutdown Option to "Shutdown" and click OK. Your VM will reboot and you'll automatically be logged on as "Administrator" and the sysprep (System Preparation Tool) will be running. The quickest way to do this from here is to hit CTRL+SHIFT+F3 to bypass the initial oobe screens and boot into Audit mode.
![ms office testen ms office testen](https://arme-schonen.com/cikl/RJcWMzIJN4Cb1QYMZhwNXAHaFB.jpg)
You need to sysprep the installation of windows just as if you were preparing a customised image. The provisioning pack we created won't work here - this isn't how you receive a device from the manufacturer.
![ms office testen ms office testen](https://www.heise.de/ct/imgs/04/2/7/2/3/6/0/3/FAQ_Office-Lizenzen-2071417447bf219a.jpeg)
This is the first screen of the out of box experience for a fresh installation of Windows 10.
![ms office testen ms office testen](https://www.oracle.com/webfolder/technetwork/tutorials/obe/cloud/bics/MigratingData/images/sampleapp.jpg)
You should stop your installation at this point.
MS OFFICE TESTEN HOW TO
The first thing to do is to install Windon a virtual machine and stop at the first OOBE screen I'm not going to go through all the steps to do this as there's plenty blog posts on how to do that but I've recorded the world's most boring GIF you can watch if you like. When you turn on your new tablets, they'll boot up into OOBE ("out-of-box experience") so this is the scenario we're going to look at testing (versus just double clicking on a ppkg in a running OS - you'd have to go through all the OOBE screens and create a user account to get to that stage which you just aren't going to do on 100 tablets.)
MS OFFICE TESTEN PRO
Now we want to test that in a VM before you go deploying it to all those shiny Surface Pro 4s you've got to get ready before the big technology demo event tomorrow. So in Part 1 we created a simple provisioning package. Hello again, is it really a week since I wrote Part 1 ? First published on TECHNET on Feb 20, 2017