Custom variables

[TommiHaarala]

I am currently using OSDCloud orginal version integrated with ConfigMgr task sequence and looking now to start using the newer module. I currently use $Global:MyOSDCloud variables to customize some of the settings before running Start-OSDCloud.

Has the new version same kind of feature, where you can easily replace some of the default variables with your own?

Thanks,
TH

[OSDeploy]

The new version has been presented at MMSMOA, WPNinjasUK, and WPNinja Summit. If you didn't attend these events, you'll need to wait for updated documentation.
Currently, the new version has not been tested with ConfigMgr, nor does it use variables, so my advice, keep using what you know for now.

[OSDeploy]

Which variables, what are you looking to control?

[TommiHaarala]

I currently use these $Global:MyOSDCloud variables when leveraging OSDCloud in task sequence.
Restart
RecoveryPartition
SkipAllDiskSteps
MSCatalogFirmware
WindowsUpdate
WindowsDefenderUpdate
ImageFileName
ImageFileUrl

I think I took some of those straight from Gary Blok's task sequence and some are additions that I needed later. For example targeting to specific esd file, because latest version had some known issue. All in all, just the possibility to replace any default variable value with my own when needed makes it much more flexible to use in task sequence.

And of course the different OS -parameters that you can feed to Start-OSDCloud command to choose the OS version to be installed.

[OSDeploy]

Thanks for the information. At this time, Deploy-OSDCloud does not contain the same functionality, and has not been tested in a running Task Sequence. Variables are not being used.
Are you having issues with PSModule OSD using OSDCloud from there?

[TommiHaarala]

No, the OSD PSModule works great and using that currently in production. Kudos for great tool.

I understood from the MMSMOA/WPNinja slides that at some point the OG version will not be developed anymore and that's why I have been starting to look also into this newer module if I can get it work in our deployment process. Still quite trial and error because not much updated documentation.