Windows 10 Mobile
Windows 10 Desktop
How to use these packages:
There are two different versions of the Office Deployment Tool available – one for Office 2013 and a different one for Office 2016. Each Office Deployment Tool works only with that specific version of Office. You can download them from the Microsoft Download Center by using the following links:
Configuration.xml
<Configuration>
<Add SourcePath=”d:\2016\” OfficeClientEdition=”32″ Branch=”Current”>
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
<Language ID=”nl-nl” />
</Product>
<Product ID=”VisioProRetail”>
<Language ID=”en-us” />
<Language ID=”nl-nl” />
</Product>
</Add>
<!– <Updates Enabled=”TRUE” Branch=”Current” /> –>
<Display Level=”Full” AcceptEULA=”TRUE” />
<Logging Name=”OfficeSetup.txt” Path=”%temp%” />
<Property Name=”AUTOACTIVATE” Value=”1″ />
</Configuration>
Download
D:\2016\setup.exe /download d:\2016\configuration.xml
Install / Configure Office 365 (2016)
D:\2016\setup.exe /configure d:\2016\configuration.xml
Source: https://technet.microsoft.com/en-us/library/jj219424.aspx
Today is the day. An independent group of volunteers within Microsoft has successfully open sourced and forked Windows Live Writer. The fork is called Open Live Writer (also known as OLW) and it is part of the .NET Foundationand managed by this group of volunteers. Read the fantastic announcement at the .NET Foundation Blog! Download Open Live Writer now!
Windows Live Writer 2012 was the last version Microsoft released and can still be downloaded from http://www.windowslivewriter.com. If you’re not comfortable using Open Source Software, I recommend you stick with classic WLW.
If you’re willing to put up with some bugs, then join us in this brave new world, you can download Open Live Writer from http://www.openlivewriter.org. We’re calling today’s release version 0.5.
Here’s some of the added features, the removed features, the stuff that doesn’t work, and our plans for the future:
Our roadmap for the future is published here on GitHub.
Lync Basic 2013 provides all the basic functionality that’s available in the full version of Lync (Lync 2013). However, if you want to use any of the following features, you will need to upgrade to Lync 2013:
Download Skype for Business Basic
Microsoft Skype for Business Basic (64 Bit)
http://www.microsoft.com/en-us/download/details.aspx?id=49440
Microsoft Skype for Business Basic (32 Bit)
http://www.microsoft.com/en-us/download/details.aspx?id=49439
Office Lens trims, enhances and makes pictures of whiteboards and docs readable, and saves them to OneNote. You can use Office Lens to convert images to PDF, Word and PowerPoint files too. Office Lens is like having a scanner in your pocket. Like magic, it will digitalize notes on whiteboards or blackboards. Always find important documents or business cards. Sketch your ideas and snap a picture for later. Don’t lose receipts or stray sticky notes again!
What’s new:
– Now you can convert your pictures to PDF files with selectable text, in addition to Word and PowerPoint files, and save them to OneDrive.
Scenarios:
– Capture and crop a picture of a whiteboard or blackboard and share your meeting notes with co-workers.
– Make digital copies of your printed documents, business cards or posters and trim them precisely.
– Printed text will be automatically recognized (using OCR) so you can search for words in images and copy and edit them.
Features:
– With Whiteboard mode, Office Lens trims and cleans up glare and shadows.
– With Document mode, Office Lens trims and colors images perfectly.
– Pictures are saved to your camera roll and also directly into OneNote, so you can see the images across all your devices.
– Choose to convert images to PDF (.pdf), Word (.docx), or PowerPoint (.pptx) files that are automatically saved to OneDrive.
Note: Office Lens requires logging in with your Microsoft Account. Your Microsoft Account must be same as the one registered on your device.
Microsoft released a security update for Exchange 2013 to fix a new vulnerability. MS15-064 has a severity rating of ‘Important’.
Download the update for Exchange 2013 CU8 and Exchange 2013 SP1. More information:Vulnerabilities in Microsoft Exchange Server Could Allow Elevation of Privilege (3062157)
Move Public Folder script from 2007/2010 to Office 365 Script created by Ward Vissers
www.wardvissers.nl
THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK
OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER
Please Select the Choice You Want
Prepare for Migration (Legacy Exchange Server
00) Add the Office 365 Domain Name
01) Take a snapshot of the original source folder structure
02) Take a snapshot of public folder statistics such as item count, size, and owner.
03) Take a snapshot of the permissions
04) Locate public folders that have a backslash in the name
05) Rename Public Folder
06) Checks the public folder migration status.
07) Set PublicFolderMigrationComplete to False
Check Office 365
08) Get-PublicFolderMigrationRequest
09) Get-Mailbox -PublicFolder
10) Get-PublicFolder
Generate CSV Files and create Public Folder Mailboxes (Legacy Exchange Server)
11) Export-PublicFolderStatistics PFSizeMap.csv
12) PublicFolderToMailboxMapGenerator PFMailboxMap.csv
Create the public folder mailboxes on Exchange Online
13) Master Public Folder Name
14) Create Public Folder Mailboxen (Check PFMailboxMap.csv)
Migrating the Public Folders
15) Export mail-enabled public folders from Active Directory
16) LegacyExchangeDN Administrator
17) LegacyExchangeDN Public Folder Server
18) External Name Outlook Anywhere
19) Set the XML file
20) Give the CSV file to start the Migration
21) Public Folder Migration Status
Lock down the public folders on the legacy Exchange server for final migration (downtime required)
22) Lock the legacy public folders for finalization
Finalize the public folder migration (downtime required)
23) Finalize the public folder migration (downtime required)
Test and unlock the public folder migration
24) Add Public Folder to Test User
25) Unlock the public folders for all other users
26) Public Folder Migration Complete (Legacy Exchange Server)
27) Public Folders Enabled Local
Final Check
28) Take a snapshot of the original source folder structure.
29) Take a snapshot of the public folder statistics such as item count, size, and owner
30) Take a snapshot of the permissions
99) Exit 
Download: https://gallery.technet.microsoft.com/scriptcenter/Public-Folder-Migratie-to-25bd50a0
With ThinApp 5.1 support for virtualizing Internet Explorer 11 was introduced.
1. Start your Windows 7 capture’n’build machine (Windows 7 SP1 with non Windows Updates)
2. Install Prerequisite updates for Internet Explorer 11
3. Download Download Internet Explorer 11 32-bit Installer English or Download Internet Explorer 11 64-bit Installer English
4. Start ThinApp Setup Capture
5. Do a prescan
6. Install Internet Explorer 11
7. Do a post scan
8. Build your project
9. Finish
KEMP gives away the LoadMaster for free. Now the virtual appliance is available in a free edition too. Available for all supported hypervisors (VMware, Hyper-V, enz).
The free VLM has some limitations, for instance the HA setup with an active and hot stand-by unit is not supported. Another important limitation is that the free LoadMaster doesn’t come with the awesome support paying customers receive. Also there are some bandwidth and SSL TPS limitations, all in all not much special for most home, lab, testing and other non-production deployments.
After a customer migrated to Exchange Online some time ago.
They wanted not a hybrid situation. but they are using still DirSync!
After reading: Decommissioning your Exchange 2010 servers in a Hybrid Deployment a I read its not a real problem.
Changed DirSync & After that Uninstalling Exchange 2013 was very easy.
I had only to disable the Arbitration mailboxes: I did that with the following powershell command:
Get-Mailbox -Arbitration | disable-Mailbox -arbitration -RemoveLastArbitrationMailboxAllowed
I did not publish this article because i has still some doubts!!
I had still a question: Do want to remove the last Exchange Server? Have you a supported Environment without a local Exchange Server and still using DirSync??
Yes & No!!
After reading Concerning Trends Discovered During Several Critical Escalations
Microsoft Says:
You may remove the last Exchange Server locale when you move totally to Office 365/Exchange Online, but change Exchange Attribuuts trough ADSI is not supported.
If you don’t have a third party tool for that. The only way is trough ADSI and that is not supported.
My Conclusion:
You have a support issue when you dropped a Call at Microsoft and they investigate your environment.
Don’t remove the last Exchange Server even when all mailboxen exist in Office 365/Exchange Online and keep them up to date!
You can always install a Exchange Server but most of the times it will be always to late!