Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

xExchAutoMountPoint storage configuration vs Exchange 2019 version of Exchange Server Role Requirements Calculator #413

Open
FunkyMonkey888 opened this issue Apr 1, 2019 · 1 comment
Open

xExchAutoMountPoint storage configuration vs Exchange 2019 version of Exchange Server Role Requirements Calculator #413

FunkyMonkey888 opened this issue Apr 1, 2019 · 1 comment
Labels
needs investigation The issue needs to be investigated by the maintainers or/and the community.

Comments

@FunkyMonkey888
Copy link

xExchange contains an example of xExchAutoMountPoint storage configuration using the Exchange Server Role Requirements Calculator. The Server.CSV embedded in that example is from version 7.6 of the Calculator. A new updated version of the Calculator for Exchange 2019 is expected to be released soon. Will an update of xExchange be coming to support the new Calculator version for Exchange 2019?
@FunkyMonkey888 FunkyMonkey888 reopened this Apr 1, 2019
@mhendric
Copy link
Contributor

mhendric commented Apr 1, 2019

Hi @FunkyMonkey888 , I've tested this with newer calculators (up to v9.1 I think), and I haven't noticed any Schema changes in the output .CSV files that would require us treating the output differently. Are you seeing something not work specifically?

@SteveL-MSFT SteveL-MSFT removed this from Backlog in powershell/dscresources Nov 27, 2019
@johlju johlju added the needs investigation The issue needs to be investigated by the maintainers or/and the community. label Oct 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs investigation The issue needs to be investigated by the maintainers or/and the community.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@johlju @mhendric @FunkyMonkey888