Skip to content

Deployment Issue #6

Description

@CptSternn

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions