You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am doing recovery test for backups of aad users (1000+ users). My envelopesize is already 128mb, but I am running into this error: MOF file size exceeded max size limit.
+ CategoryInfo : ResourceBusy: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : MI RESULT 27
+ PSComputerName : localhost
From some issues documented here it seems like it is proposed to break down the backups even more.
My question is, what are the actual limits for the mof files size?
Best
Microsoft 365 DSC Version
1.24.904.1
Which workloads are affected
Azure Active Directory (Entra ID)
The DSC configuration
@{
AllNodes=@(
@{
NodeName="localhost"PSDscAllowPlainTextPassword=$true;
PSDscAllowDomainUser=$true;
#region Parameters# Default Value Used to Ensure a Configuration Data File is GeneratedServerNumber="0"
}
)
NonNodeData=@(
@{
# Tenant's default verified domain nameOrganizationName="xyz.onmicrosoft.com"# Azure AD Application Id for AuthenticationApplicationId="xyz"# The Id or Name of the tenant to authenticate againstTenantId="xyz.onmicrosoft.com"# Thumbprint of the certificate to use for authenticationCertificateThumbprint="xyz"
}
)
}
Verbose logs showing the problem
AUSFÜHRLICH: Vorgang "CIM-Methode aufrufen" mit den folgenden Parametern durchführen,"'methodName' =SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' =root/Microsoft/Windows/DesiredStateConfiguration".
AUSFÜHRLICH: An LCM method call arrived from computer vm-colli-0 with user sid
S-1-12-1-1239345608-1301440490-3343379598-3488004834.
AUSFÜHRLICH: [vm-colli-0]: LCM: [ StartSet ]
AUSFÜHRLICH: [vm-colli-0]: LCM: [ EndSet ]
MOF file size exceeded max size limit.
+ CategoryInfo : ResourceBusy: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : MI RESULT 27+ PSComputerName : localhostAUSFÜHRLICH: Vorgang "CIM-Methode aufrufen" wurde abgeschlossen.
AUSFÜHRLICH: Die Ausführung des Konfigurationsauftrags hat 73.426 Sekunden gedauert.
@Thomas-Methner You can set the MaxEnvelopeSizeKb in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WSMAN\Client to a value like 1000000, which is approx. 1GB. Maybe that will work?
@FabienTschanz hej. My value is about 512MB at the moment, but I will try the maximum also. I hope there is some experience here with the filesizes in general. The only other option I see is to chunk the exports right away by e.g. export groups a-c/ d-f and so on.
Description of the issue
Hej,
I am doing recovery test for backups of aad users (1000+ users). My envelopesize is already 128mb, but I am running into this error:
MOF file size exceeded max size limit.
+ CategoryInfo : ResourceBusy: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : MI RESULT 27
+ PSComputerName : localhost
From some issues documented here it seems like it is proposed to break down the backups even more.
My question is, what are the actual limits for the mof files size?
Best
Microsoft 365 DSC Version
1.24.904.1
Which workloads are affected
Azure Active Directory (Entra ID)
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: