Test Layout

I'm doing some experimentation with Windows 10 deployment and attempted to run Sysprep. When I ran it, I got the following error: Sysprep was not able to validate your Windows installation. Review the log file at %WINDIR%\System32\Sysprep\Panther\setupact.log for details. After resolving the issue, use Sysprep to validate your installation again. When I read the log file, I found this: Package 9E2F88E3.Twitter_4.3.3.0_x86__wgeqdkkx372wm was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image. So, apparently the Twitter app that is included by default is causing my issue. I did some research and found references to other packages causing the same issue if Windows 10 communicates with the Internet. The VM I'm using does have Internet connectivity. To remove the app, I ran the following command. Note that you can use wildcards in PackageName for Get-AppxPackage, such as *twitter*. Get-AppxPackage PackageName | Rem

This is a unique scenario, because it applies primarily to testing environments. I have a lab setup with Exchange Server 2016 and Outlook 2016. I was going a bit nuts because each time Outlook 2016 tried to configure the profile I got the following error message: The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action. This error can occur when you get names wrong in your internal or external URLs. So, I verified the names in all of my internal and external URLs. I also tested connectivity in Outlook and the URLs from Autodiscover were correct. Also verified the names in the certificate. It turned out to be an issue with the default gateway. As part the connection process, Outlook 2016 was attempting to connect with the default gateway (which didn't exist on my test network). When connectivity to the default gateway failed, Outlook provided that error. To fix this, I pointed the client running Outlook 2016 at a valid IP for t

As part of developing the new Microsoft Exchange Server 2016 course, I needed to get Office Online Server Preview (formerly Office Web Apps Server) working with Exchange Server 2016. If you read the instructions it's pretty straight forward. There isn't much to do other than run setup and run a single command to create a farm. Instructions are here: https://technet.microsoft.com/en-us/library/jj219455%28v=office.16%29.aspx The command to create the farm for Office Online Server is: New-OfficeWebAppsFarm -InternalURL https://office.adatum.com -ExternalURL https://office.adatum.com -Certificate OOSCertificate -EditingEnabled After creating the farm, you need to set Exchange 2016 to use it with the following command: Set-OrganizationConfig -WacDiscoveryEndPoint https://office.adatum.com/hosting/discovery After running the command in Exchange 2016, you need to restart the MSExchangeOwaAppPool. Or If you're lazy, just do an IISreset. After this, I was able to send a Word documen