Windows 10 build 10240 has released to the Fast Ring… Release To Manufacturing (RTM) build???

Windows 10 build 10240 has been released to the Fast Ring. That’s what I’m running on my laptop now. There were heavy rumors yesterday that this is the to Release To Manufacturing (RTM) build and is the one to be publically available on July 29th. But there is no hard confirmation on this by Microsoft yet Build 10240 now available for Windows Insiders in Fast and Slow rings.

“Over the past few days we’ve been preparing our release pipelines and processes, and this build is one step closer to what customers will start to receive on 7/29 …

On Monday we announced that builds from here on will only be available through Windows Update, so to get this one you can either wait and it will be installed automatically.”

Here’s how you prepare to roll it out in your company.

In a previous blog post I wrote about the update you needed for your KMS server to be able to activate Windows 10 clients. Read about that in KB3058168: Update that enables Windows 8.1 and Windows 8 KMS hosts to activate a later version of Windows

Meanwhile Microsoft has also published the Windows 10 client KMS activation which keys can be found here Appendix A: KMS Client Setup Keys

Windows 10

Operating system edition
KMS Client Setup Key

Windows 10 Professional: W269N-WFGWX-YVC9B-4J6C9-T83GX
Windows 10 Professional N: MH37W-N47XK-V7XM9-C7227-GCQG9
Windows 10 Enterprise: N: NPPR9-FWDCX-D2C8J-H872K-2YT43
Windows 10 Enterprise N: DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4
Windows 10 Education: NW6C2-QMPVW-D7KKK-3GKT6-VCFB2
Windows 10 Education N: 2WH4N-8QGBV-H22JP-CT43Q-MDWW
Windows 10 Enterprise 2015 LTSB: WNMTR-4C88C-JK8YV-HQ7T2-76DF9
Windows 10 Enterprise 2015 LTSB N: 2F77B-TNFGY-69QQF-B8YKP-D69TJ

Do note this is the key you use when you activate the Windows 10 Client against a KMS server. It is not the KMS license server key. That one you’ll need to obtain from your valid Microsoft licenses.

new CMDlet parameters missing in Exchange 2013 CU9 KB3075700

When you upgrade your Exchange 2013 server to CU9 some command are missing.

These you need wen you want more control over Sent Items when using shared mailboxes.

Whether a mailbox is used by multiple users as a communication tool, a shared mailbox remains an important business requirement.
Early releases from Exchange 2013 there was a no way to configure this behavior.

In Office 365 and Exchange 2013 CU9, this feature on shared mailboxes is disabled by default.

If you mis it run:
setup.exe /preparead /iacceptexchangeserverlicenseterms

Get-Mailbox -RecipientTypeDetails Shared | Set-Mailbox -MessageCopyForSentAsEnabled $True
Get-Mailbox -RecipientTypeDetails Shared | Set-Mailbox -MessageCopyForSendOnBehalfEnabled $True

https://support2.microsoft.com/kb/3075700/

Update that enables Windows 8.1, Windows Server 2012 R2, Windows 8, and Windows Server 2012 Key Management Service (KMS) hosts to activate a later version of Windows.

Windows 10 will be available on July 29th 2015. Microsoft has prepared for this by already making an Update(KB3058168) that enables Windows 8.1, Windows Server 2012 R2, Windows 8, and Windows Server 2012 Key Management Service (KMS) hosts to activate a “later version of Windows”. This must means Windows 10. I do not know if this means that is even for Windows Server 2016. Windows 10 will be activated by a KMS server running this update but it might.

Select the version you need for the KMS server or servers you use and install them.

image

Cumulative Update 9 for Exchange Server 2013

Exchange Team released Cumulative Update 9 for Exchange Server 2013

Fixes:

Rollup 10 for Exchange Server 2010 Service Pack 3

Exchange Team released Rollup 10 for Exchange Server 2010 Service Pack 3

Fixes:

KB 3069055 Various DAG maintenance scripts do not work in an Exchange Server 2010 environment
KB 3057422 “MapiExceptionNoAccess: Unable to query table rows” error and some mailboxes cannot be moved
KB 3056750 Exchange ActiveSync application pool crashes in an Exchange Server 2010 environment
KB 3054644 “The item no longer exists” error when you access an archive mailbox in Outlook Web App in Exchange Server 2010
KB 3051284 Event ID 4999 is logged and MSExchangeServicesAppPool crashes in an Exchange Server 2010 environment
KB 3049596 Event ID 4999 is logged and remote procedure call Client Access service crashes in an Exchange Server 2010 environment
KB 2964344 MSExchangeRPC service stops working intermittently in Exchange Server 2010

Download

Update Rollup 17 for Exchange Server 2007 Service Pack 3

Microsoft released Rollup 17 for Exchange 2007 SP3

Fixes:

KB 3057222 “InvaIidOperationException” error and cannot open digitally signed or NDR messages in FIPS-enabled Exchange Server 2007

Download

Outlook 2007 and Exchange 2013 not a real good combination

Exchange 2013 and Outlook 2007 is a interrested thing

Outlook 2007 SP3 is supported with with April 2014 Public Update KB 2863811
See https://technet.microsoft.com/library/dn803988(v=office.14).aspx

For you as a System or Exchange administrator or Consultant you might consider some things before migrating to Exchange 2013.

You can’t share your calendar in Outlook 2007
When you use Microsoft Office Outlook 2007 to share your calendar, you receive the following error message:

Error while preparing to send sharing message.

Also, if you try to check the permissions on the calendar, you may receive the following error message:

An error occurred when setting schedule permissions.

Solotion Microsoft: Using OWA

It works for share the calendar and you can set editor calendar permissies. All other permissions are not availible

image

  • Accessrights Missing
    None
    Owner
    PublishingEditor
    PublishingAuthor
    Author
    NonEditingAuthor
    Reviewer
    Contributor

    With Powershell you can set the permissions

Add-MailboxFolderPermission –identity (username+’:\calendar’) –user testuser –Accessrights PublishingEditor

Better solution

Upgrade your Outlook Client to 2010 or 2013

Free ebook “Introducing Windows 10 for IT Professionals, Preview Edition”

Microsoft has released a free ebook of “Introducing Windows 10 for IT Professionals, Preview Edition”. You can download the ebook here. Special thanks to Mark Swinkels

2015-06-02_16h08_34-244x300

How to add a driver to the DriverStore

All drivers are stored in the so called DriverStore, which is located under %SYSTEMDRIVE%\Windows\System32\DriverStore.

With the built-in command line tool pnputil you can add or remove drivers.

How does it work?

  1. Start an elevated command prompt (Start, type CMD, hit Ctrl+Shift+Enter)
  2. Adding a driver:
    • Pnputil.exe -a c:\LOCATION_OF_DRIVER\DRIVER_NAME.inf
      The location can be either local or remote
    • Pnputil.exe -a C:\LOCATION_OF_DRIVER\*.inf
      Copy all drivers from that folder
  3. Deleting a driver:
    • Pnputil.exe -d DRIVER_NAME.inf

Configure your Exchange 2013 server with Configure-Echange2013.ps1 Updated to V3.0

Updated to V3.0

Change List:

# V1.0 Begin
# V1.1 Added Some New Options 12-10-2014
# V1.2 Added Hyper-V Best Practise & NTFS Partition Offset
# V1.3 Added KB2995145 .NET Framework 4.5 garbage collector heap Fix
# V1.4 Added Set Minimum Disk Space Warning level (180GB Default CU6 200GB CU5)
# V1.5 Added Some new features
# V1.6 Changed the Layout & Add Move Arbitration Mailbox
# V1.7 Added PST Export & KB2990117
# V1.8 Added Full backup, Database in GB and Mailbox Size in GB Export CSV
# V1.9 Added Outlook AnyWhere & SafetyNetHoldTime
# V2.0 Added Check DatacenterActivationMode, Get-DatabaseAvailabilityGroupNetwork, Add Static Route, Disable Replation Network on DAG, Database Copies Per Volume (AutoReseed)
# V2.1 Added Edge Subscription
# V2.2 Added Check Transaction Log Growth
# V2.3 Changed the Menu to Submenu’s
# V2.4 Added Check Database White Space
# V2.5 Added MAPI HTTP External URL
# V2.6 Fixed OWA Virtual URL & HTTP URL
# V2.7 Added Fixes & Mountpoints & Changed Set Minimum Disk Space Warning Level from REG to GlobalOverride
# V2.8 Maintaince Added
# V2.9 Set Power to Highperformance
# V3.0 Check of Microsoft.Exchange.Management.PowerShell.SnapIn is loaded

Download: https://gallery.technet.microsoft.com/scriptcenter/Configure-Exchange-2013-e0ffb2a6

Translate »