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.

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

Deployment Issue #6

Open
CptSternn opened this issue Aug 25, 2022 · 1 comment
Open

Deployment Issue #6

CptSternn opened this issue Aug 25, 2022 · 1 comment

Comments

@CptSternn
Copy link

CptSternn commented Aug 25, 2022

First of all I would like to say thanks for the update! It is brilliant.

I did however find an issue at least with my update. The script worked deleting the current Operational folder and contents however it could not create the new collections due to an issue with the schedule parameter. I was able to fix this though by just removing -RefreshSchedule $schedule from the code and it worked perfectly then. It also used the default refresh schedule which is the same as listed in the code so it had no effect. I don't know if this is an issue related to ConfigMgr in my environment or if there is something specific on my server but wanted to share this just in case someone else encounters the same problem where it cannot create the collections.

Thanks again for the great work on this!

Line 1464 I commented out and added in a new line without the Refresh Parameter:

#New-CMDeviceCollection -Name $Collection.Name -Comment $Collection.Comment -LimitingCollectionName $Collection.LimitingCollection -RefreshSchedule $Schedule -RefreshType 2 | Out-Null

New-CMDeviceCollection -Name $Collection.Name -Comment $Collection.Comment -LimitingCollectionName $Collection.LimitingCollection -RefreshType 2 | Out-Null

@FranzSchenk
Copy link

FranzSchenk commented Aug 25, 2022

Thank you CptSternn, have exactly the same issue. SCCM 2203 with HF Rollup. And removing the -RefreshSchedule Parameter does solve the problem also for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants