-
Notifications
You must be signed in to change notification settings - Fork 527
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.
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
SPOUserProfileProperty: failed to restore #3226
Comments
When you say "restored" a full snapshot, you mean that your scenario is the following? 1 - Take a snapshot of SPOUserProfileProperty from Tenant A |
Take a "full" snapshot as in: Export-M365DSCConfiguration -CertificateThumbprint $Cert.Thumbprint -TenantId <redacted>.onmicrosoft.com -ApplicationId 01234567-890a-bcde-f012-34567890abcd -Path full -Mode Full -MaxProcesses 64 Then I updated the Finally I ran a restore towards the same tenant. |
Based on the scenario you describe above, you are taking a snapshot and then applying that extracted configuration to the same tenant you just exported from. Your expectations are that nothing will happen when running Start-DSCConfiguration since you the tenant has no drifts, correct? Just want to make sure I understand what you are trying to achieve here. |
Yes, that sounds like what I expect. As a side node I did change a few configurations in the tenant between "extract" and "apply" so it actually had drifts. |
Details of the scenario you tried and the problem that is occurring
I exported a clean developer tenant with default sample data (https://developer.microsoft.com/en-us/microsoft-365/dev-program).
Then, when I restored the full snapshot,
SPOUserProfileProperty
failed with the following log (with slightly altered values for privacy reasons):Verbose logs showing the problem
See above.
Suggested solution to the issue
N/A
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Using Windows Server Core container,
mcr.microsoft.com/windows/servercore:1809-amd64
.The operating system the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
The text was updated successfully, but these errors were encountered: