Closed hkystar35 closed 4 years ago
I've addressed that NO_SMS_ON_DRIVE.SMS file already exists issue for now. I will continue to ponder about the -IgnoreExistingSteps
idea (and allowing static IP config for DC + CM like we discussed in Discord)
Cheers for your help
Working through some other issues with the AutomatedLab build for ConfigMgr TP 2002 baseline, when re-running the script, it throws a terminating error if
NO_SMS_ON_DRIVE.SMS
already exists on the target VM for the ConfigMgr Primary Site Server. I'm guessing this is left as a check in case the environment is already up and running, but it would be great to have a way to ignore this for cases like re-running theCM-2002.ps1
build.Adding a switch to
cm-2002.ps1 -IgnoreExistingSteps
or something similar would be great to avoid this, especially while troubleshooting the actual ConfigMgr TP install issues so it takes less time to re-run.Full error: